Courseiva

AWS Certified Solutions Architect Professional SAP-C02 (SAP-C02) — Questions 601–675

984 questions total · 14 pages · All types, answers revealed

Page 8

Page 9 of 14

Page 10
601
MCQhard

Refer to the exhibit. A company uses this IAM policy to allow an automation script to manage Amazon EBS snapshots. The script runs on an EC2 instance with this attached IAM role. The script is failing when trying to create a snapshot from a volume and tag it. The error message indicates an authorization failure. What is the root cause?

A.The policy does not grant permission to call ec2:DescribeSnapshots, which is required before creating a snapshot.
B.The policy lacks a condition key to restrict the snapshot creation to specific volumes.
C.The policy does not grant permission to call ec2:CreateSnapshot on the volume resource.
D.The policy does not include ec2:CreateTags for the volume, only for snapshots.
AnswerC

CreateSnapshot requires permission on the volume (e.g., arn:aws:ec2:region:account:volume/*) and optionally on the snapshot.

Why this answer

The error occurs because the IAM policy grants `ec2:CreateSnapshot` only on the `arn:aws:ec2:*::snapshot/*` resource, but the API call to create a snapshot also requires permission on the source volume resource (`arn:aws:ec2:*:*:volume/*`). Without that volume-level permission, the request fails with an authorization error, even though the snapshot-level permission is present.

Exam trap

The trap here is that candidates assume only the target snapshot resource needs permission, but AWS requires explicit authorization on the source volume resource for the `ec2:CreateSnapshot` action.

How to eliminate wrong answers

Option A is wrong because `ec2:DescribeSnapshots` is a read-only action and is not required before creating a snapshot; the failure is due to missing resource-level permissions, not a missing read action. Option B is wrong because the policy does not include any condition keys, but the absence of a condition key is not the root cause—the core issue is the missing volume resource in the `ec2:CreateSnapshot` action. Option D is wrong because the policy does include `ec2:CreateTags` on the snapshot resource (`arn:aws:ec2:*::snapshot/*`), and the error is about creating the snapshot itself, not tagging it.

602
MCQhard

A media company is designing a new video transcoding pipeline. Source files are uploaded to an Amazon S3 bucket, and the company wants each upload to trigger processing without managing servers. Jobs can take up to 20 minutes, and the company must be able to retry a failed job without reprocessing successful ones. The operations team wants visibility into which specific uploads failed and the ability to replay only those. The company also wants to decouple the upload event from the worker so that bursts of thousands of simultaneous uploads do not overwhelm the processing tier. Which design should the solutions architect recommend?

A.Configure S3 Event Notifications to publish to an Amazon SNS topic that fans out to an AWS Step Functions state machine per upload
B.Configure S3 Event Notifications to send each upload to an Amazon SQS queue, and run workers on Amazon ECS that poll the queue and delete messages only after successful transcoding
C.Enable S3 Transfer Acceleration and use S3 Batch Operations to transcode all objects nightly regardless of which uploads succeeded
D.Configure S3 Event Notifications to invoke an AWS Lambda function directly for each upload, with a 15-minute timeout and built-in retries
AnswerB

SQS durably buffers bursts of uploads so the worker tier is not overwhelmed, and each message maps to one upload, giving per-job retry granularity. Workers delete the message only after success, so failed jobs remain visible and can be replayed individually. ECS workers have no 15-minute invocation limit, so 20-minute transcodes complete normally while the queue absorbs traffic spikes.

Why this answer

The design must buffer unpredictable bursts, support jobs longer than a Lambda invocation, and allow selective replay of only failed uploads. An SQS queue between S3 event notifications and a long-running ECS worker tier satisfies all three: the queue absorbs spikes, workers process at their own pace, and messages are deleted only on success so failures remain individually replayable. This also keeps the pipeline serverless at the ingestion edge without imposing a compute timeout.

Exam trap

The trap here is reaching for a direct Lambda invocation from S3 notifications and forgetting the 15-minute invocation ceiling and the lack of durable per-upload failure records.

603
MCQhard

A multinational enterprise uses AWS Organizations with 300 accounts. The network team wants to centrally manage VPC IP address allocation and share subnets across multiple accounts to simplify connectivity. They also need to ensure that when a new account is created, it automatically receives a VPC with a predefined CIDR that does not overlap with existing VPCs. Which combination of AWS services should they use?

A.AWS Resource Access Manager (RAM) to share subnets and AWS Service Catalog to provision VPCs with predefined CIDRs.
B.AWS Transit Gateway to connect VPCs and AWS Direct Connect to manage IP allocation.
C.AWS Resource Access Manager (RAM) to share subnets and Amazon VPC IP Address Manager (IPAM) to allocate non-overlapping CIDRs automatically.
D.AWS CloudFormation StackSets to deploy VPCs with predefined CIDRs and VPC peering to connect them.
AnswerC

AWS RAM allows sharing subnets across accounts within an organization, centralizing subnet management. Amazon VPC IPAM provides automated CIDR allocation from a central pool, ensuring non-overlapping address ranges across VPCs and accounts. Together, they meet the requirements for centralized IP management and subnet sharing, with minimal manual effort and built-in scalability.

Why this answer

AWS RAM enables subnet sharing across accounts, centralizing subnet management. Amazon VPC IPAM automates CIDR allocation from a central pool, preventing overlaps and simplifying IP address management at scale. This combination directly addresses the need for centralized IP allocation and subnet sharing, and it scales across many accounts without manual tracking.

Exam trap

The trap here is assuming that AWS Transit Gateway or CloudFormation StackSets handle IP address management, when they do not; IPAM is the dedicated service for automated CIDR allocation.

604
MCQmedium

A company has 200 AWS accounts in AWS Organizations. The security team wants to centrally manage IAM roles that grant cross-account access to a central security tooling account. The roles must be created consistently in every account, and any change to the role trust policy must propagate automatically. Which approach requires the LEAST ongoing effort?

A.Create an IAM role in each account using a script that assumes a role in each account and calls CreateRole, and schedule the script to run weekly.
B.Use AWS Resource Access Manager to share an IAM role from the security tooling account to all other accounts.
C.Create a single IAM role in the management account and use AWS Single Sign-On permission sets to map users to that role in all accounts.
D.Use AWS CloudFormation StackSets with service-managed permissions to deploy a stack set containing the IAM role to all accounts in the organization, and update the stack set when the trust policy changes.
AnswerD

CloudFormation StackSets with service-managed permissions automatically deploy and update stacks across all accounts in an organization, including new accounts as they are added. Updating the stack set propagates the new trust policy to every account without manual intervention, providing consistent role creation and low ongoing effort.

Why this answer

CloudFormation StackSets with service-managed permissions is designed for organization-wide deployment of resources such as IAM roles. It automatically targets all accounts, including new ones, and a stack set update rolls the new trust policy to every account. This yields consistent role definitions and minimal ongoing operational effort compared with scripts or unsupported sharing mechanisms.

Exam trap

The trap here is assuming AWS Resource Access Manager can share IAM roles or that IAM Identity Center permission sets are the right tool for a service-to-service cross-account role, when StackSets is the managed deployment mechanism.

605
Multi-Selecteasy

A company is migrating a legacy application to AWS. The application requires a relational database with high availability and automated backups. Which TWO AWS services should the company consider? (Choose two.)

Select 2 answers
A.Amazon Redshift
B.Amazon RDS with Multi-AZ deployment
C.Amazon ElastiCache
D.Amazon DynamoDB
E.Amazon Aurora
AnswersB, E

Amazon RDS with Multi-AZ deployment provisions a synchronous standby replica in a second Availability Zone, with automatic failover, satisfying the high availability requirement. RDS also handles automated backups and point-in-time recovery natively, meeting the backup constraint without custom scripting or additional services.

Why this answer

Amazon RDS with Multi-AZ deployment (B) is correct because it provides a relational database engine with a synchronous standby replica in a different Availability Zone for automatic failover and high availability, plus automated backups with point-in-time recovery. Amazon Aurora (E) is also correct because it is a MySQL- and PostgreSQL-compatible relational database that stores data across multiple Availability Zones, supports automated backups and point-in-time recovery, and offers high availability through replicas and failover. Amazon Redshift (A) is a data warehousing service optimized for analytics, not a general-purpose relational database for a legacy application.

Amazon ElastiCache (C) is an in-memory caching service (Redis or Memcached), not a relational database. Amazon DynamoDB (D) is a NoSQL key-value and document database, so it does not meet the requirement for a relational database.

606
MCQeasy

A company is planning to migrate a Microsoft SQL Server database to Amazon RDS for SQL Server. They want to automate the migration process and minimize manual effort. Which AWS service should they use?

A.AWS CloudEndure Migration
B.AWS DataSync
C.AWS Database Migration Service (DMS)
D.AWS Schema Conversion Tool (SCT)
AnswerC

DMS performs continuous, automated data replication between heterogeneous or homogeneous engines, including SQL Server to RDS for SQL Server, using change data capture to keep source and target synchronised. This directly satisfies the requirement to automate the migration and minimise manual effort, rather than scripting backups or native restore.

Why this answer

AWS DMS can migrate SQL Server to RDS with minimal downtime. Option A is wrong because CloudEndure Migration is for server migration. Option B is wrong because DataSync is for file data.

Option D is wrong because Schema Conversion Tool is for schema conversion.

607
MCQeasy

Refer to the exhibit. An AWS Lambda function logs the error above. The function uses the AWS SDK to call an Amazon DynamoDB table. What is the MOST likely cause?

A.The Lambda function timed out while waiting for a response.
B.The DynamoDB table specified in the function does not exist.
C.The Lambda function does not have permission to access DynamoDB.
D.The DynamoDB table is throttling requests.
AnswerB

DynamoDB returns ResourceNotFoundException when the SDK targets a table name that does not exist in that region or account. The function's request therefore fails before any read or write occurs, matching the logged error more directly than permission or throttling causes.

Why this answer

The error shown in the exhibit is a ResourceNotFoundException from DynamoDB, which indicates that the table specified in the function's request does not exist. This is the most likely cause when the SDK call fails with that specific exception, as opposed to permission or throttling errors.

Exam trap

SAP-C02 often tests the ability to distinguish DynamoDB error types — candidates may pick permissions or throttling without noting that ResourceNotFoundException specifically means the table does not exist.

How to eliminate wrong answers

Option A is wrong because a Lambda timeout would produce a Task timed out error, not a DynamoDB ResourceNotFoundException. Option C is wrong because missing permissions would result in an AccessDeniedException or UnrecognizedClientException, not ResourceNotFoundException. Option D is wrong because throttling produces a ProvisionedThroughputExceededException or ThrottlingException, not a ResourceNotFoundException.

608
Multi-Selecteasy

A company is designing a multi-account strategy for development, testing, and production environments. They want to ensure that developers can deploy resources in development and testing accounts but not in production. Which TWO methods should the company use to achieve this? (Choose TWO.)

Select 2 answers
A.Enable AWS CloudTrail to monitor and alert on production changes.
B.Apply an SCP to the production OU that denies all actions to non-approved IAM roles.
C.Use resource tags to identify development and production resources and enforce policies via SCPs.
D.Create IAM roles in production with no permissions, and allow only a central CI/CD role to assume a privileged role.
E.Use AWS Config rules to detect unauthorized deployments in production.
AnswersB, D

An SCP attached to the production OU denies actions for every principal except approved roles, giving a hard permissions boundary that developers cannot bypass. This satisfies the constraint that developers deploy only in development and testing accounts.

Why this answer

Option B is correct because AWS Organizations Service Control Policies (SCPs) applied at the production OU level set the maximum permissions for all accounts within that OU, so a deny statement targeting non-approved IAM roles (for example, denying all actions unless the principal is an approved role) blocks developers from deploying in production while leaving development and testing OUs unaffected. Option D is correct because creating production IAM roles with no permissions and allowing only a central CI/CD role to assume a privileged role enforces least privilege and separation of duties, ensuring developers cannot directly deploy to production and only the controlled pipeline can. Option A is not correct because CloudTrail only records and can alert on API activity after the fact; it is detective, not preventive, so it does not stop developers from deploying to production.

Option C is not correct because resource tags combined with SCPs are not a reliable enforcement mechanism for this requirement; SCPs do not evaluate resource tags for most services, and tag-based authorization is better handled with IAM policies and conditions, not as the primary control here. Option E is not correct because AWS Config rules are detective controls that flag noncompliant resources after deployment, not preventive controls that block deployments.

Exam trap

The trap here is that candidates often confuse detective controls (CloudTrail, Config) with preventive controls (SCPs, IAM policies), leading them to select options that only alert or audit rather than block the action entirely.

609
Multi-Selectmedium

A company is using AWS Organizations to manage 50 accounts. They want to centralize billing and also allow a central team to manage IAM roles across all accounts. The central team needs to be able to assume a role in any member account to perform administrative tasks. They have already enabled all features in Organizations. Which two steps are required to allow the central team to assume roles in member accounts? (Choose two.)

Select 2 answers
A.Create an IAM role in each member account that trusts the central team's account, and attach the necessary permissions.
B.Use AWS Organizations to create a service control policy (SCP) that allows sts:AssumeRole.
C.Create an organization trail in AWS CloudTrail to log the role assumptions.
D.Enable AWS Single Sign-On (SSO) and configure permission sets for each member account.
E.Attach an IAM policy to the central team's users or roles that allows sts:AssumeRole for the member account roles.
AnswersA, E

To allow the central team to assume a role in a member account, you must create an IAM role in that member account. The role's trust policy must specify the central team's AWS account as a trusted principal. The central team's users or roles can then assume this role. This is a fundamental step for cross-account access.

Why this answer

To enable cross-account role assumption, you need two things: a role in the target account that trusts the source account, and an IAM policy in the source account that allows the principal to call sts:AssumeRole on that role. These two steps establish the trust and the permission. Other services like AWS SSO or CloudTrail are helpful but not required for this specific access pattern.

Exam trap

The trap here is thinking that SCPs can grant permissions or that enabling Organizations automatically allows cross-account access.

610
MCQeasy

A company runs a stateless web tier on Amazon EC2 instances behind an Application Load Balancer. Traffic is highly variable, with sharp spikes during flash sales. The company wants the web tier to scale out quickly during spikes and scale in when demand drops, while keeping costs low. Which configuration should a solutions architect recommend?

A.Use an Auto Scaling group with a target tracking scaling policy based on average CPU utilization, and enable the Application Load Balancer health checks.
B.Use an Auto Scaling group with a simple scaling policy and a cooldown period of 600 seconds.
C.Use a larger fixed fleet of EC2 instances sized to handle peak flash-sale traffic at all times, behind the Application Load Balancer.
D.Use an Auto Scaling group with a scheduled scaling policy that adds instances every day at a fixed hour.
AnswerA

Target tracking scales the fleet automatically to hold average CPU utilization near a target value, adding instances quickly during flash sales and removing them as demand falls. ALB health checks ensure traffic only reaches healthy instances, so the design responds to variable load while controlling cost, which matches the stated requirements.

Why this answer

Variable demand with sharp spikes and a desire for low cost calls for dynamic scaling that follows actual load. Target tracking on average CPU utilization adjusts capacity automatically as utilization moves, adding instances during flash sales and removing them afterward, while ALB health checks keep traffic on healthy targets.

Exam trap

The trap here is choosing scheduled or fixed-capacity scaling, which cannot respond to the unpredictable timing of flash-sale spikes.

611
Multi-Selecthard

A company is designing a data lake on S3 with sensitive data that must be encrypted at rest and audited. Which TWO services should be used? (Choose TWO.)

Select 2 answers
A.S3 Server-Side Encryption (SSE-S3)
B.Amazon Macie
C.AWS CloudTrail
D.AWS KMS
E.Amazon GuardDuty
AnswersC, D

AWS CloudTrail records S3 data-plane and management API activity, including GetObject and PutObject calls, delivering an audit trail of who accessed the sensitive objects and when. This satisfies the stem's auditing requirement, complementing encryption at rest rather than providing it.

Why this answer

AWS CloudTrail (C) is correct because it records S3 data events and management events, providing the audit trail required to track who accessed or modified the sensitive objects in the data lake. AWS KMS (D) is correct because it provides customer-managed keys and envelope encryption for S3 objects, satisfying the requirement that data be encrypted at rest with controlled, auditable key usage. SSE-S3 (A) does encrypt objects at rest, but it uses AWS-managed keys with no customer control over key rotation or access policies, so it does not meet the audited key-management requirement.

Amazon Macie (B) is a data discovery and classification service that identifies sensitive data but does not itself provide encryption or auditing. Amazon GuardDuty (E) is a threat-detection service that analyzes logs for malicious activity but does not encrypt data or deliver the required audit records.

Exam trap

The trap here is that candidates often focus solely on either encryption or auditing, failing to recognize that both are required: encryption (KMS) to meet the 'encrypted at rest' requirement and auditing (CloudTrail) to meet the 'audited' requirement.

612
Multi-Selectmedium

Which TWO actions would improve the security of an S3 bucket that contains sensitive data? (Choose two.)

Select 2 answers
A.Enable S3 Server Access Logging.
B.Enable default encryption (SSE-S3).
C.Enable S3 Block Public Access.
D.Enable S3 Versioning.
E.Configure S3 Lifecycle to expire objects.
AnswersB, C

SSE-S3 applies AES-256 encryption at rest automatically to every object written to the bucket, so sensitive data is protected even if callers omit encryption headers. This satisfies the question's security requirement without depending on client behaviour or key management overhead.

Why this answer

Option B is correct because enabling default encryption with SSE-S3 ensures that all objects written to the bucket are automatically encrypted at rest using AES-256, protecting sensitive data even if the underlying storage media is compromised. Option C is correct because S3 Block Public Access overrides any bucket or object ACLs and bucket policies that would otherwise grant public access, preventing accidental exposure of sensitive data. Option A is not correct because Server Access Logging only records requests for auditing purposes; it does not itself restrict access or encrypt data.

Option D is not correct because Versioning preserves multiple variants of objects, which aids recovery but does not improve confidentiality or access control. Option E is not correct because Lifecycle expiration deletes objects after a set period, which is a cost or retention control rather than a security hardening measure.

613
MCQeasy

A company wants to reduce costs for its Amazon RDS for MySQL database without affecting performance. The database is used by a read-intensive application. Which action should the company take?

A.Change the DB instance to a Multi-AZ deployment.
B.Upgrade to the latest generation instance type.
C.Implement a Read Replica and direct read traffic to it.
D.Purchase Reserved Instances for the database.
AnswerC

Read Replicas offload read queries from the primary MySQL instance via asynchronous replication, so the read-intensive application's traffic no longer competes with writes on the primary. This reduces load and cost without degrading performance, satisfying the no-impact constraint.

Why this answer

Implementing a Read Replica allows offloading read traffic from the primary DB instance. This reduces the load on the primary, potentially enabling the use of a smaller instance size or lowering provisioned IOPS, thereby reducing costs without affecting performance for the read-intensive application. Option A is incorrect because Multi-AZ deployment adds a standby instance and synchronous replication, increasing costs without direct performance benefit.

Option B is incorrect; upgrading to the latest generation instance type may improve performance but generally does not reduce costs. Option D is incorrect; purchasing Reserved Instances provides a discount on hourly rates but does not address the utilization or instance size, so it does not directly reduce costs based on workload.

614
MCQhard

A Solutions Architect is reviewing the IAM policy shown in the exhibit. The policy is attached to an IAM user. Which of the following is true about this policy?

A.The policy allows s3:GetObject on example-bucket only from the specified IP range.
B.The policy denies access if the source IP is not in the specified range.
C.The policy is invalid because the Resource is not specific enough.
D.The policy allows all S3 actions on all buckets.
AnswerA

The policy's Condition block uses aws:SourceIp with an IpAddress operator, so the s3:GetObject Allow statement applies only to requests originating from the listed CIDR range; requests from other addresses are not permitted by this statement.

Why this answer

The IAM policy uses a `Condition` block with `IpAddress` to restrict the `s3:GetObject` action on `example-bucket` to requests originating from the specified IP range. The `Effect` is `Allow`, so the policy grants the `s3:GetObject` permission only when the source IP matches the condition, effectively limiting access to that range.

Exam trap

The trap here is that candidates confuse an `Allow` with a condition for an implicit `Deny`—they incorrectly assume the policy explicitly denies access from outside the IP range, when in fact it simply does not grant permission, and an explicit deny would require a separate `Deny` statement.

How to eliminate wrong answers

Option B is wrong because the policy does not include a `Deny` effect; it uses an `Allow` effect with a condition, which does not explicitly deny access from other IPs—it simply does not grant permission for those IPs, and an explicit deny would be needed to block them. Option C is wrong because the `Resource` is specific enough: it targets `arn:aws:s3:::example-bucket/*`, which precisely identifies objects within the named bucket, and IAM policies require an ARN format that is valid and specific. Option D is wrong because the policy only allows `s3:GetObject` (not all S3 actions) and only on `example-bucket` (not all buckets), as clearly specified in the `Action` and `Resource` fields.

615
MCQmedium

A financial services company has an AWS Organizations structure with a management account, a dedicated Network account, and 40 workload accounts. The Network team wants to share a single AWS Transit Gateway with all workload accounts so that each account can attach its own VPCs. Workload accounts must not be able to modify the Transit Gateway route tables owned by the Network account. Which combination of actions should a solutions architect take to meet these requirements with the LEAST operational overhead?

A.Create a separate Transit Gateway in each workload account and peer them together using static routes in each account's route tables.
B.Create the Transit Gateway in the Network account and create a VPC peering connection from each workload VPC to a shared services VPC that hosts the Transit Gateway.
C.Create the Transit Gateway in the management account and grant each workload account an IAM role that allows creating attachments in the management account.
D.Create the Transit Gateway in the Network account and use AWS Resource Access Manager (AWS RAM) to share it with the organization. In each workload account, create a transit gateway attachment for the VPC and associate it with the shared transit gateway route table.
AnswerD

Sharing the Transit Gateway through AWS RAM with the organization allows every workload account to create attachments without duplicating the Transit Gateway. The Network account retains ownership of the route tables, so workload accounts can associate attachments but cannot modify the Network-owned route tables unless explicitly granted. This minimizes overhead and preserves the required boundaries.

Why this answer

AWS RAM is the native mechanism to share a Transit Gateway across an organization. The owner account keeps control of the Transit Gateway and its route tables, while participant accounts create VPC attachments. This satisfies both the sharing requirement and the restriction that workload accounts cannot alter Network-owned route tables, with minimal ongoing administration.

Exam trap

The trap here is assuming that sharing a Transit Gateway via AWS RAM also shares administrative control of its route tables, when in fact ownership and route table modification rights remain with the owner account.

616
MCQeasy

A company is designing a new application that will run on Amazon EKS. The development team wants to deploy containers in a way that minimizes operational overhead. Which compute option should the company choose?

A.AWS Fargate
B.Amazon EKS managed node groups
C.Amazon EC2 instances
D.Self-managed EC2 nodes
AnswerA

AWS Fargate runs pods on serverless compute, so the team never provisions or patches worker nodes. This directly satisfies the minimise-operational-overhead constraint, unlike managed node groups or self-managed nodes, which require capacity and lifecycle management.

Why this answer

AWS Fargate is the correct compute option because it is a serverless compute engine for containers that eliminates the need to provision, configure, or manage the underlying EC2 instances. By using Fargate with Amazon EKS, the development team can deploy containers without worrying about node scaling, patching, or cluster capacity, thereby minimizing operational overhead.

Exam trap

The trap here is that candidates often confuse 'managed node groups' with 'serverless' and assume they eliminate all operational overhead, but managed node groups still require you to manage EC2 instances, whereas Fargate truly removes the need to manage any underlying compute infrastructure.

How to eliminate wrong answers

Option B (Amazon EKS managed node groups) is wrong because, while it reduces some operational burden by automating node provisioning and updates, it still requires you to manage EC2 instances (e.g., instance types, scaling policies, and patching), which adds operational overhead compared to Fargate. Option C (Amazon EC2 instances) is wrong because it requires full manual management of the underlying virtual machines, including OS patching, security updates, and scaling, which contradicts the goal of minimizing operational overhead. Option D (Self-managed EC2 nodes) is wrong because it places the entire burden of node lifecycle management (provisioning, patching, scaling, and troubleshooting) on the development team, resulting in the highest operational overhead.

617
MCQmedium

A company runs a web application on EC2 instances behind an Application Load Balancer. Users report intermittent 503 errors. CloudWatch logs show the ALB's healthy host count occasionally drops to zero during traffic spikes. Which design change should a solutions architect implement to improve availability?

A.Enable EC2 instance refresh for the Auto Scaling group.
B.Increase the size of the Auto Scaling group and adjust scaling policies.
C.Purchase Reserved Instances for the existing EC2 fleet.
D.Replace the ALB with a larger Network Load Balancer.
AnswerB

The healthy host count hitting zero means capacity is exhausted before new instances register. Enlarging the Auto Scaling group and tuning its policies keeps sufficient healthy targets behind the ALB during spikes, preventing the 503s caused by having no available backend.

Why this answer

The ALB's healthy host count dropping to zero during traffic spikes indicates the Auto Scaling group cannot provision enough healthy instances fast enough to handle the load, causing the ALB to return 503 errors. Increasing the group size (raising the minimum/desired capacity) and tuning scaling policies (lower thresholds, shorter cooldowns, larger step adjustments) ensures more instances are available and scale-out happens sooner, improving availability.

Exam trap

The trap is picking a cost or deployment option (Reserved Instances, instance refresh) when the symptom — healthy host count dropping to zero — clearly points to a capacity and scaling responsiveness problem.

How to eliminate wrong answers

Option A is wrong because EC2 instance refresh replaces instances with the latest launch template configuration — it is a deployment/update mechanism, not a capacity or scaling solution, and would not prevent healthy host count from dropping during spikes. Option C is wrong because purchasing Reserved Instances is a billing optimization that reduces cost for steady-state usage; it does not add capacity or improve scaling responsiveness during traffic spikes. Option D is wrong because replacing the ALB with a Network Load Balancer does not address the root cause — the backend EC2 fleet is under-provisioned; NLB operates at layer 4 and would not fix insufficient healthy targets, and ALB is already appropriate for HTTP workloads.

618
MCQmedium

A company is migrating 50 on-premises VMware virtual machines to AWS. The migration must complete within a four-week maintenance window, and the company wants to minimize application changes. The VMs run a mix of Windows and Linux. Which AWS service should the company use to migrate these VMs to Amazon EC2?

A.AWS Database Migration Service (AWS DMS)
B.AWS Application Migration Service (AWS MGN)
C.AWS Server Migration Service (AWS SMS)
D.AWS DataSync
AnswerB

AWS Application Migration Service (AWS MGN) performs agent-based, block-level replication of source servers into a staging area in AWS, then launches test or cutover instances on EC2. It supports both Windows and Linux, requires no application changes, and is designed for large-scale lift-and-shift migrations within tight cutover windows, making it appropriate for this scenario.

Why this answer

AWS Application Migration Service (MGN) is purpose-built for lift-and-shift migrations of physical, virtual, or cloud servers to EC2. It supports Windows and Linux, uses block-level replication, and enables test launches and cutover with minimal downtime. The other services address data-only movement or legacy tooling, not full server migration.

Exam trap

The trap here is assuming that AWS Server Migration Service is still the recommended tool for VM migrations, when AWS now directs new migrations to AWS Application Migration Service.

619
Multi-Selectmedium

A company is designing a new serverless data-processing workflow on AWS. The workflow must orchestrate multiple AWS Lambda functions, wait for a human approval, and retry failed steps with exponential backoff. The solutions architect must choose AWS services that provide durable state and built-in error handling. (Choose two.)

Select 2 answers
A.Use AWS Step Functions to define the workflow as a state machine with Task states, Wait states, and Retry and Catch fields.
B.Use Amazon SQS FIFO queues between each Lambda function to ensure ordered processing and automatic retries.
C.Use AWS Lambda destinations to send failed invocations to an Amazon SQS queue and reprocess them with another Lambda function.
D.Use AWS Step Functions with a callback task token pattern, where the human approval invokes SendTaskSuccess or SendTaskFailure to resume the workflow.
E.Use Amazon EventBridge to route events between Lambda functions and configure dead-letter queues for failed events.
AnswersA, D

Step Functions provides durable state, built-in retries with exponential backoff, and supports human approval via a callback pattern using a task token. It is a fully managed orchestrator designed for exactly this use case, so it meets the requirements for orchestration, waiting, and error handling.

Why this answer

AWS Step Functions provides durable state, built-in retry with exponential backoff, and Wait states, while the callback task token pattern enables a human approval step by pausing the workflow until SendTaskSuccess or SendTaskFailure is called. Together they satisfy the orchestration, waiting, and error-handling requirements without custom state management.

Exam trap

The trap here is assuming that EventBridge or Lambda destinations can replace a stateful orchestrator for multi-step workflows with human approval.

620
MCQeasy

A company uses AWS Lambda functions to process events from Amazon S3. They notice that some Lambda invocations are failing with 'ResourceNotFoundException' errors when trying to write to an Amazon DynamoDB table. The Lambda execution role has a policy that grants dynamodb:PutItem on the table. What is the most likely cause of these errors?

A.The Lambda function is using the wrong AWS credentials.
B.The Lambda function is in a VPC without a DynamoDB VPC endpoint.
C.The DynamoDB table is in a different AWS account and the Lambda role does not have cross-account access.
D.The DynamoDB table name is misspelled in the Lambda code.
AnswerD

Correct. A misspelled table name in the Lambda code causes DynamoDB to return 'ResourceNotFoundException' because the specified table does not exist in the account and region. This is the most likely cause given the error message.

Why this answer

A 'ResourceNotFoundException' from DynamoDB means the API call reached DynamoDB successfully but the table name in the request did not resolve to an existing table in the caller's account/region. Because the execution role already grants dynamodb:PutItem, the failure is not authorization-related — it is a resource-resolution problem, and a misspelled table name in the Lambda code is the classic cause. The error is returned by the DynamoDB service itself, which confirms the request was authenticated and authorized.

Exam trap

SAP-C02 often tests the distinction between ResourceNotFoundException (resource name/region mismatch) and AccessDeniedException (IAM/permission failure) — candidates see 'Lambda' and 'DynamoDB' and jump to VPC endpoint or IAM issues instead of reading the error code literally.

How to eliminate wrong answers

Option A is wrong because using the wrong AWS credentials would produce an AccessDeniedException or UnrecognizedClientException, not ResourceNotFoundException — Lambda always uses the execution role unless the code explicitly assumes another role. Option B is wrong because a VPC without a DynamoDB gateway endpoint would cause a network timeout or connection error, not a ResourceNotFoundException, since the request would never reach the DynamoDB endpoint. Option C is wrong because cross-account access failures manifest as AccessDeniedException on the resource ARN, and the question states the role already has PutItem permission on the table, implying same-account access.

621
MCQmedium

A healthcare company is building a new patient records system on AWS. The system must store documents in Amazon S3 and provide access to authenticated patients and clinicians. The company requires that all data be encrypted at rest with keys that the company can rotate annually and immediately disable if compromised, and that access to the keys be logged for compliance. The company does not want to manage any hardware security modules. Which solution meets these requirements?

A.Use S3 server-side encryption with Amazon S3 managed keys (SSE-S3) and enable S3 server access logging.
B.Use S3 client-side encryption with a customer-provided key stored in AWS Secrets Manager, and enable AWS CloudTrail data events on the bucket.
C.Use S3 server-side encryption with AWS KMS AWS managed keys (aws/s3) and enable Amazon S3 Inventory to track encryption status.
D.Use S3 server-side encryption with AWS KMS customer managed keys (SSE-KMS) and enable AWS CloudTrail logging of KMS API calls.
AnswerD

SSE-KMS with customer managed keys lets the company define and rotate keys annually via KMS, and disabling the key immediately blocks decryption. CloudTrail logs every KMS API call, including Decrypt and DisableKey, providing the required audit trail. No HSMs need to be managed because KMS is a managed service, satisfying all stated constraints.

Why this answer

The requirements demand customer-controlled key lifecycle (annual rotation and immediate disablement) and detailed auditing of key usage, all without managing HSMs. SSE-KMS with customer managed keys provides configurable rotation and the ability to disable a key instantly, while CloudTrail captures all KMS API activity for compliance. The other options either lack key control, lack audit logging, or add unnecessary operational burden.

Exam trap

The trap here is assuming that any S3 encryption option provides customer-controlled key rotation and disablement, when only SSE-KMS with customer managed keys offers that level of control.

622
MCQhard

A company runs a microservices application on Amazon ECS with the Fargate launch type. The application uses an Application Load Balancer (ALB) to distribute traffic. During a recent incident, one service became unresponsive, but the ALB continued to send traffic to it because the health check only verified that the container was running. The company wants to improve the health check to detect application-level failures and automatically replace unhealthy tasks. Which solution should a solutions architect recommend?

A.Increase the ALB health check timeout and unhealthy threshold to give the application more time to recover.
B.Enable ECS container health checks by adding a HEALTHCHECK instruction to the Dockerfile, and rely on ECS to replace unhealthy tasks.
C.Configure the ALB health check to use a custom path that returns a 200 OK only when the application is fully functional, and set the health check interval and thresholds appropriately.
D.Use AWS App Mesh to implement outlier detection and eject unhealthy tasks from the load balancing pool.
AnswerC

A custom health check path allows the ALB to verify application-level health, not just that the container is running. By returning a 200 OK only when dependencies are available and the service is ready, the ALB can detect failures and stop routing traffic to unhealthy tasks. Adjusting intervals and thresholds ensures timely detection and replacement.

Why this answer

Configuring the ALB health check to use a custom path that reflects application health ensures that only fully functional tasks receive traffic. This is a straightforward and effective way to detect application-level failures without introducing additional components. It leverages existing ALB features and integrates with ECS task replacement.

Exam trap

The trap here is assuming that container-level health checks or increased timeouts can detect application-level failures, when they only check process liveness.

623
MCQhard

A company is deploying a containerized application on Amazon Elastic Kubernetes Service (Amazon EKS). The application requires persistent storage that must be accessible from multiple pods simultaneously across different Availability Zones. The storage must provide high throughput and low latency, and it must be shared read-write. Which storage solution should a solutions architect recommend?

A.Amazon FSx for Windows File Server with the ReadWriteMany access mode.
B.Amazon Elastic Block Store (Amazon EBS) volumes with the ReadWriteMany access mode.
C.Amazon S3 mounted as a file system using the AWS CSI driver with the ReadWriteMany access mode.
D.Amazon Elastic File System (Amazon EFS) with the ReadWriteMany access mode.
AnswerD

Amazon EFS is a fully managed, elastic NFS file system that supports the ReadWriteMany access mode, allowing multiple pods across different Availability Zones to access the same data simultaneously. It provides high throughput and low latency, and it integrates natively with Amazon EKS using the EFS CSI driver. This meets all the requirements.

Why this answer

Amazon EFS is a shared file system that supports the ReadWriteMany access mode and can be mounted across multiple Availability Zones. It is designed for Linux workloads and integrates with Amazon EKS via the EFS CSI driver, providing the required high throughput and low latency for shared read-write access.

Exam trap

The trap here is selecting Amazon EBS with ReadWriteMany, but EBS does not support multi-attach for ReadWriteMany and is limited to a single Availability Zone.

624
MCQmedium

A company has a management account in AWS Organizations and wants to share a central Amazon VPC subnet with multiple member accounts for a shared services VPC. Which AWS service should be used to share the subnet?

A.VPC peering connection
B.AWS Resource Access Manager
C.AWS PrivateLink
D.Service control policy
AnswerB

AWS Resource Access Manager (RAM) shares subnets directly between accounts via resource shares, letting member accounts launch resources into the central VPC subnet. This satisfies the cross-account subnet sharing requirement without VPC peering or Transit Gateway, which cannot share subnets themselves.

Why this answer

AWS Resource Access Manager (RAM) is the correct service because it enables you to share a central VPC subnet from a management account with multiple member accounts in AWS Organizations without requiring VPC peering or transit gateways. With RAM, you create a resource share that includes the subnet and specify the member accounts or organizational units (OUs) to grant them access, allowing those accounts to launch resources directly into the shared subnet while maintaining centralized network management.

Exam trap

The trap here is that candidates often confuse VPC peering (which connects entire VPCs) with subnet sharing (which allows direct resource placement into a shared subnet), leading them to select VPC peering instead of AWS Resource Access Manager.

How to eliminate wrong answers

Option A (VPC peering connection) is wrong because VPC peering connects entire VPCs at the network layer using private IP addresses, but it does not allow you to share a subnet; it only enables routing between VPCs, and each account still needs its own subnet. Option C (AWS PrivateLink) is wrong because PrivateLink provides private connectivity to services via interface VPC endpoints powered by AWS PrivateLink, not for sharing subnets or VPC resources across accounts. Option D (Service control policy) is wrong because SCPs are used to manage permissions and enforce guardrails across accounts in AWS Organizations, not for sharing infrastructure resources like subnets.

625
MCQeasy

A retail company is designing a new order-processing application on AWS. The application must survive the loss of an entire AWS Region with minimal data loss, and the recovery point objective is 1 minute. The primary database is Amazon Aurora MySQL. Which approach should the solutions architect choose to meet these requirements?

A.Enable Aurora MySQL global database with the primary in one Region and a secondary in a second Region
B.Take automated Aurora snapshots every minute and copy them to a second Region
C.Create an Aurora MySQL cross-Region read replica in a second Region and configure it to be promoted during a Regional failure
D.Use Aurora MySQL Multi-AZ with two reader instances in a second Region
AnswerA

Aurora global database replicates at the storage layer with typical lag under one second, which comfortably meets the one-minute RPO, and it supports fast promotion of a secondary Region, usually in under a minute. This is the purpose-built design for cross-Region disaster recovery with minimal data loss.

Why this answer

Aurora global database is designed for cross-Region disaster recovery, replicating changes at the storage layer with sub-second typical latency and enabling promotion of a secondary Region in about a minute. That meets the one-minute RPO while providing a fast, low-loss failover path for the order-processing application.

Exam trap

The trap here is treating a cross-Region read replica or Multi-AZ as equivalent to a global database, when only the global database provides storage-level replication fast enough for a one-minute RPO with rapid promotion.

626
MCQhard

Refer to the exhibit. A company is using AWS Migration Hub to track database migration tasks. The migration task for 'app-server-01' has failed. The progress update stream is 'DMS'. Which AWS service is most likely responsible for the migration failure?

A.AWS Application Migration Service (CloudEndure)
B.AWS Database Migration Service (DMS)
C.AWS Server Migration Service (SMS)
D.AWS CloudEndure Migration
AnswerB

The progress update stream is named DMS, and Migration Hub attributes each task to the service that reported it. The failed task was therefore submitted by AWS Database Migration Service, making DMS the service responsible for the failure.

Why this answer

The progress update stream is explicitly 'DMS', which stands for AWS Database Migration Service. In AWS Migration Hub, the progress update stream identifies the migration tool that is reporting the task status. Since the stream is DMS, the task was created and is being executed by AWS Database Migration Service, making it the service responsible for the failure.

Other services like Application Migration Service or Server Migration Service would report under different progress update streams (e.g., 'MGN' or 'SMS').

Exam trap

SAP-C02 often tests the ability to distinguish between migration services based on their progress update streams in AWS Migration Hub, and candidates may incorrectly assume that a failed task named 'app-server-01' implies a server migration service rather than a database migration service.

How to eliminate wrong answers

Option A is wrong because AWS Application Migration Service (CloudEndure) is used for server migration, not database migration, and would report under a different progress update stream (e.g., 'MGN'). Option C is wrong because AWS Server Migration Service is for migrating on-premises servers to AWS, not databases, and its progress update stream would be 'SMS'. Option D is wrong because AWS CloudEndure Migration is a server migration service (now part of AWS Application Migration Service) and is not associated with the 'DMS' progress update stream.

627
MCQhard

A company is building a microservices architecture on Amazon ECS. Services need to communicate with each other and with external SaaS applications. The architect must ensure that service discovery is dynamic and that traffic to external services is routed through a single egress point for security and monitoring. Which combination of services should the architect use?

A.AWS Cloud Map for service discovery and a NAT gateway for egress
B.Amazon Route 53 for service discovery and an Application Load Balancer for egress
C.AWS Cloud Map for service discovery and an Internet Gateway for egress
D.Amazon Route 53 for service discovery and VPC endpoints for egress
AnswerA

AWS Cloud Map registers ECS tasks and resolves them dynamically as they scale, removing hard-coded endpoints, while a NAT gateway gives all tasks a single managed egress IP for external SaaS traffic, satisfying both the dynamic discovery and centralised egress monitoring constraints.

Why this answer

AWS Cloud Map is the correct choice for dynamic service discovery in Amazon ECS because it allows services to register themselves with a logical service name and be discovered via DNS or API calls, which is ideal for microservices that scale and change frequently. A NAT gateway provides a single, controlled egress point for outbound traffic to external SaaS applications, enabling centralized security monitoring and consistent IP address management, unlike an Internet Gateway which would expose instances directly.

Exam trap

The trap here is confusing the roles of an Internet Gateway (which allows direct bidirectional internet access) with a NAT gateway (which provides controlled outbound-only egress), and assuming Route 53 can handle dynamic service discovery when it lacks the necessary registration and health-check integration for ephemeral containers.

How to eliminate wrong answers

Option B is wrong because Amazon Route 53 is designed for static DNS resolution and does not natively support dynamic service registration and health checking for ephemeral ECS tasks, making it unsuitable for dynamic service discovery in a microservices architecture; additionally, an Application Load Balancer is an ingress point for incoming traffic, not an egress point for outbound traffic to external services. Option C is wrong because while AWS Cloud Map is correct for service discovery, an Internet Gateway is used for bidirectional communication between a VPC and the internet, not as a single egress point—it would allow direct outbound access from all resources, bypassing centralized security and monitoring. Option D is wrong because Amazon Route 53 is not designed for dynamic service discovery in ECS, and VPC endpoints are used for private connectivity to AWS services, not for routing traffic to external SaaS applications over the internet.

628
Multi-Selectmedium

A company is designing a web application that must support millions of concurrent users. The application uses a RESTful API frontend and a relational database backend. Which TWO strategies should be implemented to improve scalability?

Select 2 answers
A.Use Amazon SQS to queue database write requests.
B.Use sticky sessions (session affinity) on the load balancer.
C.Implement read replicas for the database.
D.Implement a caching layer such as ElastiCache.
E.Use a single large EC2 instance for the database.
AnswersC, D

Read replicas offload read traffic from the primary database.

Why this answer

Read replicas (Option C) offload read traffic from the primary database instance, allowing the relational database to handle a higher volume of concurrent read queries without degrading write performance. This directly improves scalability for read-heavy workloads common in web applications.

Exam trap

The trap here is that candidates often confuse queuing (SQS) with database scalability, but SQS does not increase database throughput—it only buffers requests, which can lead to backpressure and eventual inconsistency if not carefully designed.

629
MCQhard

An IAM policy is attached to an IAM user. The policy allows the `s3:PutObject` action on the resource `arn:aws:s3:::my-bucket/uploads/*` with a condition that the request must come from IP address `10.0.1.5`. The user is testing from an IP address `10.0.1.5`. What is the effect of the policy?

A.Allow all actions on the bucket
B.Allow PutObject in uploads/ only
C.Allow GetObject because the second statement overrides
D.Deny all actions because of IP mismatch
AnswerB

The policy grants s3:PutObject on the uploads/* prefix, and the IP condition matches the tester's source address 10.0.1.5, so the request is allowed. Access remains scoped to that prefix only, not the whole bucket, because the resource ARN restricts it.

Why this answer

The attached IAM policy grants permission to perform PutObject on the 'uploads/' prefix, and the IP address condition matches the user's test IP (10.0.1.5). Therefore, the effect is to allow PutObject specifically on objects within the 'uploads/' folder.

Exam trap

The trap here is that candidates may misinterpret the IP condition as a Deny when it actually allows the action only if the condition is met, leading them to incorrectly select Option D.

How to eliminate wrong answers

Option A is wrong because the policy only allows s3:PutObject, not all actions on the bucket. Option C is wrong because there is no second statement; the policy has a single statement with an Allow effect, and GetObject is not included. Option D is wrong because the IP address matches the condition (10.0.1.5), so the Allow effect applies, not a Deny.

630
MCQmedium

A financial services company is building a new payment processing system on AWS. The system must durably retain transactional records for seven years to meet regulatory requirements, and the records must be encrypted at rest with a customer-provided key that the company can rotate on demand. The company wants the simplest operational model and does not want to manage any servers. Which solution should a solutions architect recommend?

A.Store records in Amazon S3 with a bucket policy that enforces SSE-KMS using a customer managed key, and use S3 Object Lock in compliance mode for the retention period.
B.Store records in Amazon DynamoDB with encryption at rest using an AWS owned key, and enable point-in-time recovery with a seven-year retention window.
C.Store records in Amazon S3 Glacier Deep Archive with server-side encryption using Amazon S3 managed keys (SSE-S3), and rely on S3 Versioning to prevent deletion for seven years.
D.Store records in Amazon EBS volumes attached to EC2 instances, and use AWS KMS customer managed keys to encrypt the volumes. Configure a lifecycle policy to snapshot the volumes every day for seven years.
AnswerA

S3 provides eleven nines of durability, and SSE-KMS with a customer managed key lets the company rotate the key on demand through AWS KMS. S3 Object Lock in compliance mode enforces the seven-year retention immutably, and there are no servers to manage. This directly satisfies every stated requirement with minimal operational overhead.

Why this answer

The requirement for a customer-provided key that can be rotated on demand points to SSE-KMS with a customer managed key, and the seven-year immutable retention requirement points to S3 Object Lock in compliance mode. S3 offers the highest durability with no server management, making it the simplest solution that fully meets the regulatory, encryption, and operational requirements.

Exam trap

The trap here is assuming that any encrypted, highly durable storage service automatically supports customer-controlled key rotation and multi-year immutable retention.

631
MCQeasy

A company is designing a multi-tier web application on AWS. The application requires high availability across multiple Availability Zones. Which AWS service should be used to distribute incoming traffic across multiple EC2 instances in different Availability Zones?

A.AWS Global Accelerator
B.Application Load Balancer
C.AWS Direct Connect
D.Amazon Route 53
AnswerB

An Application Load Balancer operates across multiple Availability Zones, distributing layer 7 requests to healthy EC2 targets in each zone and performing health checks to route around failures. This directly satisfies the multi-AZ high availability constraint for the multi-tier web application.

Why this answer

The Application Load Balancer (ALB) operates at Layer 7 of the OSI model and is designed to distribute incoming HTTP/HTTPS traffic across multiple targets, such as EC2 instances, in different Availability Zones. By registering instances in multiple AZs and enabling cross-zone load balancing, the ALB provides high availability and fault tolerance for the multi-tier web application.

Exam trap

The trap here is that candidates often confuse DNS-based routing (Route 53) with actual load balancing, but Route 53 only provides DNS resolution and does not actively distribute traffic across instances or perform health checks at the application layer.

How to eliminate wrong answers

Option A is wrong because AWS Global Accelerator improves performance by directing traffic to the optimal endpoint based on health and geography, but it does not distribute traffic across EC2 instances within a region; it uses anycast IPs and routes to Application Load Balancers or Network Load Balancers. Option C is wrong because AWS Direct Connect establishes a dedicated network connection from on-premises to AWS, not for distributing traffic across EC2 instances in multiple AZs. Option D is wrong because Amazon Route 53 is a DNS service that resolves domain names to IP addresses and can route traffic to multiple endpoints using policies like weighted or latency routing, but it does not perform load balancing at the application layer or distribute traffic across instances in real time.

632
MCQmedium

A company is modernizing its legacy PHP application to run on AWS. The application is currently deployed on a single on-premises server with a LAMP stack. The company wants to use containerization to improve scalability and deployment speed. Which AWS service should be used to run the containers with minimal operational overhead?

A.AWS Lambda
B.Amazon ECS with AWS Fargate
C.Amazon EKS with Amazon EC2
D.Amazon ECS with Amazon EC2 launch type
AnswerB

Fargate removes the need to provision or patch EC2 instances, since ECS schedules the PHP container tasks onto AWS-managed compute. This directly satisfies the minimal operational overhead constraint while delivering the containerisation-based scalability and faster deployments the LAMP migration requires.

Why this answer

Amazon ECS with AWS Fargate is correct because Fargate is a serverless compute engine for containers that eliminates the need to provision, configure, or manage EC2 instances. The company can run its containerized PHP application without patching hosts or scaling clusters, delivering minimal operational overhead while supporting containerization for scalability and faster deployments.

Exam trap

SAP-C02 often tests the distinction between 'containerized' and 'serverless functions' — candidates incorrectly pick Lambda for containerized web apps, ignoring Lambda's execution model and time limits.

How to eliminate wrong answers

Option A is wrong because AWS Lambda runs event-driven functions with a 15-minute execution limit and does not natively run long-lived containerized web applications like a LAMP stack. Option C is wrong because Amazon EKS with EC2 requires managing Kubernetes control plane integrations and worker nodes, adding operational overhead. Option D is wrong because ECS with the EC2 launch type requires the customer to manage, patch, and scale the underlying EC2 instances, which is not minimal operational overhead.

633
MCQmedium

A company is migrating an on-premises Java application to AWS. The application uses a shared file system for storing configuration files and user uploads. The company wants to minimize changes to the application and ensure that the file system is highly available and scalable. Which AWS service should be used?

A.Amazon Elastic File System (Amazon EFS).
B.Amazon S3 with the AWS SDK for Java to read and write files.
C.Amazon Elastic Block Store (Amazon EBS) with Multi-Attach enabled.
D.Amazon FSx for Windows File Server.
AnswerA

Amazon EFS is a fully managed, scalable, and highly available NFS file system that can be mounted on multiple EC2 instances across Availability Zones. It supports POSIX permissions and can be used without application changes. This makes it ideal for a shared file system for configuration files and user uploads, meeting the requirements for high availability and scalability.

Why this answer

Amazon EFS is a fully managed NFS file system that provides shared access across multiple EC2 instances and Availability Zones. It requires no application changes and automatically scales, meeting the requirements for high availability and scalability. Other options either do not provide a shared file system or require application modifications.

Exam trap

The trap here is assuming that Amazon S3 can be used as a file system without changes, but S3 requires SDK integration and is not a POSIX-compliant shared file system.

634
Multi-Selectmedium

Which TWO strategies can reduce the cost of storing infrequently accessed data in Amazon S3 while maintaining millisecond retrieval latency? (Choose two.)

Select 2 answers
A.Transition objects to S3 Glacier Flexible Retrieval after 90 days.
B.Use S3 Glacier Deep Archive for data older than 30 days.
C.Use S3 Standard-IA for data that is accessed less frequently but requires millisecond retrieval.
D.Use S3 Intelligent-Tiering to automatically move objects between access tiers.
E.Use S3 One Zone-IA for all data to reduce storage costs.
AnswersC, D

S3 Standard-IA delivers the same millisecond first-byte latency as S3 Standard while charging a lower storage rate, so infrequently accessed objects stay immediately retrievable. It satisfies the stem's dual constraint, unlike Glacier tiers, whose retrieval takes minutes to hours.

Why this answer

Option C is correct because S3 Standard-IA (Infrequent Access) is explicitly designed for data accessed less frequently but still needing rapid, millisecond retrieval, and it charges lower storage rates than S3 Standard in exchange for a retrieval fee. Option D is correct because S3 Intelligent-Tiering automatically moves objects between access tiers (Frequent Access, Infrequent Access, Archive Instant Access, and optional archive tiers) based on changing access patterns, lowering storage costs while keeping millisecond retrieval for the frequent and infrequent access tiers. Option A is not correct because S3 Glacier Flexible Retrieval does not provide millisecond retrieval—its expedited retrieval still takes 1–5 minutes, with standard retrievals taking hours.

Option B is not correct because S3 Glacier Deep Archive has retrieval times of 12 hours (standard) or 48 hours (bulk), far exceeding millisecond latency. Option E is not correct because S3 One Zone-IA reduces cost only by storing data in a single Availability Zone, which lowers durability/resilience rather than being a general strategy for infrequently accessed data, and it still may not be appropriate for all data.

Exam trap

The trap here is that candidates often confuse storage classes with retrieval latency, assuming that any 'Glacier' or 'Archive' class can provide millisecond retrieval, when in fact only S3 Standard, S3 Standard-IA, S3 One Zone-IA, and S3 Intelligent-Tiering (with frequent/infrequent tiers) offer that latency.

635
MCQhard

A company is migrating a legacy .NET Framework 4.8 application to AWS. The application uses Windows authentication integrated with Active Directory and relies on a shared file system for configuration files. The company wants to minimize operational overhead and use managed services. Which combination of AWS services should the company use to modernize the application?

A.AWS Managed Microsoft AD, Amazon EFS, and AWS Elastic Beanstalk for .NET on Windows
B.Amazon Cognito, Amazon RDS for SQL Server, and AWS Lambda
C.AWS Directory Service for Microsoft AD, Amazon S3, and AWS App Runner
D.AWS Managed Microsoft AD, Amazon FSx for Windows File Server, and AWS Elastic Beanstalk for .NET on Windows
AnswerD

AWS Managed Microsoft AD supplies the managed domain for Windows authentication, FSx for Windows File Server provides the shared SMB file system, and Elastic Beanstalk removes patching and scaling overhead, satisfying the minimise-operational-overhead and managed-services constraints.

Why this answer

AWS Managed Microsoft AD provides Windows authentication integrated with Active Directory, FSx for Windows File Server provides a managed shared file system that supports Windows-native SMB protocol and NTFS permissions, and AWS Elastic Beanstalk for .NET on Windows minimizes operational overhead for hosting a .NET Framework 4.8 application. Option A (EFS) does not natively support Windows authentication or SMB protocol, making it unsuitable. Option B (RDS for SQL Server) is unnecessary as the application does not require a database.

Option C (App Runner) does not support .NET Framework applications, and S3 cannot function as a Windows shared file system.

636
MCQmedium

A company is migrating a .NET application from Windows Server to Linux on EC2. The application uses a proprietary COM+ component that cannot be recompiled. Which migration path should they take?

A.Rehost the application on Linux EC2 using Wine
B.Rehost the application on Windows Server EC2 instances
C.Refactor the COM+ component to a REST API
D.Replatform the application to .NET Core and run on Linux
AnswerB

COM+ relies on Windows-specific component services unavailable on Linux, so recompilation is impossible. Rehosting to Windows Server EC2 preserves the proprietary binary unchanged, satisfying the constraint that the component cannot be recompiled while still moving to AWS.

Why this answer

The application uses a proprietary COM+ component that cannot be recompiled, and COM+ is a Windows-specific technology. Therefore, the only viable migration path is to rehost the application on Windows Server EC2 instances, where COM+ is natively supported. Migrating to Linux would require recompilation or emulation, which is not feasible for a proprietary component.

Exam trap

SAP-C02 often tests the misconception that Wine or .NET Core can replace COM+ functionality, when in reality COM+ is Windows-specific and cannot be easily ported.

How to eliminate wrong answers

Option A is wrong because Wine is a compatibility layer for running Windows applications on Linux, but it does not support COM+ components reliably, especially proprietary ones, and is not recommended for production. Option C is wrong because refactoring the COM+ component to a REST API would require recompilation or rewriting, which is not possible since it cannot be recompiled. Option D is wrong because replatforming to .NET Core and running on Linux would require the COM+ component to be ported, which is not feasible without recompilation.

637
MCQhard

A company is designing a new data lake on AWS. The data lake will store raw data in Amazon S3 and use Amazon Athena for ad-hoc queries. The company needs to ensure that only authorized users can query specific partitions based on their department. Which approach should the company use to implement fine-grained access control?

A.Use AWS Lake Formation to define data filters and grant permissions to departments at the partition level.
B.Use S3 bucket policies to restrict access to prefixes corresponding to each department.
C.Store each department's data in separate databases and use Amazon Redshift Spectrum to query.
D.Create separate IAM roles for each department and attach policies that grant access to specific partitions in Athena.
AnswerA

Lake Formation provides fine-grained access control, including partition-level filtering for Athena.

Why this answer

AWS Lake Formation provides fine-grained access control for data lakes, including table- and column-level permissions and data filters that can restrict access at the partition level. By defining data filters and granting permissions to departments, the company can ensure that each department can query only the partitions relevant to them, even when using Amazon Athena.

Exam trap

SAP-C02 often tests the difference between S3 bucket policies and Lake Formation for fine-grained access control, tempting candidates to choose S3 policies when partition-level or row-level filtering within Athena queries is required.

How to eliminate wrong answers

Option B is wrong because S3 bucket policies restrict access at the prefix level but do not provide the fine-grained, partition-level control needed for Athena queries; they also do not integrate with the Glue Data Catalog to enforce row- or column-level filtering. Option C is wrong because storing each department's data in separate databases and using Redshift Spectrum introduces unnecessary complexity and does not leverage Athena's native integration with Lake Formation; it also does not provide the required fine-grained access control. Option D is wrong because IAM roles with policies granting access to specific partitions in Athena are not sufficient for partition-level control; IAM policies operate at the API/action level and cannot enforce partition-level filtering within a table, whereas Lake Formation data filters can.

638
MCQmedium

A company runs a stateful web application on EC2 instances behind an Application Load Balancer. The application stores session data locally on the instances. The company wants to improve availability and scalability. What should a solutions architect recommend?

A.Move session state to Amazon ElastiCache and make the application stateless.
B.Use Auto Scaling to add more EC2 instances.
C.Enable sticky sessions on the ALB.
D.Use larger EC2 instances to handle more sessions.
AnswerA

ElastiCache (Redis or Memcached) externalises session state so any instance behind the ALB can serve any user request. This removes instance affinity, letting the architect scale horizontally and survive instance loss without dropping sessions, satisfying the availability and scalability goals.

Why this answer

Moving session state to Amazon ElastiCache makes the application stateless, allowing EC2 instances to be added or removed without session loss, which improves both availability and scalability. Option B (Auto Scaling alone) is wrong because without external session storage, scaling out will cause new instances to lack existing session data, and terminating instances will lose sessions. Option C (sticky sessions) is wrong because it only routes a user to the same instance, but if that instance fails, the session is lost.

Option D (larger instances) is wrong because it does not address scalability; it only increases capacity of individual instances, but does not allow for horizontal scaling or improve availability beyond a single instance.

639
MCQeasy

A startup is building a serverless photo-sharing application on AWS. Users upload photos via a web app, which stores them in Amazon S3. Each upload triggers an AWS Lambda function that creates a thumbnail and stores it in another S3 bucket. The application is expected to have unpredictable traffic patterns. The startup wants to minimize costs and operational overhead while ensuring the thumbnail generation completes reliably. Which solution should a Solutions Architect recommend?

A.Use Amazon ECS with Fargate to run a container that processes S3 events and generates thumbnails.
B.Upload to S3, send a message to an SQS queue, and have a Lambda function poll the queue to generate thumbnails.
C.Use an Auto Scaling group of EC2 instances to poll S3 for new uploads and generate thumbnails.
D.Configure S3 event notifications to invoke a Lambda function directly upon upload to generate thumbnails.
AnswerD

S3 event notifications invoking Lambda directly provide native, event-driven thumbnail generation with no polling or servers, scaling automatically with unpredictable upload volumes. This satisfies the reliability requirement while minimising cost and operational overhead, since AWS manages invocation and retries.

Why this answer

S3 event notifications can invoke a Lambda function directly on each object-created event, giving a fully serverless, event-driven pipeline with no polling, no servers to manage, and pay-per-invocation pricing that scales automatically with unpredictable traffic. This satisfies the reliability, cost, and operational-overhead requirements in one step.

Exam trap

SAP-C02 often tests whether candidates over-engineer solutions by inserting SQS or ECS when a direct S3-to-Lambda integration already meets the reliability and cost requirements — the trap is choosing the more complex option thinking it is more robust.

How to eliminate wrong answers

Option A is wrong because ECS with Fargate still requires managing task definitions, services, and cluster capacity, and it does not natively consume S3 events — you would need additional plumbing, adding operational overhead the startup wants to avoid. Option B is wrong because introducing an SQS queue adds an intermediary that is unnecessary when Lambda can be invoked directly by S3; it increases complexity and latency without a stated requirement for buffering or decoupling. Option C is wrong because polling S3 from EC2 instances is inefficient, requires managing an Auto Scaling group, and S3 does not provide a native polling API for new objects — you would have to list and diff, which is slow and error-prone.

640
MCQeasy

A company is deploying a serverless application using AWS Lambda, Amazon API Gateway, and Amazon DynamoDB. The company wants to secure the API by requiring authentication via a JSON Web Token (JWT). Which service should the company use to manage user authentication and issue JWTs?

A.Amazon Cognito User Pools
B.AWS Secrets Manager
C.AWS Identity and Access Management (IAM)
D.AWS Security Token Service (STS)
AnswerA

Amazon Cognito User Pools natively issues and signs JWTs, handling sign-up, sign-in and token refresh. API Gateway validates these tokens through a Cognito authoriser, so the JWT authentication requirement is met without custom token-signing code.

Why this answer

Amazon Cognito User Pools is the correct choice because it is a fully managed identity provider that handles user sign-up, sign-in, and issues JSON Web Tokens (JWTs) for authentication. It integrates directly with API Gateway Lambda authorizers to validate JWTs and control access to API endpoints without custom code.

Exam trap

The trap here is that candidates often confuse AWS STS (which issues temporary AWS credentials) with a service that issues JWTs for application users, leading them to select STS instead of Cognito User Pools.

How to eliminate wrong answers

Option B (AWS Secrets Manager) is wrong because it is designed to securely store and rotate secrets such as database credentials or API keys, not to manage user authentication or issue JWTs. Option C (AWS Identity and Access Management) is wrong because IAM is used for managing AWS resource permissions via policies and roles, not for authenticating end users or issuing JWTs; it cannot issue tokens for external user identities. Option D (AWS Security Token Service) is wrong because STS issues temporary AWS credentials (access keys, session tokens) for IAM roles or federated users, not JWTs for application-level authentication.

641
MCQmedium

A company is designing a new microservices-based application on AWS. They want to ensure that services can discover each other dynamically and that traffic can be load balanced across multiple Availability Zones. Which AWS service should they use for service discovery?

A.AWS Service Catalog
B.Amazon Route 53 private hosted zones
C.AWS Systems Manager Parameter Store
D.AWS Cloud Map
AnswerD

AWS Cloud Map provides dynamic service discovery by maintaining a registry that maps service names to endpoints, letting microservices locate each other without hard-coded addresses. It integrates with Route 53 health checks to return only healthy instances, and supports multi-AZ load balancing across registered endpoints, satisfying the stem's discovery and cross-AZ traffic requirements.

Why this answer

AWS Cloud Map is a cloud resource discovery service that allows microservices to dynamically register their endpoints (IP addresses, ports) and discover each other via DNS or API calls. It integrates with Amazon Route 53 auto-naming and health checks, enabling load-balanced traffic across multiple Availability Zones by returning healthy, available endpoints. This makes it the correct choice for dynamic service discovery in a microservices architecture.

Exam trap

The trap here is that candidates often confuse Route 53 private hosted zones (which provide static DNS resolution) with a dynamic service discovery solution, overlooking that Cloud Map is specifically designed for dynamic registration and health-aware endpoint resolution.

How to eliminate wrong answers

Option A is wrong because AWS Service Catalog is a governance tool for creating and managing a catalog of approved IT services (e.g., pre-configured CloudFormation templates), not a service discovery mechanism. Option B is wrong because Amazon Route 53 private hosted zones provide DNS resolution within a VPC but require manual registration of records and do not support dynamic registration or health-based filtering of service instances without additional automation. Option C is wrong because AWS Systems Manager Parameter Store is a secure hierarchical store for configuration data and secrets, not a service discovery service; it lacks native DNS or API-based endpoint resolution and health checking for dynamic service instances.

642
MCQmedium

A company is designing a new application that will run on Amazon ECS with Fargate. The application must be able to read and write files to a shared file system that is accessible from multiple tasks simultaneously. The file system must be durable and support NFS protocol. Which storage solution should be used?

A.Amazon EBS with Multi-Attach
B.Amazon EFS
C.Amazon S3
D.Amazon FSx for Lustre
AnswerB

Amazon EFS provides a durable, multi-AZ NFSv4 file system that many ECS Fargate tasks can mount concurrently, satisfying the shared read-write and NFS protocol constraints. Unlike instance store or EBS, which attach to a single host or task, EFS scales elastically and persists independently of task lifecycle.

Why this answer

Amazon EFS is the correct choice because it provides a fully managed, durable, NFS-based (Network File System) shared file system that can be mounted concurrently by multiple Amazon ECS tasks running on Fargate. EFS supports the NFSv4.1 and NFSv4.0 protocols, ensuring simultaneous read/write access across tasks, and its data is replicated across multiple Availability Zones for durability.

Exam trap

The trap here is that candidates often confuse Amazon EBS Multi-Attach with a shared file system, but EBS Multi-Attach is block-level storage limited to a single AZ and incompatible with Fargate, whereas EFS is a fully managed NFS file system designed for multi-task, multi-AZ access.

How to eliminate wrong answers

Option A (Amazon EBS with Multi-Attach) is wrong because EBS Multi-Attach only supports a maximum of 16 Nitro-based EC2 instances in a single Availability Zone, and it does not support Fargate tasks, which are serverless and cannot attach EBS volumes directly. Option C (Amazon S3) is wrong because S3 is an object storage service that does not support the NFS protocol; it uses RESTful APIs (HTTP/HTTPS) and is not a POSIX-compliant file system mountable via NFS. Option D (Amazon FSx for Lustre) is wrong because FSx for Lustre is designed for high-performance computing (HPC) workloads with a POSIX-compliant file system but does not natively support the NFS protocol; it uses the Lustre client protocol instead.

643
MCQmedium

A company is migrating a legacy three-tier application to AWS. The application tier is stateless and can be containerized, but the database tier is a commercial relational database that the vendor will only license on specific instance types. The company wants to reduce operational overhead for the database while keeping the same engine and minimizing schema changes. Which migration approach should a solutions architect recommend?

A.Rehost the database to Amazon EC2 on vendor-certified instance types and manage patching, backups, and high availability manually
B.Replatform the database to Amazon Aurora with aBabelfish endpoint to emulate the commercial engine's wire protocol
C.Refactor the database to a NoSQL model on Amazon DynamoDB to eliminate instance management entirely
D.Replatform the database to Amazon RDS for the same engine using a vendor-supported instance class, and use Multi-AZ for high availability
AnswerD

Amazon RDS supports several commercial engines on specific instance classes, and it provides automated backups, patching, and Multi-AZ failover without schema changes. Because the engine stays the same, the application's SQL and drivers remain compatible, satisfying the minimal-change requirement. This reduces operational overhead compared with self-managed EC2 while honoring vendor licensing constraints.

Why this answer

Replatforming to Amazon RDS for the same commercial engine keeps SQL and driver compatibility while offloading patching, backups, and failover to AWS. Multi-AZ provides synchronous standby replication for high availability, and instance classes can be chosen to satisfy vendor licensing terms. Self-managing on EC2 reduces managed benefits, while NoSQL or Babelfish approaches change the engine and risk schema or feature incompatibility.

Exam trap

The trap here is assuming that any managed AWS database service will accept the existing commercial engine unchanged, when only Amazon RDS for that specific engine preserves full compatibility.

644
MCQhard

A company operates a multi-account AWS Organization with AWS Control Tower. A new compliance rule requires that all Amazon S3 buckets in every account block public access and that any noncompliant bucket be remediated automatically within minutes. The security team wants a central view of compliance and minimal per-account configuration. Which solution BEST meets these requirements?

A.Enable S3 Block Public Access at the organization level using AWS Organizations, and deploy an AWS Config conformance pack with automatic remediation in each account.
B.Create an IAM policy in the management account that denies s3:PutBucketPublicAccessBlock and attach it to every account's administrator role.
C.Use AWS Control Tower guardrails to detect public buckets and send findings to AWS Security Hub for manual review by the security team.
D.Deploy an AWS Lambda function in each account that runs on a schedule to call PutBucketPublicAccessBlock for every bucket.
AnswerA

Organization-level S3 Block Public Access applies the setting to every current and future account in the organization, so new accounts inherit it automatically. An AWS Config conformance pack with automatic remediation detects and fixes any bucket that is later made public. This combination gives central enforcement plus automatic remediation with minimal per-account setup.

Why this answer

Organization-level S3 Block Public Access enforces the setting across all accounts and future accounts from a single place, satisfying the central control requirement. AWS Config conformance packs with automatic remediation detect noncompliant buckets and fix them quickly. Together they provide both preventive enforcement and automatic corrective action with little per-account effort.

Exam trap

The trap here is choosing a detection-only mechanism such as Control Tower guardrails or Security Hub, and overlooking that automatic remediation within minutes requires AWS Config remediation actions.

645
Multi-Selectmedium

A company is migrating a legacy application to AWS. The application requires a relational database with read replicas for reporting. The company wants to minimize operational overhead. Which TWO database services meet these requirements?

Select 2 answers
A.Amazon DynamoDB
B.Amazon Redshift
C.Amazon Aurora
D.Amazon RDS for MySQL
E.Amazon ElastiCache
AnswersC, D

Managed relational with up to 15 read replicas.

Why this answer

Amazon Aurora is a MySQL- and PostgreSQL-compatible relational database built for the cloud, combining the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. It supports up to 15 low-latency read replicas, which can be used for reporting workloads, and it automates time-consuming tasks such as hardware provisioning, database setup, patching, and backups, thereby minimizing operational overhead.

Exam trap

The trap here is that candidates may confuse Amazon RDS for MySQL (Option D) as the only correct relational database with read replicas, but Amazon Aurora is also correct because it is a fully managed relational database that natively supports read replicas with lower operational overhead than standard RDS.

646
MCQeasy

A company is designing a new web application that will run on Amazon EC2 instances behind an Application Load Balancer (ALB). The application must support sticky sessions. What should they do?

A.Configure an Amazon CloudFront distribution with session affinity.
B.Store session data in Amazon ElastiCache and use a cookie to reference it.
C.Enable sticky sessions on the ALB using duration-based cookies.
D.Use a Network Load Balancer (NLB) with cross-zone load balancing.
AnswerC

ALB duration-based cookies issue an AWSELB cookie that binds each client to the same target for the configured duration, satisfying the sticky-session requirement. This operates at the load balancer layer, requiring no application changes on the EC2 instances.

Why this answer

Application Load Balancers natively support sticky sessions (session affinity) using duration-based cookies. The ALB generates a cookie (AWSALB) that binds a user's session to a specific target instance for the duration of the cookie's lifetime, ensuring consistent user experience without external dependencies.

Exam trap

The trap here is that candidates often confuse stateless session management (e.g., ElastiCache) with ALB sticky sessions, or incorrectly assume that CloudFront or NLB can provide HTTP-level session affinity, when only ALB duration-based cookies directly satisfy the requirement for sticky sessions on the load balancer.

How to eliminate wrong answers

Option A is wrong because Amazon CloudFront session affinity (using the CloudFront-Viewer-Address header or cookies) is designed for content delivery and does not integrate with ALB sticky sessions; it would not ensure the ALB routes requests to the same EC2 instance. Option B is wrong because storing session data in ElastiCache with a cookie reference is a valid stateless architecture pattern, but the question explicitly requires sticky sessions on the ALB, not external session storage. Option D is wrong because Network Load Balancers do not support sticky sessions at Layer 4; they operate at the transport layer (TCP/UDP) and cannot inspect or manage HTTP cookies for session affinity.

647
MCQhard

A company is designing a new data lake on Amazon S3 using AWS Glue for ETL. The data is partitioned by date and sensitive columns must be masked for non-privileged users. The solution must minimize storage costs and allow different masking policies per user. Which approach should the architect recommend?

A.Use AWS Lake Formation to define column-level permissions and masking policies.
B.Create separate S3 buckets for each masking policy and copy data accordingly.
C.Use AWS Glue ETL jobs to mask data based on user role at query time.
D.Store masked data in separate prefixes in the same bucket and use S3 bucket policies.
AnswerA

AWS Lake Formation enforces column-level security and data filters directly on the AWS Glue Data Catalog, so non-privileged users querying through Athena or Redshift Spectrum receive masked values while privileged users see raw data. This satisfies the per-user masking requirement without duplicating masked copies in Amazon S3, keeping storage costs minimal.

Why this answer

AWS Lake Formation provides native column-level security and dynamic masking policies that can be applied per user or role without duplicating data. This approach minimizes storage costs because the data remains in a single location, and masking is applied at query time based on the requesting principal's permissions, satisfying the requirement for different masking policies per user.

Exam trap

The trap here is that candidates often confuse S3 bucket policies or Glue ETL jobs with the ability to perform dynamic, per-user column masking at query time, when in fact only Lake Formation provides this capability without data duplication or batch processing.

How to eliminate wrong answers

Option B is wrong because creating separate S3 buckets for each masking policy would multiply storage costs and require complex data synchronization, violating the cost minimization requirement. Option C is wrong because AWS Glue ETL jobs process data in batch, not at query time; masking at query time requires a service like Lake Formation or a query engine that supports dynamic data masking. Option D is wrong because S3 bucket policies cannot apply column-level masking or differentiate masking rules per user; they control access at the object or prefix level, not at the column or row level within a file.

648
Multi-Selectmedium

Which TWO actions will improve the security posture of an Amazon S3 bucket used to store sensitive data? (Choose two.)

Select 2 answers
A.Enable S3 Versioning on the bucket.
B.Enable S3 Block Public Access settings at the account or bucket level.
C.Enable default encryption using SSE-S3.
D.Enable S3 server access logging for the bucket.
E.Configure a bucket policy that denies access unless the request originates from a specific VPC or IP range.
AnswersB, E

S3 Block Public Access overrides bucket policies and ACLs that would otherwise grant public access, providing an account- or bucket-level guardrail. This directly prevents accidental exposure of sensitive objects, satisfying the requirement to improve the bucket's security posture.

Why this answer

Option B is correct because S3 Block Public Access provides a centralized set of controls (BlockPublicAcls, IgnorePublicAcls, BlockPublicPolicy, RestrictPublicBuckets) that override bucket policies and ACLs to prevent unintended public exposure of sensitive data, which is a foundational S3 security measure. Option E is correct because a bucket policy with a Deny effect conditioned on aws:SourceVpc or aws:SourceIp (using the IpAddress/NotIpAddress condition keys) enforces network-level least privilege, ensuring only requests from trusted networks can access the objects. Option A is not a security control — S3 Versioning only preserves object versions for recovery and does not restrict access or exposure.

Option C is helpful for data-at-rest protection but SSE-S3 is the baseline AWS-managed encryption already applied by default to all new objects, so it does not materially improve posture versus SSE-KMS or bucket keys. Option D is a detective/monitoring control that records access requests but does not prevent unauthorized access, so it does not directly improve the security posture.

Exam trap

The trap here is that candidates often confuse data protection features like Versioning and encryption with access control mechanisms, leading them to select options that protect data integrity or confidentiality at rest but do not prevent unauthorized access or exposure.

649
MCQhard

A company has multiple VPCs across different AWS accounts and wants to establish private connectivity between them. They also need to centrally manage network traffic for security inspection. Which architecture should they use?

A.Create VPC peering connections between all VPCs and use security groups for inspection
B.Configure a VPN between each VPC and a central virtual appliance
C.Deploy an AWS Transit Gateway with a central inspection VPC that hosts security appliances, and configure route tables to route traffic through the inspection VPC
D.Use AWS Direct Connect to connect all VPCs to a common router
AnswerC

Transit Gateway acts as a regional hub, giving transitive routing between many VPCs and accounts without full-mesh peering. Attaching a central inspection VPC and steering route tables through it forces east-west traffic across the security appliances, meeting the centralised inspection requirement.

Why this answer

AWS Transit Gateway acts as a central hub to interconnect multiple VPCs across accounts, and by deploying a dedicated inspection VPC with security appliances (e.g., firewalls, IDS/IPS), you can centrally route all inter-VPC traffic through those appliances for security inspection. This is achieved by configuring Transit Gateway route tables to propagate routes from the inspection VPC and using static routes to force traffic through the inspection VPC's attachments, enabling granular traffic steering without complex peering meshes.

Exam trap

The trap here is that candidates often confuse VPC peering (which is simple but unscalable and lacks central inspection) with Transit Gateway, or they incorrectly assume that Direct Connect or VPNs are designed for inter-VPC connectivity rather than hybrid connectivity to on-premises.

How to eliminate wrong answers

Option A is wrong because VPC peering creates a full-mesh topology that does not scale beyond a few VPCs, and security groups cannot inspect traffic between VPCs (they are stateful firewalls at the instance/ENI level, not a central inspection point). Option B is wrong because configuring a VPN between each VPC and a central virtual appliance introduces bandwidth limitations, latency from encryption overhead, and operational complexity for routing and failover; it also does not leverage native AWS networking constructs for high availability. Option D is wrong because AWS Direct Connect provides dedicated physical connectivity to on-premises networks, not private connectivity between VPCs; it would require additional routing and does not inherently provide centralized traffic inspection.

650
MCQhard

A gaming company is designing a new real-time multiplayer game backend on AWS. The game requires low-latency communication between players (< 50 ms) and the ability to handle up to 100,000 concurrent players. The backend must manage game state, player matchmaking, and chat. The company wants to use managed AWS services to reduce operational overhead. Which solution should a Solutions Architect recommend?

A.Use Amazon DynamoDB for game state, AWS Lambda for game logic, and API Gateway for client communication.
B.Use Amazon GameLift for session-based game server hosting, with its built-in matchmaking and fleet management.
C.Deploy game servers on EC2 instances behind a Network Load Balancer. Use ElastiCache for Redis for game state and SQS for chat messages.
D.Use Amazon ECS with Fargate to run game server containers, and use Application Auto Scaling to handle load.
AnswerB

Amazon GameLift satisfies the sub-50 ms latency and 100,000 concurrent player constraints through session-based server hosting, placing game servers close to players via multi-region fleets. Its built-in FlexMatch handles matchmaking, while automatic fleet scaling manages capacity, removing the operational burden of self-managed game state and chat infrastructure.

Why this answer

Amazon GameLift is a managed service specifically designed for session-based multiplayer game hosting. It provides low-latency game server hosting, built-in matchmaking (FlexMatch), and fleet management, which reduces operational overhead. It can scale to handle large numbers of concurrent players and integrates with other AWS services for game state and chat.

Exam trap

SAP-C02 often tests the choice between managed game-specific services and general compute services, where candidates may overlook GameLift's built-in matchmaking and low-latency optimizations, opting for custom solutions that increase operational overhead.

How to eliminate wrong answers

Option A is wrong because DynamoDB, Lambda, and API Gateway are not optimized for real-time, low-latency multiplayer game communication; Lambda has cold starts and API Gateway adds latency, making it unsuitable for <50 ms requirements. Option C is wrong because managing EC2 instances, NLB, ElastiCache, and SQS requires significant operational overhead and does not provide built-in matchmaking or game session management. Option D is wrong because ECS with Fargate and Application Auto Scaling is not tailored for game server hosting; it lacks built-in matchmaking and game session management, and scaling may not meet low-latency requirements.

651
Multi-Selecteasy

A company uses AWS CloudFormation to manage infrastructure. The operations team wants to ensure that all future stack updates follow best practices for change management. Which THREE actions should the team implement?

Select 3 answers
A.Enable drift detection to identify resources that have changed outside of CloudFormation.
B.Use IAM policies to restrict who can update stacks and require approval.
C.Use nested stacks to reuse templates across multiple environments.
D.Apply a stack policy to protect critical resources from accidental updates.
E.Require change sets to be created and reviewed before executing stack updates.
AnswersB, D, E

Restricting stack-update permissions through IAM policies enforces least privilege and separation of duties, ensuring only authorised personnel can initiate changes. Requiring approval before updates satisfies the change-management control the stem demands, preventing unvetted modifications from reaching production infrastructure.

Why this answer

Option B is correct because IAM policies are the mechanism to enforce least privilege and change control on CloudFormation operations: you can deny cloudformation:UpdateStack/ExecuteChangeSet to most principals and allow it only to an approved role, and combine that with manual approval gates so no unauthorized or unreviewed update can run. Option D is correct because a CloudFormation stack policy is a JSON document that explicitly denies Update:Modify/Update:Replace/Update:Delete actions on specified logical resources, protecting critical resources such as databases from accidental replacement or deletion during a stack update. Option E is correct because change sets let you preview exactly which resources will be added, modified, or deleted (and whether replacement occurs) before committing, so creating and reviewing a change set prior to ExecuteChangeSet is the standard best practice for controlled stack updates.

Option A is not part of the answer because drift detection only reports resources whose actual configuration diverges from the template; it detects and informs but does not enforce change management on future updates. Option C is not part of the answer because nested stacks address template reuse, modularity, and per-environment composition, not approval or protection of update operations.

652
MCQeasy

A company is using AWS CloudFormation to manage infrastructure. The operations team wants to be notified when a stack operation fails. Which approach is the MOST efficient?

A.Create a scheduled CloudWatch Events rule that calls the DescribeStacks API and sends an alert if status is FAILED
B.Configure an SNS topic as a notification option in the CloudFormation stack
C.Use a Lambda function that is invoked by CloudFormation via custom resource
D.Use Amazon EventBridge to monitor CloudFormation API calls and trigger a Lambda function
AnswerB

CloudFormation natively publishes stack event notifications to an SNS topic specified in the stack's notification configuration, covering failure events without custom polling or Lambda. This satisfies the requirement for efficient, event-driven alerting on stack operation failure.

Why this answer

CloudFormation natively supports SNS notifications via the NotificationARNs property on a stack, which emits events for stack operations such as CREATE_FAILED, UPDATE_FAILED, ROLLBACK_IN_PROGRESS, and DELETE_FAILED. Configuring an SNS topic directly on the stack is the least-effort, lowest-latency, and most operationally simple way to be alerted on failures because it requires no polling, no Lambda, and no custom code.

Exam trap

The trap here is that candidates over-engineer the solution by reaching for EventBridge or Lambda, when the exam expects recognition that CloudFormation has a built-in SNS notification feature that is the most efficient answer.

How to eliminate wrong answers

Option A is wrong because a scheduled CloudWatch Events rule that polls DescribeStacks introduces latency, consumes API rate limits, and requires custom logic to detect state transitions — it is neither efficient nor event-driven. Option C is wrong because Lambda-backed custom resources are invoked by CloudFormation during stack lifecycle events to create/update/delete resources; they are not a notification mechanism and cannot reliably report on the stack's own failure state. Option D is wrong because although EventBridge can capture CloudFormation API calls via CloudTrail, wiring it to a Lambda just to send an alert adds unnecessary moving parts when SNS notification is a first-class stack feature.

653
MCQeasy

A development team deploys a web application on Amazon EC2 instances behind an Application Load Balancer. The application experiences intermittent 503 errors. A Solutions Architect notices that the errors coincide with high CPU utilization on the EC2 instances. What is the MOST effective way to improve the application's availability?

A.Increase the idle timeout setting on the Application Load Balancer.
B.Decrease the health check interval on the Application Load Balancer.
C.Configure an Auto Scaling group for the EC2 instances with a scaling policy based on average CPU utilization.
D.Use larger EC2 instance types to handle the load.
AnswerC

An Auto Scaling group with a target-tracking or step policy on average CPU utilisation adds EC2 capacity before sustained high CPU causes 503s, then removes it afterwards. This directly addresses the CPU-driven availability constraint with less operational effort than manual intervention.

Why this answer

The 503 errors correlate with high CPU on the EC2 instances, meaning the instances are overwhelmed and the ALB is returning 503s when targets fail health checks or cannot respond. An Auto Scaling group with a CPU-based target tracking policy automatically adds instances when average CPU rises, distributing load and restoring healthy responses. This directly addresses the root cause rather than masking symptoms.

Exam trap

SAP-C02 often tests whether candidates choose reactive fixes (bigger instances, faster health checks) instead of the elastic, root-cause solution — auto scaling based on the actual bottleneck metric.

How to eliminate wrong answers

Option A is wrong because increasing the ALB idle timeout only affects how long idle connections are held; it does nothing for CPU saturation and can actually worsen resource consumption by holding connections longer. Option B is wrong because a shorter health check interval only detects failures faster — it does not prevent them and may even mark healthy-but-busy instances as unhealthy, causing more 503s. Option D is wrong because larger instance types provide a static capacity bump but do not adapt to variable load, and they are less cost-effective than horizontal scaling for availability.

654
MCQhard

A company has a bucket policy on an S3 bucket as shown in the exhibit. A cross-account role (CrossAccountRole) is used to access the bucket. The role has an IAM policy that allows s3:GetObject and s3:PutObject on the bucket. When users assume the role and try to upload objects without specifying encryption, the upload fails. What must the users do to successfully upload objects?

A.Remove the condition from the bucket policy.
B.Add an IAM policy that allows s3:PutObject to the role.
C.Include the x-amz-server-side-encryption header with value aws:kms in the upload request.
D.Grant the role permission to use the KMS key.
AnswerC

The bucket policy likely denies PutObject unless the request specifies SSE-KMS encryption. Adding the x-amz-server-side-encryption header with aws:kms satisfies that condition, so the assumed role's s3:PutObject permission is no longer blocked by the explicit deny.

Why this answer

The bucket policy includes a condition that requires the `x-amz-server-side-encryption` header to be set to `aws:kms` for `s3:PutObject` operations. When users assume the cross-account role and upload objects without specifying encryption, the request fails because it does not satisfy this condition. Including the `x-amz-server-side-encryption: aws:kms` header in the upload request explicitly meets the condition, allowing the upload to succeed.

Exam trap

The trap here is that candidates often assume the failure is due to missing KMS key permissions (Option D) or missing IAM permissions (Option B), but the actual cause is the bucket policy condition requiring the encryption header, which is a common S3 security pattern tested on the SAP-C02 exam.

How to eliminate wrong answers

Option A is wrong because removing the condition would weaken security by allowing unencrypted uploads, but the question asks what users must do to successfully upload, not how to change the policy. Option B is wrong because the role already has an IAM policy allowing `s3:PutObject`; the failure is due to the bucket policy condition, not a lack of IAM permissions. Option D is wrong because the bucket policy condition only requires the encryption header to be set to `aws:kms`; it does not require the role to have KMS key permissions, and the upload fails at the S3 condition check before any KMS authorization is evaluated.

655
Multi-Selecteasy

A company is using AWS CloudFormation to deploy infrastructure. They want to ensure that updates to a stack do not cause downtime for a critical web application. Which THREE strategies should they consider? (Choose THREE.)

Select 3 answers
A.Use the DeletionPolicy attribute to retain resources.
B.Apply a stack policy to protect critical resources.
C.Use a rolling update strategy with an appropriate batch size.
D.Use Change Sets to preview stack updates.
E.Use nested stacks to isolate components.
AnswersB, C, D

Stack policies prevent accidental updates to protected resources.

Why this answer

Option B is correct because a CloudFormation stack policy lets you explicitly deny Update:Replace or Update:Delete actions on critical resources (for example, the production load balancer or database), preventing an update from accidentally replacing or removing them and thereby avoiding downtime. Option C is correct because rolling updates with an appropriate batch size (such as MaxBatchSize/MinInstancesInService settings in an UpdatePolicy for Auto Scaling groups or ECS services) replace instances or tasks incrementally while keeping a minimum number in service, so the web application stays available throughout the deployment. Option D is correct because Change Sets let you preview exactly which resources will be added, modified, or replaced before executing the update, allowing you to detect disruptive replacements (for example, a resource that would be recreated) and adjust the template before any downtime-causing change is applied.

Option A is not appropriate here because DeletionPolicy only controls what happens to a resource when it is removed from the stack or the stack is deleted; it does not prevent or mitigate downtime during an update. Option E is not appropriate because nested stacks are a code-organization and reuse mechanism, not a strategy that by itself prevents update-related downtime.

Exam trap

The trap here is confusing DeletionPolicy with update protection — candidates see 'retain resources' and assume it prevents downtime, when it only affects deletion behavior, not in-place replacement during an update.

656
MCQmedium

A company uses AWS CloudFormation to deploy infrastructure. A stack update fails with a resource update failure. The team wants to investigate the specific error without rolling back the stack. What is the BEST approach?

A.Rerun the stack update with the --disable-rollback flag and then describe the stack events.
B.Delete the stack and review the CloudFormation logs.
C.Create a change set to preview the updates.
D.Use the AWS CLI describe-stack-resources command to see the status of each resource.
AnswerA

The --disable-rollback flag preserves the failed stack state so the team can inspect the exact resource error via describe-stack-events, rather than losing it to an automatic rollback. This satisfies the requirement to investigate the specific failure without reverting the stack.

Why this answer

Using the --disable-rollback flag on the update-stack command prevents CloudFormation from rolling back when a resource update fails, leaving the stack in UPDATE_FAILED state so you can inspect the exact error via describe-stack-events. This is the standard way to debug a failed update without losing the partially applied changes.

Exam trap

SAP-C02 often tests the difference between change sets (preview only) and disable-rollback (execute and preserve failure state) — candidates pick change sets thinking they show errors, but they do not execute the update.

How to eliminate wrong answers

Option B is wrong because deleting the stack destroys all resources and does not preserve the failed state for investigation — it is destructive and counterproductive. Option C is wrong because a change set only previews what will change; it does not execute the update or surface runtime resource errors. Option D is wrong because describe-stack-resources shows resource status (e.g., UPDATE_FAILED) but not the underlying error message, which is in the stack events.

657
MCQeasy

A company is migrating an application that uses a commercial database to Amazon RDS. The database size is 500 GB. Which migration approach minimizes downtime?

A.Use native database tools to export and import data.
B.Use AWS Snowball Edge to transfer the database files.
C.Use AWS Database Migration Service (AWS DMS) with ongoing replication (change data capture).
D.Copy database files to Amazon S3 and restore to RDS.
AnswerC

AWS DMS with change data capture performs a full load then continuously replicates ongoing changes from the source database to Amazon RDS, keeping the target synchronised until cutover. This minimises downtime because the application stays live on the source during migration, with only a brief final switchover.

Why this answer

AWS DMS with ongoing replication uses change data capture (CDC) to continuously apply changes from the source database to the target RDS instance after the initial full load. This keeps the target in sync until cutover, minimizing downtime to only the final switchover window. It is the standard AWS-recommended approach for minimal-downtime heterogeneous or homogeneous database migrations.

Exam trap

SAP-C02 often tests whether candidates confuse bulk transfer tools (Snowball) or simple dump/restore with true minimal-downtime migration — the key differentiator is continuous replication via CDC, which only AWS DMS provides among these options.

How to eliminate wrong answers

Option A is wrong because native export/import requires taking the source offline during the dump and load, producing significant downtime for a 500 GB database. Option B is wrong because Snowball Edge is for bulk offline data transfer and does not provide continuous replication or database-aware migration — it also requires shipping time. Option D is wrong because copying raw database files to S3 and restoring to RDS is not a supported or practical path for most commercial databases and offers no ongoing replication.

658
MCQmedium

A company has multiple AWS accounts and wants to share a centrally managed Amazon VPC subnet for workloads that require low latency. The VPC is in the networking account. Which solution meets these requirements with the LEAST operational overhead?

A.Create a separate VPC in each account and connect them with VPC peering.
B.Use AWS Resource Access Manager (RAM) to share the subnet with the workload accounts.
C.Set up an AWS Transit Gateway and attach the VPCs from each account.
D.Create VPC peering connections between the networking account and each workload account.
AnswerB

AWS RAM shares the existing subnet in place, so workload accounts launch resources directly into it without duplicating VPCs or peering. This satisfies the low-latency requirement because resources remain in one subnet, and it minimises operational overhead since no additional networking infrastructure is provisioned or maintained.

Why this answer

AWS Resource Access Manager (RAM) allows you to share a subnet from a central VPC in the networking account with other AWS accounts without creating separate VPCs or complex networking. This enables workload accounts to launch resources directly into the shared subnet, achieving low latency by keeping them in the same VPC and Availability Zone. RAM handles the cross-account sharing with minimal operational overhead, as it does not require additional network appliances or routing configuration.

Exam trap

The trap here is that candidates often overcomplicate the solution by choosing Transit Gateway or VPC peering, thinking they need to interconnect VPCs, when the simplest and most cost-effective approach is to share the existing subnet directly using AWS RAM.

How to eliminate wrong answers

Option A is wrong because creating separate VPCs in each account and connecting them with VPC peering introduces additional complexity, does not share a single subnet, and VPC peering is not transitive, requiring full mesh connectivity for multiple accounts. Option C is wrong because AWS Transit Gateway adds operational overhead for managing attachments, route tables, and potentially higher costs, while the requirement is simply to share a subnet, not to interconnect multiple VPCs. Option D is wrong because VPC peering connections between the networking account and each workload account would require managing multiple peering connections and routing updates, and does not allow direct sharing of a subnet; resources would still be in separate VPCs, potentially increasing latency.

659
Drag & Dropmedium

Drag and drop the steps to configure an Application Load Balancer with HTTPS listeners in the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

First get the certificate, then create the target group, then the ALB with HTTPS, register targets, and update DNS.

660
MCQmedium

A company is designing a new application that requires a relational database with high read capacity. The application is read-heavy and requires low latency. Which database configuration should be used?

A.Amazon RDS with read replicas
B.Amazon DynamoDB with DAX
C.Amazon RDS with Multi-AZ deployment
D.Amazon ElastiCache for Redis
AnswerA

Read replicas offload read queries from the primary instance via asynchronous replication, directly satisfying the read-heavy, low-latency requirement. They scale read capacity horizontally across multiple replicas, unlike a single Multi-AZ standby which serves no read traffic.

Why this answer

Amazon RDS with read replicas is the correct choice because the application is read-heavy and requires low latency. Read replicas offload read traffic from the primary database instance, scaling read capacity and reducing latency for read operations by distributing the load across multiple copies of the data.

Exam trap

The trap here is that candidates often confuse Multi-AZ deployments with read replicas, assuming Multi-AZ also improves read performance, but Multi-AZ only provides failover redundancy and does not offload read traffic.

How to eliminate wrong answers

Option B is wrong because Amazon DynamoDB with DAX is a NoSQL key-value and document database, not a relational database, and the question explicitly requires a relational database. Option C is wrong because Amazon RDS with Multi-AZ deployment provides high availability and failover support, but does not increase read capacity or reduce read latency; it only maintains a standby replica for disaster recovery. Option D is wrong because Amazon ElastiCache for Redis is an in-memory data store, not a relational database, and while it can cache data to improve read performance, it does not serve as the primary relational database itself.

661
MCQmedium

A company is migrating a critical application to AWS. The application requires consistent performance and low latency. The company has selected an instance type that meets the performance requirements. However, during testing, the application experiences variable performance due to CPU stealing from other instances on the same physical host. What should the company do to mitigate this issue?

A.Use Amazon EC2 Dedicated Hosts for the instances
B.Launch instances in a cluster placement group
C.Use T2 or T3 instances with the unlimited credit option
D.Switch to a compute-optimized instance type such as C5
AnswerA

Amazon EC2 Dedicated Hosts give the instance exclusive use of a physical server, so no other tenants share the host and CPU stealing cannot occur. This satisfies the requirement for consistent performance and low latency.

Why this answer

Dedicated Hosts provide dedicated physical servers, eliminating CPU stealing. Option B (placement group) helps with network performance, not CPU isolation. Option C (T2/T3 unlimited) is for burstable instances, not dedicated.

Option D (C5 instance) does not prevent CPU stealing.

662
MCQhard

A company is designing a new data lake on AWS. The data lake will store petabytes of data from various sources, including IoT devices, application logs, and streaming data. The data must be stored cost-effectively, and access patterns vary from frequently accessed recent data to rarely accessed historical data. The company also needs to run SQL queries on the data. Which solution should the architect recommend?

A.Store data in S3 with lifecycle policies to transition between storage classes, and use Amazon Athena for queries
B.Store data in S3 with lifecycle policies to transition to Glacier, and use S3 Select for queries
C.Store data in Amazon EMR on EC2 and query with Hive
D.Store data in Amazon Redshift and query with Redshift Spectrum
AnswerA

S3 lifecycle policies transition objects between storage classes, matching the varying access patterns cost-effectively at petabyte scale, while Athena runs SQL directly against S3 without loading data. This satisfies both the cost and query requirements in one serverless design.

Why this answer

Amazon S3 lifecycle policies allow automatic transition of objects between storage classes (e.g., S3 Standard to S3 Standard-IA to S3 Glacier Deep Archive) based on age, optimizing cost for varying access patterns. Amazon Athena enables serverless SQL querying directly on data stored in S3, making it ideal for a petabyte-scale data lake without managing infrastructure.

Exam trap

The trap here is that candidates may confuse S3 Select with Athena, not realizing S3 Select is limited to single-object filtering and cannot perform joins or aggregations across multiple files, which is required for SQL queries on a data lake.

How to eliminate wrong answers

Option B is wrong because S3 Select is designed for simple filtering of single objects (e.g., retrieving a subset of rows/columns from a CSV file), not for running complex SQL queries across multiple objects or petabytes of data. Option C is wrong because storing data in Amazon EMR on EC2 requires provisioning and managing clusters, which is less cost-effective and more operationally complex than a serverless approach for a data lake. Option D is wrong because Amazon Redshift is a data warehouse optimized for structured, aggregated data, not a cost-effective storage layer for raw, diverse data at petabyte scale; Redshift Spectrum can query S3 but still requires a Redshift cluster, incurring additional costs.

663
Multi-Selecteasy

Which TWO AWS services can be used to decouple components in a new microservices architecture? (Choose two.)

Select 2 answers
A.Amazon Simple Notification Service (SNS)
B.AWS Direct Connect
C.Amazon Route 53
D.Amazon Simple Queue Service (SQS)
E.Amazon ElastiCache
AnswersA, D

Amazon SNS decouples components through the publish/subscribe pattern: producers publish messages to a topic, which fans out to multiple subscribed endpoints asynchronously. This satisfies the stem's decoupling requirement by removing direct service-to-service dependencies, letting microservices communicate without knowing each other's identities or availability.

Why this answer

Amazon SNS (option A) is correct because it is a fully managed pub/sub messaging service that decouples microservices by allowing a publisher to send messages to multiple subscribers via topics, so producers and consumers do not need to know about each other. Amazon SQS (option D) is correct because it is a fully managed message queueing service that decouples components by storing messages in queues, enabling asynchronous communication and absorbing traffic spikes between microservices. AWS Direct Connect (option B) is not correct because it is a dedicated network connection service for hybrid connectivity, not an application decoupling mechanism.

Amazon Route 53 (option C) is not correct because it is a DNS and traffic-routing service, not a messaging or queueing service. Amazon ElastiCache (option E) is not correct because it is an in-memory caching service, which improves performance but does not decouple components through asynchronous messaging.

Exam trap

The trap here is that candidates often confuse caching services (ElastiCache) or network services (Direct Connect, Route 53) with messaging services, failing to recognize that decoupling requires asynchronous communication via queues or pub/sub topics.

664
MCQmedium

A company is designing a new serverless application that processes messages from an Amazon SQS queue. The messages contain sensitive data that must be encrypted at rest. The company wants to use a customer-managed AWS KMS key for encryption and ensure that only the application's Lambda function can decrypt the messages. Which approach should be used?

A.Enable server-side encryption (SSE) for the SQS queue using the default AWS managed key (aws/sqs). The Lambda function's execution role does not need any KMS permissions.
B.Use Amazon SQS FIFO queue with content-based deduplication and enable SSE with an AWS managed key. The Lambda function can decrypt messages without additional permissions.
C.Store the messages in an Amazon S3 bucket encrypted with a customer-managed KMS key, and have the Lambda function read from S3. Use SQS only for notification.
D.Enable SSE for the SQS queue using a customer-managed KMS key. Grant the Lambda function's execution role kms:Decrypt permission on that key, and ensure the key policy allows the role to use it.
AnswerD

Enabling SSE with a customer-managed KMS key allows the company to control the key policy and restrict decryption to specific principals. Granting the Lambda execution role kms:Decrypt permission and allowing it in the key policy ensures only that role can decrypt messages. This meets the requirements for encryption at rest with a customer-managed key and restricted access.

Why this answer

Using server-side encryption with a customer-managed KMS key on the SQS queue allows control over the key policy. The Lambda execution role must be granted kms:Decrypt permission, and the key policy must allow that role. This ensures only the Lambda function can decrypt messages, meeting the security requirements.

Exam trap

The trap here is thinking that enabling SSE with the default AWS managed key is sufficient, but it does not allow customer control over key policies or restrict access to specific roles.

665
MCQmedium

A company runs a containerized application on Amazon ECS with the Fargate launch type. The application writes logs to stdout, which are captured by the awslogs driver and sent to Amazon CloudWatch Logs. The operations team notices that during peak hours, log ingestion costs have increased significantly, and they want to reduce costs without losing critical error logs. Which solution should a solutions architect recommend?

A.Configure the awslogs driver to use a different log group with a shorter retention period.
B.Reduce the ECS task count during peak hours to lower the volume of logs generated.
C.Enable CloudWatch Logs subscription filters to export logs to Amazon S3 and delete them from CloudWatch Logs.
D.Use the FireLens log router to filter and route only error-level logs to CloudWatch Logs.
AnswerD

FireLens is a log router for ECS that uses Fluent Bit or Fluentd to process and route logs. By configuring filters, you can drop non-error logs before they reach CloudWatch Logs, reducing ingestion volume and cost. Critical error logs are still captured, meeting the requirement. This approach is native to ECS and requires only task definition changes.

Why this answer

The awslogs driver sends all logs to CloudWatch Logs, incurring ingestion costs. FireLens allows you to filter logs at the source, so only error-level logs are forwarded to CloudWatch Logs. This reduces ingestion volume and cost while preserving critical error logs.

It is a native ECS feature that requires only task definition changes, making it the most efficient solution.

Exam trap

The trap here is thinking that changing retention or exporting logs will reduce ingestion costs, when the real cost driver is the volume of logs ingested into CloudWatch Logs.

666
Multi-Selectmedium

A company is migrating a legacy application to AWS. The application requires a relational database. The company wants to minimize operational overhead. Which TWO options should the company consider? (Choose two.)

Select 2 answers
A.AWS Database Migration Service
B.Amazon Aurora
C.Amazon S3
D.Amazon RDS
E.Amazon EC2 with self-managed database
AnswersB, D

Amazon Aurora is a fully managed relational engine, so it satisfies the requirement to minimise operational overhead: AWS handles provisioning, patching, backups and replication. Unlike self-managed engines on Amazon EC2, Aurora removes database administration, and its MySQL and PostgreSQL compatibility suits a legacy relational workload being migrated.

Why this answer

Amazon Aurora (B) is correct because it is a fully managed relational database engine compatible with MySQL and PostgreSQL, and AWS handles provisioning, patching, backups, replication, and scaling, which directly minimizes operational overhead for a relational workload. Amazon RDS (D) is also correct because it is a managed relational database service that automates routine administration tasks such as backups, software patching, and Multi-AZ failover, making it a low-overhead fit for a legacy relational application. AWS Database Migration Service (A) is a migration tool rather than a target database, so it does not itself satisfy the application's relational database requirement.

Amazon S3 (C) is object storage, not a relational database, so it cannot run the legacy application's relational workload. Amazon EC2 with a self-managed database (E) requires the company to handle installation, patching, backups, and scaling, which increases rather than minimizes operational overhead.

667
MCQmedium

A company is building a new microservices-based application on AWS using Amazon ECS with Fargate. The application has a frontend service, an order service, and a payment service. Services communicate synchronously via REST APIs. The company expects variable traffic and wants to ensure that failures in one service do not cascade to others. Which solution should a Solutions Architect recommend?

A.Use Amazon API Gateway in front of each service to throttle requests and protect against traffic spikes.
B.Implement retry logic with exponential backoff, circuit breakers, and timeouts in each service's client code.
C.Convert all inter-service communication to asynchronous messaging using Amazon SQS or SNS.
D.Deploy multiple instances of each service across multiple Availability Zones and use an Application Load Balancer.
AnswerB

Retries with exponential backoff, circuit breakers and timeouts directly contain synchronous REST failures, preventing a slow or failing payment service from exhausting order service threads and cascading. This satisfies the stem's isolation requirement, unlike infrastructure scaling alone, because resilience must live in the calling client code where the synchronous dependency is invoked.

Why this answer

For synchronous REST-based microservices on ECS Fargate with variable traffic and a requirement to prevent cascading failures, implementing retry logic with exponential backoff, circuit breakers, and timeouts in each service's client code is the correct approach. These patterns handle transient failures gracefully, prevent a failing service from overwhelming upstream callers, and ensure that a slow or unavailable dependency does not cause thread exhaustion or cascading timeouts.

Exam trap

SAP-C02 often tests the difference between high availability (multi-AZ, load balancing) and resilience patterns (circuit breakers, timeouts, retries) — candidates pick multi-AZ deployment thinking it prevents cascading failures, when it only addresses availability.

How to eliminate wrong answers

Option A is wrong because API Gateway throttling protects against traffic spikes but does not address cascading failures from service-to-service synchronous calls; it also adds a layer that may not be suitable for internal service communication. Option C is wrong because converting all communication to asynchronous messaging changes the architecture significantly and is not required to prevent cascading failures; the question states services communicate synchronously, and the goal is resilience, not re-architecture. Option D is wrong because deploying multiple instances across AZs with an ALB improves availability but does not prevent cascading failures — if a service is slow or failing, callers can still exhaust resources waiting on it.

668
MCQmedium

A company wants to migrate a legacy monolithic application to AWS with minimal changes. The application currently runs on a single on-premises server with a Microsoft SQL Server database. The company wants to use AWS managed services to reduce operational overhead. Which combination of services should the company use to meet these requirements?

A.AWS Application Migration Service (MGN) to Amazon EC2, and AWS DMS to Amazon DynamoDB
B.AWS Application Migration Service (MGN) to Amazon EC2, and AWS DMS to Amazon RDS for SQL Server
C.AWS Server Migration Service (SMS) to Amazon EC2, and AWS DMS to Amazon RDS for SQL Server
D.AWS CloudFormation to provision EC2 instances, and AWS DMS to Amazon RDS for SQL Server
AnswerB

MGN replicates the legacy server to Amazon EC2 with minimal application change, while AWS DMS migrates the SQL Server database to Amazon RDS for SQL Server, a managed service that reduces operational overhead and preserves engine compatibility.

Why this answer

AWS Application Migration Service (MGN) enables lift-and-shift migration of the on-premises server to Amazon EC2 with minimal changes, while AWS DMS can migrate the Microsoft SQL Server database to Amazon RDS for SQL Server, a fully managed service that reduces operational overhead. This combination meets the requirement of minimal application changes and leverages AWS managed services for the database.

Exam trap

The trap here is that candidates might choose Option A thinking DynamoDB is a managed database service, but they overlook the requirement for minimal changes, which is broken by switching from a relational to a NoSQL database, or they might pick Option C not realizing SMS is deprecated and lacks the continuous replication capabilities of MGN.

How to eliminate wrong answers

Option A is wrong because AWS DMS cannot migrate a SQL Server database to Amazon DynamoDB (a NoSQL database) without significant application changes to adapt to a different data model and query language, violating the 'minimal changes' requirement. Option C is wrong because AWS Server Migration Service (SMS) is deprecated and replaced by AWS Application Migration Service (MGN); using SMS would not be a current best practice and may lack support. Option D is wrong because AWS CloudFormation is an infrastructure-as-code provisioning tool, not a migration service; it does not directly migrate the application or database, and using it alone would not reduce operational overhead for the migration itself.

669
MCQeasy

A company is designing a network architecture for a multi-account AWS environment. They need to establish a central inspection VPC through which all traffic between VPCs in different accounts must pass. Which AWS service should be used to route traffic between VPCs through the inspection VPC?

A.AWS Direct Connect gateway
B.VPC peering with full mesh connectivity
C.Elastic Load Balancer
D.AWS Transit Gateway
AnswerD

AWS Transit Gateway acts as a regional hub, attaching VPCs across accounts and routing inter-VPC traffic through a central inspection VPC via route tables. This satisfies the requirement that all cross-account traffic pass through the inspection VPC.

Why this answer

AWS Transit Gateway (D) is the correct service because it acts as a central hub that can route traffic between multiple VPCs across different accounts, and it supports route tables that can force all inter-VPC traffic through a dedicated inspection VPC (e.g., using a blackhole route or a network appliance). This enables transitive routing without requiring full mesh peering, and it integrates with AWS Resource Access Manager (RAM) for cross-account sharing.

Exam trap

The trap here is that candidates often confuse VPC peering with transitive routing, assuming that a full mesh of peering connections can achieve the same centralized inspection as Transit Gateway, but VPC peering explicitly does not support transitive routing (per AWS documentation), making it impossible to force all traffic through a single inspection VPC without additional, unsupported workarounds.

How to eliminate wrong answers

Option A is wrong because AWS Direct Connect gateway is used to connect on-premises networks to AWS via Direct Connect, not for routing traffic between VPCs in different accounts. Option B is wrong because VPC peering with full mesh connectivity does not support transitive routing—each peering connection is a one-to-one relationship, so traffic cannot be forced through a central inspection VPC without complex, non-scalable configurations. Option C is wrong because Elastic Load Balancer is a traffic distribution service for applications, not a routing service for inter-VPC traffic; it cannot route packets between VPCs or enforce inspection paths.

670
MCQeasy

A company is designing a new microservices architecture on AWS. Each microservice must store its own data and communicate with other services via RESTful APIs. The company wants to minimize operational overhead. Which data store should the company use for each microservice?

A.Amazon ElastiCache for Redis
B.Amazon Redshift
C.Amazon RDS for PostgreSQL
D.Amazon DynamoDB
AnswerD

DynamoDB is fully managed and serverless, so it removes provisioning, patching and scaling chores, directly satisfying the minimise-operational-overhead constraint. Its per-table design also lets each microservice own its data, and it exposes RESTful access through the AWS SDK and HTTPS endpoints.

Why this answer

Amazon DynamoDB is a fully managed NoSQL key-value and document database that provides single-digit millisecond latency at any scale, making it ideal for microservices that need to store their own data and communicate via RESTful APIs. It requires no operational overhead for scaling, patching, or replication, and its pay-per-request billing aligns with the unpredictable traffic patterns common in microservices architectures.

Exam trap

The trap here is that candidates often choose Amazon RDS for PostgreSQL because they assume relational databases are required for structured data, but the question emphasizes minimizing operational overhead, and DynamoDB's serverless, fully managed nature eliminates the need for schema management, scaling, and patching that RDS still requires.

How to eliminate wrong answers

Option A is wrong because Amazon ElastiCache for Redis is an in-memory cache, not a durable primary data store; it is designed for caching, session management, and real-time analytics, not for persistent storage of microservice data. Option B is wrong because Amazon Redshift is a petabyte-scale data warehouse optimized for complex analytical queries on large datasets, not for transactional or operational data storage required by individual microservices. Option C is wrong because Amazon RDS for PostgreSQL, while a fully managed relational database, introduces operational overhead for schema management, connection pooling, and scaling that contradicts the goal of minimizing operational overhead for microservices, and its relational model is less flexible for the independent data persistence patterns of microservices.

671
MCQhard

A company is designing a new data lake on AWS. The data lake will store structured and unstructured data from various sources. The company needs a solution that can automatically catalog the data and make it searchable. Data will be stored in Amazon S3. Which AWS service should be used to catalog and enable search across the data lake?

A.Amazon Athena
B.Amazon EMR
C.Amazon Redshift Spectrum
D.AWS Glue Data Catalog
AnswerD

AWS Glue Data Catalog provides a centralised, Hive-compatible metastore that crawls S3 data, automatically infers schemas and partitions, and exposes tables to Athena, Redshift Spectrum and EMR for search. This directly satisfies the requirement to catalogue structured and unstructured S3 data and make it queryable without managing separate metadata stores.

Why this answer

AWS Glue Data Catalog automatically discovers and catalogs metadata from data stored in Amazon S3, making it searchable. Option A, Amazon Athena, is a serverless query service that uses the Glue Data Catalog but does not itself catalog data. Option B, Amazon EMR, is a big data processing service using frameworks like Spark and Hadoop, not a catalog.

Option C, Amazon Redshift Spectrum, allows querying data in S3 from Redshift but does not provide a catalog.

672
MCQmedium

A healthcare company is migrating a legacy patient records system to AWS. The system uses an Oracle database with complex stored procedures and triggers. The company wants to move to Amazon Aurora PostgreSQL to reduce licensing costs. They need to convert the schema and code with minimal manual effort. Which AWS service should they use?

A.AWS Schema Conversion Tool (AWS SCT)
B.AWS Database Migration Service (AWS DMS)
C.AWS DataSync
D.AWS Application Migration Service (AWS MGN)
AnswerA

AWS Schema Conversion Tool is designed to convert database schemas and code objects from one database engine to another, such as from Oracle to PostgreSQL. It automatically converts stored procedures, triggers, and views, and provides an assessment report highlighting items that require manual intervention. This directly reduces manual effort and accelerates the migration to Aurora PostgreSQL.

Why this answer

AWS Schema Conversion Tool is specifically built to convert database schemas and procedural code from one engine to another. It automates the conversion of Oracle PL/SQL to PostgreSQL PL/pgSQL, significantly reducing manual effort. While AWS DMS handles data migration, it does not convert schema objects, so SCT is the correct choice for this scenario.

Exam trap

The trap here is confusing data migration with schema conversion; AWS DMS moves data, but AWS SCT converts the schema and code.

673
MCQeasy

A company is designing a new application to store and retrieve user profile pictures. The images will be accessed frequently and must be served with low latency. Which storage solution should they use?

A.Amazon EBS
B.Amazon S3
C.Amazon EFS
D.Amazon RDS
AnswerB

Amazon S3 delivers low-latency object retrieval for frequently accessed images, satisfying the stem's performance requirement. Objects are served directly over HTTP without provisioning servers, and S3 scales elastically for profile picture workloads. For even lower latency, CloudFront can cache content at edge locations, though S3 alone meets the stated need.

Why this answer

Amazon S3 is ideal for storing and serving static content like images with low latency. Option A (Amazon EBS) is block storage for EC2, Option C (Amazon EFS) is file storage, and Option D (Amazon RDS) is a relational database.

674
MCQeasy

A company is designing a web application that must handle sudden spikes in traffic. The application runs in a VPC and uses an Application Load Balancer (ALB) to distribute traffic to EC2 instances. The solution must be cost-effective for variable traffic patterns. Which scaling strategy should be used?

A.Simple scaling with step adjustments
B.Target tracking scaling policy based on average CPU utilization
C.Scheduled scaling
D.Manual scaling
AnswerB

Target tracking adjusts EC2 capacity automatically to hold average CPU at a defined target, matching capacity to demand during sudden spikes. Unlike scheduled or manual scaling, it reacts to actual load, and paying only for needed instances keeps costs low for variable traffic.

Why this answer

Target tracking scaling policy is the correct choice because it automatically adjusts the desired capacity of the Auto Scaling group to maintain a target metric (e.g., average CPU utilization at 50%) without requiring manual thresholds or step adjustments. This policy is ideal for variable traffic patterns as it dynamically scales in response to real-time demand, optimizing cost by adding or removing instances only as needed.

Exam trap

The trap here is that candidates often confuse simple scaling with step adjustments as being more granular, but target tracking is actually more responsive and cost-effective for variable traffic because it continuously adjusts capacity based on a single target value rather than fixed thresholds.

How to eliminate wrong answers

Option A is wrong because simple scaling with step adjustments requires predefined thresholds and step adjustments, which can lead to over-provisioning or under-provisioning during sudden traffic spikes due to lack of dynamic responsiveness. Option C is wrong because scheduled scaling is designed for predictable traffic patterns (e.g., time-of-day peaks) and cannot handle sudden, unpredictable spikes. Option D is wrong because manual scaling requires human intervention to adjust capacity, which is not cost-effective or responsive for variable traffic patterns.

675
MCQmedium

A solutions architect deployed an AWS Lambda function using a deployment package. The function logs the error shown in the exhibit. What is the most likely cause?

A.The deployment package does not include the 'express' npm dependency.
B.The Lambda function has exceeded the maximum memory limit.
C.The Lambda function handler is incorrectly configured.
D.The Lambda execution role does not have permissions to access the module.
AnswerA

The error 'Cannot find module' means the module is missing from the package.

Why this answer

The error indicates that the 'express' module is not found, which means it was not included in the deployment package. Option B is wrong because the function ran, so the handler is correct. Option C is wrong because the Lambda execution role does not affect module availability.

Option D is wrong because the error is a missing module, not a memory issue.

Page 8

Page 9 of 14

Page 10