Oracle Updated 1z0-908 Exam Questions and Answers by maira

ALTER USER 'joe'@'%' ACCOUNT LOCK

ALTER USER 'joe'@'%' SET password='*invalid*'

REVOKE ALL PRIVILEGES ON *.* FROM 'joe'@'%'

ALTER USER 'joe'@'%' PASSWORD HISTORY 0

ALTER USER 'joe'@'%' IDENTIFIED BY '*invalid*' PASSWORD EXPIRE

REVOKE USAGE ON *.* FROM 'joe'@'%'

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

Configuring SSL group communication also configures SSL distributed recovery.

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

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

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

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

If OPTIMIZE TABLE; is invoked, it will create a table lock on t and force a transaction rollback.

If OPTIMIZE LOCAL TABLE t; is invoked from another session, it executes normally and returns the status.

mysqlcheck --analyze --all-databases will execute normally on all tables and return a report.

If ANALYZE TABLE; is invoked from the same session, it hangs until the transaction is committed or rolled back.

mysqlbinlog --rewrite-db=’mydb1->mydb2’ | mysql

mysqlbinlog --datebase=mydb1 --database=mydb2 | mysql

mysqlbinlog --rewrite-db=’mydb1’ --rewrite-db=’mydb2’ | mysql

mysqlbinlog --read-from-remote-server --raw | sed ‘s/mydb1/mydb2/g’ | mysql