Download Oracle.1z0-883.SelfTestEngine.2019-01-23.56q.tqb
| Vendor: | Oracle |
| Exam Code: | 1z0-883 |
| Exam Name: | MySQL 5.6 Database Administrator |
| Date: | Jan 23, 2019 |
| File Size: | 457 KB |
Demo Questions
Question 1
A database exists as a read-intensive server that is operating with query_cachek_type = DEMAND.
The database is refreshed periodically, but the resultset size of the queries does not fluctuate.
Note the following details about this environment:
- A web application uses a limited set of queries.
- The Query Cache hit rate is high.
- All resultsets fit into the Query Cache.
- All queries are configured to use the Query Cache successfully.
The response times for queries have recently started to increase. The cause for this has correctly been identified as the increase in the number of concurrent users
accessing the web service.
Based solely on the information provided, what is the most likely cause for this slowdown at the database level?
- The Query Cache is pruning queries due to an increased number of requests.
- Query_cache_min_res_unit has been exceeded, leading to an increased performance overhead due to additional memory block lookups.
- Mutex contention on the Query Cache is forcing the queries to take longer due to its single-threaded nature.
- The average resultset of a query is increasing due to an increase in the number of users requiring SQL statement execution.
Correct answer: C
Question 2
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?
- The command prints all parameters for the login-path. The password is printed in plain text.
- The command prints all parameters for the login-path. The password is shown only when you provide the –password option.
- The command prints all parameter for the login-path. The password is replaced with stars.
- The command prints the encrypted entry for the login-path. The is only possible to see if an entry exists.
Correct answer: C
Question 3
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?
- Ensure that none of the attached slaves are using any of the binary logs you want to delete.
- Use the command PURGE BINARY LOGS and specify a binary log file name or a date and time to remove unused files.
- Execute the PURGE BINARY LOGE NOT USED command.
- Remove all of the binary log files that have a modification date earlier than today.
- Edit the .index file to remove the files you want to delete.
Correct answer: AB
Explanation:
A: To safely purge binary log files, follow this procedure:On each slave server, use SHOW SLAVE STATUS to check which log file it is reading. Obtain a listing of the binary log files on the master server with SHOW BINARY LOGS. 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. Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.) 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 A: To safely purge binary log files, follow this procedure:
- On each slave server, use SHOW SLAVE STATUS to check which log file it is reading.
- Obtain a listing of the binary log files on the master server with SHOW BINARY LOGS.
- 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.
- Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.)
- 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
