Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 9 Question 76 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 76
Topic #: 9
[All BDS-C00 Questions]

Your company operates a website for promoters to sell tickets for entertainment events. You are using a load balancer in front of an Auto Scaling group of web server. Promotion of popular events can cause surges of websites visitors. During scaling-out at theses times, newly launched instances are unable to complete configuration quickly enough, leading to user disappointment.

What option should you choose to improve scaling yet minimize costs? Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Clement
2 months ago
I bet AWS is just trying to trick us with all these options. They're probably going to pick the one that costs them the most money to implement!
upvoted 0 times
Alyce
25 days ago
E) Configure an Amazon S3 bucket for website hosting. Upload into the bucket an HTML holding page with its 'x-amz-website-redirect-location' metadata property set to the load balancer endpoint. Configure Elastic Load Balancing to redirect to the holding page when the load on web servers is above a certain level
upvoted 0 times
...
Judy
1 months ago
B) Use Auto Scaling pre-warming to launch instances before they are required. Configure pre-warming to use the CPU trend CloudWatch metric for the group
upvoted 0 times
...
Charlie
1 months ago
A) Create an AMI with the application pre-configured. Create a new Auto Scaling launch configuration using this new AMI, and configure the Auto Scaling group to launch with this AMI
upvoted 0 times
...
...
Jodi
2 months ago
Redirecting to a holding page? That's a creative solution, but I'm not sure it's the best way to handle scaling issues. Seems like a bit of a Band-Aid approach.
upvoted 0 times
...
Micheal
2 months ago
I like the idea of using past data to predict future scaling needs. Scheduled scaling seems like a smart way to stay ahead of the curve.
upvoted 0 times
That sounds like a good plan. Predictive scaling based on past data can definitely help in optimizing resources.
upvoted 0 times
...
Carman
2 days ago
D) Using the history of past scaling events for similar event sales to predict future scaling requirements. Use the Auto Scaling scheduled scaling feature to vary the size of the fleet
upvoted 0 times
...
Freeman
17 days ago
A) Create an AMI with the application pre-configured. Create a new Auto Scaling launch configuration using this new AMI, and configure the Auto Scaling group to launch with this AMI
upvoted 0 times
...
...
Bette
2 months ago
I personally think option E could also be beneficial. Redirecting to a holding page during high load could help manage user disappointment.
upvoted 0 times
...
Gene
2 months ago
I agree with Leonora. Creating a new AMI with pre-configured application and using past scaling events for prediction seem like practical solutions.
upvoted 0 times
...
Leonora
2 months ago
I think options A and D could be good choices to improve scaling and minimize costs.
upvoted 0 times
...
Darell
2 months ago
Ooh, using a custom metric to trigger scaling is an interesting idea. I wonder if that would give us more granular control over the scaling process.
upvoted 0 times
Lashandra
1 months ago
C) Publish a custom CloudWatch metric from your application on the number of tickets sold, and create an Auto Scaling policy based on this
upvoted 0 times
...
Toshia
2 months ago
A) Create an AMI with the application pre-configured. Create a new Auto Scaling launch configuration using this new AMI, and configure the Auto Scaling group to launch with this AMI
upvoted 0 times
...
...
Elena
2 months ago
B looks promising, but I'm not sure how well pre-warming would work with unpredictable traffic surges. Might be worth a try though.
upvoted 0 times
...
Tashia
2 months ago
I see your point, Edna. Option D could definitely help in planning ahead. I personally think a combination of options A and D would be the best approach
upvoted 0 times
...
Edna
2 months ago
I agree with Mel, option A seems like a good choice. But I also think option D could be useful for predicting future scaling requirements
upvoted 0 times
...
Therese
2 months ago
A and D seem like a good combination to me. Pre-configuring the AMI and using scheduled scaling based on past trends could really help with the scaling challenges.
upvoted 0 times
Ammie
29 days ago
Absolutely, being prepared for high traffic events is key to providing a seamless user experience.
upvoted 0 times
...
Kattie
1 months ago
It's important to have a proactive approach to scaling to ensure a smooth experience for website visitors during surges.
upvoted 0 times
...
Myra
1 months ago
I agree, using both options together can definitely improve scaling efficiency and minimize costs.
upvoted 0 times
...
Earlean
2 months ago
A and D are good options. Pre-configuring the AMI can speed up the launch process, and using scheduled scaling based on past trends can help predict future requirements.
upvoted 0 times
...
...
Mel
2 months ago
I think option A could help by reducing the time it takes for new instances to configure
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77