Q18 — AWS SAA-C03 Ch.15

Question 18 of 100 | ← Chapter 15

Q1118. A company wants to restrict access to the content of its web application. The company needs to protect the content by using authorization techniques that are available on AWS. The company also wants to implement a serverless architecture for authorization and authentication that has low login latency.The solution must integrate with the web application and serve web content globally. The application currently has a small user base, but the company expects the application's user base to increase.Which solution will meet these requirements?

Correct Answer: A. Configure Amazon Cognito for authentication. Implement Lambda@Edge for authorization. Configure Amazon CloudFront to serve the web application globally.

Explanation

The best solution to meet the requirements for restricting access to the content of a web application while implementing a serverless architecture is:A. Configure Amazon Cognito for authentication. Implement Lambda@Edge for authorization. Configure Amazon CloudFront to serve the web application globally.Explanation:Amazon Cognito provides user authentication and authorization, allowing easy management of user pools and integration with your web application.Lambda@Edge allows you to run Lambda functions at CloudFront edge locations, enabling you to implement custom authorization logic with low latency as requests are processed close to the user. Amazon CloudFront serves content globally, providing low-latency access to your web application while integrating seamlessly with both Cognito and Lambda@Edge.Why Other Options Are Not Suitable:B: Using AWS Directory Service for Microsoft Active Directory may be more complex and is typically better suited for enterprise environments with existing Active Directory setups. This solution also does not leverage serverless components effectively.C: While Amazon Cognito is suitable for authentication, using Amazon S3 Transfer Acceleration is not the best choice for serving a web application globally, as CloudFront is specifically designed for content delivery and caching.D: Similar to option B, using AWS Directory Service adds unnecessary complexity. Additionally, AWS Elastic Beanstalk is not a serverless solution, which contradicts the requirement for a serverless architecture.Thus, option A is the most effective and suitable solution for the company's needs.