Free Top Amazon/AWS DEA-C01 Actual Exam Questions - Question 10 Discussion

It’s not C because just upgrading instance size without increasing storage won’t fix root disk space issues. Also, restarting the cluster could cause downtime which isn’t needed here. Expanding storage is more direct.

D imo, specifying a target volume for a topic doesn’t affect the broker’s root disk usage directly. The issue is more about overall storage capacity on the brokers, so expanding storage like in A seems more relevant here.

A imo, since the alarm is about RootDiskUsed on the broker, expanding broker storage makes the most sense. ZooKeeper storage usually isn't a problem from adding topics, so B seems off.

The alarm on RootDiskUsed really points to running out of storage on the brokers, so expanding broker storage (A) fits best here. ZooKeeper nodes don’t usually fill up root disk just from adding topics, so B can be eliminated. Upgrading instance size (C) helps CPU/memory more than disk space specifically. D talks about setting a parameter for topic volume, but I don’t think there’s such a setting that directly controls disk usage per topic like that. So A makes the most sense to fix the disk usage alarm quickly.

A/D? Increasing storage on brokers makes sense since topic data goes there, but D could help if the issue is about topic size limits. ZooKeeper usually doesn’t impact root disk much, so B feels off.

A/B? The alarm’s on the root disk, so it’s probably about where Kafka stores the topic data, pointing towards A. ZooKeeper mostly handles metadata and shouldn’t be filling the disk by just adding topics, so B feels less likely. Also, D sounds off because you don’t usually fix disk space issues by changing topic parameters. C might help if the broker is underpowered, but here the issue is disk space, not CPU or memory. So focusing on increasing or auto-expanding broker storage seems the most direct fix.

B tbh, I ruled out C and D because changing instance type or topic parameters doesn’t directly fix disk usage issues. Between A and B, since the alarm is on the root disk, it’s more likely about the brokers’ storage rather than ZooKeeper. ZooKeeper usually handles metadata and isn’t storing the main data that grows with new topics. So expanding broker storage or enabling auto-expansion (A) should do the trick.

I’m leaning towards A. Adding a new topic means more data, so expanding broker storage or enabling auto-expansion makes sense to prevent disk full issues. B and C seem less related to disk space, and D doesn’t sound like a valid parameter. Anyone else think the same?