Online Access Free 1z1-320 Practice Test

You are required to set up a backup user (mysqlbackup@localhost) on the MySQL Database. The user should have the backup and restore privileges and additional privileges required for using transportable tablespaces (TTS). To back up and restore InnoDB tables.
Which syntax accomplishes this?

• A.CREATE USER 'mysqlbackup'@'localhost' IDENTIFIED BY 'new-password';GRANT RELOAD ON *.* TO ''mysqlbackup'@'localhost';GRANT CREATE, INSERT, DROP, UPDATE ON mysql.backup_progress TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, SELECT, DROP, UPDATE ON mysql.backup_history TO 'mysqlbackup'@localhost';
• B.CREATE USER 'mysqlbackup'@localhost'IDENTIFIED BY 'new-password';
• C.CREATE USER 'mysqlbackup'@'localhost' IDENTIFIED BY 'new-password';GRANT RELOAD ON *.* TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, DROP, UPDATE ON mysql.backup_progress TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, SELECT, DROP, UPDATE ON mysql.backup_history TO 'mysqlbackup'@'localhost';GRANT REPLICATION CLIENT ON *.* TO 'mysqlbackup'@'localhost';
• D.CREATE USER 'mysqlbackup'@localhost' IDENTIFIED BY 'new-password';GRANT RELOAD ON
  *.* TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, DROP, UPDATE ON
  mysql.backup_progress TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, SELECT, DROP, UPDATE ON mysql.backup_history TO 'mysqlbackup'@'localhost';GRANT REPLICATION CLIENT ON *.* TO 'mysqlbackup'@'localhost';GRANT SUPER ON *.* TO 'mysqlbackup'@' localhost;GRANT PROCESS ON *.* 'mysqlbackup'@'localhost';
• E.CREATE USER 'mysqlbackup'@'localhost' IDENTIFIED BY 'new-password';GRANT RELOAD ON *.* to 'mysqlbackup'@localhost';GRANT CREATE, INSERT, DROP, UPDATE ON, mysql.backup_progress TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, SELECT, DROP, UPDATE ONmysql.backup_history TO 'mysqlbackup'@'localhost';GRANT REPLICATION CLIENT ON *.* to 'mysqlbackup'@'localhost';GRANT SUPER ON *.* TO
  'mysqlbackup'@'localhost';GRANT PROCESS ON *.* TO 'mysqlbackup'@'localhost';GRANT LOCK TABLES, SELECT, CREATE, ALTER ON *.* TO 'mysqlbackup'@'localhost';GRANT CREATE, INSERT, DROP, UPDATE ON mysql.backup_sbt_history TO 'mysqlbackup'@'localhost';

Which three installation options are available for installing the MySQL Enterprise Monitor/Agent on Linux?

• A.A GUI for installing MySQL Enterprise Monitor, Agent, and a MySQL Repository database
• B.A script (with an option file) for installing MySQL Enterprise Monitor, Agent, and a MySQL Repository database
• C.A CLI-based wizard MySQL Enterprise Monitor, Agent, and a MySQL Repository database
• D.A MySQL Enterprise Monitor to remotely deploy the MySQL Monitor Agent
• E.A browser-based wizard to remotely deploy the MySQL Monitor Agent

When there are long-running queries, mysqbackup hangs there to wait for the completion of the queries. You know that the system has only user data on InnoDB and there is no DDL execution during the backup period.
There is no update/alternation to tables with non-InnoDB storage engines.
Which two ways allow the MySQL Enterprise Backup to be executed without being blocked or without locking?

• A.Running mysqlbqckup from a remote machine enabled you to back up the database without locking.
• B.The locked phase at the end of a mysqlbackup run is short (maybe a few seconds), and does not disturb the normal processing of mysqld much. However, use the - - only-innodb option to back up only InnoDB tables, to avoid blocking.
• C.There is no extra option. MySQL Enterprise Backup does this automatically by kicking out the long-running queries.
• D.The locked phase at the end of a mysqlbackup run is short (maybe a few seconds) and does not disturb the normal processing of mysqld much. However, use - -single-user-mode to back up the long-running queries to allow mysqlbackup to run successfully without locking.
• E.The locked phase at the end of a mysqlbackup run is short (maybe a few seconds), and does not disturb the normal processing of mysqld much. However, use the - -no-locking option to backup up the non-InnoDB files. Note that MyISAM, .frm, and other files copied under the --no-locking setting cannot be guaranteed to be consistent, if they are updated during this final phase of the backup.

Which four options are valid reasons for using a PRIMARY KEY in a table?

• A.Exporting data faster with mysqldump
• B.Eliminating the need for accessing the database cache
• C.Maintaining a history of row insertions or updates
• D.Auto-generating values via AUTO_INCREMENT
• E.Increasing performance when using SELECT statements
• F.Automatic storage of data in a sorted order
• G.Preventing duplicate keys

Your customer has provided you with the following server specifications: 64-bit, Oracle Linux 6, 24 Numa CPU cores, 48 GB memory, and sequential write-optimized drives in the /var/lib/seq-write directory. The customer wants you to optimize their MySQL 5.7.10 installation for the server resources available.
Identify three correct configurations for this server setup.

• A.mysql_numa_interleave=ON, innodb_buffer_pool_instances=8, innodb_log_file_size=24G
• B.innodb_buffer_pool_instances=12, innodb_buffer_pool_size=24G, innodb_log_file_size=12G
• C.innodb_file_per_table=ON, innodb_numa_interleave=ON, lower_case_table_names=1
• D.plugin_load= "thread_pool.so", innodb_page_cleaners=12,
  innodb_log_group_home_dir=/var/lib/seq-write
• E.innodb_data_file_path=/var/lib/seq-write, innodb_buffer_pool_size=36G, innodb_page_cleaners=8
• F.innodb_log_file_size=12G, innodb_buffer_pool_instances=12, innodb_buffer_pool_size=48G