SOA-C02 · Question #589
A company migrated a non-production application that is I/O intensive to a general purpose Amazon EC2 instance. A General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volume is attached…
The correct answer is C. Modify the EBS volume properties to increase the IOPS. Option C is correct because a consistently high VolumeQueueLength means I/O requests are backing up waiting for the disk - the volume can't process them fast enough. On a gp3 volume, IOPS are independently configurable (up to 16,000), so increasing IOPS directly raises the…
Question
A company migrated a non-production application that is I/O intensive to a general purpose Amazon EC2 instance. A General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volume is attached to the EC2 instance. Users report that actions that require intensive reading and writing to the disk are taking longer than normal or are failing. A SysOps administrator reviews the performance metrics of the EBS volume. The VolumeQueueLength metric is consistently high during the same times in which the users report issues. The SysOps administrator needs to resolve this problem to restore full performance to the application. Which action will meet this requirement?
Options
- AAttach an Amazon ElastiCache cluster to the EBS volume.
- BModify the EBS volume properties by enabling the Auto-Enabled IO volume attribute.
- CModify the EBS volume properties to increase the IOPS.
- DModify the EC2 instance to enable enhanced networking. Reboot the EC2 instance.
How the community answered
(50 responses)- A4% (2)
- B16% (8)
- C72% (36)
- D8% (4)
Explanation
Option C is correct because a consistently high VolumeQueueLength means I/O requests are backing up waiting for the disk - the volume can't process them fast enough. On a gp3 volume, IOPS are independently configurable (up to 16,000), so increasing IOPS directly raises the volume's throughput capacity and clears the queue.
Why the distractors are wrong:
- A - ElastiCache is an in-memory caching layer for databases/applications; it cannot be "attached" to an EBS volume and doesn't address disk I/O capacity.
- B -
Auto-Enabled IOis a fault-recovery feature that re-enables a volume after it's disabled due to data inconsistency errors - it has no effect on performance or throughput. - D - Enhanced networking improves network packet throughput between the EC2 instance and AWS infrastructure (useful for high network traffic), but EBS I/O bottlenecks are governed by the volume's IOPS/throughput limits, not the instance's network configuration.
Memory tip: Think of VolumeQueueLength like a checkout line - if the line is always long, you need more cashiers (IOPS), not a faster parking lot (networking) or a sign saying "stay open after a crash" (Auto-Enabled IO).
Topics
Community Discussion
No community discussion yet for this question.