Online Access Free 1z1-883 Practice Test

Which statement is true about the log-output variable?

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

Consider the Mysql Enterprise Audit plugin.
A CSV file called data.csv has 100 rows of data.
The stored procedure prepare_db ( ) has 10 auditable statements.
You run the following statements in the mydb database: Mysql> CALL prepare_db ( );
Mysql> LOAD DATA INFILE '/tmp/data.cav' INTO TABLE mytable;
Mysql> SHOW TABLES;
How many events are added to the audit log as a result of the preceding statements?

• A.12; only top-level statements and stored procedure events are logged.
• B.102; top-level statements are logged, but LOAD DATA INFILE is logged as a separate event.
• C.111; top-level statements and all lower-level statements are logged.
• D.3; only the top-level statements are logged.

A Mysql instance is running on a dedicated server. Developers access the server from the same network subnet. Users access the database through an application that is running on a separate server in a DMZ.
Which two will optimize the security of this setup?

• A.Running the server with - skip-networking specified
• B.Disabling connections from named pipes or socket files (depending on the operating system of the server)
• C.Installing Mysql on the application server, and running the database and application on the same server
• D.Enabling and using SSL for connections to the Mysql database
• E.Starting the server with - bind- address=0.0.0.0 specified
• F.Limiting logins to originate from the application server or the server's subnet

Which two statements are true about InnoDB auto-increment locking?

• A.InnoDB always protects auto-increment updates with a table-level lock.
• B.InnoDB never uses table-level locks.
• C.InnoDB does not use locks to enforce auto-increment uniqueness.
• D.Some settings for innodb_autoinc_lock_mode can help reduce locking.
• E.The auto-increment lock can be a table-level lock.

A simple master-to-slave replication is currently being used. The following information is extracted from the SHOW SLAVE STATUS output:
Last_SQL_Error: Error 'Duplicate entry '8' for key 'PRIMARY' ' on query. Default database: 'mydb'.
Query: 'insert into mytable VALUES ('8' , 'George') '
Skip_Counter: 0
Retrieved _Gtid_Set: 38f32e23480a7-32a1-c323f78067fd37821: 1-8
Auto _Position: 1
You execute a "SHOW CREATE TABLE mytable" on the slave:
CREATE TABLE 'mytable' (
'ID' int(11) NOT NULL DEFAULT '0',
'name' char(10) DEFAULT NULL,
PRIMARY KEY ('ID')
)
The table mytable on the slave contains the following:

You have issued a STOP SLAVE command. One or more statements are required before you can issue a START SLAVE command to resolve the duplicate key error.
Which statement should be used?

• A.SET GTID_EXECUTED="38f32e23480a7-32a1-c323f78067fd37821 : 9";
• B.SET GLOBAL enforce_gtid_consistency=ON
• C.SET GTID_NEXT="CONSISTENCY";
  BEGIN; COMMIT;
  SET GTID_NEXT=" AUTOMATIC';
• D.SET GTID_NEXT="38f32e23480a7-32a1-c323f78067fd37821 : 9";
  BEGIN; COMMIT;
  SET GTID_NEXT="AUTOMATIC";
• E.SET GLOBAL SQL_SKIP_SLAVE_COUNTER=1