Exam AWS Certified SysOps Administrator - Associate topic 1 question 251 discussion

Nested stack declaration: AWS::CloudFormation::Stack -> TemplateURL: https://s3.amazonaws.com/cloudformation-templates-us-east-1/template.yml StackSets are used with AWS Organizations to share stacks between different accounts.

Option C (Develop CloudFormation nested stacks) is the correct option for managing common components in multiple templates. Nested stacks allow you to break down complex templates into smaller, more manageable units, where each nested stack can have its own set of parameters, conditions, and resources. This approach promotes code reusability, simplifies template management, and reduces duplication of common components across templates. By creating dedicated templates as nested stacks, you can define and maintain the common components in a single location and then reference them from other templates. This helps ensure consistency and makes it easier to update and maintain the infrastructure as changes can be made in one place and propagated to all templates that use the nested stack.

'common component' --> nested stack.

As your infrastructure grows, common patterns can emerge in which you declare the same components in multiple templates. You can separate out these common components and create dedicated templates for them. Then use the resource in your template to reference other templates, creating nested stacks.

- Cross Stacks : export A stack -> import B stack Export Value를 여러stack에서 Import해서 공유 (ex. VPC) - Nested Stacks : share common stack 재사용 용도 (ex. RDS, ASG, ELB)

Concur with C - refer to this supporting document - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.html

The correct answer is C. Develop CloudFormation nested stacks. CloudFormation nested stacks allow you to create a parent stack that references multiple child stacks. Each child stack can have its own parameters and conditions, and the parent stack can be used to create or update all the resources across all the child stacks at once. By using CloudFormation nested stacks, the SysOps administrator can create dedicated templates for the common components, each with their own parameters and conditions. The common components can be declared once in a shared template, which can then be referenced by the child stacks.

As your infrastructure grows, common patterns can emerge in which you declare the same components in multiple templates. You can separate out these common components and create dedicated templates for them. Then use the resource in your template to reference other templates, creating nested stacks.