Oracle MySQL 5.7 Database Administrator 1z0-888 Exam Dumps: Updated Questions & Answers (October 2025)

Enable compression on the table, causing InnoDB to release unused pages on disk to the file system:

Execute OPTIMIZE TABLE so that the InnoDB engine frees unused pages on disk back to the file system:

Set the server to use its own tablespace, and then alter the table so that data is moved from the shared tablespace to its own:

Take a backup, stop the server, remove the data files, and restore the backup:

The ‘adam’ user must also have SINGLE TRANSACTION global grant to take a consistent backup.

The ‘adam’ user needs the PROCESS privilege to be able to take a consistent backup while other users are connected.

The ‘adam’ user must have the SUPER privilege in order to take data backups.

The ‘adam’ user must also have SELECT on the football database for backup to work.

Yes. Shut down the mysqld process, enable the transportable_tablespace option, and move the UNDO directory to the SSD.

Yes. Shut down, copy the UNDO tablespaces to the new location, and change the innodb_undo_directory value in your my.cnf.

No. The UNDO tablespaces must remain on the same file system as the system tablespaces.

No. The sequential write pattern of the UNDO tablespaces is not supported on modern SSD block devices.

Install the X509 plug-in on the server.

Set the X509 option in the [client] section of the MySQL server’s configuration file.

Restart the server with the --require-x509 option.

Distribute client digital certificates to the client computers being used to log in by the user accounts.

Provide users access to the server’s private key.

Check the rate of change in the status value Aborted_connects and compare to the rate of change in Connections.

Check the difference between the InnoDB status values “Log Sequence number” and “Last Checkpoint” positions then compare that to the total size of the redo log.

Check the rate of change in the status value Select_scan and compare to the rate of change in Com_select.

Check the difference between the InooDB status values “Trx id counter” and “Purge done for” and compare to the state substatus of the main “Main thread”

Check the rate of change in the statis value Qcache_hits and compare that to the rate of change of Qcache_not_cached.

whether a new password is rejected if it contains a word found in a dictionary file.

whether a new password is rejected if it contains the current user’s username.

the amount of delay after an incorrect password is entered

the length of time before a newly created password expires

Query the INFORMATION_SCHEMA.PARTITIONS table

Use the command: SHOW TABLE STATUS

Query the performance_schema.objects_summary_global_by_type table

Query the INFORMATION_SCHEMA.TABLES table for the partition_count

Use the command: SHOW CREATE TABLE

InnoDB never uses table-level locks.

InnoDB always protects auto-increment updates with a table-level lock

InnoDB does not use locks to enforce auto-increment uniqueness.

The auto-increment lock can be a table-level lock.

Some settings for innodb_autoinc_lock_mode can help reduce locking.

Start the MySQL Server in --safe-mode, which only loads the privilege system for changes as data is inaccessible.

Start the MySQL Server with reset-root-password in my.cnf, which will prompt you to enter a new root user password.

Start the MySQL Server with --init-file pointing to SQL that executes an ALTER USER statement to change the root user password.

Start the MySQL Server with --skip-grant-tables and execute SQL, which will update the root password.

Start the MySQL Server with –initialize-insecure to force a password reset procedure on the command line.

The mysql user needs to have sudo privileges.

The mysqld process owner should own all files and directories to which the server writes.

The root or administrator users should own all files and directories to which the server writes.

The mysqld process should be run as root or administrator.

The mysqld process should not be run as root or administrator.