Replication (Primary-Replica) — Concept Check
Questions on Replication (Primary-Replica). Binary log replication streams changes from primary to replicas asynchronously or semi-synchronously; replicas serve read traffic and provide failover capability.
Questions in this quiz
7 questions on Replication (Primary-Replica) — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A MySQL primary server crashes before a replica acknowledges a transaction. What happens to the transaction?
- AThe transaction is lost if using asynchronous replication.
- BThe transaction is preserved if using GTID mode.
- CThe transaction is always preserved on the replica.
- DThe transaction is immediately applied on the replica.
2.A replica shows 'Seconds_Behind_Source: 0'. What does this indicate?
- AThe replica is not running.
- BThe replica is lagging behind the primary.
- CThe replica has stopped replication.
- DThe replica is fully caught up with the primary.
3.You enable semi-synchronous replication on a MySQL primary. What is a potential benefit?
- AReduced risk of data loss on primary failure.
- BIncreased read performance on replicas.
- CAutomatic failover to replicas.
- DFaster write operations on the primary.
4.A developer configures GTID-based replication but sees transaction offset errors. What might be wrong?
- AGTID mode is not properly enabled on the primary or replica.
- BThe network connection between primary and replica is down.
- CThe primary server is not running.
- DThe replica server is not running.
5.In Spring Boot, how does AbstractRoutingDataSource determine the data source for a transaction?
- ABy the size of the transaction.
- BBy checking if the transaction is read-only.
- CBy checking the transaction isolation level.
- DBy the number of queries in the transaction.
6.A replica is lagging significantly behind the primary. What is a likely consequence?
- AImmediate synchronization with the primary.
- BImproved write performance on the primary.
- CAutomatic failover to the replica.
- DIncreased risk of stale data on read operations.
7.Why might someone choose asynchronous replication over semi-synchronous?
- ATo ensure data is always preserved on replicas.
- BTo automatically handle failover scenarios.
- CTo avoid waiting for replica acknowledgment, reducing write latency.
- DTo guarantee no data loss on primary failure.