1z0-908 Oracle MySQL 8.0 Database Administrator Free Practice Exam Questions (2025 Updated)

[mysqld]

default_authentication_plugin=sha256_password

ALTER USER user -

IDENTIFIED WITH mysql_native_password

BY 'password';

[mysqld]

default_authentication_plugin=caching_sha2_password

ALTER USER user -

IDENTIFIED WITH caching_sha2_password

BY 'password';

ALTER USER user -

IDENTIFIED WITH sha256_password -

BY 'password';

[mysqld]

default_authentication_plugin=mysql_native_password

on slave: --replicate-wild-ignore=example.%

on slave: --replicate-ignore-db=example

on master: --replicate-ignore-db=example

on master: --binlog-ignore-db=example

on slave: --binlog-ignore-db=example

/usr/mysql

/usr/bin

/etc/my.cnf

/var/lib/mysql

/usr

The instance deployed on host3 must be rebuilt with a backup from the primary instance.

The cluster is running and there is at least one ONLINE instance.

The instance deployed on host3 must be synchronized from a donor deployed on host1 by using the command cluster.addInstance(‘host1:3377’).

It is possible to determine the most up-to-date instance by comparing different global transaction identifier (GTID) sets with GTID_SUBSET(set1,set2).

The active session instance is invalid and must be re-created by using the command shell.connect (‘host3:3377’).

recording incoming SQL statement to facilitate the creation of a whitelist of permitted commands

blocking of potential threats by configuring pre-approved whitelists

modifying SQL statement dynamically with substitutions

automatic locking of user accounts who break your firewall

provides stateless firewall access to TCP/3306

They take roughly twice as long as logical backups.

They allow direct copying of table rows with operating system copy commands.

They work best for transaction storage engines that can perform their own recovery when restored.

The backup window is almost zero from the perspective of the application.

They do not back up views, stored procedures, or configuration files.

There is a slight performance cost while the snapshot is active.

They do not use additional disk space.

You can provide the root password interactively.

You must manually initialize the data directory.

The MySQL RPM package installation supports deploying multiple MySQL versions on the same host.

MySQL uses the RPM relocatable installation target feature.

The functionality is split among several RPM package files.

You can find the root password in the error log after the first start.

It supports backing up only table structures.

It can perform hot or warm backups.

It creates logical backups.

It supports the creation of incremental backups.

It supports backup of a remote MySQL system.

It supports restoring to a remote MySQL system.

No committed transactions are lost.

The slave automatically identifies that the master is unreachable and performs any required actions so that applications can start using the slave as the new master.

As soon as the incident happens, application can read data from the slave and rely on it to return a full and current set of data.

Reads from the slave can return outdated data until the value of the rpi_semi_sync_master_timeout variable is reached.

Reads from the slave can return outdated data for some time, until it applies all transactions from its relay log.

A small amount of committed transactions may be lost in case they were committed just before the disk failure.

It reconfigures InnoDB Cluster if the cluster was stopped.

It performs InnoDB Cluster instances rolling restart.

It only starts all InnoDB Cluster instances.

It is not mandatory that all instances are running and reachable before running the command.

It stops and restarts all InnoDB Cluster instances and initializes the metadata.

It only stops and restarts all InnoDB Cluster instances.

It picks the minimum number of instances necessary to rebuild the quorum and reconfigures InnoDB Cluster.

MySQL TDE uses an appropriate keyring plugin to store the keys in a centralized location.

Both MyISAM and InnoDB tables can be encrypted by setting the keyring_engine = ALL variable in the MySQL configuration file.

Lost tablespace encryption keys can be regenerated only if the master database key is known or present in the Key Vault specification.

TDE can encrypt InnoDB and MyISAM tables only when the tables are stored in the SYSTEM tablespace.

UPDATE world.country SET Name='all';

UPDATE world.country SET Name='one' LIMIT 1;

UPDATE world.country SET Name='new' WHERE Name='old';

UPDATE world.country SET Name=CONCAT('New ',Name);

UPDATE world.country SET Name='first' ORDER BY Name LIMIT

mysqldump --single-transaction > full-backup-$(date +%Y%m%d).sql

mysqlpump --include-databases=% > full-backup-$(date +%Y%m$d).sql

mysqlpump --all-databases > full-backup-$(date +%Y%m%d).sql

mysqldump --all-databases > full_backup-$(date +%Y%m%d).sql

GRANT ALL PRIVILEGES ON ‘world’.‘city’ TO ‘tom’@’%’;

GRANT SELECT (‘code’) ON ‘world’.‘country’ TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.* TO ‘tom’@’%’;

GRANT ALL PRIVILEGES ON ‘world’.‘country’ TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.‘city’ TO ‘tom’@’%’; GRANT SELECT ON ‘world’.* TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.‘city’ TO ‘tom’@’%’; GRANT SELECT ON ‘world’.‘country’ TO ‘tom’@’%’;

You can scale writes by creating a replicated mesh.

It guarantees near real-time replication between a master and a slave.

You can scale reads by adding multiple slaves.

MySQL Enterprise Backup will automatically back up from an available slave.

It allows backup to be done on the slave without impacting the master.

ALTER USER baduser@hostname PASSWORD DISABLED;

ALTER USER baduser@hostname MAX_USER_CONNECTIONS 0;

ALTER USER baduser@hostname ACCOUNT LOCK;

ALTER USER baduser@hostname IDENTIFIED WITH mysql_no_login;

ALTER USER baduser@hostname DEFAULT ROLE NONE;

Execute SET GLOBAL log_error = ‘’.

Execute SET GLOBAL max_error_count = .

Execute SET GLOBAL expire_logs_days=0 to enforce a log rotation.

Rename the error log file on disk, and then execute FLUSH ERROR LOGS.

They are pushed from the master to the slave.

They contain events that describe database changes on the master.

They contain events that describe all queries run on the master.

They contain events that describe only administrative commands run on the master.

They are pulled from the master to the slave.

It can be recovered from a donor instance on host3 by cloning using the command cluster.rejoinInstance ('@host3:3377')

It can rejoin the cluster by using the command cluster.addInstance('@host3:3377')

It has been removed from the cluster by using the command STOP GROUP_REPLICATION;

It can rejoin the cluster by using the command dba.rebootClusterFromCompleteOutage()

It has been expelled from the cluster because of a transaction error.