Deal of The Day! 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 MLA-C01 Exam - Topic 1 Question 12 Discussion

Actual exam question for Amazon's MLA-C01 exam
Question #: 12
Topic #: 1
[All MLA-C01 Questions]

An ML engineer needs to implement a solution to host a trained ML model. The rate of requests to the model will be inconsistent throughout the day.

The ML engineer needs a scalable solution that minimizes costs when the model is not in use. The solution also must maintain the model's capacity to respond to requests during times of peak usage.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Rosenda at Nov 01, 2025, 07:53 PM

Limited Time Offer

25%

Off

Get Premium MLA-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ty
9 hours ago
Agreed! It saves costs when demand is low.
upvoted 0 times
...
Chantay
19 days ago
I think option D is the best. Auto scaling is key for fluctuating requests.
upvoted 0 times
...
Bambi
24 days ago
I agree, D is definitely the way to go for cost efficiency and responsiveness.
upvoted 0 times
...
Emmett
29 days ago
Wait, can SageMaker really auto scale like that? Sounds too good to be true!
upvoted 0 times
...
Aliza
1 month ago
B seems too rigid for fluctuating requests.
upvoted 0 times
...
Tegan
1 month ago
I think A could work too, but fixed concurrency might limit flexibility.
upvoted 0 times
...
Vallie
1 month ago
I'm a big fan of the serverless approach, but Option A with Lambda doesn't seem like the right fit here. The SageMaker auto-scaling in Option D is the way to go.
upvoted 0 times
...
Barney
2 months ago
Haha, using Lambda functions with fixed concurrency? That's like trying to put a square peg in a round hole. Option D is clearly the way to go.
upvoted 0 times
...
Novella
2 months ago
Option C with the Application Load Balancer could work, but it might be overkill for this use case. The SageMaker auto-scaling in Option D seems more straightforward.
upvoted 0 times
...
Sina
2 months ago
I'm not sure about Option B. Manually setting the number of tasks on ECS seems like it might not be flexible enough to handle the changing demand.
upvoted 0 times
...
Salena
2 months ago
I recall that using multiple copies of the model in option C could help with load balancing, but it might not be the most cost-efficient solution when the model is idle.
upvoted 0 times
...
Luann
2 months ago
I feel like option D with SageMaker and auto-scaling makes the most sense since it can adjust based on demand, but I’m not entirely clear on how the scaling policies work.
upvoted 0 times
...
William
3 months ago
I think deploying on Amazon ECS with Fargate could work, but it seems like having a static number of tasks might not be cost-effective during low usage times.
upvoted 0 times
...
Javier
3 months ago
Option D sounds like the best choice for scalability!
upvoted 0 times
...
King
3 months ago
Option D sounds like the best solution. Automatically scaling the SageMaker endpoint based on CloudWatch metrics seems like a great way to handle the inconsistent request rate.
upvoted 0 times
...
Madelyn
4 months ago
I remember we discussed using AWS Lambda for handling variable request rates, but I'm not sure if fixed concurrency is the best approach for this scenario.
upvoted 0 times
...
Martha
4 months ago
The SageMaker options (C and D) seem like the most straightforward way to address the requirements. I'm not as familiar with the Lambda and ECS solutions, so I'd want to do some more research on how they would work in this scenario.
upvoted 0 times
...
Gwen
4 months ago
I'm leaning towards option D as well. The ability to dynamically adjust the number of instances based on usage patterns seems like it would meet the requirements of scalability and cost-effectiveness.
upvoted 0 times
...
Sarah
4 months ago
Option C with the Application Load Balancer routing traffic between multiple copies of the model on a SageMaker endpoint also seems like a good choice. That way you can handle fluctuations in demand without over-provisioning resources.
upvoted 0 times
...
Tonette
5 months ago
I'm a bit confused by the different options. Can someone explain the differences between the AWS Lambda and Amazon ECS solutions? I'm not sure I fully understand how they would work for this use case.
upvoted 0 times
...
Craig
5 months ago
I think option D sounds like the best approach here. Deploying the model to a SageMaker endpoint and using auto-scaling policies based on CloudWatch metrics seems like a scalable and cost-effective solution.
upvoted 0 times
Alline
3 months ago
Yeah, it keeps costs low when usage is low. Smart choice!
upvoted 0 times
...
Dominque
3 months ago
I agree, option D is definitely the way to go. Auto-scaling is crucial.
upvoted 0 times
...
Paz
4 months ago
I like how it can handle peak loads efficiently too.
upvoted 0 times
...
...

Save Cancel