MirrorMaker 2 for Geo-Replication — Concept Check
Questions on MirrorMaker 2 for Geo-Replication. MirrorMaker 2 (MM2) is a Kafka Connect-based tool that replicates topics across clusters for disaster recovery, data locality, or multi-region active-active deployments.
Questions in this quiz
8 questions on MirrorMaker 2 for Geo-Replication — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A company uses MirrorMaker 2 to replicate topics from 'us-east' to 'eu-west'. They notice that 'us-east.orders' is not being replicated back to 'us-east'. Why is this happening?
- AReplication is only one-way by default
- BMirrorCheckpointConnector is misconfigured
- CDefaultReplicationPolicy prevents cycle replication
- DThe topic is not listed in replication properties
2.In an active-active deployment using MM2, what happens if the 'us-east' cluster goes down?
- AReplication stops completely
- B'eu-west' cannot accept new writes
- CData is lost permanently
- D'eu-west' continues to operate independently
3.A team configures MM2 for active-passive DR but notices high replication lag. What could be a cause?
- AReplication factor is too high
- BTopics are not prefixed correctly
- CHeartbeats are not enabled
- DMirrorSourceConnector is disabled
4.Why might a consumer fail to resume at the correct offset after a failover using MM2?
- AHeartbeats are not enabled
- BConsumer group is misconfigured
- CCheckpoints are not emitted
- DTopics are not replicated
5.A developer believes MM2 automatically resolves all naming collisions. What is a potential issue with this belief?
- AIt requires custom replication policy for full control
- BIt cannot replicate topics with wildcards
- CIt does not handle consumer group names
- DIt only prefixes topics with the source alias
6.What is the role of MirrorCheckpointConnector in MM2?
- ATranslates source consumer group offsets
- BPrevents replication cycles
- CWrites periodic heartbeats
- DReplicates topic data
7.If MM2 is configured for GDPR compliance, what feature is likely being utilized?
- AData locality
- BReplication factor adjustment
- CCycle prevention
- DActive-active replication
8.A team sets 'us-east->eu-west.emit.checkpoints.enabled = false'. What impact does this have?
- AConsumers can't resume at correct offsets
- BReplication stops entirely
- CTopics are not replicated
- DHeartbeats are disabled