Explanation:
General Purpose SSD (gp3) volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s of throughput regardless of the volume size. Furthermore, gp3 volumes are typically up to 20% cheaper per GB than gp2 volumes. Therefore, changing from gp2 to gp3 is the most cost-effective way to achieve the sustained 3,000 IOPS required without increasing the volume size (which would incur unnecessary storage costs) or migrating to more expensive io2 volumes.
Ultimate access to all questions.
A company hosts a continuous integration and continuous delivery (CI/CD) environment on AWS. The CI/CD environment includes a Jenkins server that is hosted on an Amazon EC2 instance. A 500 GB General Purpose SSD (gp2) Amazon Elastic Block Store (Amazon EBS) volume is attached to the EC2 instance. Because of disk throughput limitations, the Jenkins server reports performance issues that are resulting in slower builds on the server. The EBS volume needs to sustain 3,000 IOPS while performing nightly build tasks. A SysOps administrator examines the server’s history in Amazon CloudWatch. The BurstBalance metric has had a value of 0 during nightly builds. The SysOps administrator needs to improve the performance and meet the sustained throughput requirements. Which solution will meet these requirements MOST cost-effectively?
A
Double the gp2 EBS volume size from 500 GB to 1,000 GB.
B
Change the volume type from gp2 to General Purpose SSD (gp3).
C
Change the volume type from gp2 to Throughput Optimized HDD (st1).
D
Change the volume type from gp2 to Provisioned IOPS SSD (io2).
No comments yet.