CareerExamPro

AWS Certified Solutions Architect – Professional (SAP-C02) practice test

9 practice questions for this exam, each with a full explanation and cited rule or blueprint reference.

Start practising

CCNA, CCNP, Terraform, AWS SAP & CKS: practice drill

10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.

Practice tests that prepare you for this exam

Practise by topic

About this exam

Agency / Issuer
Amazon Web Services
Region
Global / Online

Exact question counts, passing scores, and allowed reference materials vary by testing window and state/agency. Always confirm current rules with the official testing provider.

Sample questions

A platform engineering team stores Terraform state in a shared Amazon S3 bucket without state locking configured. Two CI/CD pipelines simultaneously execute terraform apply against the same workspace after merging separate pull requests. What is the primary operational risk, and how should the team prevent it?

  1. Terraform merges concurrent state diffs via S3 Object Versioning, so only S3 PUT costs rise.
  2. The second pipeline fails with a syntax error; adding terraform init -reconfigure prevents this.
  3. Concurrent writes can corrupt state or leave orphaned resources; enable remote state locking (S3 native/DynamoDB or HCP Terraform).
  4. Concurrent applies safely serialize at the AWS API layer through IAM throttling, so enabling S3 Transfer Acceleration is the only required change.
Show the answer

C. Concurrent writes can corrupt state or leave orphaned resources; enable remote state locking (S3 native/DynamoDB or HCP Terraform).

Without remote state locking, two concurrent terraform apply runs read the same starting state and race to overwrite the remote state file, causing lost updates, corrupted state, or untracked/duplicated cloud resources. Enabling state locking—via an S3 backend with native S3 lockfiles (use_lockfile = true) or a DynamoDB lock table, or via HCP Terraform's managed remote execution and locking—ensures only one state-mutating operation runs at a time.

Reference: HashiCorp Terraform Documentation (State Locking & S3 Backend / HCP Terraform)

An engineering team manages an AWS Auto Scaling Group (ASG), a Launch Template attached to it, and a stateful production RDS cluster in Terraform. They must ensure: (1) replacing the Launch Template never leaves the ASG without a valid template, (2) accidental terraform destroy cannot delete the RDS cluster, and (3) Terraform ignores ASG desired_capacity changes made dynamically by scaling policies. Which lifecycle settings satisfy all three requirements?

  1. prevent_destroy = true on the template, ignore_changes = all on RDS, and create_before_destroy on ASG.
  2. create_before_destroy = true on the template, prevent_destroy = true on RDS, and ignore_changes = [desired_capacity] on the ASG.
  3. replace_triggered_by on the Launch Template, read_only = true on the RDS cluster, and skip_refresh = true on the ASG desired capacity.
  4. create_before_destroy = false on the template, protect_state = true on RDS, and ignore_changes = [launch_template].
Show the answer

B. create_before_destroy = true on the template, prevent_destroy = true on RDS, and ignore_changes = [desired_capacity] on the ASG.

Terraform's default replacement order is destroy-then-create; setting `create_before_destroy = true` on the Launch Template (or ACM cert / target group) provisions the replacement before removing the old dependency. Setting `prevent_destroy = true` on the stateful RDS cluster causes Terraform to reject any plan that would destroy it. Setting `ignore_changes = [desired_capacity]` on the ASG prevents Terraform from reverting runtime scaling adjustments made by AWS Auto Scaling.

Reference: HashiCorp Terraform Documentation (The `lifecycle` Meta-Argument)

A multi-account AWS Organization uses a central Shared Services VPC connected to on-premises over Direct Connect. On-premises clients must resolve private DNS records in AWS Route 53 Private Hosted Zones (aws.example.internal), and EC2 workloads across 30 spoke VPCs must resolve on-premises Active Directory records (corp.example.internal). Which architecture provides scalable, managed bidirectional hybrid DNS resolution?

  1. Deploy a single Route 53 Resolver Inbound Endpoint in the Shared Services VPC and attach forwarding rules to it so traffic flows bidirectionally.
  2. Enable Route 53 DNSSEC on all Private Hosted Zones and point on-premises DHCP clients directly to the VPC +2 resolver IP (169.254.169.253).
  3. Deploy Inbound and Outbound Resolver Endpoints in the Shared Services VPC, add forwarding rules for corp.example.internal, and share rules via AWS RAM.
  4. Create identical Public Hosted Zones for both domains and restrict them using VPC Gateway Endpoints so queries stay on the AWS private backbone.
Show the answer

C. Deploy Inbound and Outbound Resolver Endpoints in the Shared Services VPC, add forwarding rules for corp.example.internal, and share rules via AWS RAM.

Route 53 Resolver Endpoints are unidirectional: an Inbound Endpoint provides ENI IPs in the Shared Services VPC that on-premises DNS servers forward aws.example.internal queries to (resolving associated Private Hosted Zones), while an Outbound Endpoint paired with a Resolver Forwarding Rule forwards corp.example.internal queries from AWS to on-premises DNS servers. Sharing the forwarding rule to all 30 spoke accounts/VPCs via AWS Resource Access Manager (RAM) avoids deploying redundant endpoints in every spoke VPC.

Reference: AWS Route 53 Developer Guide (Hybrid Cloud DNS with Route 53 Resolver Endpoints & RAM)

Taking this exam soon?

Tell us which exam domains or calculation drills you want more practice on.

Other Enterprise Networking & DevOps exams