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 BDS-C00 Exam - 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

by Arthur at Jul 09, 2023, 11:43 PM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Valentine
3 months ago
Wait, E is just a redirect? That seems too simple!
upvoted 0 times
...
Page
3 months ago
D could be useful, but it feels a bit hit-or-miss.
upvoted 0 times
...
Misty
4 months ago
B sounds interesting, but does it really work?
upvoted 0 times
...
Marcos
4 months ago
Totally agree, pre-configured AMIs save time!
upvoted 0 times
...
Virgie
4 months ago
A is a solid choice for faster scaling!
upvoted 0 times
...
Cammy
4 months ago
I feel like option C could be useful too, but I’m not sure how effective a custom CloudWatch metric would be in this scenario.
upvoted 0 times
...
Detra
4 months ago
I’m a bit confused about option D. Using historical data for scaling sounds good, but I wonder if it’s reliable enough for unpredictable events.
upvoted 0 times
...
Mabelle
5 months ago
I remember practicing a question about pre-warming instances. Option B sounds familiar, and it could help ensure instances are ready when traffic spikes.
upvoted 0 times
...
Jenelle
5 months ago
I think option A makes sense because having an AMI with everything pre-configured could really speed up the launch process. But I'm not sure if that's the only solution we need.
upvoted 0 times
...
Gary
5 months ago
This seems pretty straightforward to me. The initiation phase is all about laying the groundwork and getting the project organized, so option B - identifying the project team members - is probably the best answer here. The other options don't seem to capture the essence of what happens in this phase.
upvoted 0 times
...
Jules
5 months ago
This seems like a straightforward data privacy question. I'll carefully read through the scenario and think about the roles of the two companies based on the information provided.
upvoted 0 times
...
Tamesha
5 months ago
I'm a bit confused on the difference between the configuration files mentioned in the options. I'll need to review my notes to make sure I understand which one to use.
upvoted 0 times
...
Sharee
5 months ago
Okay, I think I've got this. The server is sitting between the internal and external networks, acting as a controlled access point. That's the classic role of a bastion host, so I'm pretty confident that's the right answer here.
upvoted 0 times
...
Clement
10 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
9 months 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
9 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
10 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
10 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
10 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
Lavonna
8 months 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
...
Kimbery
8 months ago
That sounds like a good plan. Predictive scaling can definitely help in managing surges in website traffic.
upvoted 0 times
...
Herminia
8 months 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
...
Maile
8 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
...
Brandon
8 months 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
...
Natalya
8 months ago
That sounds like a good plan. Predictive scaling based on past data can definitely help in optimizing resources.
upvoted 0 times
...
Carman
8 months 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
9 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
...
...
Bette
10 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
10 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
10 months ago
I think options A and D could be good choices to improve scaling and minimize costs.
upvoted 0 times
...
Darell
10 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
10 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
10 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
10 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
10 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
11 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
11 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
9 months ago
Absolutely, being prepared for high traffic events is key to providing a seamless user experience.
upvoted 0 times
...
Kattie
10 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
10 months ago
I agree, using both options together can definitely improve scaling efficiency and minimize costs.
upvoted 0 times
...
Earlean
10 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
11 months ago
I think option A could help by reducing the time it takes for new instances to configure
upvoted 0 times
...

Save Cancel