Nested stacks for modularity in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding Nested Stack References

You have a main AWS CloudFormation stack that includes a nested stack for a VPC configuration. Which of the following correctly references the nested stack resource in the main template?

AWS

Resources:
  VPCStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: https://s3.amazonaws.com/examplebucket/vpc-template.yaml
      Parameters:
        VpcCIDR: 10.0.0.0/16

A

61/0.0.0.01 :RDICcpV    
:sretemaraP  
lmay.etalpmet-cpv/tekcubelpmaxe/moc.swanozama.3s//:sptth :LRUetalpmeT  
:seitreporP
kcatS::noitamroFduolC::SWA :epyT

B

Type: AWS::EC2::VPC
Properties:
  CidrBlock: 10.0.0.0/16

C

Type: AWS::CloudFormation::Stack
Properties:
  TemplateBody: |
    Resources:
      VPC:
        Type: AWS::EC2::VPC
        Properties:
          CidrBlock: 10.0.0.0/16

D

Type: AWS::CloudFormation::Stack
Properties:
  TemplateURL: https://s3.amazonaws.com/examplebucket/vpc-template.yaml
  Parameters:
    VpcCIDR: 10.0.0.0/16

💡 Hint

Look for the correct way to specify the nested stack's template location and parameters.

Option D correctly uses Type: AWS::CloudFormation::Stack with a valid TemplateURL and parameters. Option D is a direct resource, not a nested stack. Option D uses TemplateBody which is valid but not referencing an external nested stack. Option D uses an invalid TemplateURL format.

❓ service_behavior

intermediate

Behavior of Parameter Passing in Nested Stacks

When you pass parameters from a parent stack to a nested stack, what happens if the nested stack template expects a parameter that the parent stack does not provide?

A The nested stack deployment fails with a missing parameter error.

B The nested stack uses a default value for the missing parameter automatically.

C The parent stack ignores the missing parameter and continues deployment.

D The nested stack creates the parameter with a null value.

💡 Hint

Think about required parameters and deployment validation.

If a nested stack expects a parameter and it is not provided by the parent stack, the deployment fails because the nested stack cannot resolve the required input.

❓ security

advanced

Security Best Practices for Nested Stack Templates

You want to secure your nested stack templates stored in Amazon S3. Which approach best protects the templates from unauthorized access while allowing CloudFormation to deploy them?

A Make the S3 bucket public and restrict access using bucket policies.

B Use S3 bucket policies to allow access only from CloudFormation service principal and encrypt templates with SSE-S3.

C Store templates in a private bucket without any policies and rely on IAM roles for access.

D Use pre-signed URLs with long expiration times for template URLs.

💡 Hint

Consider least privilege and encryption.

Option B ensures the templates are encrypted and only accessible by CloudFormation via bucket policies, following security best practices. Public buckets or long-lived pre-signed URLs increase risk.

❓ Configuration

advanced

Troubleshooting Nested Stack Rollback Behavior

You deploy a parent stack with nested stacks. One nested stack fails during creation. What is the default behavior of CloudFormation regarding the parent and other nested stacks?

A CloudFormation rolls back the entire parent stack and all nested stacks created so far.

B CloudFormation deletes only the failed nested stack and keeps the rest.

C CloudFormation continues creating other nested stacks and leaves the failed one in rollback state.

D CloudFormation pauses deployment and waits for manual intervention.

💡 Hint

Think about atomic deployment and rollback.

CloudFormation treats the parent stack and nested stacks as a single unit. If any nested stack fails, the entire deployment rolls back to maintain consistency.

🧠 Conceptual

expert

Advantages of Using Nested Stacks for Large Infrastructure

Which of the following is NOT a primary advantage of using nested stacks in AWS CloudFormation for modular infrastructure design?

A Improved template readability and maintainability by breaking large templates into smaller ones.

B Reuse of common infrastructure components across multiple stacks.

C Automatic scaling of resources within nested stacks without manual intervention.

D Simplified updates by isolating changes to specific nested stacks.

💡 Hint

Consider what nested stacks manage versus what AWS services handle automatically.

Nested stacks help organize and reuse templates but do not provide automatic scaling of resources; scaling is managed by specific AWS services like Auto Scaling groups.