Is it true that binary backups always take less space than text backups?
Yes, because binary backups only contain data, and not statements required to insert data into the tables.
No, because text backups can have optimizations, which make them smaller, such as updating many rows at once.
No, because if InnoDB tables contain many empty pages, they could take more space than the INSERT statements.
Yes, because even if InnoDB tables contain many empty pages, text backups have empty INSERT statements for them.
Correct answer: C
Question 2
You have a consistent InnoDB backup created with mysqldump, the largest table is 50 GB in size.
You start to restore your backup with this command;
shell> mysql –u root –p < backup.sql
After 30 minutes, you notice that the rate of restore seems to have slowed down. No other processes or external factors are affecting server performance.
Which is the most likely explanation for this slowdown?
The MySQL server has stopped inserting data to check index consistency.
InnoDB is doing CRC32 checks over the tablespace data as it grows.
The MySQL server is taking a periodical snapshot of data so it can resume the restore if it is interrupted mid-way.
InnoDB has filled the redo log and now must flush the pages.
Secondary indexes no longer fit into the buffer pool.
Correct answer: A
Question 3
Which three are key advantages of standard MySQL replication? (Choose three.)
supports native automatic failover
enables automatic resync of databases when discrepancies are detected
provides arbitrary geographic redundancy with minimal overhead to master
synchronously guarantees identical slave copy
is easy to configure and has low performance overhead