Q3 — AWS SAA-C03 Ch.16
Question 3 of 100 | ← Chapter 16
Q1203. An analytics application runs on multiple Amazon EC2 Linux instances that use Amazon Elastic File System (Amazon EFS) Standard storage.The files that the application uses vary in size and access frequency.The company accesses the files infrequently after 30 days. However, users sometimes request older files to generate reports.The company wants to reduce storage costs for files that are accessed infrequently.The company also wants throughput to adjust based on the size of the file system. The company wants to use the TransitionTolA Amazon EFS lifecycle policy to transition files to Infrequent Access (lA) storage after 30 days.Which solution will meet these requirements?
- A. Configure files to transition back to Standard storage when a user accesses the files again. Specify the provisioned throughput mode.
- B. Specify the provisioned throughput mode only.
- C. Configure files to transition back to Standard storage when a user accesses the files again. Specify the bursting throughput mode. ✓
- D. Specify the bursting throughput mode only.
Correct Answer: C. Configure files to transition back to Standard storage when a user accesses the files again. Specify the bursting throughput mode.
Explanation
To meet the requirements of reducing storage costs for infrequently accessed files while ensuring throughput adjusts based on the file system size and allowing files to transition back to Standard storage when accessed again, the most suitable solution is:C. Configure files to transition back to Standard storage when a user accesses the files again. Specify the bursting throughput mode.Analysis:Transitioning Files Back to Standard Storage: The requirement specifies that users sometimes request older files to generate reports, which means these files need to be accessible when needed. By configuring files to transition back to Standard storage when accessed again, the company ensures that these files are readily available with low latency when requested, while still benefiting from cost savings when the files are not being accessed. This is typically achieved through Amazon EFS lifecycle policies, where files can be automatically moved back to Standard storage upon access.Bursting Throughput Mode: The requirement also mentions that throughput should adjust based on the size of the file system. Bursting throughput mode is the default and recommended mode for most use cases in Amazon EFS. In this mode, throughput scales with the size of the file system in the Standard storage class. This means that as the file system grows, the available throughput also increases, providing the necessary performance without requiring manual intervention or pre-provisioning. Additionally, bursting throughput mode allows for short bursts of high throughput when needed, which can be beneficial for applications with varying workloads.Why the Other Options Are Not Suitable:A. Configure files to transition back to Standard storage when a user accesses the files again. Specify the provisioned throughput mode.Why Not: While configuring files to transition back to Standard storage upon access is correct, specifying the provisioned throughput mode may not be the best choice for this scenario. Provisioned throughput mode requires you to specify a fixed throughput level, which may not be cost-effective if the workload is variable. Bursting throughput mode is more flexible and can automatically adjust based on the file system size and workload.B. Specify the provisioned throughput mode only.Why Not: This option does not address the requirement of transitioning files back to Standard storage when accessed again. Additionally, as mentioned above, provisioned throughput mode may not be the most cost-effective or flexible choice for varying workloads.D. Specify the bursting throughput mode only.Why Not: While bursting throughput mode meets the requirement of adjusting throughput based on the file system size, it does not address the requirement of transitioning files back to Standard storage when accessed again. This is crucial for ensuring that older files are readily available when needed for report generation.