Host slave1 has ip address 192.0.2.10.
Host slave2 has ip address 203.0.113.50
Examine these commands:

Why did this error occur?

• A.The host on the command line is not defined in the login path.
• B.The DNS is not configured correctly for slave1 host.
• C.The mysqldinstance has not been restarted after creating the login path.
• D.There is no password defined in the login path.
• E.The .mylogin.cnffile is not readable.

Comment: *

Name: *

Email: *

Verification: *

Which are three facts about backups with mysqldump? (Choose three.)

• A.will lock all storage engines for duration of backup
• B.are able to back up specific items within a database
• C.create automatically compressed backups
• D.are always faster to restore than binary backups
• E.allow a consistent backup to be taken
• F.can back up a remote database server

Comment: *

Name: *

Email: *

Verification: *

A MySQL Server has been running an existing application successfully for six months. The my.cnf is adjusted to contain this additional configuration:

The MySQL Server is restarted without error.
What effect will the new configuration have on existing account?

• A.They will have to change their password the next time they login to the server.
• B.They will have their passwords updated on start-up to sha256_password format.
• C.They all connect via the secure sha256_password algorithm without any configuration change.
• D.They are not affected by this configuration change.

Comment: *

Name: *

Email: *

Verification: *

You are remotely logged in to MySQL as the user "backup".
The account has temporarily been granted full privileges WITH GRANT to perform the actions required.
You want to change the password for the locally existing "backup" user.
Select the three commands which will perform the required action. (Choose three.)

• A.ALTER USER 'backup' IDENTIFIED BY 'password';
• B.SET PASSWORD = 'password';
• C.ALTER USER 'backup'@'localhost' IDENTIFIED BY 'password';
• D.ALTER USER USER() IDENTIFIED BY 'password';
• E.SET PASSWORD FOR 'backup'@'localhost' = 'password';
• F.SET PASSWORD FOR 'backup'@'localhost' = PASSWORD ('password')
• G.CREATE USER 'backup'@'localhost' IDENTIFIED BY 'password';

Comment: *

Name: *

Email: *

Verification: *

You have a MySQL replication setup and you intentionally stop the SQL thread on the slave.

What are two reasons that you may stop the SQL thread on the slave while keeping the I/O thread running?

• A.to allow a backup to be created under reduced load
• B.to allow for point-in-time recovery on the slave
• C.to prevent schema changes from propagating to the slave before they are validated
• D.to allow the remaining events to be processed on the slave while not receiving new events from the master
• E.to prevent any transaction experiencing a deadlock

Comment: *

Name: *

Email: *

Verification: *