PAS-C01 · Question #27
A company has deployed its SAP applications into multiple Availability Zones in the same AWS Region. To accommodate storage of media files, database table export and import, and files dropped by…
The correct answer is C. Apply a lifecycle policy on the files in Amazon EFS to move the files to EFS Standard-Infrequent. Amazon EFS lifecycle management policies automatically move files that have not been accessed for a configurable period (e.g., 7, 14, 30, 60, or 90 days) to the EFS Standard-Infrequent Access (Standard-IA) storage class, which costs significantly less per GB than EFS Standard…
Question
A company has deployed its SAP applications into multiple Availability Zones in the same AWS Region. To accommodate storage of media files, database table export and import, and files dropped by third-party tools, the company has mounted Amazon Elastic File System (Amazon EFS) file systems between the SAP instances. The company needs to retrieve the files quickly for installations, updates, and system refreshes. Over time, the EFS file systems have grown exponentially to multiple terabytes. An SAP solutions architect must optimize storage cost for the files that are stored in Amazon EFS. Which solution will meet this requirement with the LEAST administrative overhead?
Options
- AScan the files manually to identify unnecessary files. Delete the unnecessary files.
- BMove the files to Amazon S3 Glacier Deep Archive.
- CApply a lifecycle policy on the files in Amazon EFS to move the files to EFS Standard-Infrequent
- DMove the files to Amazon S3 Glacier. Apply an S3 Glacier vault lock policy to the files.
How the community answered
(34 responses)- A6% (2)
- B9% (3)
- C82% (28)
- D3% (1)
Explanation
Amazon EFS lifecycle management policies automatically move files that have not been accessed for a configurable period (e.g., 7, 14, 30, 60, or 90 days) to the EFS Standard-Infrequent Access (Standard-IA) storage class, which costs significantly less per GB than EFS Standard. Files remain accessible through the same mount point and path, so no application changes are needed. This is a fully managed, zero-touch optimization that requires only a one-time policy configuration. Option A (manual scanning and deletion) is labor-intensive and risky. Options B and D (S3 Glacier and Glacier Deep Archive) require data movement away from EFS, breaking application access patterns and requiring significant administrative effort.
Topics
Community Discussion
No community discussion yet for this question.