1Z0-908 無料問題集「Oracle MySQL 8.0 Database Administrator」

（A）MySQL Query Analysis data

（B）CPU utilization

（C）MySQL Replication monitoring

（D）operating system memory utilization

（E）security-related advisor warnings

（F）disk usage and disk characteristics including disk advisors warnings

（G）network-related information and network characteristics

（A）A new instance is installed, initialized, and provisioned with data from an instance already in the cluster and joined to the cluster.

（B）It is always slower than {recoveryMethod: 'incremental'}.

（C）A target instance must exist, then it will be provisioned with data from an instance already in the cluster and joined to the cluster.

（D）InnoDB redo logs must not rotate for the duration of the execution; otherwise, the recovery will fail.

（E）The account used to perform this recovery needs the BACKUP_ADMIN privilege.

（F）InnoDB tablespaces outside the datadir are able to be cloned.

（A）UPDATE world.country SET Name='all';

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

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

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

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

（A）Sort the "Exec" column and check for SQL queries with low Query Response Time index (QRTi) values.

（B）Look for queries with big prolonged spikes in row activity/access graph in the times series graph.

（C）Sort the "Exec" column and check for SQL queries with high Query Response Time index (QRTi) values.

（D）Look for queries with low total latency times in the Latency section in the times series graph.

（A）monitoring the availability of the MySQL instance

（B）deploying the MySQL agent on supported target operating system

（C）creating e-mail alerts and SNMP traps for MySQL warnings

（D）monitoring of NDB Cluster API nodes

（E）tracing import and export with mysqidump

（F）analyzing executed MySQL queries

（G）starting and stopping the MySQL instance

（A）Snapshot backups can be used only in virtual machines.

（B）There is no need for InnoDB tables to perform its own recovery when restoring from the snapshot backup.

（C）A separate physical copy must be made before releasing the snapshot backup.

（D）Snapshot-based backups greatly reduce time during which the database and applications are unavailable.

（E）The frozen file system can be cloned to another virtual machine immediately into active service.

（A）$HOME/.mylogin.cnf file

（B）$HOME/.mysql/auth/login file

（C）DATADIR/mysqld-auto.cnf file

（D）$HOME/.my.cnf file

（E）/etc/my.cnf file

（F）$MYSQL_HOME/my.cnf file

（G）$HOME/.mysqlrc file

（A）access control lists

（B）server configuration rollback

（C）server runtime configuration

（D）view definitions

（E）performance metrics

（F）InnoDB buffer pool LRU management data

（G）stored procedure definitions

（H）table definitions

（A）access control lists

（B）server configuration rollback

（C）server runtime configuration

（D）view definitions

（E）performance metrics

（F）InnoDB buffer pool LRU management data

（G）stored procedure definitions

（A）Remove the world read/execute privilege from the accounting directory.

（B）Remove group read/write privileges from the private_key.pem file.

（C）Change the parent directory owner and group to mysql.

（D）Remove world read privileges from the server-cert.pem certificate file.

（E）Change the group ownership of the mysql directory to the mysql user group.

（F）Remove world read privileges from the public_key.pem file.