SOA-C02 · Question #643
A company runs its workload on Nitro-based Amazon EC2 instances that are in an Auto Scaling group. The instances have General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volumes that…
The correct answer is C. Increase the EBS volume IOPS. D. Increase the EBS volume throughput. Amazon EBS gp3 volumes allow you to provision additional IOPS and throughput independent of capacity. In this scenario, the instances experience heavy disk I/O during bootstrap, which maxes out the current settings. Increasing the provisioned IOPS (Option C) and the provisioned…
Question
A company runs its workload on Nitro-based Amazon EC2 instances that are in an Auto Scaling group. The instances have General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volumes that are configured with baseline performance. During bootstrap time, the EC2 instances download large Docker images and run initialization steps that require high disk I/O. The Auto Scaling group is terminating instances before the instances are in service. The EBSWriteBytes metric is almost constantly at maximum. Which combination of actions should a SysOps administrator take to resolve this issue? (Choose two.)
Options
- AIncrease the EC2 instance size.
- BIncrease the EBS volume capacity.
- CIncrease the EBS volume IOPS.
- DIncrease the EBS volume throughput.
- EChange the instance type to an instance that is not Nitro-based.
How the community answered
(26 responses)- A4% (1)
- B8% (2)
- C85% (22)
- E4% (1)
Explanation
Amazon EBS gp3 volumes allow you to provision additional IOPS and throughput independent of capacity. In this scenario, the instances experience heavy disk I/O during bootstrap, which maxes out the current settings. Increasing the provisioned IOPS (Option C) and the provisioned throughput (Option D) for the gp3 volume will provide the additional performance needed during initialization. This approach directly addresses the disk I/O bottleneck without changing the instance type or volume capacity.
Topics
Community Discussion
No community discussion yet for this question.