Courseiva
Deployment →hardMultiple Select

CV0-004 Deployment Practice Question

A company is deploying a new application on AWS and needs to ensure that the infrastructure is defined as code. The team wants to use AWS CloudFormation to provision resources. They require that the template can be reused across multiple environments (dev, test, prod) with different configurations, such as instance types and subnet IDs. The team also needs to ensure that changes to the infrastructure are applied in a controlled manner. Which two features should the team use to meet these requirements? (Choose two.)

⚠ Common exam trap

Watch out — candidates often confuse features that improve template organization or safety with those that directly enable environment-specific customization and controlled change preview.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use CloudFormation parameters to pass environment-specific values into the template.

Parameters enable the same CloudFormation template to be used across multiple environments by supplying different values at stack creation or update time. Change sets allow you to preview the effects of updates before applying them, ensuring controlled changes. Together, they satisfy the need for reusable templates with environment-specific configurations and safe, controlled updates. The other features address different concerns such as modularity, resource protection, and drift detection.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Use CloudFormation drift detection to identify resources that have been modified outside of CloudFormation.

    Why it's wrong here

    Drift detection identifies when resources have been changed outside of CloudFormation, which helps with compliance and troubleshooting, but it does not enable environment-specific configurations or controlled updates. It is a monitoring feature, not a deployment configuration or change management tool. Thus, it does not meet the requirements for template reuse and controlled change application.

  • ✓

    Use CloudFormation parameters to pass environment-specific values into the template.

    Why this is correct

    CloudFormation parameters allow you to input custom values when creating or updating a stack, such as instance types, key pairs, and subnet IDs. This enables template reuse across environments without modifying the template itself. Parameters can have default values, allowed values, and descriptions, making them ideal for environment-specific configurations. This directly addresses the requirement for different configurations per environment.

  • ✗

    Use CloudFormation stack policies to prevent updates to specific resources.

    Why it's wrong here

    Stack policies are used to prevent accidental updates or deletions of specific resources during a stack update. They provide a level of control but do not facilitate environment-specific configurations. They also do not provide a preview of changes; they simply block updates. Therefore, they do not fulfill the need for reusable templates with different configurations and controlled change preview.

  • ✓

    Use CloudFormation change sets to preview how proposed changes will impact running resources before executing them.

    Why this is correct

    Change sets provide a summary of proposed changes to a stack, allowing you to see how the changes will affect resources before applying them. This helps ensure that changes are applied in a controlled manner, as you can review the impact and decide whether to proceed. It is a key feature for managing updates safely and aligns with the requirement for controlled application of changes.

  • ✗

    Use CloudFormation nested stacks to modularize the template into smaller, reusable components.

    Why it's wrong here

    Nested stacks are useful for breaking down complex templates into reusable components, but they do not directly address environment-specific configurations or controlled change application. While they promote reuse, parameters are still needed for environment differences. Nested stacks alone do not provide a preview of changes or enforce controlled updates, so they do not meet the stated requirements as directly as parameters and change sets.

Visual reference

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

About these practice questions

This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official CompTIA exam blueprint

This CV0-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CV0-004 exam.