Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 9 discussion

Answer directly points towards file gateway with lifecycles, D is wrong because utility function is vague and there is no need for flexible storage.

B answwer is correct. low latency is only needed for newer files. Additionally, File GW provides low latency access by caching frequently accessed files locally so answer is B

B is correct

The same question and answer explanation exists in a Udemy course. Correct answer is B. Amazon S3 File Gateway provides a seamless way to connect to the cloud to store application data files and backup images as durable objects in Amazon S3 cloud storage. Amazon S3 File Gateway offers SMB or NFS-based access to data in Amazon S3 with local caching. It can be used for on-premises data-intensive Amazon EC2-based applications that need file protocol access to S3 object storage. Lifecycle policies can then transition the data to S3 Glacier Deep Archive after 7 days. D is wrong because is involves too much extra configuration which is unnecessary.

Option B, creating an Amazon S3 File Gateway and an S3 Lifecycle policy to transition data to S3 Glacier Deep Archive, would meet the requirements specified in the prompt. The S3 File Gateway allows you to store and retrieve objects in Amazon S3 using standard file system protocols, such as SMB and NFS. This would provide additional storage space for the company's data and allow for low-latency access to the most recently accessed files, as the data would still be stored on the SMB file server.

Explanation: Since the company needs to increase available storage space while maintaining low-latency access to recently accessed files and implement file lifecycle management to avoid future storage issues, the best solution is to use Amazon S3 with a File Gateway. Using an Amazon S3 File Gateway, the company can access its SMB file server through an S3 bucket. This provides low-latency access to recently accessed files by caching them on the gateway appliance. The solution also supports file lifecycle management by using S3 Lifecycle policies to transition files to lower cost storage classes after they haven't been accessed for a certain period of time. In this case, the company can create an S3 Lifecycle policy to transition files to S3 Glacier Deep Archive after 7 days of not being accessed. This would allow the company to store large amounts of data at a lower cost, while still having easy access to recently accessed files.

Keywords: - After 7 days the files are rarely accessed. -The total data size is increasing and is close to the company's total storage capacity. - Increase the company's available storage space without losing low-latency access to the most recently accessed files. -> (for rarely accessed files we can access it with high-latency) - Must also provide file lifecycle management to avoid future storage issues. A: Incorrect - Don't mention how to increase company's available storage space. B: Correct - extend storage space and fast access with S3 File Gateway (cache recent access file), reduce cost and storage by move to S3 Glacier Deep Archive after 7 days. C: Incorrect - Didn't handle file lifecycle management. D: Incorrect - Don't mention about increase the company's available storage space.

according to documentation the minimum storage timeframe for an object inside S3 before being able to transition using lifecycle policy is 30 days , so those 7 days policies kinda seem wrong to me Transition actions – These actions define when objects transition to another storage class. For example, you might choose to transition objects to the S3 Standard-IA storage class 30 days after creating them, or archive objects to the S3 Glacier Flexible Retrieval storage class one year after creating them. For more information, see Using Amazon S3 storage classes. I was thinking of option A using DataSync as a scheduled task? am i wrong here?

A. DataSync is focused on transferring data when we need synchronization (for example, from an on-premises DB that updates daily to a DB in AWS). In this case, we don’t need to transfer data or synchronize data, we only need to increase the storage. So, this option is not correct. B. S3 File Gateway allows communication between a File System/Server and S3, and it supports SMB protocol. We can use S3 FGW to move files from the FS to the S3 bucket. Then, the question says that files older than seven days are rarely accessed, so we can transition to S3 Glacier for those files to archive, in a costly-efficient way. So, this option is correct. C. You have two different storages for saving the files, making the interoperability unnecessarily more complex (and you need constant data synchronization, regarding to option A). D. This is a mess. The solution is not scalable and It depends on the number of users, which is not a static number. Additionally, Flexible Retrieval is unnecessary.

answwer is correct. low latency is only needed for newer files. Additionally, File GW provides low latency access by caching frequently accessed files locally so answer is B

B is correct

Ans B: Low latency is only required for recent files in last 7 days; the rest can effectively be archived.

I'm new to this site, B is obviously correct, so how can D be shown as the "Correct Answer"? Makes no sense..

B: Explanation: Amazon S3 File Gateway: This service provides a seamless and secure integration between on-premises environments and the Amazon S3 cloud storage, allowing users to store and retrieve objects in S3 using the standard file protocols. S3 Lifecycle policy: By creating a lifecycle policy, you can automatically transition data that is older than 7 days to a more cost-effective storage class like S3 Glacier Deep Archive, which is suitable for infrequently accessed data.

Best answer opt C

File gateway has a cache and when hybrid is needed always think a storage gateway solution

Option B: Use an Amazon S3 File Gateway to extend storage space and create an S3 Lifecycle policy to transition data to S3 Glacier Deep Archive after 7 days. This solution provides seamless storage expansion, low-latency access for recent files, and cost-effective lifecycle management for older data.