A financial company recently added more features to its mobile app. The new features required the company to create a new topic in an existing Amazon Managed Streaming for Apache Kafka (Amazon MSK)…

Question

Options

• AExpand the storage of the MSK broker. Configure the MSK cluster storage to expand
• BExpand the storage of the Apache ZooKeeper nodes.
• CUpdate the MSK broker instance to a larger instance type. Restart the MSK cluster.
• DSpecify the Target Volume-in-GiB parameter for the existing topic.

• A
  85% (51)
• B
  3% (2)
• C
  2% (1)
• D
  10% (6)

Explanation

The RootDiskUsed metric in Amazon MSK indicates that the storage space on the broker's disk is filling up. To resolve this, the company can expand the storage for the MSK brokers to prevent them from running out of disk space. Amazon MSK supports automatic storage scaling, which can be configured to avoid similar issues in the future. By enabling auto-scaling, MSK will automatically expand the storage when needed, ensuring that the brokers have enough space to handle new topics or additional data. ZooKeeper is used for managing the state of Kafka brokers, but the RootDiskUsed metric pertains to the Kafka brokers, not the ZooKeeper nodes. Expanding ZooKeeper storage will not resolve the issue. While increasing the instance size may improve performance, it does not address the issue of running out of disk space on the broker's root volume, which is causing the CloudWatch alarm. Kafka topics do not have a direct volume specification. Storage for Kafka is managed at the broker level, not at the individual topic level. Therefore, this option does not apply to the issue of

No community discussion yet for this question.