Multi-Datacenter Replication (MirrorMaker 2) — Concept Check
Questions on Multi-Datacenter Replication (MirrorMaker 2). MirrorMaker 2 replicates Kafka topics across clusters and datacenters for disaster recovery, geo-replication, and data aggregation pipelines.
Questions in this quiz
7 questions on Multi-Datacenter Replication (MirrorMaker 2) — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A company wants to replicate Kafka topics from their us-east cluster to eu-west for disaster recovery. They notice that consumer group offsets are not mirrored. What could be the issue?
- AThe tasks.max is set to 4
- BThe replication factor is set to 3
- CThe configuration lacks 'us-east->eu-west.groups=.*'
- DThe bootstrap servers are not defined
2.During a failover test, a team finds that messages in the eu-west cluster are not up-to-date with the us-east cluster. Which configuration should they check first?
- AConfirm if 'connect-mirror-maker.sh' is running
- BCheck if 'us-east->eu-west.enabled=true' is set
- CVerify if 'replication.factor=3' is correct
- DEnsure 'tasks.max=4' is sufficient
3.A team sets up MM2 but notices a replication loop forming. What configuration prevents this?
- ASetting 'replication.factor=3'
- BUsing remote topic naming like 'source.topic'
- CDefining multiple clusters in 'clusters' property
- DConfiguring 'tasks.max=4'
4.An engineer configures MM2 but replication is not occurring. They suspect the issue is with topic selection. Which setting should they verify?
- A'clusters=us-east, eu-west'
- B'us-east->eu-west.topics=orders.*,payments.*'
- C'tasks.max=4'
- D'replication.factor=3'
5.Which of the following is a necessary step to start MirrorMaker 2?
- ASet 'replication.factor=3'
- BEnable 'us-east->eu-west.groups=.*'
- CRun 'connect-mirror-maker.sh mm2.properties'
- DDefine 'tasks.max=4'
6.A team configures MM2 for active-active replication but notices performance issues. What might they be overlooking?
- ANetwork latency between datacenters
- BIncorrect 'replication.factor'
- CUnspecified bootstrap servers
- DMisconfigured 'tasks.max'
7.A developer thinks that setting 'replication.factor=3' ensures data consistency across datacenters. What is the flaw in this reasoning?
- AIt guarantees immediate consistency
- BIt directly mirrors consumer offsets
- CReplication factor affects fault tolerance, not consistency
- DIt reduces network latency