Exam AWS-SysOps topic 1 question 615 discussion

It should be B. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html Use the CreationPolicy attribute when you want to wait on resource configuration actions before stack creation proceeds. For example, if you install and configure software applications on an EC2 instance, you might want those applications to be running before proceeding. In such cases, you can add a CreationPolicy attribute to the instance, and then send a success signal to the instance after the applications are installed and configured.

The CreationPolicy attribute in CloudFormation allows you to specify a timeout period for resource creation. By adding a CreationPolicy with a timeout set to 4 hours, you are setting a maximum time limit for the installation and configuration process to complete.

B Creation Policy

The correct answer is C. With the DependsOn attribute you can specify that the creation of a specific resource follows another. When you add a DependsOn attribute to a resource, that resource is created only after the creation of the resource specified in the DependsOn attribute. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-dependson.html

B. https://aws.amazon.com/blogs/devops/use-a-creationpolicy-to-wait-for-on-instance-configurations/

B is the answer Creation Policy is to be used when you need to wait for a resource to be configured during the stack creation procedures.

Answerer is B When you provision an Amazon EC2 instance in an AWS CloudFormation stack, you might specify additional actions to configure the instance, such as install software packages or bootstrap applications. Normally, CloudFormation proceeds with stack creation after the instance has been successfully created. However, you can use a CreationPolicy so that CloudFormation proceeds with stack creation only after your configuration actions are done. That way you’ll know your applications are ready to go after stack creation succeeds. A CreationPolicy instructs CloudFormation to wait on an instance until CloudFormation receives the specified number of signals. This policy takes effect only when CloudFormation creates the instance.

B. CreationPolicy with a timeout set to 4 hours.

answer: B

I'll go with B

B. CreationPolicy with a timeout set to 4 hours.

it is B。。。 "AutoScalingGroup": { "Type": "AWS::AutoScaling::AutoScalingGroup", "Properties": { ... }, "CreationPolicy": { "ResourceSignal": { "Count": "3", "Timeout": "PT5M" } } }

Answer B is correct: https://aws.amazon.com/blogs/devops/use-a-creationpolicy-to-wait-for-on-instance-configurations/

Answer B is correct: https://aws.amazon.com/blogs/devops/use-a-creationpolicy-to-wait-for-on-instance-configurations/

The answer is B. This question has a timeout period. It can be set in CreationPolicy. The timeout period starts after AWS CloudFormation starts creating the resource, and the timeout expires no sooner than the time you specify but can occur shortly thereafter. The maximum time that you can specify is 12 hours.

A AWS CloudFormation creates a wait condition just like any other resource. When AWS CloudFormation creates a wait condition, it reports the wait condition’s status as CREATE_IN_PROGRESS and waits until it receives the requisite number of success signals or the wait condition’s timeout period has expired. If AWS CloudFormation receives the requisite number of success signals before the time out period expires, it continues creating the stack; otherwise, it sets the wait condition’s status to CREATE_FAILED and rolls the stack back.

Should be B Always tricky questions but here's a video that explans why CreationPolicy and not a WaitCondition https://www.youtube.com/watch?v=K9TyYZbI--o