Exam AWS Certified SAP on AWS - Specialty PAS-C01 topic 1 question 87 discussion

This is clearly C & D as Jeanz details. System performance cannot be impaired, which eliminates A. Savings plans / RIs will reduce cost, and powering down non-prod systems afterhours (assuming that they do not have developers working overnight etc)

Scheduled start and stop are one of cost optimizations according to #4 in https://aws.amazon.com/blogs/awsforsap/optimization-techniques-for-running-sap-workloads-on-aws-a-cost-savings-guide/ Although scale down is mentioned as #1 in the above blog, it says it should be based on actual usage. Because A does not clarify if the resizing is based on the usage, it is not the answer.

AD is correct

Goal is Cost Savings without changing Performance or Availability. So no reduction in EC2 instances that will be noticed and no scaling down of resources of the instances. Therefore A is incorrect as scaled down non-prod still impacts performance (eg performance testing) during business hours. B. will stop and start SAP application systems, but does not say what or when systems can be stopped and is not specific. If only SAP is stopped the EC2 instance is still running. This is incorrect. C is Correct as instance savings plans based on use will reduce cost and impacts neither performance nor availability. D is like B but specifies only stopping non-prod outside of business hours when it shouldn't impact developers or testers and includes SAP and the EC2 instance. E is like B and D but also does not specify what and when EC2 and SAP systems will be stopped.

the best combination to optimize costs without affecting performance would be: AD

A,D: Scaling down the EC2 instances for non-production environments can reduce costs without impacting production workloads. Automating the stopping and starting of SAP systems and EC2 instances during non-business hours can also save on costs without affecting availability during operational hours.

Not a good question..