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

（A）SSL group communication requires the use of an additional set of parameters group_replication_recovery_*.

（B）If only some InnoDB Cluster members are enabled for SSL group communication, and
--ssl-mode=PREFERRED, communication will fall back to unencrypted connection.

（C）An existing InnoDB Cluster must be dissolved and created from scratch to enable SSL for group communication.

（D）Configuring SSL group communication also configures SSL distributed recovery.

（E）SSL group communication must be enabled at cluster creation time by specifying createCluster ({memberSslMode: 'REQUIRED'}).

（F）SSL group communication can be enabled for an existing cluster, one instance at time, by setting group_replication_ssl_mode.

（A）All non-active binary logs are removed from the master.

（B）All details regarding deleted logs and master metadata are captured in the output file.

（C）All databases, excluding master metadata, are backed up to the output file.

（D）All binary logs are deleted from the master.

（E）All databases are backed up to the output file.

（F）All binary logs are backed up and then deleted.

（A）Replication will fail because the master does not have the required transaction with bbbbbbbb-bbbb- bbbb-bbbb-bbbbbbbbbbbb GTIDs in its binary logs.

（B）Replication will work.

（C）Replication will fail because the master has already purged transactions with cccccccc-cccc-cccc- cccc-cccccccccccc GTIDs.

（D）Replication will fail because the slave has purged more aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa transactions than the master.

（E）Replication will fail because of inconsistent numbers in cccccccc-cccc-cccc-cccc-cccccccccccc GTIDs.

（A）The instance deployed on host3 is expelled from the cluster and must be rejoined using cluster.addInstance ('host3:3377')

（B）The issuing command cluster.switchToMuitiPrimaryMode() will fail to enable multi-primary mode.

（C）The primary instance can be specified by using the command
cluster.setPrimaryInstance(<host>:<port>).

（D）Failure of the instance deployed on host1 provokes an outage.

（E）The instance deployed on host3 will automatically rejoin the cluster when connectivity is re-established.

（F）The instance deployed on host2 is elected as the new primary instance.

（A）It can be granted to user accounts.

（B）It is stored in the mysql.role table.

（C）It can be renamed using the RENAME ROLE statement.

（D）It can be dropped using the DROP ROLE statement.

（E）It can be protected with a password.

（F）It is created as a locked account.

（A）A deadlock occurs after innodb_lock_wait_timeout seconds.

（B）Connection 25 experiences a lock wait timeout.

（C）A deadlock occurs immediately.

（D）All statements execute without error.

（E）Connection 24 experiences a lock wait timeout.

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

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

（C）It can rejoin the cluster by using the command cluster.addInstance('<user>@host3:3377')

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

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

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

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

（C）The instance deployed on host3 must be synchronized from a donor deployed on host1 by using the command cluster.addInstance('host1:3377').

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

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