A MySQL 5.7 is monitored via 3306 without a MySQL agent (agentless installation).
Which two options are not available in such a setup in the MEM GUI?

• A. Disk usage and disk characteristics including disk advisors warnings
• B. Network-related information and network characteristics
• C. MySQL Replication monitoring
• D. MySQL Query Analysis data.
• E. Security-related advisors warning (for example, password warnings and firewall warnings)

Identify an example of creating an Enterprise Encryption function.

• A. CREATE FUNCTION asymmetric_decrypt RETURNS STRING SONAME 'openssl_udf.so';
• B. SET@function = CREATE_ASYMMETRIC_PRIV_KEY (@algo, @key_len);
• C. INSERT INTO t1 (key-col) FUNCTION(CREATE_ASYMMETRIC_PRIV_KEY('RSA', 1024));
• D. VALIDATE FUNCTION create_asymmetric_priv_key WITH 'openssl_udf.so';

You use MySQL Enterprise Monitor for a group of MySQL servers. In recent weeks, the MySQL Enterprise Monitor has slowed down significantly.
Which two preventative actions should you take if your number of monitored MySQL instances has changed?

• A. Increase the disk space with at least 10% of the database size.
• B. Increase the amount of RAM available to the JVM installed with Tomcat. The JVM memory settings are defined by the JAVA_OPTS line of the setenv file, which sets the environment variables for Tomcat (--JvmMs/-Xms and -JvmMx/-Xmx).
• C. Increase the necessary operating system swap space (Linux): mkswap /dev/sdx; swapon/dev/sdx,
  /etc/fstab.
• D. Tune the InnoDB Buffer Pool of the MySQL Enterprise Monitor Repository database. This can have a significant impact on performance (innodb_buffer_pool_size).

The replication for a Master and Slave MySQL Servers is up and running. The disk space for Master Server is continuously growing.
The binlog size keeps growing. Identify two methods to fix the issue.

• A. Delete all binlog files manually on the file system to release storage spaces.
• B. Set the expire_logs_days system variable to expire binary log files automatically after a given number of days.
• C. To safely purge binary log files, perform the following steps:1. On each slave server, use SHOW SLAVE STATUS to check which log file it is reading.2. Obtain a listing of the binary log files on the master server with SHOW BINARY LOGS.3. Determine the earliest log file among all the slaves. This is the target file. If all the slaves are up-to-date, this is the last log file on the list.4. Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.)5. Purge all log files up to but not including the target file by using the PURGE BINARY LOGS statement.
• D. On the Master server, disable binlog by removing the - - log -bin option.
• E. Execute the PURGE BINARY LOGS statement without argument.

By using the asynchronous MySQL Replication architecture, data can be replicated to slaves. Identify three use cases of MySQL Replication.

• A. MySQL Enterprise Backup will back up from Slave automatically.
• B. It provides multi-master access where the application can write and read data across the database servers.
• C. You can create a slave server for reporting applications, which get only read access to the slave servers.
  It off-loads the master server. Additional servers allow different database server configuration.
• D. MySQL Replication Connector/J (ReplicationDriver) is provided to allow read capability on slave and write capability on master.
• E. It allows backup to be done on the slave without impacting the master.