Pass the Oracle MySQL Database Administration 1z0-888 Questions and answers with ExamsMirror

InnoDB handles most crash recoveries automatically.

InnoDB blocks some operations when innodb_force_recovery is set to greater than 0.

There will in general be lost committed transactions after a crash using the default settings.

It is required to enable binlog_gtid_simple_recovery to perform a crash recovery.

It is recommended to set innodb_force_recovery = 1 as part of normal operations.

It is always required to enable innodb_force_recovery to perform a crash recovery.

Add the user replication@192.168.0.25 with the correct password to the master.

Edit the DNS table on the master to include the domain name for the IP address of 192.168.0.25.

Edit the my.ini file on the slave so that the master-host variable is equal to the IP address of the master, and restart the slave.

Add the user replication@192.168.0.25 with the correct password to the slave.

The master has performed a large transaction, which will take 360 seconds to complete on the slave.

The network latency between the master and the slave is 360 milliseconds.

The slave will need an estimated 360 seconds to update the remaining contents from the relay log.

The slave was configured for delayed replication with a delay of six minutes.

–-old-passwords, to start MySQL to use the old password format while running without the grant tables.

–-reset-grant-tables, to start the server with only the mysql database accessible.

–-read-only, to set all data to read-only except for super users

–-skip-networking, to prohibit access from remote locations

Use one-way encryption for storage of passwords.

Store passwords external to the database.

Choose short passwords to save on storage space.

Use simple keyboard actions that give mixed letters.

Do not use dictionary-based words.

enabling and using SSL for connections to the MySQL database

running the server with –-skip-networking specified

disabling connections from named pipes or socket files (depending on the operating system of the server)

starting the server with –-bind-address=0.0.0.0 specified

limiting logins to originate from the application server or the server’s subnet

installing MySQL on the application server, and running the database and application on the same server

include-log-file

master-binlog

include-master-info

master-data

The host on the command line is not defined in the login path.

The mysqld instance has not been restarted after creating the login path.

There is no password defined in the login path.

The DNS is not configured correctly for slave1 host.

The .mylogin.cnf file is not readable.

Include the keyring data and/or configuration in the backup.

Restore the backup to a clean MySQL instance.

Copy the backup to a remote host.

Include the MySQL socket file in the backup.

Include the ibtmp1 file in the backup.

Include the relay logs in the backup.

Include the operating system disk encryption key in the backup.

The applications have the SUPER privilege, which allows them to update rows.

The root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewrite.

For tables with UNIQUE keys, statement-based replication must be used to maintain integrity.

The slave was created with mysqldump –u root –p --skip-lock-tables –all-databases > /data/data.sql

The slave user does not have INSERT, UPDATE, or DELETE permission and cannot execute the Write_rows function.