exam questions

Exam AWS-SysOps All Questions

View all questions & answers for the AWS-SysOps exam

Exam AWS-SysOps topic 1 question 332 discussion

Exam question from Amazon's AWS-SysOps
Question #: 332
Topic #: 1
[All AWS-SysOps Questions]

A colleague is attempting to launch several new CloudFormation stacks, and receives the following error response:

What should be done to address the error?

  • A. Add a Pause to the CloudFormation templates.
  • B. Add an exponential backoff between CreateStack API calls.
  • C. Run the CloudFormation API calls from a larger Amazon EC2 instance.
  • D. Combine stack templates into one, and retry the CreateStack API call.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
Reference:
https://forums.aws.amazon.com/thread.jspa?threadID=100414

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
karmaah
Highly Voted 6 months, 2 weeks ago
Comparing all, B is the right one. There is a possibility to have nw congestion while creating stacks which may revoke the failed resources. To avoid that, exponential backoff algorithm can be used. It used progressively longer waits between retries for consecutive error responses. You should implement a maximum delay interval, as well as a maximum number of retries. Even those are not necessarily fixed values, and should be set based on the operation being performed, as well as other local factors, such as network latency.
upvoted 6 times
...
TroyMcLure
Most Recent 5 months, 4 weeks ago
Correct Answer: B
upvoted 1 times
...
gretch
6 months ago
B "If more than a couple deploy at the same time, you will see Rate Exceeded errors, which is possibly due to the checking of the stack status. If they now all retry after 5 seconds, all will get the same error again and they will ultimately fail. That's why adding an exponential backoff with a jitter helps to prevent this from happening. I mean in general I think that adding a jitter and exponential backoff when retrying an api request is a good idea to prevent congestion." https://github.com/serverless/serverless/issues/6980
upvoted 1 times
...
awscertified
6 months, 1 week ago
B. Add an exponential backoff between CreateStack API calls.
upvoted 2 times
...
aksliveswithaws
6 months, 3 weeks ago
Looks like exponential backoff is the right answer. Included the following reference aws docs reference : https://docs.aws.amazon.com/general/latest/gr/api-retries.html However the above reference is not specific to CloudFormation case Appreciate any one giving us a valid CloudFormation case reference helps
upvoted 2 times
karmaah
6 months, 1 week ago
There is no specific case . AWS Provided recommendation exponential backoff option as general fix. https://forums.aws.amazon.com/thread.jspa?threadID=100414
upvoted 1 times
...
karmaah
6 months, 3 weeks ago
Thank you.
upvoted 1 times
...
...
karmaah
7 months, 1 week ago
Complicated question & Ans
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago