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

Answer is D. Lustre in the question is only available as FSx https://aws.amazon.com/fsx/lustre/

Option D. Create an Amazon FSx for Lustre file system. Attach the file system to the origin server. Connect the application server to the file system. Amazon FSx for Lustre is a fully managed file system that is designed for high-performance workloads, such as gaming applications. It provides a high-performance, scalable, and fully managed file system that is optimized for Lustre clients, and it is fully integrated with Amazon EC2. It is the only option that meets the requirements of being fully managed and able to support Lustre clients.

This one had me stumped! Thanks, community, for the link.

Não é uma prática recomendada: O padrão em sistemas assíncronos com SQS e Lambda é remover a mensagem apenas após o processamento bem-sucedido. Isso garante que, caso algo falhe, a mensagem possa ser processada novamente. Não resolve duplicidade real: Mesmo que você exclua a mensagem imediatamente, o problema de mensagens duplicadas pode ocorrer devido à lógica de envio duplicado no S3 ou por notificações redundantes do evento de criação de objetos. Assim, o problema original pode persistir.

A opção D pode parecer uma solução direta, mas não é recomendada porque introduz riscos significativos para a confiabilidade do sistema. Vamos analisar mais a fundo: O que a opção D sugere: Modificar a função Lambda para excluir cada mensagem da fila do SQS imediatamente após a mensagem ser lida, antes do processamento. Problemas com a opção D: Perda de mensagens em caso de falhas: Se a mensagem for excluída do SQS antes de ser processada e algo der errado (como falha na função Lambda ou erro na lógica de processamento), a mensagem será perdida permanentemente. O SQS é projetado para garantir que a mensagem seja processada com segurança antes de ser removida. Excluir a mensagem antes do processamento viola essa garantia.

Amazon FSx Lustre is the most suitable for managing Lustre Clients.

D, self explanatory.

the question is missing some text i think.... as none of the answers really solve the equation. if the answer is D, how is the on prem infrastructure accessing Lustre in AWS? either way the only possible option it could be is D, so D it is.

Sorry but what is origin server in this context, does it mean AWS server or premise??

D: Lustre is key requirement AB: No support for Lustre C: Cannot just configure EFS to support Lustre file system

Option D. Create an Amazon FSx for Lustre file system. Attach the file system to the origin server. Connect the application server to the file system. Amazon FSx for Lustre is a fully managed file system that is designed for high-performance workloads, such as gaming applications. It provides a high-performance, scalable, and fully managed file system that is optimized for Lustre clients, and it is fully integrated with Amazon EC2. It is the only option that meets the requirements of being fully managed and able to support Lustre clients.

Lustre clients = Amazon FSx for Lustre file system

The correct solution is D) Create an Amazon FSx for Lustre file system. Attach the file system to the origin server. Connect the application server to the file system. The key requirements are: Shared storage solution Support Lustre clients Fully managed service Amazon FSx for Lustre provides a fully managed file system that is optimized for Lustre workloads. It allows Lustre clients to seamlessly connect to the file system.

Sorry, but I disagree with everyone. The question states "a gaming application that is hosted in an on-premises data center". Option D does not address this and cannot to my knowledge address it. Thus: A. Create an AWS Storage Gateway file gateway. Create a file share that uses the required client protocol. Connect the application server to the file share. By using AWS Storage Gateway in file gateway mode, you can extend your on-premises data center storage into the AWS cloud. The file share created on AWS Storage Gateway can use the necessary client protocol (such as Lustre), which would allow the Lustre clients in your on-premises data center to access the data stored on AWS Storage Gateway. This solution enables you to use Lustre clients to access data, while still keeping the gaming application hosted in your on-premises data center. AWS Storage Gateway provides a fully managed solution for this hybrid scenario, allowing seamless integration between on-premises and AWS cloud storage.

Content of "Amazon FSx for Lustre" at this link https://aws.amazon.com/fsx/lustre/ . Focus at image, section: "On-premises clients".

A. Lustre client access is not supported by AWS Storage Gateway file gateway. B. Creating a Windows file share on an EC2 Windows instance is suitable for Windows-based file sharing, but it does not provide the required Lustre client access. Lustre is a high-performance parallel file system primarily used in high-performance computing (HPC) environments. C. EFS does not natively support Lustre client access. Although EFS is a managed file storage service, it is designed for general-purpose file storage and is not optimized for Lustre workloads. D. Amazon FSx for Lustre is a fully managed file system optimized for high-performance computing workloads, including Lustre clients. It provides the ability to use Lustre clients to access data in a managed and scalable manner. By choosing this option, the company can benefit from the performance and manageability of Amazon FSx for Lustre while meeting the requirement of Lustre client access.

https://aws.amazon.com/fsx/lustre/?nc1=h_ls#:~:text=Amazon%20FSx%20for%20Lustre%20provides%20fully%20managed%20shared%20storage%20with%20the%20scalability%20and%20performance%20of%20the%20popular%20Lustre%20file%20system.