Exam Title: MySQL Cloud Service 2018 Implementation Essentials
Associated Certification Paths MySQL Cloud Service 2018 Certified Implementation Specialist
Duration: 120 minutes
Number of Questions: 79
Passing Score: 60%
View passing score policy
Validated Against: Exam has been validated against MySQL Enterprise Edition 5.7.
Format: Multiple Choice
Complete Recommended Training
Data Management Cloud Learning Subscription (Individuals & Companies | Partners)
Additional Preparation and Information
A combination of Oracle training and hands-on experience (attained via labs and/or field experience) provides the best preparation for passing the exam.
Our certification exams are revised regularly to align with training and product release updates. Information about exam revisions and new topics are found on this page under 'Validated Statement' and within the exam topics below. Certifications reflect validated skills for year and product release version date of achievement. If you are preparing for this exam, we recommend you check these topics periodically to ensure your exam prep covers any new topics that may be added based on regular exam revision.
Oracle MySQL Enterprise Product Suite
Describe the difference between MySQL Enterprise Edition and the Community/Standard Edition
Explain the products and features of MySQL Enterprise Products
Identity the Oracle products that are certified to work with MySQL Enterprise Edition
Installation and Architecture
Explain the MySQL infrastructure architecture
Install a MySQL Enterprise Server
Configure settings for a MySQL Enterprise Server
Access MySQL databases with MySQL Workbench
Manage MySQL Database users with MySQL Workbench
Database Design
Describe Datatypes in a MySQL database
Create databases and tables
Create basic SQL queries
Maintain Databases, Tables, and Columns
Configure Indexes and Constraints
Join Tables
Partition MySQL Tables
MySQL Security
Execute MySQL Authorization and Privilege Management
Manage MySQL Password Policies
Describe MySQL Enterprise Authentication
Describe MySQL Enterprise Encryption
Configure MySQL Enterprise Firewall
Configure MySQL Enterprise Audit
Leverage MySQL Enterprise Monitor
Explain MySQL Enterprise Monitor benefits and features
Describe the topology of the MySQL Enterprise Monitor (Service Manager, Agents)
Manage MySQL Query Analyzer
Manage the customizability of MySQL Enterprise Advisors
Leverage MySQL Backup
Import and export data with MySQL Workbench
Describe the MySQL Enterprise Backup process
Install a MySQL Enterprise Backup
Configure MySQL backups
Configure MySQL Encryption and Compression
MySQL Overview of High Availability and Replication
Describe MySQL High Availability solutions
Explain Replication
Set up MySQL Replication using global transaction identifiers (GTID's) and binlog
Set up MySQL Cluster
Explain Replication utilities
Deploy High Availability and Scalability features
MySQL Cloud Service
Describe Cloud Services options
Establish Cloud Service connection via Secure Shell (SSH)
Describe security rules within Oracle Compute Cloud Service
Configure security rules within Oracle Compute Cloud Service
Troubleshoot Cloud Service connections issues
Describe alerts and notification options using Cloud Service
Configure MySQL Cloud Service Backup
QUESTION 1
The replication for a Master and Slave MySQL Servers is up and running. The disk space for Master Server is continuously growing.
The binlog size keeps growing. Identify two methods to fix the issue.
A. Execute the PURGE BINARY LOGS statement without argument.
B. On the Master server, disable binlog by removing the –log-bin option
C. Delete all binlog files manually on the file system to release storage spaces.
D. Set the expire_logs_days sysem bariable to expire binary log files automatically after a given number of days.
E. To safely purge binary log files, perform the following steps:
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 by using the PURGE BINARY LOGS statement.
Answer: B,E
QUESTION 2
A MySQL 5.7 server is monitored via 3306 without a MySQL Agent (agentless Installation). Which two options are not available In such a setup MEM GUI?
A. network related Information and network characteristics
B. security related advisors warning (for examine, password warnings and firewall warnings)
C. MySQL Query Analysis data
D. disk usage and disk characteristics including risk advisors warnings
E. MySQL Replication monitoring
Answer: C,E
QUESTION 3
Which statement would create an index by using the first 10 characters of the name column
in the customer table (assuming that name is a nonbinary string type)?
A. CREATE SUB INDEX part_of_name ON (customer,name,10);
B. CREATE INDEX (10) ON (customer.name);
C. CREATE INDEX part_of_name ON customer (name (10));
D. CREATE PARTIAL INDEX part_of_name ON customer (name,10);
E. CREATE INDEX part_of_name ON cutomer.name LIMIT 10 CHAR;
Answer: A
QUESTION 4
You have the MySQL 5.7 database fuming. MySQL Enterprise Backup 3.12 Is installed and it Is used to bade up the MySQL 5.7 database. The backup has failed. Identify the reason.
A. MySQL Enterprise Backup 3.x does not support MySQL 5.7. MySQL Enterprise Backup 4.x or later is required to back up MySQL 5.7.
B. MySQL Workbench must be Installed with MySQL Enterprise Backup to enable the backup to run successfully.
C. MySQL 5.7 Is supported in MySQL Enterprise Backup 3.x with the MySQL 5.7 extension pack.
D. MySQL 5.7 is supported In MySQL Enterprise Backup 3.x providing that the MySQL 5.7 Is pre registered In the MySQL Enterprise Backup configuration file.
E. mysqlbackup with MySQL Enterprise Backup 3.x must be executed once with the -- upgrad on MySQL 5.7 database to allow the mysql.backup_proqress and mysql.backup_history tables to be patched.
Answer: A
QUESTION 5
You have a user on your MySQL instance who is flooding the server with complex queries and large INSERTS, which prevents another user with a higher priority from running queries. Which two choices will limit the number of SELECTS to 10 per hour and the number of INSERTS to 4 per hour for user ‘employee1’ from MvSQL Workbench by first selecting Server > Users and Privileges > employee1?
A. Set Max Updates to 4 for 'employee1'.
B. Set Max. Queries to 14 for 'employee1'.
C. Set Max. Connections to 14 for 'employee1'.
D. Set Max Queries to 10 for 'employee1'.
E. Set Concurrent Connections to 14 for 'employee1'.
Answer: C
