Oracle 1z0-883 Exam Practice Questions (P. 3)
- Full Access (100 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #11
You are using replication and the binary log files on your master server consume a lot of disk space.
Which two steps should you perform to safely remove some of the older binary log files?
Which two steps should you perform to safely remove some of the older binary log files?
- AEnsure that none of the attached slaves are using any of the binary logs you want to delete.
- BUse the command PURGE BINARY LOGS and specify a binary log file name or a date and time to remove unused files.
- CExecute the PURGE BINARY LOGE NOT USED command.
- DRemove all of the binary log files that have a modification date earlier than today.
- EEdit the .index file to remove the files you want to delete.
Correct Answer:
AB
A: To safely purge binary log files, follow this procedure:
1. On each slave server, use SHOW SLAVE STATUS to check which log file it is reading.
2. Obtain a listing of the binary log files on the master server with SHOW BINARY LOGS.
3. Determine the earliest log file among all the slaves. This is the target file. If all the slaves are up to date, this is the last log file on the list.
4. Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.)
5. Purge all log files up to but not including the target file.
B: Syntax:
PURGE { BINARY | MASTER } LOGS -
{ TO 'log_name' | BEFORE datetime_expr }
Reference: 13.4.1.1 PURGE BINARY LOGS Syntax
AB
A: To safely purge binary log files, follow this procedure:
1. On each slave server, use SHOW SLAVE STATUS to check which log file it is reading.
2. Obtain a listing of the binary log files on the master server with SHOW BINARY LOGS.
3. Determine the earliest log file among all the slaves. This is the target file. If all the slaves are up to date, this is the last log file on the list.
4. Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.)
5. Purge all log files up to but not including the target file.
B: Syntax:
PURGE { BINARY | MASTER } LOGS -
{ TO 'log_name' | BEFORE datetime_expr }
Reference: 13.4.1.1 PURGE BINARY LOGS Syntax
send
light_mode
delete
Question #12
Which two statements are true about InnoDB auto-increment locking?
- AThe auto-increment lock can be a table-level lock.
- BInnoDB never uses table-level locks.
- CSome settings for innodb_autoinc_lock_mode can help reduce locking.
- DInnoDB always protects auto-increment updates with a table-level lock.
- EInnoDB does not use locks to enforce auto-increment uniqueness.
Correct Answer:
AD
A (not B): InnoDB uses a special lock called the table-level AUTO-INC lock for inserts into tables with AUTO_INCREMENT columns.
D (Not E): This lock is normally held to the end of the statement (not to the end of the transaction), to ensure that auto-increment numbers are assigned in a predictable and repeatable order for a given sequence of INSERT statements.
Reference: 14.6.5.2 Configurable InnoDB Auto-Increment Locking http://dev.mysql.com/doc/refman/5.6/en/innodb-auto-increment-configurable.html
AD
A (not B): InnoDB uses a special lock called the table-level AUTO-INC lock for inserts into tables with AUTO_INCREMENT columns.
D (Not E): This lock is normally held to the end of the statement (not to the end of the transaction), to ensure that auto-increment numbers are assigned in a predictable and repeatable order for a given sequence of INSERT statements.
Reference: 14.6.5.2 Configurable InnoDB Auto-Increment Locking http://dev.mysql.com/doc/refman/5.6/en/innodb-auto-increment-configurable.html
send
light_mode
delete
Question #13
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 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?
- A102; top-level statements are logged, but LOAD DATA INFILE is logged as a separate event.
- B3; only the top-level statements are logged.
- C111; top-level statements and all lower-level statements are logged.
- D12; only top-level statements and stored procedure events are logged.
Correct Answer:
B
Reference:
http://dev.mysql.com/doc/mysql-security-excerpt/5.5/en/audit-log-plugin-logging-control.html
B
Reference:
http://dev.mysql.com/doc/mysql-security-excerpt/5.5/en/audit-log-plugin-logging-control.html
send
light_mode
delete
Question #14
You execute the following statement in a Microsoft Windows environment. There are no conflicts in the path name definitions.
C: \> mysqld install Mysql56 defaults file = C : \my opts.cnf
What is the expected outcome?
C: \> mysqld install Mysql56 defaults file = C : \my opts.cnf
What is the expected outcome?
- AMysqld acts as an MSI installer and installs the Mysql 5.6 version, with the c: \my-opts.cnf configuration file.
- BMysql is installed as the Windows service name Mysql56, and uses c: \my-opts.cnf as the configuration file
- CAn error message is issued because – install is not a valid option for mysqld.
- DA running Mysql 5.6 installation has its runtime configuration updated with the server variables set in c: \my-opts.cnf.
Correct Answer:
B
B
send
light_mode
delete
Question #15
Consider the events_% tables in performance Schema.
Which two methods will clear or reset the collected events in the tables?
Which two methods will clear or reset the collected events in the tables?
- AUsing DELETE statements, for example, DELETE FROM performance_schema.events_watis_current;
- BUsing the statement RESET PERFORMANCE CACHE;
- CUsing the statement FLUSH PERFORMANCE CACHE;
- DUsing TRUNCATE statements, for example, TRUNCATE TABLE performance_schema.events_waits_current;
- EDisabling and re-enabling all instruments
- FRestarting Mysql
Correct Answer:
DE
D: To avoid unpredictable results if you make timer changes, use TRUNCATE TABLE to reset Performance Schema statistics.
Example:
As with other aggregate tables within Performance Schema, you can reset the statistics within the digest table with:
TRUNCATE TABLE performance_schema.events_statements_summary_by_digest;
Reference: 22.2.3.1 Performance Schema Event Timing
http://dev.mysql.com/doc/refman/5.5/en/performance-schema-timing.html
DE
D: To avoid unpredictable results if you make timer changes, use TRUNCATE TABLE to reset Performance Schema statistics.
Example:
As with other aggregate tables within Performance Schema, you can reset the statistics within the digest table with:
TRUNCATE TABLE performance_schema.events_statements_summary_by_digest;
Reference: 22.2.3.1 Performance Schema Event Timing
http://dev.mysql.com/doc/refman/5.5/en/performance-schema-timing.html
send
light_mode
delete
All Pages