Option B is correct because Elastic Fabric Adapter is not relevant for general CPU performance; enabling T2/T3 unlimited is for burstable instances, not r5; purchasing a Reserved Instance does not fix performance; moving to a larger instance is not allowed per the constraint. However, the stem says 'without changing the instance type' and the correct answer should be a valid action. Actually, for r5 instances, CPU spikes could be addressed by using AWS Compute Optimizer to recommend a different instance type, but the constraint says 'without changing the instance type'.
This is tricky. The best answer might be to use a placement group for better network performance, but that doesn't address CPU. Alternatively, the team could enable detailed monitoring to get more granular metrics, but that doesn't fix spikes.
Maybe the correct answer is to use AWS Systems Manager to automate scaling? But scaling an SAP HANA instance is complex. The stem is flawed. Let me adjust the stem to allow changing instance type.
I'll rewrite: 'without changing the instance family' or something. I'll keep it as is but ensure the correct answer is valid. Option A: Use AWS Compute Optimizer to get recommendations.
That would likely suggest a larger instance, which is not allowed. So A is wrong. B: Enable T2/T3 unlimited - not applicable.
C: Purchase a Reserved Instance - no performance benefit. D: Use a placement group - improves network, not CPU. So none are correct.
I need to fix. Let me change the correct answer to 'Use Amazon CloudWatch Synthetics to monitor and alarm before spikes' - that doesn't fix. I'll redo the question.
Instead, I'll make the correct answer: 'Enable detailed monitoring and increase the CPU credit balance' - no. I'll change the stem to say 'without changing the instance type' to 'without changing the instance family' and allow larger size. Then the correct answer is 'Change the instance type to a larger one within the r5 family, such as r5.8xlarge'.
But that's not an option. I'll rewrite the entire question to be valid. Let me think of a better scenario: SAP on AWS with HANA, the issue is high memory usage.
The team cannot increase instance size. They can use Amazon EBS optimization or something. This is getting messy.
I'll assume the correct answer is to use a larger instance type, and the stem allows it. I'll change option A to 'Upgrade to a larger instance type in the same family, such as r5.8xlarge.' and make it correct. Then B, C, D are plausible but wrong.
I'll modify accordingly.