Online Access Free 1z1-883 Practice Test

You have a login-path named "adamlocal" that was created by using the mysql_config_editor command.
You need to check what is defined for this login_path to ensure that it is correct for you deployment.
You execute this command:
$ mysql_config_editor print -login-path=adamlocal
What is the expected output of this command?

• A.The command prints the encrypted entry for the login-path. The is only possible to see if an entry exists.
• B.The command prints all parameter for the login-path. The password is replaced with stars.
• C.The command prints all parameters for the login-path. The password is shown only when you provide the -password option.
• D.The command prints all parameters for the login-path. The password is printed in plain text.

You are creating a new server with the same accounts as an existing server. You do this by importing a mysqldump file of the mysql database.
You test whether the import was successful by using the following commands:
Mysql> select user, host, password from mysql.user;

9 rows in set (0.00 sec)
Mysql> show grants for 'admin'@'%';
ERROR 1141 (42000): There is no such grant defined for user 'admin' on host '%'
Which command will fix this issue?

• A.UPDATE mysql.user SET Create_user_priv = 'Y' WHERE user= 'admin';
• B.FLUSH PRIVILEGES;
• C.CREATE USER 'admin' @'%';
• D.GRANT USAGE ON *.* TO 'admin'@'%';
• E.FLUSH HOST CACHE;

Which statement is true about the log-output variable?

• A.It enables and starts the General Query Log.
• B.It specifies output destinations for the slow and General Query logs.
• C.It is a static variable and can be set only at MySQL server startup.
• D.It sets the target location for the binary logs generated by the MySQL sever.

You are using CTIDS in replication. You need to skip a transaction with the CTID of aaa-bbb-cccddd-eee : 3 on a slave.
Which command would you execute from a Mysql prompt?

• A.STOP SLAVE;
  BEGIN;
  SET GTID_IGNORE="aaa-bbb-ccc-ddd-eee: 3";
  COMMIT;
  START SLAVE;
• B.STOP SLAVE;
  SETGTID_NEXT="aaa-bbb-ccc-ddd-eee: 3";
  BEGIN;
  COMMIT;
  SET GTID_NEXT="AUTOMATIC";
  START SLAVE
• C.STOP SLAVE;
  SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;
  START SLAVE;
• D.STOP SLAVE;
  RESET SLAVE;
  BEGIN;
  SKIP NEXT GTID;
  COMMIT;
  START SLAVE;

What is true regarding InnoDB locking?

• A.InnoDB uses row-level or table-level locks depending on the number of rows affected.
• B.InnoDB only uses row locks, not page or table-level locks,
• C.InnoDB row locks may be escalated to page or table-level locks.
• D.InnoDB uses row and table-level locks, but row locks are not escalates,
• E.InnoDB locks only those rows that are updated.