New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon SAA-C03 Exam - Topic 4 Question 28 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 28
Topic #: 4
[All SAA-C03 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

This option is the best solution because it allows the company to run its payment application on AWS with minimal operational overhead and infrastructure management. By using Amazon API Gateway, the company can create a secure and scalable API to receive payment notifications from mobile devices. By using AWS Lambda, the company can run a serverless function to validate the payment notifications and send them to the backend application. Lambda handles the provisioning, scaling, and security of the function, reducing the operational complexity and cost. By using Amazon ECS with AWS Fargate, the company can run the backend application on a fully managed container service that scales the compute resources automatically and does not require any EC2 instances to manage. Fargate allocates the right amount of CPU and memory for each container and adjusts them as needed.

A) Create an Amazon Simple Queue Service (Amazon SQS) queue Integrate the queue with an Amazon EventBndge rule to receive payment notifications from mobile devices Configure the rule to validate payment notifications and send the notifications to the backend application Deploy the backend application on Amazon Elastic Kubernetes Service (Amazon EKS) Anywhere Create a standalone cluster. This option is not optimal because it requires the company to manage the Kubernetes cluster that runs the backend application. Amazon EKS Anywhere is a deployment option that allows the company to create and operate Kubernetes clusters on-premises or in other environments outside AWS. The company would need to provision, configure, scale, patch, and monitor the cluster nodes, which can increase the operational overhead and complexity. Moreover, the company would need to ensure the connectivity and security between the AWS services and the EKS Anywhere cluster, which can also add challenges and risks.

B) Create an Amazon API Gateway API Integrate the API with anAWS Step Functions state ma-chine to receive payment notifications from mobile devices Invoke the state machine to validate payment notifications and send the notifications to the backend application Deploy the backend application on Amazon Elastic Kubernetes Sen/ice (Amazon EKS). Configure an EKS cluster with self-managed nodes. This option is not ideal because it requires the company to manage the EC2 instances that host the Kubernetes cluster that runs the backend application. Amazon EKS is a fully managed service that runs Kubernetes on AWS, but it still requires the company to manage the worker nodes that run the containers. The company would need to provision, configure, scale, patch, and monitor the EC2 instances, which can increase the operational overhead and infrastructure costs. Moreover, using AWS Step Functions to validate the payment notifications may be unnecessary and complex, as the validation logic can be implemented in a simpler way with Lambda or other services.

C) Create an Amazon Simple Queue Sen/ice (Amazon SQS) queue Integrate the queue with an Amazon EventBridge rule to receive payment notifications from mobile devices Configure the rule to validate payment notifications and send the notifications to the backend application Deploy the backend application on Amazon EC2 Spot Instances Configure a Spot Fleet with a default al-location strategy. This option is not cost-effective because it requires the company to manage the EC2 instances that run the backend application. The company would need to provision, configure, scale, patch, and monitor the EC2 instances, which can increase the operational overhead and infrastructure costs. Moreover, using Spot Instances can introduce the risk of interruptions, as Spot Instances are reclaimed by AWS when the demand for On-Demand Instances increases. The company would need to handle the interruptions gracefully and ensure the availability and reliability of the backend application.


1Amazon API Gateway - Amazon Web Services

2AWS Lambda - Amazon Web Services

3Amazon Elastic Container Service - Amazon Web Services

4AWS Fargate - Amazon Web Services

by Jovita at Jan 27, 2024, 05:31 AM

Limited Time Offer

25%

Off

Get Premium SAA-C03 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Hermila
3 months ago
Really? I thought EKS was the go-to for backend processing.
upvoted 0 times
...
Roslyn
3 months ago
SQS and EventBridge in option A look solid too.
upvoted 0 times
...
Tamera
4 months ago
Not sure about using Lambda for this. What if the load spikes?
upvoted 0 times
...
Bulah
4 months ago
I agree, Fargate is super easy to manage.
upvoted 0 times
...
Pedro
4 months ago
Option D seems like the best choice for low overhead!
upvoted 0 times
...
Aretha
4 months ago
I recall that using Fargate with ECS can reduce management overhead, but I’m not sure if it’s the best choice for a long-running backend process.
upvoted 0 times
...
Luke
4 months ago
I’m a bit confused about the differences between using SQS and API Gateway. I feel like both could work, but I’m leaning towards D for simplicity.
upvoted 0 times
...
Moon
4 months ago
I think option D sounds familiar because it uses API Gateway and Lambda, which we practiced in class. It seems like a low-overhead solution.
upvoted 0 times
...
Marcos
5 months ago
I remember we discussed using AWS Lambda for handling events like payment notifications, but I'm not sure if it's the best fit here.
upvoted 0 times
...
Truman
5 months ago
Option D seems like the simplest and most managed solution to me. Using API Gateway, Lambda, and Fargate could minimize the operational overhead, which is a key requirement. I'll focus on understanding how those services work together.
upvoted 0 times
...
Nguyet
5 months ago
Hmm, I'm a bit confused by all the AWS services mentioned. I'll need to review my notes on things like SQS, EventBridge, EKS, and Fargate to make sure I understand how they work and which one might be the best fit here.
upvoted 0 times
...
Sylvia
5 months ago
This looks like a tricky question, but I think I have a good strategy. I'll carefully read through each option and consider the key requirements like operational overhead, compute and memory adjustments, and managed infrastructure.
upvoted 0 times
...
Delmy
5 months ago
I'm feeling pretty confident about this one. The question is clearly testing our knowledge of AWS services and how to architect a scalable, managed solution. I'll carefully evaluate each option against the requirements and go with the one that seems to have the least operational overhead.
upvoted 0 times
...
Serina
5 months ago
Alright, let me walk through this step-by-step. The question is asking about medications that work in the alpha cells of the pancreas to prevent hyperglycemia. That means we're looking for drugs that would inhibit the release or action of glucagon from the alpha cells. Based on that, I believe Sulfonylureas and DPP4 Inhibitors are the correct answers here.
upvoted 0 times
...
Omega
5 months ago
Okay, I think I've got a handle on this. Limiting the plug-in to only the Case Type field should help reduce the number of errors by minimizing the data being processed. I'd go with option A.
upvoted 0 times
...
Cecilia
5 months ago
Okay, the question says I can't change any interface configuration, so that rules out some options. Let me review the OSPF basics again.
upvoted 0 times
...
Dorathy
2 years ago
I'm not sure, I'm kind of torn between options B and D. Both seem to be using managed services in different ways, but I'm worried that the self-managed nodes in option B might introduce more operational overhead than the Fargate option.
upvoted 0 times
Nickole
2 years ago
I agree, option D seems like the most efficient and least operational overhead for the company.
upvoted 0 times
...
Horace
2 years ago
That sounds like a good choice, Fargate should simplify management of the backend application.
upvoted 0 times
...
Sharee
2 years ago
I think I'll go with Option D for less operational overhead and scalability.
upvoted 0 times
...
Kris
2 years ago
True, Fargate in Option D seems like a simpler and more scalable solution.
upvoted 0 times
...
Margret
2 years ago
I agree, managing self-managed nodes in Option B might introduce more operational overhead.
upvoted 0 times
...
Freeman
2 years ago
But Option D also looks good with AWS Fargate for managing the backend application.
upvoted 0 times
...
Erick
2 years ago
Option B seems to be the best choice as it uses managed services like AWS Step Functions and AWS Lambda.
upvoted 0 times
...
...
Lashon
2 years ago
Hmm, this is a tricky one. I'm leaning towards option D because it uses a fully managed service like Fargate for the backend application, and it also leverages API Gateway and Lambda to handle the payment notification processing. That seems like it would minimize the operational overhead the most.
upvoted 0 times
...
Elenora
2 years ago
Yeah, I agree. The question is really testing our knowledge of AWS services and how they can be combined to create a solution that meets the given requirements. I think the options are trying to assess our understanding of different approaches, like using SQS, API Gateway, Lambda, and managed Kubernetes or Fargate.
upvoted 0 times
...
Bok
2 years ago
This question seems to be testing our understanding of AWS services and how they can be used to build a scalable and managed solution for a payment processing application. I think the key requirements here are to minimize operational overhead, handle compute and memory adjustments, and use managed services where possible.
upvoted 0 times
...

Save Cancel