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

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

Contribute your Thoughts:

Karan
2 days 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
...
Linn
8 days 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
...
Delsie
10 days 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
13 days 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
17 days 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
18 days 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
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