A production MSK cluster must continue serving producers and consumers during a single-AZ failure.
Align broker placement and topic replication with the availability requirement.
Which design is most important?
Place brokers across multiple Availability Zones and configure an appropriate replication factor and minimum ISR.
Detailed explanation
Without replicas, a broker failure is more likely to lose data and availability.
Without replicas, a broker failure is more likely to lose data and availability.
Replicas in another AZ can serve traffic after a broker failure and reduce the impact of an AZ outage.
Replicas in another AZ can serve traffic after a broker failure and reduce the impact of an AZ outage.
An AZ outage can affect the entire cluster and violates the availability requirement.
An AZ outage can affect the entire cluster and violates the availability requirement.
S3 object versioning does not improve MSK broker availability.
S3 object versioning does not improve MSK broker availability.
Check official documentation
Compare the following points with the official documentation.
Amazon MSKのマルチAZ配置、レプリケーション係数、可用性に関する公式説明を確認する。
What to confirm
AZ分散とKafkaレプリケーションの役割、可用性とコストのトレードオフを説明できる。
Key points
- Amazon MSK
- Multi-AZ
- Replication factor
- ISR
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Failure domain
Multi-AZ placement prevents one zone from being a common failure point.
Durability trade-off
Replication and acknowledgement settings affect durability, throughput, storage, and cost.