# Configuration Management

Configuration management is the practice of defining, tracking, and controlling system settings and components so that environments remain consistent with an approved state.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/configuration-management

> Configuration management makes infrastructure and application settings repeatable, auditable, and easier to recover when changes cause problems. In the cloud, it is a shared responsibility: the provider configures its underlying infrastructure, while customers manage the settings and software within their control.

Practice exams covering Configuration Management: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional).

## 6 key aspects of Configuration Management

Effective configuration management combines clear ownership, approved baselines, repeatable deployment, configuration history, drift detection, and controlled recovery.

1. **Responsibility boundaries**: Identify which configuration layers belong to the provider and which remain under customer control. Reassess the boundary when moving from virtual machines to managed services rather than assuming the same responsibilities apply.
2. **Approved configuration baselines**: Define expected settings, software versions, and resource properties before deployment. Baselines give engineers a concrete standard for evaluating consistency and investigating deviations.
3. **Repeatable deployment**: Use version-controlled templates and configuration automation to apply approved settings consistently. Test changes before broad deployment because automation can reproduce mistakes as efficiently as correct settings.
4. **Configuration visibility and history**: Maintain an inventory and configuration history for resources within the required scope. Combine configuration records with activity logs to investigate what changed and who initiated the change.
5. **Drift detection and remediation**: Compare actual settings against approved expectations and investigate differences. Automate remediation where the corrective action is well understood, with safeguards for changes that could disrupt workloads.
6. **Controlled changes and recovery**: Review, test, and authorize configuration changes according to their risk. Preserve previous definitions and plan recovery, recognizing that some changes require resource replacement or cannot be reversed without data recovery.

## Cloud services for Configuration Management

AWS CloudFormation establishes repeatable resource definitions, while AWS Systems Manager applies and maintains operating system and software settings on managed nodes. AWS Config records supported resource configurations and evaluates selected requirements, helping teams detect deviations from approved expectations. AWS CloudTrail supplies activity records that help explain how those deviations occurred. Together, these services support deployment, observation, investigation, and remediation across customer-controlled layers. Engineers must still define the baselines, configure permissions and coverage, review exceptions, and test corrective actions; using the services does not transfer customer configuration responsibilities to AWS.

- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records configuration information and relationships for supported resource types and can evaluate resources against configured rules. It helps identify deviations, but evaluation coverage depends on the resources, properties, and rules in scope; remediation must be configured separately.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: AWS Systems Manager helps manage operating systems and software on managed nodes. Capabilities such as State Manager, Inventory, and Automation support desired configurations, visibility, and controlled corrective actions when the required access and node prerequisites are configured.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS CloudFormation defines and provisions supported AWS resources through templates, enabling repeatable infrastructure configurations. Change sets help review proposed updates, while drift detection can identify differences for supported resources and properties.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS CloudTrail records account activity, including supported API actions that change resource configurations. It helps investigate who made a change and when, but does not define desired settings or enforce configuration baselines.

## Configuration Management exam questions

Real practice exam questions on Configuration Management, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company runs an application on Amazon EC2 instances that are regularly replaced to meet demand. Administrators enable the application's required transaction logging manually, but replacement instances start with logging disabled. The company must ensure that replacement instances meet its logging policy. Which action should the company take under the AWS shared responsibility model?

**Correct answer:** Include the approved application logging settings in a version-controlled deployment configuration, apply it to each replacement instance, and verify the settings.

**Explanation:** The customer is responsible for configuring its application. Recording approved settings and applying them consistently during deployment prevents replacement instances from losing required configuration. Verification confirms that the deployed application meets the policy.

### Question 2 (DVA-C02)

**Question:**

A company uses AWS AppConfig to manage purchase-limit settings that an application retrieves at runtime. A CI/CD pipeline creates a hosted configuration version and deploys it to a test environment before production. The configuration profile already has a JSON Schema validator that requires minimumQuantity and maximumQuantity to be positive integers.

A recent configuration passed validation but set minimumQuantity higher than maximumQuantity, causing application errors. The developer must ensure that future configurations violating this relationship are rejected before a deployment begins, without changing the application code.

Which change meets this requirement?

**Correct answer:** Add a Lambda validator to the configuration profile. Have the function decode the configuration, compare the quantities, and raise an exception if minimumQuantity exceeds maximumQuantity.

**Explanation:** AppConfig supports Lambda validators for semantic checks that go beyond the existing schema's field-level constraints. AppConfig invokes the validator before deployment and treats a Lambda invocation error as validation failure. Raising an exception rejects the invalid configuration before it is deployed.

### Question 3 (AIP-C01)

**Question:**

A company operates a Lambda-based inference router with deployed integrations for two approved foundation model providers. The router retrieves its model-routing configuration at runtime, and each execution environment adopts configuration changes within 1 minute. Operators must switch providers without updating application code or Lambda settings.

Both providers return successful API responses even when generated summaries omit important facts. An existing evaluation pipeline publishes a custom CloudWatch omission-rate metric within 8 minutes after inference. A CloudWatch alarm detects an unacceptable omission rate within another 2 minutes. Application error and latency metrics do not reveal these quality regressions.

The company wants to distribute a provider-selection change gradually over 10 minutes, then observe it for 20 additional minutes after configuration distribution reaches 100%. A quality regression detected during either period must automatically initiate restoration of the previous routing configuration, without a code deployment or custom rollback workflow.

Which solution best meets these requirements?

**Correct answer:** Store routing configuration in AWS AppConfig. Use a deployment strategy with a 10-minute deployment duration and a 20-minute final bake time. Associate the omission-rate CloudWatch alarm with the AppConfig environment, and have the router continue refreshing the deployed configuration at runtime.

**Explanation:** The deployment duration provides gradual distribution, while the final bake time keeps the deployment under observation after distribution reaches 100%. An environment-associated CloudWatch alarm can trigger automatic rollback during deployment or the bake period. Monitoring the omission-rate metric detects the stated quality failure, and runtime refresh allows execution environments to adopt the restored configuration without code changes.

### Question 4 (DOP-C02)

**Question:**

In 2023, a company operates an application on an existing AWS OpsWorks Stacks stack that uses Chef 12. During a downstream service incident, a DevOps engineer must change the application's CONNECTION_TIMEOUT environment variable on all online instances in the application layer.

The application's custom deployment recipe reads environment variables from the OpsWorks application configuration, renders a service configuration file, and restarts the service if the file changes. This recipe is assigned only to the layer's Deploy lifecycle event. The Setup and Configure recipes do not manage this file. All instances already have the approved cookbooks, and the application source is pinned to an immutable Git commit that must remain unchanged.

The engineer updates the environment variable in the OpsWorks application settings. Which additional action will apply the change to the running application without replacing instances or introducing a new application version?

**Correct answer:** Create an OpsWorks deployment with the deploy command, specify the application's AppId, and target all online instances in the application layer while retaining the pinned source revision.

**Explanation:** Updating the OpsWorks application settings does not by itself reconfigure running applications. A deploy command for the application invokes the Deploy lifecycle recipes on the targeted instances. The custom recipe then consumes the updated environment variable, renders the configuration, and restarts the service as necessary. Keeping the immutable source revision unchanged avoids introducing a new application version.

### Question 5 (ANS-C01)

**Question:**

A company uses a custom AWS Config rule to evaluate route tables tagged NetworkBaseline=Required. Each route table must have an existing IPv4 default route that targets a designated transit gateway. Automatic remediation invokes an AWS Systems Manager Automation runbook to restore the approved target. During testing, engineers observe that remediation sometimes starts after an administrator has already corrected the route, because the compliance evaluation used an earlier configuration snapshot. Remediation retries can also invoke the runbook multiple times for the same route table. The company requires remediation to converge on the approved configuration without unnecessarily modifying routes that are already compliant. Which implementation best meets these requirements?

**Correct answer:** Have the runbook retrieve the route table's current configuration through the Amazon EC2 API. If the default route already targets the approved transit gateway, finish successfully without modifying it. Otherwise, replace the route target and verify the resulting configuration.

**Explanation:** AWS Config automatic remediation can act on an earlier compliance snapshot, including after a resource has become compliant. Checking the live configuration prevents unnecessary changes. Expressing remediation as convergence to a specified target, treating an already-compliant resource as success, and verifying the result makes repeated executions safe.

## Practice Configuration Management in a full exam

Questions on Configuration Management in each practice exam, with every answer option and an explanation for each:

- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 23 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 4 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 4 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 2 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Configuration Management

Configuration management establishes what a system should contain, how it should be configured, and how changes to that configuration are recorded and controlled. A configuration can include operating system settings, installed software versions, network rules, identity permissions, database parameters, and application options. Engineers define an approved baseline, deploy it consistently, and compare running environments against that baseline to identify unexpected differences.

Under the AWS shared responsibility model, configuration management is a shared control because both AWS and the customer perform it, but for different layers. AWS maintains the configuration of the infrastructure that supports its cloud services, including physical infrastructure and underlying infrastructure devices. Customers are responsible for configuring the resources, applications, and customer-controlled software they deploy. Shared does not mean that both parties jointly approve every setting or that AWS corrects customer misconfigurations automatically.

The exact boundary depends on the service. For an Amazon EC2 instance, AWS manages the underlying hardware and virtualization infrastructure, while the customer manages the guest operating system, installed applications, and security group rules. With a managed database, AWS operates more of the underlying platform, but the customer still controls settings such as permitted network access, database users, and supported database parameters. Choosing a managed service reduces some operational work; it does not remove responsibility for customer-accessible configuration.

A practical workflow starts with an inventory of resources and their owners. Engineers define approved settings in version-controlled templates or configuration policies, review proposed changes, test them outside production, and deploy them through controlled automation. For example, a team might require restricted administrative access, approved software versions, and enabled application logging. Configuration records and change history then help establish which resources meet those requirements and when deviations appeared.

Configuration drift occurs when the actual environment differs from the approved configuration. An emergency console change that opens a firewall rule can create drift even when the original deployment template was secure. Detection should lead to investigation and either remediation or an approved baseline update. Automatic remediation is useful for clear, low-risk violations, but a poorly designed rule can interrupt legitimate traffic or repeatedly undo an intentional operational change.

Automation improves consistency but can also spread an incorrect setting across many resources quickly. Reviews, staged deployments, limited deployment permissions, and recovery procedures reduce that risk. Detection also has limits: tools differ in resource coverage, supported properties, and evaluation timing. A compliant result demonstrates alignment with the rules being checked, not proof that the entire workload is secure.

Configuration management is broader than infrastructure as code, patch management, or change logging. Infrastructure as code describes and provisions resources, patch management updates software, and audit logs record actions; each supports configuration management without replacing it. For exam scenarios, first identify the affected layer, then determine whether AWS or the customer controls its configuration.

## Learn Configuration Management in lessons

4 short lessons on Configuration Management in 3 certification courses.

- CLF-C02: Configuration Management: responsibility boundaries (Premium), https://app.blowstack.com/lessons/configuration-management-responsibility-boundaries-clf-c02
- AIP-C01: Configuration Management: runtime model-routing configuration (Premium), https://app.blowstack.com/lessons/configuration-management-runtime-model-routing-configuration-aip-c01
- DOP-C02: Configuration Management: desired-state convergence (Premium), https://app.blowstack.com/lessons/configuration-management-desired-state-convergence-dop-c02
- DOP-C02: Configuration Management: event-driven configuration changes (Premium), https://app.blowstack.com/lessons/configuration-management-event-driven-configuration-changes-dop-c02
