Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 51 discussion

C is Correct. B is WRONG because intrinsic functions can't be used in Parameter as per AWS documentation. https://repost.aws/knowledge-center/cloudformation-template-validation

C seems right

C is correct: use nested stacks and Fn::ImportValue intrinsic functions with the resources of the nested stack A: no mention of nested stack B and D: Fn::ImportValue intrinsic function is used on child template to import values from parent template. So it should not be used on root template, which is the universal parent tempalte of all other templates

C is the best answer. B is wrong as you need to use Fn::ImportValue in Resource section to import CFN template outputs.

I will go with C

B. Use nested stacks to define common infrastructure components. To access the exported values, use TemplateURL to reference the networking team’s template. To retrieve Virtual Private Cloud (VPC) and subnet values, use Fn::ImportValue intrinsic functions in the Parameters section of the root template. Use the CreateChangeSet and ExecuteChangeSet commands to update existing development environments. Nested stacks allow you to modularize and reuse CloudFormation code. For this case, this is helpful because you have common infrastructure components that are shared across environments. The Fn::ImportValue function is used to import values that have been exported in another stack. Since the networking team exports the VPC and subnet information, this can be used in the CloudFormation stack to reference those values.

C is the correct answer

C ipsingh is absolutely correct

Im 50/50 C or B, but B doesn't provide a clear approach for retrieving the exported values and placing position of Parameters section of the root template, which is not required to place it there, it must declare inside resource. So i think Answer C make sense.

C makes more sense

c is correct

B. Use nested stacks to define common infrastructure components. To access the exported values, use TemplateURL to reference the networking team’s template. To retrieve Virtual Private Cloud (VPC) and subnet values, use Fn::ImportValue intrinsic functions in the Parameters section of the root template. Use the CreateChangeSet and ExecuteChangeSet commands to update existing development environments. This approach is a good fit because it allows the developer to define reusable infrastructure components as nested stacks. To retrieve VPC and subnet values, the intrinsic function Fn::ImportValue is used in the Parameters section of the root template, which retrieves the values from the output of the networking team’s CloudFormation stack. To update existing environments, the CreateChangeSet and ExecuteChangeSet commands are used, which provides a way to easily update the deployed infrastructure. Additionally, the use of nested stacks helps to ensure consistency across environments.

Option B is correct. Using nested stacks, the common infrastructure components can be defined in separate templates that can be referenced by the root template. This allows for easy updates and maintenance of the common components. The networking team’s CloudFormation template can be used to export the VPC and subnet values, which can be referenced in the root template using Fn::ImportValue intrinsic functions in the Parameters section. The CreateChangeSet and ExecuteChangeSet commands can be used to update the existing development environments. Option C is not the best choice because using Fn::ImportValue intrinsic functions with the resources of the nested stack can lead to circular dependencies and make it difficult to manage the infrastructure.

C is correct