Exam AWS Certified Solutions Architect - Professional topic 1 question 480 discussion

B A\C\D: Would not solve the problem as the bottleneck is on the DB. Amazon ELB is able to handle the vast majority of use cases for our customers without requiring "pre-warming" (configuring the load balancer to have the appropriate level of capacity based on expected traffic). In certain scenarios, such as when flash traffic is expected, or in the case where a load test cannot be configured to gradually increase traffic, we recommend that you contact us to have your load balancer "pre-warmed". We will then configure the load balancer to have the appropriate level of capacity based on the traffic that you expect. We will need to know the start and end dates of your tests or expected flash traffic, the expected request rate per second and the total size of the typical request/response that you will be testing.

I support "B" answer. A: is not appropriate as the pre-warming ELB requires to contact AWS, and that is recommended if the traffic is expecting to have sudden increase in 5 minutes duration. C: not practical. D: does not add much enhancement. Plus the question never talked about snapshots!

Amazon RDS + Read Replicas

keyword = read replicas B

I'm also going for B. with the LEAST amount of performance degradation.

D is based on metric, still could have performance degradation. "LEAST amount of performance degradation"

C B and D need too much manual works and there is still possibility of failure by unexpected events.

B; month-end reporting == READ REPLICAS

Which of the following actions would enable the database to manage the month-end load with the LEAST amount of performance degradation? For me this is key moving all the reads to a read replica will be highly efficient .

B is an overkill, solution needs to solve the issue for the last 3 days that's why C seems more relevant, you can test it in stage to know how much time it takes to switch EBS so then you can schedule it ahead of time. Plus read replica comes with a cost and the rest of the time it won't do anything.

Option C is right - Refer https://aws.amazon.com/blogs/storage/automating-amazon-ebs-volume-resizing-with-aws-step-functions-and-aws-systems-manager/

last three days of each month owing to month-end reporting is key here in this question, I will go with B. C doesn't make any sense to me

Both B & C technically will work and satisfies the requirement. But I will choose C. Because we already know high volumes are just last 3 days. So, I will execute the lambda on 26th 11pm to change it to IOPS and run the lambda again on 1st 6am of the month to revert to original. Just bare in mind, adding read replicas comes with heavy cost and no use to do this just for 3 days high usage.

CCC: --- "You can now increase volume size, adjust performance, or change the volume type while the volume is in use. You can continue to use your application while the change takes effect. Spiking Demand – You are running a relational database on a Provisioned IOPS volume that is set to handle a moderate amount of traffic during the month, with a 10x spike in traffic during the final three days of each month due to month-end processing. You can use Elastic Volumes to dial up the provisioning in order to handle the spike, and then dial it down afterward." --> https://aws.amazon.com/blogs/aws/amazon-ebs-update-new-elastic-volumes-change-everything/ ---- Option C refers to the attached EBS volumes (not EC2 instances) While option B might work as well, I don't see the need of creating several additional read replicas to be used just in the final three days of the month. AUrora MySQL with Auto-Scaling Read Replicas would have been nice

C This will handle the spike.

after reading all comments i choose C as from the link https://aws.amazon.com/blogs/aws/amazon-ebs-update-new-elastic-volumes-change-everything/

C correct - Amazon EBS Elastic Volumes - By using Amazon CloudWatch with AWS Lambda you can automate volume changes to meet the changing needs of your applications.