Q35 — AWS SAA-C03 Ch.15

Question 35 of 100 | ← Chapter 15

Q1135. A company runs multiple applications in multiple AWS accounts within the same organization in AWS Organizations. A content management system(CMS) runs on Amazon EC2 instances in a VPC. The CMS needs to access shared files from an Amazon Elastic File System (Amazon EFS) file system that is deployed in a separate AWS account.The EFS account is in a separate VPC.Which solution will meet this requirement?

• A. Mount the EFS file system on the EC2 instances by using the EFS Elastic IP address.
• B. Enable VPC sharing between the two accounts. Use the EFS mount helper to mount the file system on the EC2 instances. Redeploy the EFS file system in a shared subnet. ✓
• C. Configure AWS Systems Manager Run Command to mount the EFS file system on the EC2 instances.
• D. Install the amazon-efs-utils package on the EC2 instances. Add the mount target in the efs-config file.Mount the EFS file system by using the EFS access point.

Correct Answer: B. Enable VPC sharing between the two accounts. Use the EFS mount helper to mount the file system on the EC2 instances. Redeploy the EFS file system in a shared subnet.

Explanation

The solution that will meet the requirement for the CMS to access shared files from an Amazon EFS file system deployed in a separate AWS account and VPC is:B. Enable VPC sharing between the two accounts. Use the EFS mount helper to mount the file system on the EC2 instances. Redeploy the EFS file system in a shared subnet.Explanation:VPC Sharing: Enabling VPC sharing allows resources from different accounts to access the same VPC. This is crucial for allowing the EC2 instances in one account to access the EFS file system in another account.EFS Mount Helper: Using the EFS mount helper simplifies the mounting process and ensures that the EFS file system can be accessed securely and efficiently. Redeploying the EFS in a shared subnet ensures that the mount targets are accessible from the EC2 instances.Why Other Options Are Not Suitable:A: Mounting the EFS file system using an Elastic IP address is not valid, as EFS does not use Elastic IPs for mounting. EFS requires specific mount targets within the VPC.C: While AWS Systems Manager Run Command can execute commands on EC2 instances, it does not inherently solve the networking and access issues between the two accounts and VPCs. This option lacks the necessary setup for cross-account access.D: Installing the amazon-efs-utils package is part of the mounting process, but without enabling proper VPC sharing and ensuring that the EFS file system is in an accessible subnet, this option would not work correctly across accounts.Thus, option B provides the best solution for enabling the CMS to access the EFS file system across different accounts and VPCs.