Online Access Free 1z0-883 Practice Test

Consider the Mysql Enterprise Audit plugin.
The following event detail is found in the audit log:
<AUDIT_RECORD
TIMESTAMP="2013-04-09t01:54:17"
NAME="Connect"
CONNECTION_ID="3"
STATUS="1045"
USER="kate"
PROXY_USER=""
HOST="localhost"
IP=""
DB=""/>
Which two points can be concluded from the given event?

• A.A connection failed because the proxy user privileges did not match the login user.
• B.A connection as the user kate was successful.
• C.A connection was blocked by a firewall or a similar security mechanism.
• D.A connection failed due to authentication being unsuccessful.
• E.A connection was attempted via socket rather than TCP.

What is true regarding InnoDB locking?

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

A user executes the statement;
PURGE BINARY LOGS TO 'mysql-bin.010';
What is the result?

• A.It deletes all binary log files after 'mysql-bin.010'.
• B.It deletes all binary log files, except 'mysql-in.010'.
• C.It deletes all binary log files up to and including 'mysql-bin.010'.
• D.It deletes all binary log files before 'mysql-bin.010'.

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

Consider the MySQL Enterprise Audit plugin,
You add the following lines to the my.cnf configuration tile:
[mysqld]
Plugin-load=audit_log.so
Audit-log=FORCE_PLUS_PERMANENT
You attempt to start up the MySQL service and notice that it fails to start.
Which two statements would explain why the service did not start?

• A.The audit_log.so library is in a location that is different from that defined by the plugin_dir option.
• B.The audit log file does not exist in which to write audit events.
• C.The audit_log.so library is not an executable file.
• D.The audit_log.so library does not exist.
• E.FORCE_PLUS_PERMANENT is not valid for the audit-log option.
• F.The audit plugin must be loaded dynamically by using the INSTALL PLUGIN command.