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 BDS-C00 Exam - Topic 10 Question 107 Discussion

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

You have been asked to use your department's existing continuous integration (CI) tool to test a three- tier web architecture defined in an AWS CloudFormation template. The tool already supports AWS APIs and can launch new AWS CloudFormation stacks after polling version control. The CI tool reports on the success of the AWS CloudFormation stack creation by using the DescribeStacks API to look for the CREATE_COMPLETE status.

The architecture tiers defined in the template consist of:

. One load balancer

. Five Amazon EC2 instances running the web application

. One multi-AZ Amazon RDS instance How would you implement this? Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, D

by Beckie at Oct 24, 2024, 02:03 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
Diane
5 months ago
Surprised that E is even an option, feels off!
upvoted 0 times
...
Tanesha
5 months ago
C seems redundant if we already have B.
upvoted 0 times
...
Reynalda
5 months ago
Wait, isn't A also a valid choice?
upvoted 0 times
...
Cecily
5 months ago
Totally agree with B, it covers all tiers!
upvoted 0 times
...
Joesph
6 months ago
I think B and D are the best options here.
upvoted 0 times
...
Gail
6 months ago
I think defining a UserDataHandle for sanity checks could be useful, but I’m not clear on how it fits with the overall architecture testing.
upvoted 0 times
...
Ashton
6 months ago
I feel like using the DescribeStacks API is important, but I’m confused about whether to implement it with a CustomResource or a WaitCondition.
upvoted 0 times
...
Lucy
6 months ago
I remember practicing with WaitConditions, but I can't recall if they were the best choice for checking the application's state after deployment.
upvoted 0 times
...
Malcolm
6 months ago
I think we might need to use a CustomResource to run integration tests through the load balancer, but I'm not entirely sure which option that would be.
upvoted 0 times
...
Leonida
6 months ago
I'm a little unsure about how to approach this. There are a lot of different options, and I'm not sure I fully understand the differences between them. I think I'll start by reviewing the CloudFormation documentation and then come back to the question. Hopefully, that will help me make a more informed decision.
upvoted 0 times
...
Sheridan
6 months ago
This looks straightforward enough. I'm pretty confident I can handle this. I'll go with options A and B - the WaitCondition for the post-install checks and the CustomResource for the integration tests. Should be a piece of cake!
upvoted 0 times
...
Nickolas
6 months ago
Okay, I think I've got a good strategy here. I'll use a WaitCondition and WaitConditionHandle to check the post-install state of the application, and then I'll define a CustomResource to run some integration tests through the load balancer. That should give me a comprehensive way to validate the entire architecture.
upvoted 0 times
...
Claudia
6 months ago
Hmm, I'm a bit confused by all the different options here. I'm not sure if I fully understand the differences between a WaitCondition, a CustomResource, and a UserDataHandle. I'll need to review the CloudFormation documentation to make sure I'm choosing the right approaches.
upvoted 0 times
...
Helene
7 months ago
This seems like a pretty straightforward question. I think I'll go with options C and D - using a WaitCondition and a CustomResource to leverage the DescribeStacks API to check the stack creation status. That should give me a reliable way to confirm the deployment is complete.
upvoted 0 times
...
Karan
12 months ago
E looks interesting, but I'm not sure about the UserDataHandle. Isn't that meant for simpler, quick checks? Running integration tests through the load balancer might be better suited for a CustomResource or WaitCondition.
upvoted 0 times
Quentin
10 months ago
Hyun: Definitely, it seems like a more robust option for running those tests.
upvoted 0 times
...
Annalee
10 months ago
User 3: Yeah, I think using a CustomResource would be a better choice for that kind of testing.
upvoted 0 times
...
Hyun
10 months ago
User 2: I agree, maybe using a CustomResource or WaitCondition would be more appropriate for running integration tests.
upvoted 0 times
...
Louann
12 months ago
User 1: I think E is interesting too, but you're right about the UserDataHandle.
upvoted 0 times
...
...
Linn
1 year ago
I like the idea of the CustomResource in D, as it allows for more flexibility in running the DescribeStacks API call. It's a bit more complex than C, but might be worth it if we need to do additional checks beyond just the stack creation status.
upvoted 0 times
Martin
11 months ago
User 2: Yeah, it might be more complex but could be worth it for additional checks.
upvoted 0 times
...
Jacklyn
12 months ago
User 1: I think using CustomResource in D is a good idea for flexibility.
upvoted 0 times
...
...
Delsie
1 year ago
C and D seem like the most straightforward options to implement the health check and ensure the stack creation is complete. The WaitCondition and WaitConditionHandle in C looks like the better choice to me.
upvoted 0 times
...
Gail
1 year ago
I'm not sure, I think option B could also work. Running architecture-level integration tests through the load balancer might provide more comprehensive testing of the entire architecture.
upvoted 0 times
...
Tegan
1 year ago
I agree with Salena. Option C seems like the most efficient way to ensure the CREATE_COMPLETE status is returned before proceeding with the testing.
upvoted 0 times
...
Salena
1 year ago
I think option C is the way to go. Using the WaitCondition and WaitConditionHandle with the DescribeStacks API seems like the most straightforward approach.
upvoted 0 times
...

Save Cancel