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 59 Discussion

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

[Design High-Performing Architectures]

The customers of a finance company request appointments with financial advisors by sending text messages. A web application that runs on Amazon EC2 instances accepts the appointmentrequests. The text messages are published to an Amazon Simple Queue Service (Amazon SQS) queue through the web application. Another application that runs on EC2 instances then sends meeting invitations and meeting confirmation email messages to the customers. After successful scheduling, this application stores the meeting information in an Amazon DynamoDB database.

As the company expands, customers report that their meeting invitations are taking longer to arrive.

What should a solutions architect recommend to resolve this issue?

Show Suggested Answer Hide Answer
Suggested Answer: D

To resolve the issue of longer delivery times for meeting invitations, the solutions architect can recommend adding an Auto Scaling group for the application that sends meetinginvitations and configuring the Auto Scaling group to scale based on the depth of the SQS queue. This will allow the application to scale up as the number of appointment requests increases, improving the performance and delivery times of the meeting invitations.


by Arleen at May 05, 2025, 01:40 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
Pearlene
3 months ago
Not sure if scaling will fix the root cause of the delays.
upvoted 0 times
...
Lavina
3 months ago
Wait, why would D be better than just optimizing the current app?
upvoted 0 times
...
Larae
3 months ago
A DAX cluster won't solve the delay in sending invites.
upvoted 0 times
...
Mila
3 months ago
I think B could help with the initial request handling too.
upvoted 0 times
...
Edna
3 months ago
D is the best option for scaling the invitation app!
upvoted 0 times
...
Martha
4 months ago
I vaguely recall something about DAX improving DynamoDB performance, but I don't see how that relates to the invitation delays. It feels like a stretch for this scenario.
upvoted 0 times
...
Ronald
4 months ago
I practiced a similar question where we had to optimize a system with SQS. I think scaling the application that sends invitations could really help, so I'm leaning towards option D as well.
upvoted 0 times
...
Lorenza
4 months ago
I'm not entirely sure, but I think adding a CloudFront distribution might not directly address the delay in sending invitations. It could help with caching, but is it really the best solution here?
upvoted 0 times
...
Krystina
4 months ago
I remember we discussed how Auto Scaling can help with performance issues, especially when demand increases. Option D seems like a good choice.
upvoted 0 times
...
Elbert
4 months ago
I'm pretty confident that option D is the way to go here. Scaling the app that sends the meeting invitations based on the SQS queue depth should help resolve the delays that the customers are experiencing. The other options don't seem to directly address the root cause of the problem.
upvoted 0 times
...
Providencia
5 months ago
Okay, let's think this through step-by-step. The web app is handling the appointment requests and publishing them to an SQS queue. Then another app is processing the queue and sending the meeting invitations. So the issue is likely with that second app. Adding auto-scaling based on the queue depth sounds like a good approach to me.
upvoted 0 times
...
Casie
5 months ago
Hmm, I'm a bit confused here. The question mentions that the customers are reporting delays in receiving their meeting invitations, but it doesn't specify where the bottleneck is. I'd want to do some more investigation before jumping to a solution.
upvoted 0 times
...
Dell
5 months ago
This seems like a classic scalability issue. I'd probably start by looking at the application that sends the meeting invitations and see if we can scale that up automatically based on the SQS queue depth.
upvoted 0 times
...
Ligia
9 months ago
Haha, the company's customers are probably wondering if the financial advisors are still living in the stone age, waiting for their meeting invitations. Option D is definitely the way to go!
upvoted 0 times
Darrel
8 months ago
Definitely, it's important to keep up with the company's expansion.
upvoted 0 times
...
Curtis
8 months ago
The customers will be happy to receive their meeting invitations faster.
upvoted 0 times
...
Celestina
8 months ago
I agree, scaling based on the depth of the SQS queue will help improve performance.
upvoted 0 times
...
Graciela
8 months ago
Option D is a great choice to speed up the meeting invitations.
upvoted 0 times
...
...
Lizbeth
9 months ago
That's a good point. Maybe we should consider that option as well.
upvoted 0 times
...
Harrison
9 months ago
But wouldn't adding an Auto Scaling group based on the SQS queue depth help with the delay issue?
upvoted 0 times
...
Lizbeth
9 months ago
I disagree. I believe adding an Amazon API Gateway API would be more effective.
upvoted 0 times
...
Edmond
9 months ago
Hmm, CloudFront might help with caching, but I'm not convinced it's the right solution here. The bottleneck seems to be with the application sending the invitations, not the web app accepting the requests.
upvoted 0 times
Weldon
8 months ago
C) Add an Amazon CloudFront distribution. Set the origin as the web application that accepts the appointment requests.
upvoted 0 times
...
Hillary
9 months ago
B) Add an Amazon API Gateway API in front of the web application that accepts the appointment requests.
upvoted 0 times
...
Fallon
9 months ago
A) Add a DynamoDB Accelerator (DAX) cluster in front of the DynamoDB database.
upvoted 0 times
...
...
Harrison
9 months ago
I think we should add a DynamoDB Accelerator (DAX) cluster.
upvoted 0 times
...
Delmy
10 months ago
I'm not sure if adding an API Gateway will actually resolve the issue with the meeting invitations. Seems like a bit of an overkill for this use case.
upvoted 0 times
...
Leatha
10 months ago
Option D sounds like the most efficient solution. Scaling the application based on the SQS queue depth will ensure the meeting invitations are sent out in a timely manner as the business grows.
upvoted 0 times
Kindra
8 months ago
Yes, it's important to have a scalable solution in place to handle the increasing number of appointment requests efficiently.
upvoted 0 times
...
Latia
8 months ago
I agree, scaling based on the SQS queue depth seems like the best way to address the delay in sending meeting invitations.
upvoted 0 times
...
Daryl
9 months ago
Option D sounds like the most efficient solution. Scaling the application based on the SQS queue depth will ensure the meeting invitations are sent out in a timely manner as the business grows.
upvoted 0 times
...
...

Save Cancel