MySQL replication can be used to
create a development server to test and benchmark new code on real data without risk
improve performance
make backups less disruptive
improve availability
all of the above
The binary log file
is created by default
is useful for replication and backup recovery
is an SQL dump file renamed
Read and write operations are usually performed on
reads on slaves, writes on slaves
reads on slaves, writes on masters
reads on masters, writes on slaves
reads on masters, writes on masters
none of the above
The design of MySQL replication means that
all data is up-to-date all the time
servers need to be connected via a reliable network and if any server is unavailable, all others need to wait for it to be brought back online
updates are fast but can take time to propagate to all slaves
updates can be made to any server, and they will be sent up to the master and down to all the other slaves
