SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
SOA-C03 · Domain 3

Deployment, Provisioning, and Automation practice questions

Deployment, Provisioning, and Automation is worth 22% of the SOA-C03 exam — the heaviest of the 5 domains. Provisioning with CloudFormation and the AWS CDK, image building, cross-account resource sharing, and event-driven operational automation. 6 fully worked examples are further down this page, answers included.

Exam weight
22%
the heaviest of the 5 domains
Questions
114
across 2 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 5 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Deployment, Provisioning, and Automation questions, fully explained

Questions from the SOA-C03 bank mapped to domain 3, with the answer key and the reasoning behind every option. None of them repeat the examples on the main SOA-C03 practice page.

Question 1Deployment, Provisioning, and Automation

A company's disaster recovery plan requires launching its hardened web server image in a second Region within minutes of a decision to fail over. The AMI currently exists only in us-east-1, and the DR Region's launch template is still empty. What should a CloudOps engineer do now to meet the plan?

Choose one.

  • a
    Reference the us-east-1 AMI ID directly in the launch template created in the DR Region.

    AMI IDs are Regional; a launch template in another Region cannot resolve an AMI that exists only in us-east-1, so launches would fail.

  • b
    Wait for the failover decision, then copy the AMI into the DR Region and launch from it.

    Copying an AMI copies all of its snapshot data and can take a long time for large images, so starting the copy at failover time risks missing the within-minutes requirement.

  • c
    Copy the AMI's backing snapshots into the DR Region and reference them in the launch template.

    A launch template needs an AMI ID as its image; snapshots alone are not a launchable image until someone registers an AMI from them, which adds a manual step at failover.

  • d
    Copy the AMI from us-east-1 into the DR Region now and reference the new AMI ID there. Correct

    Copying the AMI creates a new AMI (with its own ID and snapshots) in the DR Region, which the DR launch template can then reference.

The concept

AMIs are Regional resources: to launch an image in another Region you copy it there, which creates a new AMI with a new ID.

Why that’s the answer

An AMI and its snapshots live in one Region, so launching the same image elsewhere needs a copy there, and the copy gets a new AMI ID. Because a copy moves all the snapshot data and can take a long time, it must be done ahead of a failover, not at the moment of it. A foreign AMI ID does not resolve in another Region, and copied snapshots are not a launchable image until an AMI is registered from them.

How to reason it out
  1. Recognise that AMI IDs are scoped to a single Region.
  2. Note the time constraint: a copy is not instant, so it must exist before failover.
  3. Copy the AMI into the DR Region now (CopyImage, or an EC2 Image Builder distribution setting for every new build).
  4. Reference the new Regional AMI ID in the DR launch template and re-copy whenever the golden image changes.

Exam tip: One AMI, one Region - copy it to every Region that must launch it.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

Question 2Deployment, Provisioning, and Automation

A security team has approved a hardened base AMI in its tooling account. Two specific workload accounts in the same organization need to launch instances from it, and no other account in the organization may see it. What should a CloudOps engineer do with the LEAST operational effort?

Choose one.

  • a
    Share the AMI with the organization so that both workload accounts can launch it.

    Sharing with the organization's ARN would expose the AMI to every member account, which breaks the requirement that no other account can see it.

  • b
    Run a copy-image operation from the tooling account into both of the workload accounts.

    CopyImage creates the copy in the caller's own account; it cannot push an AMI into another account. The target accounts would first need launch access to copy it themselves.

  • c
    Share the AMI's backing snapshots with both workload accounts through snapshot permissions.

    Snapshot permissions let the accounts create volumes from the snapshots or register their own AMIs from them, which is extra work per account and leaves separate images to manage; it does not share the AMI itself.

  • d
    Add the two account IDs to the AMI's launch permissions in the tooling account. Correct

    Adding specific account IDs to an AMI's launch permissions shares it privately with exactly those accounts, which is the intended mechanism.

The concept

A private AMI is shared by adding account IDs (or an organization/OU ARN) to its launch permissions; scope the share to exactly the principals that need it.

Why that’s the answer

Launch permissions are the AMI's own sharing control and can name individual accounts, an OU or the whole organization. Naming the two account IDs gives access to them and nobody else in one step. Organization-wide sharing breaks the visibility constraint, CopyImage only creates copies in the calling account, and sharing only the snapshots makes each account rebuild its own AMI. If the AMI's snapshots are encrypted with a customer managed KMS key, the key policy must also let those accounts use the key, or launches fail.

How to reason it out
  1. Identify the narrowest principal set that needs access: here, two account IDs.
  2. Add those account IDs to the AMI's launch permissions (ModifyImageAttribute).
  3. If the snapshots use a customer managed KMS key, grant the accounts kms:Decrypt/CreateGrant on that key.
  4. Have the workload accounts launch from the AMI ID, or copy it to own a local copy.

Exam tip: Private AMI sharing = launch permissions, scoped to the exact accounts or OUs; encrypted AMIs also need the key shared.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

Question 3Deployment, Provisioning, and Automation

One CloudFormation template must deploy dev, staging, and production stacks that differ only in instance size and environment name, with the values supplied at deploy time. Which template section should hold these per-environment values?

Choose one.

  • a
    Parameters Correct

    Parameters are exactly the mechanism for deploy-time inputs: one template serves every environment, and instance size and environment name arrive as values when each stack is created.

  • b
    Mappings

    Mappings are static lookup tables baked into the template — useful for Region-to-AMI tables, but they cannot accept values supplied at deploy time.

  • c
    Outputs

    Outputs surface values after a stack is deployed, such as a load balancer DNS name; they are results, not inputs.

  • d
    Conditions

    Conditions switch resources on or off based on evaluated expressions; they consume parameter values but are not where deploy-time inputs are declared.

The concept

CloudFormation template anatomy assigns each section one job: Parameters take deploy-time input, Mappings hold static lookup tables, Conditions toggle resources, Resources declare the infrastructure, and Outputs surface results.

Why that’s the answer

Values that differ per environment and arrive at deploy time are the textbook definition of Parameters. Mappings fail because they are fixed inside the template, Outputs are post-deployment results rather than inputs, and Conditions only evaluate expressions (often over parameters) to include or exclude resources.

How to reason it out
  1. Declare parameters for the instance size and environment name, with types, defaults, and allowed values where sensible.
  2. Reference the parameters in the Resources section instead of hard-coding values.
  3. Deploy the same template three times, passing different parameter values for dev, staging, and production.
  4. Optionally add Conditions keyed on the environment parameter to create production-only resources.

Exam tip: Per-environment, deploy-time values belong in Parameters — one template, many stacks.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

Question 4Deployment, Provisioning, and Automation

A CloudOps engineer tries to delete a shared networking stack, but CloudFormation rejects the request because the stack's exported subnet IDs are still in use by three application stacks. The application stacks must keep running. What must the engineer do before the networking stack can be deleted?

Choose one.

  • a
    Set DeletionPolicy: Retain on the subnets in the networking stack, then retry the delete.

    DeletionPolicy controls what happens to a resource when it is deleted; it does not remove the export or the imports that block the delete.

  • b
    Run drift detection on the networking stack to clear the stale export references to it.

    Drift detection compares live resources with the template; it does not touch exports or the stacks that import them.

  • c
    Replace the Fn::ImportValue references in the application stacks, then retry the delete. Correct

    An export cannot be deleted (or changed) while any stack imports it. Updating the importing stacks to use another value (for example a parameter) releases the export, after which the delete succeeds.

  • d
    Retry the delete and choose to retain the exported subnets when the console prompts.

    Choosing resources to retain is offered only when retrying a stack in DELETE_FAILED; it does not override the rule that an export in use blocks the delete.

The concept

A stack export cannot be deleted or modified while another stack imports it with Fn::ImportValue; the importers must stop referencing it first.

Why that’s the answer

CloudFormation enforces cross-stack references: as long as any stack imports a value, the exporting stack cannot remove that export, so deleting the stack is refused. The fix is to update the importing stacks so they no longer use Fn::ImportValue for those IDs (pass them as parameters or SSM parameters instead), then delete. DeletionPolicy and retain-on-delete act on resources, not on exports, and drift detection only reports configuration differences.

How to reason it out
  1. Run list-imports for each export to find which stacks import it.
  2. Update those stacks to take the subnet IDs some other way (parameter, SSM Parameter Store).
  3. Confirm list-imports returns nothing for the exports.
  4. Delete the networking stack.

Exam tip: Exports in use lock the exporter - remove the imports first, then delete.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

Question 5Deployment, Provisioning, and Automation

Before updating a production stack, a CloudOps engineer creates a change set. The change set lists the stack's Amazon RDS DB instance with Action: Modify and Replacement: True. The template sets no snapshot identifier for the instance. What will happen if the change set is executed as-is?

Choose one.

  • a
    CloudFormation creates a new DB instance and deletes the old one, so the new one starts empty. Correct

    Replacement means CloudFormation creates a new physical resource, switches references to it and then deletes the old one. Without a snapshot to restore from, the new instance does not contain the old data.

  • b
    CloudFormation modifies the existing DB instance in place, with a brief interruption to it.

    An in-place change with an interruption is what Replacement: False (with a reboot) looks like; Replacement: True means a new physical resource.

  • c
    CloudFormation pauses before the replacement and waits for an operator to approve the step.

    Executing a change set runs the whole update; CloudFormation has no built-in per-resource approval pause. Approval gates belong in a pipeline before execution.

  • d
    CloudFormation replaces the DB instance and copies the existing data into the new instance.

    CloudFormation does not migrate data between the old and new physical resources during a replacement.

The concept

In a change set, Replacement: True means CloudFormation will create a new physical resource and delete the old one - for a database, the new instance does not carry the old data.

Why that’s the answer

Change sets classify each modification as no replacement, conditional replacement or replacement. With Replacement: True, CloudFormation builds the new resource, updates references, then deletes the original during cleanup. For RDS that means a fresh database. An in-place modification is a different classification, there is no approval pause during execution, and CloudFormation never copies data between the old and new resources.

How to reason it out
  1. Read the Replacement column for every stateful resource in the change set.
  2. Find which property change forces replacement (for example a changed DB identifier or engine).
  3. Either avoid the change, or protect the data first (UpdateReplacePolicy: Snapshot or Retain, a manual snapshot, or a stack policy denying Update:Replace).
  4. Execute the change set only when the replacement is intended and the data is safe.

Exam tip: Replacement: True on a database means a brand-new, empty database - stop and protect the data first.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

Question 6Deployment, Provisioning, and Automation

During an audit, a CloudOps engineer suspects that security group rules created by a CloudFormation stack were edited directly in the console weeks ago. Which action shows every resource in the stack whose live configuration no longer matches the template?

Choose one.

  • a
    Run drift detection on the stack and review the drift status of each resource. Correct

    Drift detection compares each supported resource's live configuration with the template's expected values and reports MODIFIED, DELETED or IN_SYNC per resource.

  • b
    Create a change set from the current template and review the proposed changes.

    A change set compares the submitted template with the stack's recorded template, not with live resources, so console edits do not appear in it.

  • c
    Review the stack's event history for update events on the security group resources.

    Stack events record CloudFormation's own operations; edits made outside CloudFormation never appear there.

  • d
    Run a stack update with the unchanged template so CloudFormation reports the differences.

    An update with an unchanged template is rejected with 'No updates are to be performed'; CloudFormation does not re-check live configuration during an update.

The concept

Drift detection is the CloudFormation feature that compares live resource configuration with the stack template; change sets and stack events only see CloudFormation's own view.

Why that’s the answer

Out-of-band console edits are invisible to anything that compares templates with templates (change sets) or records CloudFormation's own actions (stack events). Only drift detection reads the live configuration of each supported resource and reports which ones are MODIFIED or DELETED, with property-level differences.

How to reason it out
  1. Run drift detection on the stack (or a stack set).
  2. Filter the results for MODIFIED and DELETED resources.
  3. Open the property differences to see the expected versus actual values.
  4. Reconcile by updating the template or reverting the resource, then re-run detection.

Exam tip: Template vs template = change set; template vs live resources = drift detection.

CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.

What SOA-C03 domain 3 tests, topic by topic

The official exam guide breaks Deployment, Provisioning, and Automation into 2 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published SOA-C03 practice questions per topic in Deployment, Provisioning, and Automation
TopicWhat it coversQuestions
Provision and maintain cloud resourcesExam guide task 3.1. Creating and managing AMIs and container images (EC2 Image Builder); managing resource stacks with CloudFormation and the AWS CDK and remediating deployment issues (subnet sizing, CloudFormation errors, permissions); provisioning and sharing resources across Regions and accounts (AWS RAM, CloudFormation StackSets); deployment strategies and third-party automation tools (Terraform, Git).57
Automate the management of existing resourcesExam guide task 3.2. Automating operational processes with Systems Manager; event-driven automation with Lambda, S3 Event Notifications, EventBridge, and AWS DevOps Agent.57
Total114

Revise Deployment, Provisioning, and Automation before you drill it

Other SOA-C03 domains

Deployment, Provisioning, and Automation: your questions

Deployment, Provisioning, and Automation is domain 3 of the SOA-C03 exam guide and carries 22% of the scored content — the heaviest of the 5 domains. On a 65-question paper that works out to roughly 14 questions, though AWS does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official SOA-C03 exam guide.