Home › Forums › AWS › AWS Certified SysOps Administrator Associate › Problem in question on EC2 High IOPS
-
Problem in question on EC2 High IOPS
JR-TutorialsDojo updated 3 weeks, 6 days ago 2 Members · 4 Posts -
A tech startup plans to launch a data analytics application that uses a MongoDB database and an NGINX server. The SysOps Administrator is instructed to provision a service that provides more than 200,000 IOPS in 4kB random I/O reads for the database.
Which of the following options will meet this requirement?
<ul data-question_id=”12312″ data-type=”single”>
- Throughput Optimized HDD (st1) EBS Volumes
- Storage Optimized Instances
Cold HDD (sc1) Volumes
Provisioned IOPS SSD (io1) EBS Volumes
I guessed “D” and was told it was incorrect “because this is not an instance type” But the question didn’t specify that the correct answer should be an instance type, and the use of multiple io1 vols should meet the requirement just fine. (And there are *no* storage-optimized instances that will run at 200k IOPS off of EBS. Specifications for Amazon EC2 storage optimized instances – Amazon EC2. You’ll need an “accelerated compute” instance type for that.)
-
Hello PeterMescher,
Thank you for your feedback.
In the given scenario, a tech startup plans to launch a data analytics application that uses a MongoDB database and an NGINX server. We need to use an instance to run these services. Storage-optimized instances are designed for workloads that require high, sequential read and write access to very large data sets on local storage.
For storage-optimized instances that will run at 200k IOPS, an i3.4xlarge instance can provide you with 825,000 Random Read IOPS and 360,000 Write IOPS.
I hope this helps! Let us know if you need any further questions.
Regards,
JR @ Tutorials Dojo-
An i3.xlarge will only provide those massive iOPS to Instance Storage. Since the requirement didn’t mention the data would be ephemeral, that would be a pretty awful thing to assume, given the loss in case of the instance stopping.
A RAID0 or 10 array of io-class vols to an accelerated compute instance is the answer here.
(And in any case, the wrong answer isn’t wrong. Instance Store is unlikely to be suitable, and certainly of the EBS-based answers, the io1s are correct. “That’s not an instance type” certainly isn’t a sufficient explanation as to why it’s not correct, since the question didn’t ask for an instance type.)
- This reply was modified 4 weeks, 1 day ago by PeterMescher.
-
Hello PeterMescher,
Thank you for pointing that out.
The i3.4xlarge instance indeed provides impressive IOPS, but it’s important to note that these high IOPS are specific to the ephemeral instance storage. Relying solely on instance storage would be risky if the data isn’t meant to be temporary.
As per your request, we will make the necessary updates to ensure that the question clearly specifies whether the answer should involve an instance type or an EBS volume type, in order to avoid any confusion. Your insights are valuable, and we appreciate your attention to detail.
If you have any further suggestions or feedback, feel free to share them with us. We’re committed to improving our practice tests based on user input.
Based regards,
JR @ Tutorials Dojo
-
Log in to reply.