Q35 — AWS SAA-C03 Ch.12

Question 35 of 100 | ← Chapter 12

Q835. A company wants to run its payment application on AWS. The application receives payment notifications from mobile devices. Payment notifications require a basic validation before they are sent for further processing.The backend processing application is long running and requires compute and memory to be adjusted. The company does not want to manage the infrastructure.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: D. Create an Amazon API Gateway API. Integrate the API with AWS Lambda to receive payment notifications from mobile devices. Invoke a Lambda function to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Container Service (Amazon ECS). Configure Amazon ECS with an AWS Fargate launch type.

Explanation

To meet the requirements of running a payment application on AWS that receives payment notifications from mobile devices and requires basic validation, while minimizing operational overhead, the solution with the least operational overhead is:D. Create an Amazon API Gateway API. Integrate the API with AWS Lambda to receive payment notifications from mobile devices. Invoke a Lambda function to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Container Service (Amazon ECS). Configure Amazon ECS with an AWS Fargate launch type.Here's why:Option D suggests creating an Amazon API Gateway API to receive payment notifications from mobile devices. The API can be integrated with AWS Lambda, which allows for serverless execution of code. A Lambda function can handle the basic validation of payment notifications and send them to the backend application.The backend application can be deployed on Amazon ECS, which provides container orchestration and management. By configuring Amazon ECS with an AWS Fargate launch type, the company can avoid managing the underlying infrastructure. AWS Fargate abstracts away the infrastructure and allows for running containers without the need to provision or manage EC2 instances.This solution minimizes operational overhead because it leverages serverless computing (Lambda) for the validation logic and container orchestration (ECS with Fargate) for the backend application. The company does not need to manage and scale the infrastructure manually.Options A, B, and C are not the optimal solutions to meet the requirements with the least operational overhead.Option A suggests using Amazon SQS and Amazon EventBridge to receive payment notifications and integrating with an Amazon EKS cluster. While this provides scalability and event-driven architecture, it introduces the complexity of managing an EKS cluster, which adds operational overhead.Option B suggests using an API Gateway API integrated with AWS Step Functions and deploying the backend application on Amazon EKS with self-managed nodes. This also introduces the complexity of managing an EKS cluster and requires additional operational effort.Option C suggests using Amazon SQS and Amazon EventBridge, but deploying the backend application on Amazon EC2 Spot Instances with a Spot Fleet. While Spot Instances can provide cost savings, they require management and monitoring to handle potential interruptions.Therefore, the recommended solution is to create an API Gateway API integrated with AWS Lambda to handle payment notifications and deploy the backend application on Amazon ECS with an AWS Fargate launch type, minimizing operational overhead.