PAS-C01 · Question #11
A company has an SAP environment that runs on AWS. The company wants to enhance security by restricting Amazon EC2 Instance Metadata Service (IMDS) to IMDSv2 only. The company's current…
The correct answer is B. Ensure that the EC2 instances are Nitro based. Before enforcing IMDSv2-only on SAP environments, the company must verify that all EC2 instances are Nitro-based. Nitro-based instances have full, reliable support for IMDSv2 session-oriented requests. Older, non-Nitro (Xen-based) instances may have compatibility issues when…
Question
A company has an SAP environment that runs on AWS. The company wants to enhance security by restricting Amazon EC2 Instance Metadata Service (IMDS) to IMDSv2 only. The company's current configuration option supports both IMDSv1 and IMDSv2. The security enhancement must not create an SAP outage. What should the company do before it applies the security enhancement on EC2 instances that are running the SAP environment?
Options
- AEnsure that the SAP kernel versions are 7.45 or later.
- BEnsure that the EC2 instances are Nitro based.
- CEnsure that the AWS Data Provider for SAP is installed on each EC2 instance.
- DStop the EC2 instances.
How the community answered
(18 responses)- A6% (1)
- B72% (13)
- C17% (3)
- D6% (1)
Explanation
Before enforcing IMDSv2-only on SAP environments, the company must verify that all EC2 instances are Nitro-based. Nitro-based instances have full, reliable support for IMDSv2 session-oriented requests. Older, non-Nitro (Xen-based) instances may have compatibility issues when IMDSv2 is enforced, potentially causing disruptions to instance metadata access that SAP workloads depend on. SAP kernel version (A) and the AWS Data Provider for SAP (C) are not prerequisites for IMDSv2 enforcement. Stopping instances (D) would directly cause the SAP outage the company is trying to avoid.
Topics
Community Discussion
No community discussion yet for this question.