Courseiva

CCNA Design for New Solutions Questions

75 of 321 questions · Page 4/5 · Design for New Solutions · Answers revealed

226
MCQmedium

A company is designing an event-driven architecture using Amazon EventBridge. They have multiple AWS accounts that need to receive events from a central account. What is the MOST scalable and secure way to route events to these accounts?

A.Use Amazon EventBridge cross-account event buses in each target account
B.Publish events to an AWS Lambda function in each target account
C.Use Amazon Kinesis Data Streams with cross-account access
D.Create an Amazon SNS topic in the central account and subscribe SQS queues in each target account
AnswerA

Cross-account event buses let the central account publish events that each target account's bus receives via resource-based policies, avoiding per-account polling or fan-out infrastructure. This satisfies the scalability and security constraints through native, policy-scoped cross-account delivery.

Why this answer

Amazon EventBridge cross-account event buses allow a central account to route events directly to event buses in target accounts using resource-based policies. This approach is serverless, fully managed, and scales horizontally without any intermediate components, making it the most scalable and secure solution. It avoids the complexity and potential bottlenecks of Lambda invocations, Kinesis stream management, or SNS-to-SQS fan-out across accounts.

Exam trap

The trap here is that candidates often default to SNS or SQS for cross-account messaging, but EventBridge's native cross-account event bus feature is specifically designed for this use case and is more scalable and secure because it uses resource-based policies and avoids intermediate services.

How to eliminate wrong answers

Option B is wrong because publishing events to a Lambda function in each target account introduces a single point of failure and scaling bottleneck per function, and requires managing cross-account IAM roles for each invocation, which is less scalable and more complex than native EventBridge cross-account routing. Option C is wrong because Amazon Kinesis Data Streams is designed for real-time data streaming with consumer-based processing, not for event routing to multiple accounts; it would require custom consumers and cross-account access policies, adding operational overhead and latency compared to EventBridge's direct push model. Option D is wrong because creating an SNS topic in the central account and subscribing SQS queues in each target account requires SQS to poll from SNS, which introduces latency and does not support event filtering or schema validation natively; also, SNS does not natively support cross-account subscriptions without additional SQS policy configuration, making it less secure and more complex than EventBridge's resource-based policies.

227
MCQmedium

A company is designing a new microservices architecture on AWS. Each microservice must be independently deployable and scalable. The company expects unpredictable traffic patterns with sudden spikes. Which combination of AWS services should be used to build a decoupled, resilient system?

A.Use Amazon API Gateway, AWS Lambda, Amazon SQS, Amazon DynamoDB, and Amazon CloudWatch.
B.Use Application Load Balancer, Amazon EC2 Auto Scaling, Amazon SQS, and Amazon RDS.
C.Use Amazon API Gateway, AWS Lambda, Amazon Kinesis Data Streams, and Amazon DynamoDB.
D.Use Application Load Balancer, Amazon ECS with Fargate, Amazon SQS, and Amazon RDS with read replicas.
AnswerA

API Gateway fronts requests, Lambda scales per-invocation for sudden spikes, SQS decouples producers from consumers, DynamoDB provides scalable persistence, and CloudWatch supplies observability. This combination delivers independent deployability and resilience, satisfying the decoupled architecture and unpredictable-traffic constraints.

Why this answer

It combines API Gateway as a managed entry point, Lambda for stateless compute, SQS for decoupling and buffering sudden traffic spikes, DynamoDB for serverless NoSQL storage, and CloudWatch for observability. This serverless stack ensures each microservice is independently deployable and scales automatically without provisioning, handling unpredictable spikes via SQS queue depth and Lambda concurrency limits.

Exam trap

The trap here is that candidates often choose Kinesis Data Streams (Option C) thinking it provides better decoupling, but they overlook that SQS is specifically designed for asynchronous message buffering with per-message visibility timeouts, which is more appropriate for microservices decoupling than Kinesis's shard-based streaming model.

How to eliminate wrong answers

Option B is wrong because it relies on EC2 Auto Scaling and ALB, which have slower scaling response times (minutes) compared to Lambda's sub-second scaling, making it less resilient to sudden spikes. Option C is wrong because Kinesis Data Streams is designed for real-time streaming analytics with shard-level scaling, not for decoupling request-response microservices; it lacks the buffering and visibility timeout features of SQS that are critical for resilient decoupling. Option D is wrong because RDS with read replicas introduces a relational database bottleneck that does not scale horizontally for unpredictable write-heavy spikes, and ECS with Fargate still requires container startup time and task definition management, which is less elastic than Lambda's instant scaling.

228
MCQeasy

A company is deploying a new web application on AWS. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The company wants to ensure that the application can handle sudden spikes in traffic and maintain high availability across multiple Availability Zones. The solution must be cost-effective and require minimal manual intervention. Which solution should a solutions architect recommend?

A.Use an Auto Scaling group with a scheduled scaling policy that scales out during business hours and scales in at night.
B.Use an Auto Scaling group with a launch template that spans multiple Availability Zones, and configure a target tracking scaling policy based on average CPU utilization.
C.Use AWS Lambda functions behind an Application Load Balancer to handle the web traffic, with provisioned concurrency to reduce cold starts.
D.Use a fixed number of EC2 instances in two Availability Zones and configure an Application Load Balancer with sticky sessions.
AnswerB

An Auto Scaling group across multiple AZs provides high availability. A target tracking scaling policy automatically adjusts capacity based on CPU utilization, handling traffic spikes without manual intervention. This is cost-effective because instances scale in during low demand, and it meets the requirements with minimal effort.

Why this answer

An Auto Scaling group spanning multiple Availability Zones with a target tracking policy based on CPU utilization automatically adjusts capacity to handle traffic spikes, ensures high availability, and is cost-effective by scaling in during low demand. It requires minimal manual intervention, making it the best choice.

Exam trap

The trap here is assuming that scheduled scaling or fixed capacity can handle unpredictable spikes, but only dynamic scaling policies like target tracking respond in real time to demand changes.

229
MCQeasy

A company is designing a new web application that will run on Amazon EC2 instances behind an Application Load Balancer. The application must handle sudden spikes in traffic without manual intervention. Which scaling approach should they use?

A.Manual scaling
B.Scheduled scaling
C.Target tracking scaling policies
D.Simple scaling policies
AnswerC

Target tracking scaling policies continuously adjust EC2 capacity to hold a chosen metric, such as average CPU utilisation or request count per target, at a specified target value. This automatically absorbs sudden traffic spikes without manual intervention, directly satisfying the stem's requirement for hands-off elasticity behind the Application Load Balancer.

Why this answer

Target tracking scaling policies are the correct choice because they allow Auto Scaling to automatically adjust capacity based on a target value for a specific CloudWatch metric (e.g., average CPU utilization or request count per target). This approach handles sudden traffic spikes without manual intervention by continuously monitoring the metric and adding or removing EC2 instances to maintain the target, making it ideal for unpredictable workloads.

Exam trap

The trap here is that candidates often confuse simple scaling policies with target tracking, assuming any policy based on CloudWatch alarms is sufficient, but simple scaling's cooldown period and single-step adjustment make it inadequate for sudden, sustained spikes that require rapid, continuous scaling.

How to eliminate wrong answers

Option A is wrong because manual scaling requires human intervention to adjust capacity, which cannot handle sudden spikes without delay and defeats the purpose of automation. Option B is wrong because scheduled scaling adjusts capacity at predetermined times, which is ineffective for unexpected traffic spikes that do not follow a predictable pattern. Option D is wrong because simple scaling policies only perform a single scaling adjustment based on a CloudWatch alarm breach and then must wait for a cooldown period, making them slower to react to rapid, sustained spikes compared to target tracking's continuous adjustment.

230
Multi-Selectmedium

A company is designing a new solution that requires a highly available and scalable architecture for a stateless web application. The application will run on Amazon EC2 instances behind an Application Load Balancer (ALB). The company wants to ensure that the instances are automatically replaced if they fail health checks and that the application scales based on demand. The company also wants to minimize costs by using a mix of On-Demand and Spot Instances. Which two actions should be taken to meet these requirements? (Choose two.)

Select 2 answers
A.Use Spot Fleet with a diversified allocation strategy to launch instances across multiple instance types and Availability Zones.
B.Attach the Auto Scaling group to the ALB target group, and configure the group to use ELB health checks.
C.Configure a scheduled scaling policy to add instances every hour to handle expected traffic increases.
D.Create an Auto Scaling group with a launch template that specifies multiple instance types and purchase options, and configure the group to use a mixed instances policy.
E.Enable termination protection on all EC2 instances to prevent accidental termination.
AnswersB, D

Attaching the Auto Scaling group to the ALB target group and enabling ELB health checks ensures that instances failing ALB health checks are automatically replaced. This integrates the scaling group with the load balancer for health monitoring and replacement, meeting the requirement for automatic replacement of failed instances.

Why this answer

Using an Auto Scaling group with a mixed instances policy allows a mix of On-Demand and Spot Instances, reducing costs while maintaining availability. Attaching the group to the ALB target group and using ELB health checks ensures that unhealthy instances are automatically replaced. Together, these actions provide scalability, high availability, and cost optimization.

Exam trap

The trap here is assuming that Spot Fleet alone can provide automatic scaling and health checks, but it lacks the integrated lifecycle management of an Auto Scaling group.

231
MCQhard

A financial services firm runs a payment API on Amazon EC2 instances behind a Network Load Balancer. Regulators require that all data be encrypted in transit using certificates the firm controls, that the backend instances see the original client IP address, and that no TLS termination occur on the load balancer. Which configuration meets these requirements?

A.Configure a TCP listener on port 443 without a certificate, and enable client IP preservation on the target group so instances handle TLS themselves.
B.Configure a UDP listener on port 443 and enable Proxy Protocol v2, then install the firm's certificates on the EC2 instances.
C.Configure a TLS listener on port 443 with a security policy, and register the instances as IP targets with client IP preservation turned off.
D.Configure a TCP listener on port 443 with a TLS certificate imported into AWS Certificate Manager, and enable Proxy Protocol v2 on the target group.
AnswerA

A Network Load Balancer TCP listener passes encrypted traffic straight through, so the instances terminate TLS with certificates the firm fully controls. Client IP preservation is enabled by default for instance target groups on TCP listeners, letting the application read the original source address and satisfy the regulatory logging and access-control requirements.

Why this answer

Passing TLS through a Network Load Balancer requires a TCP listener with no certificate attached, letting the EC2 instances perform the handshake with firm-managed certificates. Client IP preservation, which is on by default for instance targets on TCP listeners, keeps the original client address visible to the backend, avoiding the need for Proxy Protocol parsing.

Exam trap

The trap here is equating end-to-end encryption with a TLS listener, when attaching any certificate to the load balancer actually forces termination there.

232
Multi-Selectmedium

A company is designing a new serverless application that processes sensitive financial data. The application uses AWS Lambda functions that read from and write to an Amazon S3 bucket. The company requires that the data be encrypted at rest and in transit, and that access to the S3 bucket be restricted to only the Lambda functions. The company also wants to minimize management overhead. Which two actions should a solutions architect take to meet these requirements? (Choose two.)

Select 2 answers
A.Configure the S3 bucket to use server-side encryption with AWS KMS (SSE-KMS) and grant the Lambda execution role permissions to use the KMS key.
B.Use Amazon S3 presigned URLs to allow Lambda functions to access the bucket without credentials.
C.Attach an S3 bucket policy that allows access only from the Lambda function's execution role and enforces encryption in transit using aws:SecureTransport.
D.Enable S3 default encryption with Amazon S3 managed keys (SSE-S3) and use VPC endpoints to access the bucket.
E.Store the S3 bucket credentials in AWS Secrets Manager and have the Lambda functions retrieve them at runtime.
AnswersA, C

SSE-KMS provides encryption at rest with centralized key management. Granting the Lambda execution role permissions to the KMS key allows the functions to encrypt and decrypt data. This approach meets the encryption requirement and minimizes overhead by using managed keys.

Why this answer

To encrypt data at rest with granular control, use SSE-KMS and grant the Lambda execution role access to the KMS key. To restrict access to only Lambda functions and enforce encryption in transit, attach an S3 bucket policy that allows the Lambda execution role and denies non-HTTPS requests. These actions meet the requirements with minimal overhead.

Exam trap

The trap here is thinking that presigned URLs or stored credentials are needed for Lambda to access S3, but Lambda should use IAM roles, and presigned URLs are for external users.

233
Multi-Selectmedium

A company is designing a new event-driven architecture using AWS services. The system must process events from multiple sources, filter and route events to different consumers, and ensure that events are processed exactly once. Which THREE services should be used to build this architecture? (Choose three.)

Select 3 answers
A.Amazon Kinesis Data Firehose to deliver events to destinations.
B.AWS Lambda functions to consume events from queues and process them.
C.AWS AppSync to provide real-time subscriptions for events.
D.Amazon SQS FIFO queues to ensure exactly-once processing.
E.Amazon EventBridge to ingest events and route them based on rules.
AnswersB, D, E

Lambda can poll SQS queues and process events.

Why this answer

AWS Lambda functions are correct because they can be triggered by Amazon SQS FIFO queues to process messages one at a time, preserving the order and enabling idempotent processing. Lambda integrates natively with SQS, automatically scaling the number of concurrent executions based on the queue depth, which supports the exactly-once processing requirement when combined with FIFO queues.

Exam trap

The trap here is that candidates often confuse Amazon Kinesis Data Firehose with Amazon Kinesis Data Streams, assuming Firehose supports exactly-once processing, but Firehose only provides at-least-once delivery and lacks the FIFO ordering and deduplication capabilities required for this use case.

234
MCQmedium

A company is deploying a new microservices application on Amazon ECS using Fargate. The application consists of several services that need to communicate with each other. The company wants to use service discovery so that services can find each other by name. Additionally, the company needs to ensure that traffic between services is encrypted in transit. The security team requires that all inter-service traffic uses TLS. Which combination of services should be used to meet these requirements?

A.Use AWS Cloud Map for service discovery and an Application Load Balancer for inter-service communication with TLS termination.
B.Use the built-in service discovery in Amazon ECS and encrypt traffic using AWS Certificate Manager (ACM) certificates.
C.Use an Application Load Balancer with target groups for each service and enable TLS on the load balancer.
D.Use AWS Cloud Map for service discovery and AWS App Mesh with TLS enforcement for inter-service communication.
AnswerD

AWS Cloud Map registers Fargate tasks and resolves service names to endpoints, while App Mesh enforces mutual TLS between proxies, encrypting all inter-service traffic in transit. This satisfies both the discovery and the security team's TLS mandate without application code changes.

Why this answer

AWS Cloud Map provides service discovery so ECS services can find each other by name, and AWS App Mesh enforces TLS for inter-service communication via its virtual nodes and mesh-wide TLS policies. This combination meets both the discovery and encryption-in-transit requirements. App Mesh acts as a service mesh that manages traffic between microservices and can enforce mTLS.

Exam trap

SAP-C02 often tests whether candidates confuse TLS termination at a load balancer with end-to-end encryption, so the trap is selecting an ALB-based solution that only encrypts traffic up to the load balancer, not between services.

How to eliminate wrong answers

Option A is wrong because an Application Load Balancer terminates TLS at the load balancer, so traffic between the load balancer and the backend services is not encrypted end-to-end, violating the requirement for encrypted inter-service traffic. Option B is wrong because ECS built-in service discovery does not provide TLS encryption; ACM certificates are for load balancers and CloudFront, not for encrypting traffic between ECS tasks directly. Option C is wrong because an ALB with target groups terminates TLS at the ALB and does not provide service discovery by name or end-to-end encryption between services.

235
Multi-Selectmedium

A company is designing a new data lake on Amazon S3. They need to ensure that data is encrypted at rest and that access is audited. Which services should they use? (Choose TWO.)

Select 2 answers
A.Amazon Macie
B.Amazon GuardDuty
C.AWS KMS
D.AWS Config
E.AWS CloudTrail
AnswersC, E

AWS KMS supplies the customer managed keys used for server-side encryption of S3 objects, satisfying the encryption-at-rest requirement. S3 SSE-KMS integrates directly with bucket default encryption and key policies, giving the data lake centralised control over who may decrypt stored data.

Why this answer

AWS KMS (C) is correct because it provides the customer-managed and AWS-managed keys used for server-side encryption of S3 objects (SSE-KMS), satisfying the requirement that data be encrypted at rest. AWS CloudTrail (E) is correct because it records S3 data events and management events, providing the audit trail of who accessed the data and when. Amazon Macie (A) is a data-discovery and PII-classification service, not an encryption or access-auditing mechanism.

Amazon GuardDuty (B) is a threat-detection service that identifies malicious activity but does not itself encrypt data or provide the required access audit log. AWS Config (D) tracks resource configuration changes and compliance, but it does not perform encryption at rest or capture the detailed access auditing required here.

236
MCQmedium

A company is migrating a legacy on-premises application to AWS. The application requires a shared file system that supports the NFS protocol and must be accessible from multiple EC2 instances across different Availability Zones. The file system must provide high durability and low latency. The company also needs to control access to the file system using IAM policies. The solutions architect needs to choose the appropriate AWS storage service. Which service should the architect use?

A.Amazon S3 with S3 File Gateway to present as a file system.
B.Amazon EBS with a Provisioned IOPS volume type, mounted on multiple instances using a cluster file system.
C.Amazon EFS with IAM authorization.
D.Amazon FSx for Lustre with a persistent deployment type.
AnswerC

Amazon EFS provides a shared, Multi-AZ NFS file system with high durability and low latency, satisfying the cross-AZ access requirement. Enabling IAM authorization lets you enforce access control through IAM policies, meeting the stated security constraint. FSx for Windows uses SMB, and EBS cannot be shared across Availability Zones.

Why this answer

Amazon EFS is a fully managed, scalable, elastic NFS file system for Linux-based workloads. It supports the NFS protocol and can be mounted on multiple EC2 instances across different Availability Zones simultaneously. EFS provides high durability (11 9's) and low latency.

Additionally, EFS supports IAM authorization for controlling access to the file system, allowing fine-grained permissions. Therefore, Amazon EFS with IAM authorization meets all requirements.

Exam trap

SAP-C02 often tests the difference between EFS and FSx for Lustre. Candidates might choose FSx for Lustre for high performance, but overlook the requirement for NFS and IAM authorization, which EFS provides.

How to eliminate wrong answers

Option A is wrong because S3 File Gateway presents S3 as a file system but is not a native shared file system; it adds latency and does not provide the same low-latency performance as EFS. Option B is wrong because EBS volumes cannot be mounted on multiple instances across AZs; they are tied to a single AZ and typically attached to one instance (except for multi-attach io1/io2 which is limited to a single AZ). Option D is wrong because FSx for Lustre is a high-performance file system for compute-intensive workloads, not general-purpose NFS with IAM authorization; it also does not support IAM authorization natively.

237
MCQmedium

A company runs a web application on Amazon EC2 instances behind an Application Load Balancer (ALB). They want to implement a blue/green deployment strategy with minimal impact on users. Which approach should they use?

A.Create a new target group with the green instances. Modify the ALB listener rule to forward traffic to the new target group.
B.Stop all instances, launch new instances with the new version, and update the target group.
C.Update the existing target group's instances to the new version, one at a time.
D.Create a new ALB and update DNS to point to the new ALB.
AnswerA

Registering green instances in a new target group and repointing the ALB listener rule shifts traffic at the load balancer, giving instant cutover and rollback to blue. This achieves blue/green with minimal user impact, unlike DNS-based approaches with caching delays.

Why this answer

Blue/green deployment with an ALB is achieved by creating a new target group for the green instances and modifying the ALB listener rule to forward traffic to the new target group. This allows instant traffic shifting with zero downtime, as the ALB can route traffic between target groups without changing the DNS or creating a new ALB. The blue (old) target group remains available for instant rollback if needed.

Exam trap

The trap here is confusing blue/green deployment with rolling updates or assuming that a new ALB and DNS change are required, when in fact ALB listener rule modifications provide immediate traffic switching without DNS propagation delays.

How to eliminate wrong answers

Option B is wrong because stopping all instances causes complete downtime, violating the requirement for minimal impact on users. Option C is wrong because updating instances one at a time in the existing target group is a rolling update strategy, not a blue/green deployment; it does not maintain two separate environments for instant switchover. Option D is wrong because creating a new ALB and updating DNS introduces DNS propagation delays and potential disruption, whereas blue/green with ALB should leverage listener rule changes for immediate traffic shift.

238
MCQeasy

A company wants to decouple a microservices architecture where one service (producer) sends events to another service (consumer). The producer can generate bursts of events, and the consumer processes them in batches. The solution must be serverless and handle potential consumer failures without losing events. Which AWS service should be used as the message broker?

A.Amazon SNS
B.Amazon Kinesis Data Streams
C.Amazon EventBridge
D.Amazon SQS
AnswerD

Amazon SQS is serverless, buffers bursty producer traffic, and retains messages until the consumer deletes them, so failed batches are retried rather than lost. It decouples the services and satisfies the no-event-loss requirement, unlike a synchronous invocation model.

Why this answer

Amazon SQS is a fully managed, serverless message queue that decouples producers and consumers, buffers bursts, and supports batch processing. It provides at-least-once delivery and, with a standard queue, high throughput; messages persist until successfully processed, so consumer failures do not lose events. These characteristics match the requirement for a serverless broker that handles bursts and failures.

Exam trap

SAP-C02 often tests the confusion between SNS (push, no buffering) and SQS (pull, buffered queue), leading candidates to choose SNS for decoupling when message persistence and failure handling are required.

How to eliminate wrong answers

Option A is wrong because Amazon SNS is a pub/sub notification service that pushes messages to subscribers; it does not buffer messages for later batch consumption and does not retain messages if a subscriber fails. Option B is wrong because Kinesis Data Streams is a streaming service that requires provisioned or on-demand shards and is not inherently serverless in the same sense; it also does not provide the same simple queue-based decoupling and automatic message retention for failed consumers. Option C is wrong because EventBridge is an event bus for routing events based on rules; it does not provide queue-based buffering or batch consumption semantics for a single consumer.

239
Multi-Selecthard

A company is migrating a monolithic application to microservices on AWS. The current application uses a single Amazon RDS for PostgreSQL database. To avoid tight coupling, each microservice should have its own database. The company needs to minimize downtime during migration. Which THREE strategies should be used?

Select 3 answers
A.Design each microservice with its own database.
B.Use a single shared database with separate schemas for each service.
C.Use AWS Database Migration Service (DMS) for ongoing replication.
D.Implement the Strangler Fig pattern to gradually migrate functionality.
E.Deploy all microservices on a single large EC2 instance.
AnswersA, C, D

Giving each microservice its own database removes the shared-schema coupling that forces coordinated releases. This directly satisfies the stem's requirement to avoid tight coupling, letting services evolve, scale and fail independently rather than sharing one PostgreSQL instance.

Why this answer

Option A is correct because giving each microservice its own database enforces the bounded-context isolation that prevents tight coupling, allowing services to evolve schemas and scale independently as required by the migration goal. Option C is correct because AWS DMS supports ongoing (change data capture) replication from the existing RDS for PostgreSQL source to the new per-service databases, keeping them synchronized so cutover can happen with minimal downtime. Option D is correct because the Strangler Fig pattern incrementally routes functionality from the monolith to new microservices, letting the team migrate piece by piece and roll back safely, which directly minimizes downtime and risk.

Option B is wrong because a single shared database with separate schemas still creates a shared point of coupling and contention, contradicting the requirement that each microservice own its database. Option E is wrong because deploying all microservices on one large EC2 instance is an anti-pattern that reduces isolation, scalability, and resilience, and does nothing to address database decoupling or migration downtime.

Exam trap

The trap here is that candidates often think a shared database with separate schemas is sufficient for microservices isolation, but it still creates tight coupling at the schema and transaction level, violating the database-per-service principle required for true decoupling.

240
MCQhard

A company is designing a new application that will run on Amazon ECS with Fargate. The application consists of three microservices: Service A, Service B, and Service C. Service A receives HTTP requests from an Application Load Balancer and sends messages to an Amazon SQS queue. Service B polls the SQS queue and processes the messages, storing results in Amazon DynamoDB. Service C reads from DynamoDB and sends notifications via Amazon SNS. The company expects variable traffic and wants to minimize costs. During a load test, the team observes that Service B is not scaling fast enough, causing the SQS queue to grow. The team also notices that Service C is idle most of the time. Which solution should the company implement to improve scaling and reduce costs?

A.Use AWS Lambda with Provisioned Concurrency for Service B and keep Service C as a Fargate service.
B.Use a step scaling policy for Service B based on CPU utilization and keep Service C as is.
C.Configure Service B with a target tracking scaling policy based on the SQS queue backlog and convert Service C to an AWS Lambda function triggered by DynamoDB Streams.
D.Increase the number of ECS tasks for Service B manually and use a scheduled scaling policy for Service C.
AnswerC

Target tracking on SQS queue backlog scales Service B directly against the growing queue, matching the observed constraint. Converting Service C to Lambda removes idle Fargate cost, since DynamoDB Streams invokes it only on change, satisfying the variable-traffic, cost-minimisation requirement.

Why this answer

It addresses both scaling and cost issues: Service B's scaling is improved by using a target tracking scaling policy based on the SQS queue backlog (ApproximateNumberOfMessagesVisible), which directly correlates to the work demand, ensuring faster and more precise scaling. Converting Service C to a Lambda function triggered by DynamoDB Streams eliminates idle compute costs from a constantly running Fargate service, as Lambda only runs when new data appears in DynamoDB, reducing costs significantly.

Exam trap

The trap here is that candidates often choose CPU-based scaling (Option B) because it is familiar, but they fail to recognize that queue depth is a more direct and responsive metric for scaling message-processing services, and they overlook the cost savings of replacing an idle Fargate service with a Lambda function triggered by DynamoDB Streams.

How to eliminate wrong answers

Option A is wrong because using Lambda with Provisioned Concurrency for Service B would incur costs for pre-warmed instances even when idle, and it does not address the scaling issue with the SQS queue backlog; moreover, Lambda is not ideal for long-running polling tasks. Option B is wrong because a step scaling policy based on CPU utilization is an indirect metric that does not reflect the actual work queue depth, leading to delayed scaling and continued queue growth. Option D is wrong because manually increasing tasks for Service B is not automated or cost-effective for variable traffic, and using a scheduled scaling policy for Service C does not address its idle time—it would still run tasks when not needed, wasting resources.

241
MCQmedium

A company is designing a new data lake on Amazon S3. They need to query the data using standard SQL and expect to run complex queries that scan large datasets. The query performance should be optimized to minimize data scanned. Which service should they use?

A.Amazon Redshift Spectrum
B.Amazon EMR
C.Amazon Athena
D.Amazon QuickSight
AnswerC

Athena queries S3 data using standard SQL and is serverless, and its columnar Parquet support with partition pruning minimises bytes scanned. This directly satisfies the requirement for complex SQL queries over large datasets with optimised scan performance.

Why this answer

Amazon Athena is a serverless interactive query service that uses standard SQL to analyze data directly in Amazon S3. It is optimized for querying large datasets with a pay-per-query model, and it automatically minimizes data scanned by leveraging features like columnar data formats (Parquet, ORC), partitioning, and compression to reduce the amount of data read per query.

Exam trap

The trap here is that candidates often confuse Amazon Redshift Spectrum with Athena because both query S3 data, but Redshift Spectrum requires a running Redshift cluster and is not serverless, while Athena is fully serverless and designed specifically for minimizing data scanned in a data lake scenario.

How to eliminate wrong answers

Option A is wrong because Amazon Redshift Spectrum is an extension of Amazon Redshift that allows querying data in S3, but it requires an active Redshift cluster and is designed for hybrid queries that combine local and external data, not for a standalone data lake query service with minimal data scanned. Option B is wrong because Amazon EMR is a managed big data platform that supports frameworks like Apache Spark and Hive, but it requires provisioning and managing clusters, and its primary focus is not on minimizing data scanned for ad-hoc SQL queries; it is more suited for complex ETL and processing jobs. Option D is wrong because Amazon QuickSight is a business intelligence (BI) and visualization service, not a SQL query engine for scanning large datasets; it relies on underlying data sources like Athena or Redshift for query execution.

242
Drag & Dropmedium

Drag and drop the steps to recover an Amazon RDS Multi-AZ DB instance after a primary instance failure 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 identify failure, wait for failover, verify promotion, update endpoints, then investigate.

243
MCQmedium

A company is designing a new microservices architecture on AWS. They need to ensure that services can communicate asynchronously without direct coupling. Which AWS service should they use to decouple the services?

A.AWS Step Functions
B.Amazon SNS
C.Amazon SQS
D.Amazon Kinesis
AnswerC

Amazon SQS provides fully managed message queues that buffer messages between producers and consumers, so microservices publish without waiting for a response. This satisfies the asynchronous, loosely coupled communication constraint: services interact only through the queue, tolerating consumer failures and scaling independently without direct invocation or endpoint dependencies.

Why this answer

Amazon SQS is the correct choice because it provides a fully managed message queue that enables asynchronous communication between microservices, allowing them to send, store, and receive messages without direct coupling. Services can poll or receive messages from the queue at their own pace, ensuring that the producer and consumer are decoupled and can operate independently, even if one is temporarily unavailable.

Exam trap

The trap here is that candidates often confuse Amazon SNS (pub/sub) with Amazon SQS (queue), but SNS pushes messages to subscribers and does not provide a buffer for asynchronous decoupling, whereas SQS allows services to pull messages at their own pace, which is the key requirement for decoupling.

How to eliminate wrong answers

Option A is wrong because AWS Step Functions is a serverless orchestration service that coordinates multiple AWS services into a workflow, but it does not inherently decouple services asynchronously; it tightly couples the execution flow and is not a message queue. Option B is wrong because Amazon SNS is a pub/sub messaging service that pushes messages to subscribers, which still requires subscribers to be active and does not provide a buffer for asynchronous decoupling like a queue does. Option D is wrong because Amazon Kinesis is designed for real-time streaming data ingestion and processing, not for simple asynchronous decoupling of microservices; it introduces complexity with shards and retention periods that are unnecessary for basic decoupling needs.

244
Multi-Selecthard

A financial services firm is migrating a latency-sensitive trading analytics workload to AWS. The workload runs on Amazon EC2 instances in a single VPC and requires network throughput of up to 100 Gbps per instance, consistent sub-100-microsecond inter-instance latency, and the ability to place instances close together to minimize hops. The firm also wants the instances to communicate without traversing the public internet. (Choose two.)

Select 2 answers
A.Configure a VPC peering connection between the workload VPC and a shared services VPC in another Region
B.Deploy the instances into a spread placement group across three Availability Zones
C.Attach an Elastic Fabric Adapter (EFA) to the instances and enable it for the application
D.Enable AWS Global Accelerator with endpoint groups pointing to the instances in multiple Regions
E.Launch the instances into a cluster placement group within a single Availability Zone
AnswersC, E

EFA provides a network interface that supports OS-bypass for tightly coupled HPC and analytics workloads, delivering lower and more consistent latency than standard TCP paths. It is designed for the high per-instance throughput the workload demands and works with cluster placement groups to keep traffic private and within a single Availability Zone.

Why this answer

Low-latency, high-bandwidth east-west traffic is achieved by combining a cluster placement group, which minimizes physical distance and hops within one Availability Zone, with Elastic Fabric Adapter, which provides OS-bypass networking for tightly coupled workloads. Together they deliver the required per-instance throughput and consistent latency while keeping traffic on the private AWS network.

Exam trap

The trap here is reaching for a global traffic-optimization service for inter-instance latency when the requirement is really about physical placement and the network interface technology inside a single VPC.

245
Multi-Selecthard

A company is designing a multi-region disaster recovery solution for a critical application running on Amazon EC2. The application uses an Amazon Aurora MySQL database. The RTO is 15 minutes and RPO is 1 minute. Which THREE steps should the solutions architect take to meet these requirements?

Select 3 answers
A.Pre-provision EC2 instances in the DR region with the application code and configuration.
B.Use Route 53 health checks with failover routing policy to direct traffic to the DR region.
C.Configure a cross-region read replica in the DR region and promote it during failover.
D.Take frequent snapshots of the Aurora cluster and copy them to the DR region.
E.Use Amazon Aurora Global Database for replication to the DR region.
AnswersA, B, E

Ensures compute capacity is ready for failover.

Why this answer

Pre-provisioning EC2 instances in the DR region with the application code and configuration ensures that compute capacity is ready to serve traffic immediately upon failover. This eliminates the time needed to launch and configure instances, which is critical for meeting the 15-minute RTO. Without pre-provisioning, the time to spin up and configure instances would likely exceed the RTO.

Exam trap

The trap here is that candidates often confuse cross-region read replicas (which have higher replication lag and slower promotion) with Aurora Global Database (which provides low-latency, fast failover), leading them to select Option C instead of Option E.

246
MCQhard

A financial services company is designing a highly available architecture for a critical application on AWS. The application runs on EC2 instances and uses an Oracle database. The database must be resilient to an Availability Zone failure and must have automated failover. Which database solution meets these requirements?

A.Use Amazon Aurora (MySQL-compatible) with Multi-AZ.
B.Use Amazon RDS for Oracle with a Read Replica in another AZ.
C.Deploy Oracle on EC2 in two Availability Zones and use asynchronous replication.
D.Use Amazon RDS for Oracle with Multi-AZ deployment.
AnswerD

RDS for Oracle Multi-AZ maintains a synchronous standby in a different Availability Zone and performs automated failover, so the database survives an AZ failure without manual intervention. This directly satisfies the resilience and automated failover constraints for the Oracle workload.

Why this answer

Amazon RDS for Oracle with Multi-AZ deployment provides automatic failover to a standby instance in a different Availability Zone, meeting the requirements for high availability and automated failover. Option A is incorrect because Amazon Aurora (MySQL-compatible) is not Oracle-compatible, so it cannot replace an Oracle database. Option B is incorrect because a Read Replica in another AZ does not provide automated failover; it is used for read scaling and requires manual promotion.

Option C is incorrect because deploying Oracle on EC2 with asynchronous replication requires manual failover management and does not provide automated failover.

247
MCQmedium

A company is designing a new application that will store sensitive user data in Amazon S3. Compliance requirements mandate that all data must be encrypted at rest using a key that is managed by the company and rotated automatically every year. Which solution meets these requirements?

A.Use S3 server-side encryption with AWS KMS customer managed keys (SSE-KMS) and enable automatic key rotation.
B.Use client-side encryption with the AWS SDK.
C.Use S3 server-side encryption with customer-provided keys (SSE-C).
D.Use S3 server-side encryption with S3 managed keys (SSE-S3).
AnswerA

SSE-KMS with customer managed keys satisfies the company-managed key mandate, and enabling annual automatic rotation meets the yearly requirement. Rotation re-wraps the key material while retaining the same key ID, so existing objects remain decryptable without re-encryption. AWS managed keys cannot be rotated on a customer-defined schedule.

Why this answer

SSE-KMS with customer managed keys (CMKs) meets the compliance requirements because it allows the company to manage the encryption key lifecycle, including automatic annual rotation. AWS KMS supports automatic key rotation for customer managed keys, which can be configured to rotate every year, satisfying the mandate for company-managed keys with automatic rotation.

Exam trap

The trap here is that candidates often confuse SSE-C (customer-provided keys) with customer managed keys, but SSE-C does not support automatic rotation and requires the customer to manage key material outside AWS, whereas SSE-KMS with customer managed keys provides automatic rotation and is the correct choice for company-managed keys with rotation.

How to eliminate wrong answers

Option B is wrong because client-side encryption encrypts data before it reaches S3, but the key management and rotation are handled by the client application, not by AWS, and the compliance requirement specifies that the key must be managed by the company but does not require client-side control; also, automatic rotation would require custom implementation. Option C is wrong because SSE-C requires the company to provide and manage their own encryption keys, but AWS does not support automatic key rotation for SSE-C—the customer must manually rotate keys and re-encrypt data. Option D is wrong because SSE-S3 uses AWS-managed keys (Amazon S3 managed keys), which are not managed by the company, violating the requirement that the key must be managed by the company.

248
MCQhard

A company is migrating a legacy on-premises application to AWS. The application consists of a monolithic .NET application running on Windows Server, with a Microsoft SQL Server database. The company wants to improve scalability and reduce operational overhead. The application experiences variable traffic, with peaks during business hours. The company requires a highly available architecture with automatic failover for the database. Which migration strategy should a solutions architect recommend?

A.Rehost the application on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and migrate the database to Amazon RDS for SQL Server with Multi-AZ.
B.Refactor the application into microservices running on Amazon ECS with AWS Fargate, and use Amazon Aurora for the database.
C.Retain the application on-premises and use AWS Storage Gateway for backup, and set up a VPN connection to AWS for disaster recovery.
D.Replatform the application to AWS Elastic Beanstalk for .NET, and use Amazon DynamoDB for the database.
AnswerA

Rehosting on EC2 with an Auto Scaling group and ALB provides scalability and high availability for the application tier. Migrating to RDS for SQL Server with Multi-AZ ensures automatic failover and reduces database management overhead. This approach meets the requirements for scalability, high availability, and reduced operational effort with minimal application changes.

Why this answer

Rehosting the application on EC2 with an Auto Scaling group and ALB provides scalability and high availability without code changes. Migrating the database to RDS for SQL Server with Multi-AZ offers automatic failover and reduces management overhead. This strategy balances minimal changes with the desired scalability and availability, making it the most suitable for a legacy application.

Exam trap

The trap here is assuming that replatforming to Elastic Beanstalk or refactoring to microservices is necessary for scalability, but those add complexity and may not be needed for a lift-and-shift migration.

249
MCQhard

A company is migrating a legacy application to AWS. The application requires a shared file system that can be mounted by hundreds of EC2 instances across multiple Availability Zones. The file system must provide high throughput and low latency. Which storage solution meets these requirements?

A.Use Amazon EBS with a multi-attach enabled volume.
B.Use Amazon EFS with provisioned throughput.
C.Use Amazon S3 with S3 File Gateway to present as a file system.
D.Use Amazon FSx for Windows File Server with a single file system.
AnswerB

Amazon EFS is a shared, elastic NFS file system mountable concurrently from EC2 instances in multiple Availability Zones, and provisioned throughput guarantees the required performance. This satisfies the multi-AZ shared access, high throughput, and low latency constraints.

Why this answer

Amazon EFS with provisioned throughput is the correct choice because it provides a fully managed, scalable, shared file system that can be mounted by hundreds of EC2 instances across multiple Availability Zones simultaneously. It uses the NFSv4.1 protocol, delivers high throughput and low latency, and allows you to provision throughput independently of storage size to meet performance requirements.

Exam trap

The trap here is that candidates often confuse Amazon EBS multi-attach with a true shared file system, overlooking its single-AZ limitation and low instance count cap, while also underestimating EFS's ability to handle hundreds of concurrent NFS clients across multiple AZs with provisioned throughput.

How to eliminate wrong answers

Option A is wrong because Amazon EBS multi-attach volumes can only be attached to a maximum of 16 Nitro-based EC2 instances in a single Availability Zone, not hundreds across multiple AZs, and they do not provide a shared file system interface. Option C is wrong because Amazon S3 with S3 File Gateway presents an SMB or NFS file system but is designed for hybrid cloud caching and does not natively provide the low-latency, high-throughput performance required for hundreds of concurrent EC2 instances across AZs; it also introduces gateway latency and throughput limitations. Option D is wrong because Amazon FSx for Windows File Server supports only Windows-based clients via SMB protocol and is not optimized for the high-throughput, low-latency requirements of hundreds of Linux-based EC2 instances across multiple AZs; it also has a single file system that can be accessed across AZs but is not designed for the scale and performance profile described.

250
MCQeasy

A company wants to migrate an on-premises relational database to Amazon RDS for MySQL with minimal downtime. The database is 500 GB in size. Which AWS service should be used for the initial data load and ongoing replication?

A.Use AWS Snowball to transfer the database files to RDS.
B.Use an RDS read replica from the on-premises database.
C.Use AWS Database Migration Service (DMS) with ongoing replication.
D.Export the database to Amazon S3 and import into RDS.
AnswerC

AWS DMS performs the initial full load and then continuous change data capture from the source MySQL binary logs, replicating ongoing changes to RDS for MySQL. This keeps the target synchronised until cutover, satisfying the minimal-downtime constraint for the 500 GB database.

Why this answer

AWS Database Migration Service (DMS) with ongoing replication is the correct choice because it supports both a full load of the 500 GB database and continuous change data capture (CDC) using the MySQL binary log (binlog) to replicate ongoing changes with minimal downtime. DMS can perform the initial load while the source remains operational, then switch to CDC to keep the target in sync until cutover.

Exam trap

The trap here is that candidates often confuse the one-time bulk transfer capability of Snowball or S3 with the need for ongoing replication, failing to recognize that minimal downtime requires a continuous change capture mechanism like DMS CDC, not just an initial data load.

How to eliminate wrong answers

Option A is wrong because AWS Snowball is designed for offline bulk data transfer of large datasets (e.g., terabytes to petabytes) and cannot provide ongoing replication; it would require a separate replication mechanism for changes after the initial load, defeating the minimal-downtime goal. Option B is wrong because an RDS read replica can only be created from an existing RDS instance, not from an on-premises database; it uses MySQL's asynchronous replication which requires the source to be an RDS MySQL instance. Option D is wrong because exporting the database to Amazon S3 and importing into RDS is a one-time, offline process that does not capture ongoing changes, so it would result in significant downtime while the export and import occur, and it lacks CDC capabilities.

251
MCQeasy

A company is running a web application on AWS Elastic Beanstalk with an Auto Scaling group behind an Application Load Balancer. The application stores session state in an Amazon DynamoDB table. During a traffic spike, the application becomes slow and some users are logged out unexpectedly. The operations team notices that the DynamoDB table's read capacity utilization is consistently at 100%. The company needs to improve the performance of the session store without over-provisioning capacity. Which solution should be implemented?

A.Migrate the session store from DynamoDB to Amazon ElastiCache Memcached.
B.Increase the read capacity units (RCU) of the DynamoDB table to handle peak traffic.
C.Move session state to Amazon SQS and have the application poll the queue.
D.Implement Amazon DynamoDB Accelerator (DAX) as a caching layer for the session store.
AnswerD

DAX provides a write-through, in-memory cache for DynamoDB, serving session reads from microseconds-latency memory instead of consuming table read capacity units. This eliminates the 100% read utilisation bottleneck and prevents logouts without raising provisioned throughput.

Why this answer

DynamoDB Accelerator (DAX) is an in-memory cache purpose-built for DynamoDB that reduces read latency from milliseconds to microseconds and offloads read traffic from the table, directly addressing the 100% read capacity utilization. Because session state is read-heavy and latency-sensitive, DAX is the ideal fit — it requires minimal application changes (just swap the DynamoDB client for the DAX client) and does not require over-provisioning RCUs. This solves both the performance degradation and the unexpected logouts caused by read throttling.

Exam trap

SAP-C02 often tests whether candidates recognize DAX as the DynamoDB-native caching solution — distractors like ElastiCache or increasing RCUs sound plausible but either over-provision or require unnecessary re-architecture.

How to eliminate wrong answers

Option A is wrong because migrating to ElastiCache Memcached changes the session store technology entirely, requires significant application rework, and loses DynamoDB's durability and managed scaling — it is a heavier change than necessary. Option B is wrong because simply increasing RCUs is over-provisioning, which the question explicitly says to avoid, and it does not reduce latency for session reads. Option C is wrong because SQS is a message queue, not a session store — polling a queue for session state is architecturally nonsensical and would add latency, not reduce it.

252
Multi-Selectmedium

A company is designing a new serverless application that uses AWS Lambda, Amazon DynamoDB, and Amazon API Gateway. The application must handle burst traffic and cannot lose any data. The company wants to use a dead-letter queue (DLQ) for failed Lambda invocations. Which TWO services can be used as a DLQ for Lambda? (Choose two.)

Select 2 answers
A.Amazon DynamoDB Streams
B.Amazon SNS
C.Amazon Kinesis Data Streams
D.Amazon SQS
E.Amazon Simple Email Service (SES)
AnswersB, D

Amazon SNS works as a Lambda dead-letter queue because Lambda supports publishing failed asynchronous invocation records to an SNS topic, satisfying the no-data-loss requirement. Unlike SQS, SNS pushes each failed event to subscribers, enabling fan-out to email, HTTP endpoints or additional queues for immediate alerting on burst-traffic failures.

Why this answer

Amazon SNS and Amazon SQS are the two supported destinations for Lambda's dead-letter queue (DLQ) configuration, but only for asynchronous invocations. When a Lambda function is invoked asynchronously and fails after the configured number of retries, the event can be redirected to an SNS topic or an SQS queue for later reprocessing or analysis. This ensures no data is lost during burst traffic, as failed events are persisted in the DLQ.

Synchronous invocations do not support DLQ.

Exam trap

The trap here is that candidates often confuse Lambda's event sources (like DynamoDB Streams or Kinesis) with supported DLQ destinations, but Lambda only allows SQS and SNS as DLQ targets for asynchronous invocations.

253
MCQmedium

A financial services company is migrating a batch risk-calculation workload to AWS. The workload runs nightly for 90 minutes, requires 64 vCPUs and 256 GiB of memory, and must complete within a 2-hour window. The company wants to minimize cost and is open to interruption because the job can restart from a checkpoint. Which compute option should a solutions architect recommend?

A.Amazon EC2 Spot Instances with a capacity-optimized allocation strategy and checkpointing to Amazon S3.
B.AWS Fargate tasks on Amazon ECS with 16 vCPU and 120 GiB of memory, scaled by a scheduled Application Auto Scaling policy.
C.AWS Lambda functions with 10 GB of memory and a 15-minute timeout, invoked in parallel by AWS Step Functions.
D.Amazon EC2 On-Demand instances launched in an Auto Scaling group with a scheduled scaling policy.
AnswerA

Spot Instances can deliver up to 90% savings versus On-Demand and are ideal for interruption-tolerant batch jobs. The capacity-optimized allocation strategy selects pools with the most available capacity, reducing the chance of interruption during the 90-minute window. Checkpointing to Amazon S3 lets the job resume from the last completed step if a Spot Instance is reclaimed, keeping the workload within the 2-hour completion window.

Why this answer

The workload is short, deterministic, and restartable from a checkpoint, which makes it a strong fit for EC2 Spot Instances. A capacity-optimized allocation strategy improves the likelihood of obtaining and retaining capacity for the full 90 minutes, and checkpointing to Amazon S3 allows recovery if a Spot Instance is reclaimed. This combination minimizes cost while still meeting the 2-hour completion window.

Exam trap

The trap here is dismissing Spot Instances because the job has a deadline, when checkpointing and a capacity-optimized allocation strategy make Spot both safe and far cheaper for interruption-tolerant batch workloads.

254
MCQmedium

A company is designing a multi-tier web application on AWS. They want to ensure that the web tier can scale automatically based on CPU utilization. Which AWS service should they use?

A.Amazon CloudFront
B.Amazon Route 53
C.Auto Scaling groups
D.Elastic Load Balancing
AnswerC

Auto Scaling groups adjust the number of EC2 instances in the web tier based on CloudWatch CPU utilisation metrics, scaling out under load and in when idle. This delivers the automatic, demand-driven scaling the multi-tier design requires.

Why this answer

Auto Scaling groups (Option C) are the correct service because they directly manage the automatic scaling of EC2 instances based on defined policies, such as a target CPU utilization threshold. When CPU utilization exceeds the threshold, the Auto Scaling group launches new instances to handle the load, and it terminates instances when utilization drops, ensuring the web tier scales automatically.

Exam trap

The trap here is that candidates often confuse Elastic Load Balancing with automatic scaling, but ELB only distributes traffic and does not add or remove instances; the Auto Scaling group is the service that actually scales the compute capacity.

How to eliminate wrong answers

Option A is wrong because Amazon CloudFront is a content delivery network (CDN) that caches content at edge locations to reduce latency, not a service that scales compute resources based on CPU utilization. Option B is wrong because Amazon Route 53 is a DNS web service that routes end users to internet applications, but it does not provide automatic scaling of compute capacity. Option D is wrong because Elastic Load Balancing distributes incoming traffic across multiple targets (e.g., EC2 instances), but it does not automatically scale the number of instances; it works in conjunction with Auto Scaling groups to distribute traffic to scaled instances.

255
MCQmedium

A company is designing a data lake on AWS using Amazon S3. They need to run SQL queries on the data without moving it to a separate database. Which AWS service should they use?

A.Amazon EMR
B.Amazon Athena
C.Amazon Redshift
D.AWS Glue
AnswerB

Amazon Athena is a serverless query service that runs standard SQL directly against data in Amazon S3 using the Glue Data Catalog, so no data movement or separate database is needed. This satisfies the requirement to query in place without loading.

Why this answer

Amazon Athena is a serverless, interactive query service that allows you to run standard SQL queries directly against data stored in Amazon S3 without needing to move or transform the data. It uses Presto under the hood and charges only for the data scanned per query, making it ideal for ad-hoc SQL analysis on a data lake.

Exam trap

The trap here is that candidates often confuse AWS Glue (which catalogs and transforms data but does not run SQL queries) with Athena, or they assume Amazon EMR is required for SQL-on-S3, overlooking Athena's serverless and direct-query capability.

How to eliminate wrong answers

Option A is wrong because Amazon EMR is a managed big data platform that requires you to provision and configure clusters (e.g., Hadoop, Spark) to run SQL via tools like Hive or Presto, which adds operational overhead and does not allow querying data directly without moving it into a separate processing framework. Option C is wrong because Amazon Redshift is a fully managed data warehouse that requires you to load data into its columnar storage before querying, which contradicts the requirement of not moving data to a separate database. Option D is wrong because AWS Glue is a serverless data integration service primarily used for ETL (extract, transform, load) and cataloging metadata via the Glue Data Catalog; it does not provide a direct SQL query engine against S3 data.

256
MCQeasy

A company wants to serve static content (images and videos) to users worldwide with low latency. The content is stored in an Amazon S3 bucket. What is the most cost-effective solution?

A.Use AWS Global Accelerator with endpoints pointing to the S3 bucket.
B.Deploy EC2 instances in multiple Regions and use a load balancer.
C.Use Amazon CloudFront with the S3 bucket as the origin.
D.Host the content directly from the S3 bucket and use S3 Transfer Acceleration.
AnswerC

CloudFront caches objects at edge locations worldwide, so repeated requests are served from the nearest point of presence rather than from the S3 bucket's Region, cutting latency. You pay only for data transfer out and requests, with no upfront cost, satisfying the worldwide low-latency and cost-effectiveness constraints.

Why this answer

Amazon CloudFront is a global content delivery network (CDN) that caches static content at edge locations worldwide, reducing latency for users. Using an S3 bucket as the origin is cost-effective because CloudFront egress costs are often lower than direct S3 data transfer, and you only pay for data transfer out from CloudFront and occasional origin fetches. This solution minimizes origin load and provides low-latency delivery without the overhead of managing servers or additional acceleration services.

Exam trap

The trap here is that candidates confuse AWS Global Accelerator (which optimizes network path but does not cache) with a CDN like CloudFront, or mistakenly think S3 Transfer Acceleration improves download performance for end users when it only accelerates uploads to S3.

How to eliminate wrong answers

Option A is wrong because AWS Global Accelerator improves TCP/UDP traffic performance via the AWS global network but does not cache content; it would still require all requests to reach the S3 bucket, increasing latency and costs compared to a CDN. Option B is wrong because deploying EC2 instances in multiple Regions to serve static content introduces unnecessary compute costs, management overhead, and complexity, while a CDN like CloudFront provides caching at edge locations more efficiently. Option D is wrong because S3 Transfer Acceleration speeds up uploads to S3 over long distances using AWS edge locations, but it does not cache or accelerate downloads for end users; it would not reduce latency for serving content globally and can incur higher costs per GB transferred.

257
Multi-Selecthard

A company is designing a high-performance computing (HPC) workload on AWS. The workload requires tightly coupled inter-node communication with low latency and high bandwidth. Which THREE services or features should the architect consider to meet these requirements? (Choose three.)

Select 3 answers
A.EC2 instances with enhanced networking and high-throughput (e.g., p4d, p3dn)
B.VPC peering between multiple VPCs
C.AWS Global Accelerator
D.Placement Groups (Cluster Placement Group)
E.Elastic Fabric Adapter (EFA)
AnswersA, D, E

These instance types offer high network bandwidth and EFA support.

Why this answer

EC2 instances like p4d and p3dn are designed for HPC workloads, offering enhanced networking (up to 100 Gbps) and high-throughput capabilities. These instances support Elastic Fabric Adapter (EFA) and are optimized for tightly coupled inter-node communication, providing the low latency and high bandwidth required for HPC.

Exam trap

The trap here is that candidates may confuse VPC peering or Global Accelerator as solutions for inter-node latency, but these services address different problems (cross-VPC connectivity and global traffic optimization) and do not reduce latency for tightly coupled HPC communication within a single cluster.

258
MCQmedium

A company is migrating a legacy on-premises application to AWS. The application uses a shared file system that is accessed by multiple Windows servers. The company wants to use a fully managed AWS storage service that provides SMB file shares and integrates with Microsoft Active Directory for authentication. The solution must be highly available and durable. Which AWS service should the company use?

A.Amazon FSx for Lustre
B.Amazon Elastic File System (Amazon EFS)
C.Amazon S3 with S3 File Gateway
D.Amazon FSx for Windows File Server
AnswerD

Amazon FSx for Windows File Server is a fully managed file storage service built on Windows Server that supports the SMB protocol and integrates with Microsoft Active Directory for authentication. It provides high availability through Multi-AZ deployments and is designed for durability. This service directly meets the requirements for a shared Windows file system with AD integration.

Why this answer

The application requires a shared file system for Windows servers using SMB and integrated with Active Directory. Amazon FSx for Windows File Server is the only AWS service that natively supports SMB and AD integration, and it is fully managed, highly available, and durable. Other options either use different protocols or lack the required AD integration.

Exam trap

The trap here is confusing Amazon EFS or S3 File Gateway with a Windows-native file system, overlooking the need for SMB protocol and Active Directory integration.

259
MCQeasy

A startup is designing a new web application that will be hosted on AWS. The application consists of a static frontend and a backend API. The frontend is built with React and the backend is a RESTful API built with Node.js. The startup expects low traffic initially but wants to be able to scale to millions of users. The team wants to minimize operational overhead and cost. Which architecture should they use?

A.Host the frontend and backend on a single EC2 instance using Amazon Lightsail.
B.Host the frontend on Amazon S3 with static website hosting and the backend as AWS Lambda functions behind Amazon API Gateway.
C.Host the frontend on EC2 instances behind an ALB and the backend on EC2 instances behind another ALB.
D.Host the frontend on S3 and the backend on Amazon Elastic Beanstalk with a load balancer.
AnswerB

Serverless architecture minimizes operational overhead and scales automatically.

Why this answer

S3 for static hosting and API Gateway with Lambda provides a serverless, scalable solution with low overhead. Option A is wrong because EC2 requires management. Option C is wrong because Lightsail has limited scalability.

Option D is wrong because Elastic Beanstalk has more overhead than serverless.

260
MCQeasy

A company wants to build a serverless backend for a mobile application. The backend provides user authentication, a REST API for data access, and stores data in a NoSQL database. The company expects the application to have unpredictable traffic, and wants to minimize costs. Which solution should a Solutions Architect recommend?

A.Use IAM for authentication, EC2 instances behind an ALB for the API, and DynamoDB for the database.
B.Use Amazon Cognito for authentication, API Gateway with Lambda for the API, and Amazon DynamoDB for the database.
C.Use Amazon Cognito for authentication, API Gateway with Lambda for the API, and Amazon RDS for the database.
D.Use Amazon Cognito for authentication, API Gateway with Lambda for the API, and Amazon S3 for the database.
AnswerB

Cognito handles user authentication, API Gateway with Lambda provides a fully managed REST API that scales automatically, and DynamoDB offers serverless NoSQL storage. All three scale to zero and bill per request, matching the unpredictable traffic and cost-minimisation constraint.

Why this answer

The requirement is a serverless backend with authentication, REST API, NoSQL storage, unpredictable traffic, and minimized cost. Amazon Cognito provides managed user authentication, API Gateway with Lambda provides a fully serverless REST API that scales automatically, and DynamoDB is a serverless NoSQL database with on-demand capacity. This combination is fully serverless, scales with traffic, and charges only for usage, matching all requirements.

Exam trap

SAP-C02 often tests the misconception that RDS or S3 can serve as a NoSQL database; candidates must recognize that DynamoDB is the serverless NoSQL choice and that EC2/ALB breaks the serverless and cost-minimization requirements.

How to eliminate wrong answers

Option A is wrong because EC2 instances behind an ALB are not serverless; they require provisioning, patching, and incur costs even at idle, which is not cost-effective for unpredictable traffic. Option C is wrong because Amazon RDS is a relational database, not NoSQL, and is not serverless in the same way (Aurora Serverless exists but RDS standard requires provisioning); the question specifies NoSQL. Option D is wrong because Amazon S3 is object storage, not a NoSQL database; it lacks the query and item-level access patterns required for a mobile app's data store.

261
MCQmedium

A company is designing a data lake on AWS using Amazon S3. They need to query the data using standard SQL without moving it to a separate analytics store. Which AWS service should they use?

A.Amazon Athena
B.AWS Glue
C.Amazon QuickSight
D.Amazon Redshift Spectrum
AnswerA

Amazon Athena queries data directly in Amazon S3 using standard SQL, with no loading or transformation into a separate analytics store. This satisfies the stem's requirement to query the S3 data lake in place, since Athena reads S3 objects through its schema-on-read approach.

Why this answer

Amazon Athena is a serverless query service that runs standard SQL directly against data in Amazon S3 without loading it into a separate analytics store. It uses the AWS Glue Data Catalog for schema and charges per TB scanned, making it the correct choice for ad-hoc SQL on a data lake. The other services either catalog data, visualize it, or require a Redshift cluster.

Exam trap

SAP-C02 often tests whether candidates confuse the catalog/ETL role of AWS Glue with the query execution role of Athena — Glue catalogs data, Athena queries it.

How to eliminate wrong answers

Option B is wrong because AWS Glue is a serverless ETL and data catalog service — it discovers, catalogs, and transforms data but does not itself execute SQL queries against S3. Option C is wrong because Amazon QuickSight is a BI visualization tool that consumes data from Athena, Redshift, or other sources; it does not query S3 directly with SQL. Option D is wrong because Amazon Redshift Spectrum requires an Amazon Redshift cluster to be provisioned and running, which contradicts the requirement to avoid a separate analytics store.

262
MCQmedium

A company has an S3 bucket with server-side encryption using S3-Managed Keys (SSE-S3). The IAM policy shown in the exhibit is attached to a user. When the user attempts to download an object using the AWS CLI with no encryption headers, the request fails. What is the MOST likely reason?

A.The object is encrypted with SSE-KMS, not SSE-S3.
B.The user does not have the s3:GetObject permission.
C.The bucket has a bucket policy that denies all requests.
D.The policy condition requires the encryption header in the request.
AnswerD

The IAM policy's condition key evaluates request headers, so a CLI download sent without the required encryption header fails the condition and is denied. SSE-S3 itself needs no client headers, confirming the policy — not the bucket's default encryption — blocks the request.

Why this answer

The IAM policy attached to the user includes a condition that requires the presence of the `x-amz-server-side-encryption-customer-algorithm` header on the request. This header is used for SSE-C (server-side encryption with customer-provided keys) and is the only encryption header a client can supply on a GetObject request. When the user issues a download via the AWS CLI without specifying this header, the condition is not satisfied and the request is denied.

Note that SSE-S3 objects do not require any encryption header on GET requests by default, but an IAM policy can still impose such a condition, causing the request to fail if the header is omitted.

Exam trap

Candidates often assume that encryption headers are only required for uploads, but IAM and bucket policies can also require headers like `x-amz-server-side-encryption-customer-algorithm` for GET requests, even if the bucket uses SSE-S3. This trap highlights the importance of understanding all S3 condition keys.

How to eliminate wrong answers

Option A is wrong because the bucket is configured with SSE-S3, and the question states the object is encrypted with SSE-S3; there is no indication of SSE-KMS. Option B is wrong because the IAM policy explicitly grants `s3:GetObject` permission, so the user has that permission. Option C is wrong because there is no mention of a bucket policy that denies all requests; the failure is due to the condition in the IAM policy, not a blanket denial.

263
MCQmedium

A company is building a serverless data processing pipeline. Data is uploaded to an S3 bucket, which triggers a Lambda function to transform the data and store the result in another S3 bucket. The Lambda function needs to access a VPC-hosted database for enrichment. What is the MOST secure way to allow the Lambda function to access the VPC resources?

A.Assign a public IP to the Lambda function and route through an Internet Gateway.
B.Configure the Lambda function to access the VPC and use a VPC endpoint for S3.
C.Use Lambda@Edge to process data at the edge location.
D.Place the Lambda function in a public subnet and use a NAT Gateway.
AnswerB

Attaching the Lambda function to private subnets lets it reach the VPC-hosted database, while a gateway VPC endpoint for S3 keeps traffic to the bucket on the AWS network, avoiding NAT gateways and internet exposure.

Why this answer

It allows the Lambda function to be attached to a VPC, enabling it to access the VPC-hosted database securely over private IP addresses. Additionally, using a VPC endpoint for S3 ensures that data transfer between Lambda and the S3 buckets remains within the AWS network, avoiding public internet exposure and reducing data transfer costs.

Exam trap

The trap here is that candidates may think Lambda functions can be assigned public IPs or placed in public subnets like EC2 instances, but Lambda's VPC integration uses ENIs and requires private subnets, and the most secure way to access S3 from within a VPC is via a VPC endpoint, not a NAT Gateway.

How to eliminate wrong answers

Option A is wrong because assigning a public IP to a Lambda function is not supported; Lambda functions cannot have public IPs, and routing through an Internet Gateway would expose traffic to the public internet, violating security best practices. Option C is wrong because Lambda@Edge is designed for content distribution and edge processing with CloudFront, not for accessing VPC-hosted databases, and it cannot be configured to access VPC resources. Option D is wrong because placing a Lambda function in a public subnet is not possible; Lambda functions are attached to VPC subnets but do not have public IPs, and using a NAT Gateway would still route traffic through the public internet for S3 access, which is less secure and more costly than using a VPC endpoint.

264
MCQhard

A company is designing a new real-time analytics platform that processes streaming data from IoT devices. The data must be ingested, processed with windowed aggregations, and stored in Amazon S3 for long-term analytics. The solution must handle late-arriving data and provide exactly-once processing semantics. Which combination of AWS services should the architect use?

A.Use Amazon Kinesis Data Firehose to ingest data and AWS Glue for processing.
B.Use Amazon EMR with Spark Streaming to process data from Kinesis Data Streams.
C.Use AWS Lambda to process records from Kinesis Data Streams and store in S3.
D.Use Amazon Kinesis Data Analytics for Apache Flink to process data from Kinesis Data Streams and output to S3.
AnswerD

Apache Flink on Kinesis Data Analytics provides event-time processing with watermarks, enabling windowed aggregations that correctly handle late-arriving IoT records, and its checkpointing delivers exactly-once semantics. Kinesis Data Streams ingests the stream, while the Flink S3 connector writes aggregated results for long-term analytics, satisfying every stated constraint.

Why this answer

Amazon Kinesis Data Analytics for Apache Flink provides built-in support for windowed aggregations, exactly-once processing semantics, and handling late-arriving data via allowed lateness and watermarking. It can output processed results directly to Amazon S3 using a Flink sink, meeting all requirements for a real-time analytics platform.

Exam trap

The trap here is that candidates often choose AWS Lambda or Kinesis Data Firehose for simplicity, overlooking the need for stateful windowed aggregations and exactly-once processing, which are not natively supported by those services.

How to eliminate wrong answers

Option A is wrong because Kinesis Data Firehose is a near-real-time ingestion service that does not support custom windowed aggregations or exactly-once processing; it delivers data with at-least-once semantics. Option B is wrong because Amazon EMR with Spark Streaming can process streaming data but does not natively provide exactly-once processing semantics without additional configuration (e.g., checkpointing and idempotent sinks), and it is not the simplest managed service for this use case. Option C is wrong because AWS Lambda processes records from Kinesis Data Streams but has a maximum execution timeout of 15 minutes and does not support stateful windowed aggregations or exactly-once processing; it is designed for lightweight, stateless transformations.

265
Multi-Selecteasy

A company is designing a new cloud-native application on AWS. The application will use a microservices architecture and requires a way to manage configuration data and secrets. Which THREE AWS services can be used to meet these requirements? (Choose THREE.)

Select 3 answers
A.AWS Secrets Manager
B.AWS Systems Manager Parameter Store
C.AWS AppConfig
D.Amazon DynamoDB
E.Amazon S3
AnswersA, B, C

AWS Secrets Manager stores and rotates credentials, API keys and database passwords, directly satisfying the secrets requirement. Its native rotation via Lambda and fine-grained IAM and resource policies suit microservices that must retrieve secrets at runtime rather than embedding them, which the stem's cloud-native constraint demands.

Why this answer

AWS Secrets Manager (A) is correct because it is purpose-built to store, rotate, and retrieve secrets such as database credentials and API keys via API calls, which fits managing secrets in a microservices application. AWS Systems Manager Parameter Store (B) is correct because it provides centralized, hierarchical storage for configuration data and secrets, with SecureString parameters encrypted by KMS, and integrates natively with AWS services and applications. AWS AppConfig (C) is correct because it is a feature of Systems Manager designed to create, validate, deploy, and roll back application configuration updates dynamically, which suits managing configuration for microservices.

Amazon DynamoDB (D) is not a configuration or secrets management service; it is a NoSQL database, so using it for this purpose would be a custom, non-purpose-built solution. Amazon S3 (E) is object storage and, while it can hold files, it lacks native secret rotation, hierarchical parameter management, and configuration deployment/validation features required here.

Exam trap

SAP-C02 often tests whether candidates can distinguish purpose-built configuration/secrets services from general-purpose storage like S3 or DynamoDB, which lack native rotation and deployment features.

266
MCQhard

A company is designing a multi-region active-active architecture for a web application using Amazon Route 53 latency-based routing. The application runs on EC2 instances in Auto Scaling groups with Application Load Balancers in each region. The application uses an Amazon Aurora global database for its data tier. The architecture must provide the lowest possible RTO and RPO for regional failures. What should the company do to meet these requirements?

A.Configure Amazon RDS for MySQL with a cross-Region read replica and automatic failover.
B.Use Route 53 health checks to detect regional failure and automatically update the Aurora Global Database endpoint.
C.Use the Aurora Global Database failover capability to promote the secondary region to primary.
D.Use Amazon RDS Multi-AZ with synchronous replication across Regions.
AnswerC

Aurora Global Database keeps the secondary cluster continuously replicated with sub-second lag, so promoting it to primary writer achieves the lowest RTO and RPO for a regional failure. This satisfies the active-active requirement without rebuilding the data tier.

Why this answer

Amazon Aurora Global Database provides a managed cross-Region failover capability that can promote a secondary region to primary with an RTO of as low as 1 minute and an RPO of typically less than 1 second, meeting the lowest possible RTO and RPO requirements for regional failures in an active-active architecture. This is achieved through storage-level replication that is asynchronous but very low latency, and the failover operation is a single API call or can be automated via Route 53 health checks, ensuring minimal data loss and downtime.

Exam trap

The trap here is that candidates often confuse Amazon RDS Multi-AZ (which is single-Region) with cross-Region replication, or assume that Route 53 health checks alone can handle the failover without understanding that the database failover must be explicitly managed via Aurora Global Database's promotion capability.

How to eliminate wrong answers

Option A is wrong because Amazon RDS for MySQL with a cross-Region read replica does not support automatic failover; you must manually promote the read replica, resulting in higher RTO, and replication is asynchronous with potential for data loss (higher RPO). Option B is wrong because Route 53 health checks can detect regional failure and update DNS records, but they do not directly manage the Aurora Global Database endpoint; the failover must be initiated separately via the Aurora Global Database failover capability, and simply updating the endpoint does not promote the secondary region to primary. Option D is wrong because Amazon RDS Multi-AZ is designed for high availability within a single Region using synchronous replication, not across Regions; cross-Region synchronous replication is not supported, and Multi-AZ does not provide cross-Region failover.

267
Multi-Selectmedium

A company is designing a data lake on Amazon S3. Data is ingested from multiple sources and stored as Parquet files partitioned by date. The company needs to ensure that only authorized users can access the data, and that the data is encrypted at rest. Which TWO actions should the company take to meet these requirements? (Choose TWO.)

Select 2 answers
A.Enable default encryption with SSE-KMS on the S3 bucket.
B.Use client-side encryption before uploading to S3.
C.Enable S3 server access logging.
D.Use a bucket ACL to grant access to the data lake.
E.Configure an S3 bucket policy that allows access only from specific IAM roles.
AnswersA, E

SSE-KMS default encryption ensures every object written to the bucket is encrypted at rest using AWS KMS keys, satisfying the encryption requirement. It also enables granular key policies and audit trails via CloudTrail, supporting control over who can decrypt the data lake contents.

Why this answer

Option A is correct because enabling default encryption with SSE-KMS on the S3 bucket ensures all objects are encrypted at rest using AWS KMS-managed keys, satisfying the encryption requirement without relying on each uploader to set encryption headers. Option E is correct because an S3 bucket policy that allows access only from specific IAM roles enforces least-privilege authorization, ensuring that only the intended IAM principals can read or write the Parquet data. Option B is not required because server-side encryption with SSE-KMS already meets the encryption-at-rest requirement, and client-side encryption adds key-management complexity without being mandated.

Option C is incorrect because S3 server access logging only records request activity for auditing; it does not control access or encrypt data. Option D is incorrect because bucket ACLs are legacy, coarse-grained access mechanisms and cannot express the fine-grained, role-based authorization that a bucket policy provides.

Exam trap

The trap is selecting client-side encryption or ACLs as primary controls when the question asks for centralized encryption and role-based access — SSE-KMS and bucket policies are the AWS-recommended best practices.

268
MCQeasy

A solutions architect is designing a web application that will run on Amazon EC2 instances behind an Application Load Balancer (ALB). The application requires that users' session data be stored and made available across all instances. Which solution is MOST cost-effective and scalable?

A.Use Amazon ElastiCache for Redis to store session data
B.Store session data on an Amazon EBS volume attached to each instance
C.Store session data in an Amazon RDS database
D.Enable sticky sessions (session affinity) on the ALB
AnswerA

ElastiCache for Redis stores session state in an in-memory, multi-AZ replicated cluster reachable by every EC2 instance, so sessions survive instance replacement and scale horizontally. This avoids the cost and write-contention of a relational database or the latency of per-instance storage.

Why this answer

Amazon ElastiCache for Redis provides a fully managed, in-memory data store that is ideal for storing session state externally from the EC2 instances. This decouples session data from the compute layer, allowing any instance to retrieve the same session data regardless of which instance originally handled the request. Redis offers sub-millisecond latency, built-in replication, and automatic failover, making it both highly scalable and cost-effective for session management at scale.

Exam trap

The trap here is that candidates often confuse sticky sessions (session affinity) as a valid solution for session persistence, but it actually undermines scalability and fault tolerance by tying a user to a single instance, which is the opposite of what a stateless, horizontally scalable architecture requires.

How to eliminate wrong answers

Option B is wrong because storing session data on an EBS volume attached to each instance creates a single point of failure and prevents instances from sharing session data; EBS volumes are tied to a single Availability Zone and cannot be concurrently accessed by multiple instances. Option C is wrong because using Amazon RDS for session data introduces unnecessary relational database overhead, higher latency for simple key-value lookups, and increased cost compared to an in-memory cache like Redis. Option D is wrong because enabling sticky sessions (session affinity) on the ALB forces traffic from a user to the same instance, which reduces scalability and defeats the purpose of horizontal scaling; if that instance fails, the session data is lost.

269
MCQeasy

A company is designing a new application that will be deployed on EC2 instances across multiple Availability Zones. The application must be highly available and must automatically recover from instance failures. Which solution should the architect recommend?

A.Use a single EC2 instance in one AZ and a standby instance in another AZ
B.Use AWS Elastic Beanstalk with a single instance environment
C.Use AWS CloudFormation to launch a single instance in each AZ
D.Use an Auto Scaling group with a minimum of two instances across two Availability Zones
AnswerD

An Auto Scaling group spanning two Availability Zones with a minimum of two instances provides both multi-AZ redundancy and automatic replacement of failed instances. This directly satisfies the high availability and automatic failure recovery requirements for the EC2 deployment.

Why this answer

An Auto Scaling group with a minimum of two instances across two Availability Zones ensures that if one instance or an entire AZ fails, the remaining instance continues to serve traffic, and Auto Scaling automatically launches a replacement instance to restore the desired count. This architecture provides both high availability and automatic recovery from instance failures without manual intervention.

Exam trap

The trap here is that candidates often confuse 'high availability' with 'fault tolerance' and assume that simply having two instances in different AZs (Option C) is sufficient, but without an auto-recovery mechanism like Auto Scaling, a failed instance remains down and requires manual remediation.

How to eliminate wrong answers

Option A is wrong because a single active instance with a standby instance in another AZ does not provide automatic recovery; failover to the standby would require manual or custom scripting, and the standby instance is idle, wasting resources. Option B is wrong because AWS Elastic Beanstalk with a single instance environment runs only one EC2 instance, which is a single point of failure and cannot automatically recover from instance failures without additional configuration like a multi-instance environment. Option C is wrong because using AWS CloudFormation to launch a single instance in each AZ creates two independent instances but does not include any health-check or auto-replacement mechanism; if one instance fails, CloudFormation does not automatically replace it, and there is no load balancing or failover logic.

270
Multi-Selectmedium

A company is designing a new serverless application that uses Amazon API Gateway, AWS Lambda, and Amazon DynamoDB. The application must handle sudden spikes in traffic without throttling errors and must provide consistent low-latency responses. The company wants to minimize operational overhead. Which two actions should a solutions architect take to meet these requirements? (Choose two.)

Select 2 answers
A.Use DynamoDB on-demand capacity mode for the table.
B.Configure Lambda provisioned concurrency for the function to reduce cold starts.
C.Configure Lambda function reserved concurrency to ensure sufficient capacity.
D.Configure API Gateway with a usage plan and API keys to limit requests per client.
E.Enable API Gateway caching for the stage to reduce backend requests.
AnswersA, B

DynamoDB on-demand capacity mode automatically scales read and write capacity to handle sudden spikes in traffic without requiring capacity planning. It provides consistent low-latency performance and eliminates the need to manage provisioned throughput, reducing operational overhead. This is ideal for unpredictable workloads.

Why this answer

DynamoDB on-demand capacity mode automatically scales to handle traffic spikes, eliminating the need to provision capacity and reducing operational overhead. Lambda provisioned concurrency pre-warms execution environments, reducing cold starts and ensuring consistent low-latency responses. Together, these actions enable the serverless application to handle sudden spikes without throttling or performance degradation.

Exam trap

The trap here is assuming that reserved concurrency or usage plans help with spiky traffic, when they actually limit or do not address scaling.

271
MCQhard

A company is deploying a new web application on AWS that requires a highly available and scalable architecture. The application consists of a stateless web tier and a stateful database tier. The web tier runs on Amazon EC2 instances behind an Application Load Balancer. The database tier uses Amazon Aurora MySQL. The company expects variable traffic patterns and wants to automatically scale the web tier based on CPU utilization. Additionally, the company wants to ensure that the database can handle increased read traffic without manual intervention. Which combination of actions should the company take?

A.Use an Auto Scaling group with a target tracking scaling policy based on CPU utilization. Enable Aurora Auto Scaling to add read replicas based on CPU or connections.
B.Use an Auto Scaling group with a target tracking scaling policy based on CPU utilization. Use Amazon SQS to queue read requests during peak traffic.
C.Use an Auto Scaling group with a simple scaling policy based on CPU utilization. Use DynamoDB Auto Scaling for the database.
D.Use an Auto Scaling group with a step scaling policy based on CPU utilization. Use ElastiCache Auto Scaling to add cache nodes for read traffic.
AnswerA

Target tracking on CPU scales the stateless web tier automatically with variable load, while Aurora Auto Scaling adds read replicas when CPU or connection thresholds are breached. Together they satisfy both the web-tier scaling and read-capacity requirements without manual intervention.

Why this answer

Option A is correct because it pairs the two native AWS auto-scaling mechanisms that match the stated requirements: an Auto Scaling group with a target tracking policy keeps the stateless web tier's average CPU near a defined target, and Aurora Auto Scaling automatically adds/removes Aurora Replicas when a read-replica-level metric (CPU or connections) crosses a threshold. Both are managed, metric-driven, and require no manual intervention, satisfying the 'variable traffic' and 'increased read traffic' requirements.

Exam trap

SAP-C02 often tests whether candidates confuse 'scaling compute' with 'scaling database reads' — the trap is picking a queue, cache, or DynamoDB option that sounds like it offloads traffic but does not actually add Aurora read capacity.

How to eliminate wrong answers

Option B is wrong because SQS is a message queue for decoupling asynchronous workloads, not a mechanism for scaling read capacity on Aurora; queuing read requests would add latency and does not increase database read throughput. Option C is wrong because a simple scaling policy only triggers on a single CloudWatch alarm threshold with cooldowns and does not track a target value the way target tracking does, and DynamoDB Auto Scaling is irrelevant to an Aurora MySQL database. Option D is wrong because step scaling requires manually defined alarm thresholds and adjustment steps, and ElastiCache Auto Scaling scales cache nodes, not Aurora read replicas, so it does not address database read traffic.

272
MCQhard

A company is building a real-time analytics platform that ingests data from thousands of IoT devices. The data must be processed in near real-time and stored in a data lake on Amazon S3 for long-term analysis. The company also needs to run complex SQL queries on the streaming data to detect anomalies. The solution must be highly available and scale automatically. Which combination of AWS services should a solutions architect recommend?

A.Use AWS IoT Core to ingest data, AWS Lambda to process each record, and Amazon S3 to store the data directly.
B.Use Amazon Managed Streaming for Apache Kafka (Amazon MSK) to ingest data, Amazon Kinesis Data Analytics for SQL processing, and AWS Lambda to write to Amazon S3.
C.Use Amazon Kinesis Data Streams to ingest data, AWS Glue for SQL processing, and Amazon Kinesis Data Firehose to deliver to Amazon S3.
D.Use AWS IoT Core to ingest data, Amazon Kinesis Data Analytics for SQL processing, and Amazon Kinesis Data Firehose to deliver to Amazon S3.
AnswerD

AWS IoT Core ingests device data reliably. Kinesis Data Analytics for SQL allows running continuous SQL queries on streaming data to detect anomalies. Kinesis Data Firehose delivers the processed data to S3. This combination is fully managed, scales automatically, and provides near real-time processing and storage.

Why this answer

AWS IoT Core handles IoT device ingestion at scale. Kinesis Data Analytics for SQL enables real-time SQL queries on streaming data for anomaly detection. Kinesis Data Firehose reliably delivers the processed data to S3.

This combination is fully managed, scales automatically, and meets the near real-time and storage requirements.

Exam trap

The trap here is assuming that any processing service like AWS Glue or Lambda can handle real-time streaming SQL, but Glue is batch-oriented and Lambda lacks built-in SQL capabilities.

273
Multi-Selectmedium

A company is designing a new application that will run on Amazon EC2 instances in an Auto Scaling group. The application must be able to distribute incoming traffic across multiple instances. Which TWO AWS services can be used for this purpose? (Choose TWO.)

Select 2 answers
A.Amazon CloudFront
B.AWS Global Accelerator
C.Network Load Balancer
D.Application Load Balancer
E.Amazon Route 53
AnswersC, D

Network Load Balancer operates at layer 4, distributing TCP and UDP traffic across targets in the Auto Scaling group by flow hash. It satisfies the traffic-distribution requirement while preserving the client source IP address and supporting extreme throughput and low latency.

Why this answer

Option C (Network Load Balancer) is correct because it is an Elastic Load Balancing service that operates at Layer 4 (TCP/UDP/TLS) and distributes incoming traffic across targets such as EC2 instances in an Auto Scaling group, using listeners and target groups. Option D (Application Load Balancer) is correct because it is an Elastic Load Balancing service that operates at Layer 7 (HTTP/HTTPS) and also distributes incoming traffic across EC2 instances registered in target groups within an Auto Scaling group. Both load balancers integrate with Auto Scaling groups so that instances added or removed by scaling are automatically registered or deregistered as targets.

Option A (Amazon CloudFront) is a content delivery network that caches and serves content from edge locations, not a load balancer for distributing traffic across EC2 instances. Option B (AWS Global Accelerator) improves global reachability and performance by routing traffic over the AWS global network to endpoints, but it is not the primary service for distributing traffic across multiple EC2 instances in an Auto Scaling group. Option E (Amazon Route 53) is a DNS service that can perform DNS-based routing, but it does not distribute incoming traffic across EC2 instances at the connection level like a load balancer.

Exam trap

The SAP-C02 exam often tests the distinction between services that perform actual load balancing (ALB, NLB) versus services that provide DNS-based routing (Route 53) or content delivery (CloudFront) or global traffic optimization (Global Accelerator), leading candidates to mistakenly select Route 53 or CloudFront as load balancers.

274
Multi-Selecteasy

A company is designing a new application that will process images uploaded by users. The application must automatically resize images and store them in Amazon S3. The solution should be serverless and event-driven. Which THREE AWS services should be used together? (Choose three.)

Select 3 answers
A.Amazon S3
B.AWS Lambda
C.Amazon EC2
D.Amazon Simple Queue Service (SQS)
E.Amazon S3 Event Notification
AnswersA, B, E

Amazon S3 provides the event source: uploads emit `s3:ObjectCreated:*` notifications that trigger downstream compute, satisfying the event-driven requirement without polling. It also serves as the durable storage target for resized images, meeting the serverless constraint since no servers are provisioned or managed for either ingestion or persistence.

Why this answer

Amazon S3 (A) is correct because it serves as the storage layer where users upload the original images and where the resized images are ultimately stored, making it the foundation of this event-driven, serverless design. AWS Lambda (B) is correct because it provides the serverless compute that runs the image-resizing code in response to events, eliminating the need to manage servers. Amazon S3 Event Notification (E) is correct because it is the event source that detects object-created events (e.g., s3:ObjectCreated:*) on the upload bucket and triggers the Lambda function, enabling the required event-driven behavior.

Amazon EC2 (C) is not appropriate because it requires provisioning and managing virtual servers, which contradicts the serverless requirement. Amazon Simple Queue Service (D) is not needed here because S3 Event Notifications can invoke Lambda directly, so no queue is required to decouple the upload from the processing in this scenario.

Exam trap

The trap is over-engineering the solution by adding SQS for 'decoupling' when the question explicitly asks for a serverless, event-driven design that only needs S3, Lambda, and S3 Event Notifications.

275
MCQhard

A solutions architect attempts to create this stack but receives an error: "Value of property SecurityGroups must be a list of strings". What is the likely cause?

A.The SecurityGroups property should be a list, but the YAML specifies a single reference incorrectly.
B.The security group ingress rule allows SSH from anywhere.
C.There is a circular dependency between the EC2 instance and the security group.
D.The AMI ID is invalid.
AnswerA

CloudFormation expects SecurityGroups as a YAML list, so supplying a bare scalar reference rather than a sequence produces the type error. Correcting the syntax to a list of strings resolves the validation failure described in the stem.

Why this answer

The error 'Value of property SecurityGroups must be a list of strings' occurs because the YAML template specifies the SecurityGroups property as a single string (e.g., !Ref MySecurityGroup) instead of a list of strings (e.g., [!Ref MySecurityGroup]). In AWS CloudFormation, the SecurityGroups property for an EC2 instance expects a list of security group IDs or names, even if only one security group is provided. The YAML syntax must wrap the reference in square brackets to form a list, or the template will fail validation.

Exam trap

The trap here is that candidates may confuse the SecurityGroups property with SecurityGroupIds, or assume that a single reference can be passed as a scalar, but CloudFormation strictly enforces the list type for SecurityGroups even when only one security group is used.

How to eliminate wrong answers

Option B is wrong because allowing SSH from anywhere (0.0.0.0/0) is a security concern but does not cause a 'list of strings' error; it would only trigger a security review or a different validation error if the template explicitly forbids it. Option C is wrong because a circular dependency between the EC2 instance and the security group would cause a stack creation failure with a 'circular dependency' error, not a type mismatch error about SecurityGroups. Option D is wrong because an invalid AMI ID would produce an error like 'AMI ID not found' or 'InvalidAMIID.NotFound', not a property type validation error.

276
Drag & Dropmedium

Drag and drop the steps to migrate an on-premises MySQL database to Amazon RDS using AWS DMS 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 create the replication instance, then endpoints, then the migration task, start it, and finally cut over.

277
MCQmedium

A financial services company runs a critical application on Amazon EC2 instances behind an Application Load Balancer (ALB). The application is deployed across multiple Availability Zones. The company recently experienced a DDoS attack that overwhelmed the ALB and caused downtime. The security team wants to implement a solution that can absorb DDoS attacks at the edge and only forward legitimate traffic to the ALB. Additionally, the company needs to protect sensitive data in transit using TLS 1.3. What should the solutions architect do?

A.Deploy Amazon CloudFront in front of the ALB with AWS Shield Advanced and enforce TLS 1.3.
B.Use AWS WAF with rate-based rules and associate it with the ALB.
C.Use an AWS Network Firewall and configure stateful rules to block malicious IPs.
D.Enable AWS Shield Standard and use security groups to restrict traffic.
AnswerA

CloudFront absorbs volumetric DDoS at edge locations, forwarding only legitimate traffic to the ALB, satisfying the edge-absorption constraint. Shield Advanced adds enhanced mitigation and cost protection. CloudFront supports TLS 1.3 via security policies, meeting the in-transit encryption requirement. ALB alone cannot absorb edge-level attacks.

Why this answer

Amazon CloudFront is a global content delivery network that caches content at edge locations, absorbing volumetric DDoS attacks before they reach the origin ALB. AWS Shield Advanced provides enhanced DDoS protection with 24/7 access to the AWS DDoS Response Team (DRT) and cost protection, and CloudFront supports TLS 1.3 for encryption in transit. Together, they meet the requirements of edge absorption and TLS 1.3 enforcement.

Exam trap

SAP-C02 often tests the misconception that AWS WAF or Shield Standard alone can absorb large-scale DDoS attacks, but only CloudFront with Shield Advanced provides edge absorption and advanced mitigation.

How to eliminate wrong answers

Option B is wrong because AWS WAF rate-based rules only block requests exceeding a threshold at the ALB, but they do not absorb large-scale DDoS attacks at the edge; the ALB can still be overwhelmed. Option C is wrong because AWS Network Firewall is a VPC-level firewall that inspects traffic after it enters the VPC, not at the edge, and it does not provide DDoS absorption or TLS 1.3 termination. Option D is wrong because AWS Shield Standard is automatically enabled and only protects against common network-layer attacks; it does not provide advanced DDoS mitigation or edge absorption, and security groups cannot mitigate volumetric attacks.

278
MCQmedium

A company is designing a new application that will run on Amazon ECS with Fargate. The application must process messages from an Amazon SQS queue and store results in an Amazon DynamoDB table. The workload is unpredictable and can scale from 0 to thousands of messages per second. What is the MOST cost-effective and scalable architecture?

A.Run an Amazon ECS service with Fargate that polls the SQS queue and writes to DynamoDB. Configure auto scaling based on CPU utilization.
B.Use an Amazon ECS service with Fargate and a target tracking scaling policy based on SQS queue depth.
C.Use Amazon Kinesis Data Streams to ingest messages and an AWS Lambda function to process and write to DynamoDB.
D.Use an AWS Lambda function with an SQS trigger to process messages and write to DynamoDB.
AnswerD

Lambda with an SQS trigger scales automatically from zero to thousands of messages per second and charges only per invocation, eliminating idle Fargate task costs. It writes directly to DynamoDB, making it the most cost-effective and scalable choice for unpredictable workloads.

Why this answer

AWS Lambda with an SQS event source mapping is the most cost-effective and scalable choice because Lambda scales automatically and nearly instantly with the number of messages, charging only per invocation and execution time — with no cost when idle. It natively integrates with SQS (polling in batches, handling visibility timeouts, and deleting messages on success) and can write to DynamoDB with built-in retry and DLQ support. For a workload that can drop to zero, Lambda avoids the baseline cost of running an always-on ECS service.

ECS with Fargate, by contrast, requires at least one running task (or complex scaling to zero) and adds management overhead without a cost advantage at this scale.

Exam trap

SAP-C02 often tests the misconception that ECS/Fargate with auto scaling is always the most cost-effective for variable workloads, when in fact Lambda's scale-to-zero and per-invocation pricing make it the better choice for unpredictable, queue-driven processing.

How to eliminate wrong answers

Option A is wrong because CPU-based auto scaling on ECS/Fargate does not correlate well with SQS queue depth — the service may not scale out fast enough when messages spike, and it cannot scale to zero, so it is neither the most scalable nor the most cost-effective. Option B is wrong because although target tracking on SQS queue depth is better than CPU scaling, an ECS/Fargate service still cannot scale to zero and incurs cost for idle tasks; it also requires more operational overhead than Lambda's native SQS integration. Option C is wrong because Kinesis Data Streams is designed for ordered, high-throughput streaming with provisioned or on-demand shards, not for a simple SQS-style queue; it adds unnecessary cost and complexity, and Lambda with an SQS trigger is simpler and cheaper for this use case.

279
MCQhard

A company is designing a serverless application that uses AWS Lambda to process events from Amazon DynamoDB Streams. The Lambda function updates an Amazon RDS for MySQL database. The company expects a high volume of updates and is concerned about the Lambda function causing too many connections to the database. How should the company design the solution to manage the database connection pool effectively?

A.Increase the Lambda function timeout and use a single database connection per function instance.
B.Use Amazon RDS Proxy to pool database connections, and configure the Lambda function to connect through the proxy.
C.Use a singleton Lambda function with a reserved concurrency of 1 to ensure only one connection is used.
D.Use a Lambda function that batches records from DynamoDB Streams and uses a single database connection per batch.
AnswerB

RDS Proxy maintains a shared pool of database connections and multiplexes Lambda invocations onto them, so each concurrent function no longer opens its own MySQL connection. This directly addresses the stem's concern about excessive connections during high-volume updates.

Why this answer

Amazon RDS Proxy sits between the Lambda function and the RDS database, maintaining a pool of established connections. When Lambda invocations scale up, they reuse connections from the pool instead of opening new ones, preventing the database from being overwhelmed. This is the recommended AWS pattern for serverless applications with high concurrency and relational databases.

Exam trap

The trap here is that candidates often think batching or reducing concurrency is the solution, but the real challenge is managing connection reuse under elastic scaling, which only a dedicated proxy like RDS Proxy can solve without sacrificing throughput.

How to eliminate wrong answers

Option A is wrong because increasing the Lambda timeout does not reduce the number of connections; each concurrent invocation still opens its own connection, and a single connection per instance does not scale safely under high concurrency. Option C is wrong because setting reserved concurrency to 1 cripples throughput and defeats the purpose of using DynamoDB Streams, which expects parallel processing; it also does not address connection pooling, as the single instance still opens one connection per invocation. Option D is wrong because batching records does not reduce the number of concurrent Lambda invocations; each batch still runs in its own instance and opens a separate database connection, so the connection count remains high.

280
MCQmedium

A company is designing a new microservices application on AWS. The application consists of several services that need to communicate asynchronously. One service generates orders and sends them to a processing service. The order volume can vary significantly, and the processing service must scale independently. The company wants to use a managed service to decouple the services and ensure that messages are not lost. The processing service is written in Python and runs on AWS Lambda. The solutions architect needs to design the message delivery mechanism. The architect decides to use Amazon SQS. However, the Lambda function sometimes fails to process a message due to a transient error, and the message should be retried. After a maximum of three retries, the message should be moved to a dead-letter queue for analysis. Which configuration should the architect use?

A.Configure the SQS DLQ with a redrive policy that allows messages to be sent back to the source queue after 3 retries.
B.Configure the SQS queue with a visibility timeout of 6 minutes and a redrive policy with maxReceiveCount of 3, pointing to a DLQ.
C.Configure the SQS queue with a visibility timeout of 30 seconds and a redrive policy with maxReceiveCount of 3, pointing to a DLQ.
D.Configure Lambda with a reserved concurrency of 1 and set the SQS queue's redrive policy to maxReceiveCount of 3.
AnswerB

The redrive policy's maxReceiveCount of 3 moves a message to the DLQ after three failed receives, satisfying the retry limit. The visibility timeout must exceed the Lambda function's execution time so the message stays hidden during processing, preventing premature redelivery.

Why this answer

The stem does not state the Lambda function timeout, so the visibility timeout cannot be determined from the given information. The redrive policy with maxReceiveCount of 3 correctly moves messages to a DLQ after three failed receives, but the visibility timeout must be at least the Lambda function timeout to avoid duplicate processing. Since the function timeout is unspecified, the question should either provide the Lambda timeout or focus on the redrive policy configuration rather than an arbitrary visibility timeout value.

Exam trap

The trap is assuming a visibility timeout value without knowing the Lambda function timeout, or misunderstanding that the redrive policy sends messages to a DLQ rather than back to the source queue.

How to eliminate wrong answers

Option A is wrong because a redrive policy does not send messages back to the source queue; it sends them to a DLQ. Option C is wrong because a visibility timeout of 30 seconds might be too short if the Lambda function takes longer, causing duplicate processing. Option D is wrong because reserved concurrency of 1 does not affect retry logic and could throttle processing, but the redrive policy is correct; however, the visibility timeout is not specified, and the main issue is the retry configuration.

281
MCQeasy

A retail company is deploying a new static website on AWS. The website consists of HTML, CSS, JavaScript, and image files. The company wants to serve the content globally with low latency, minimize cost, and avoid managing any servers. The website must use a custom domain name with HTTPS. Which solution should a solutions architect recommend?

A.Host the website on Amazon S3 with static website hosting enabled, and use Amazon Route 53 with a public hosted zone to serve the content over HTTPS directly from the S3 website endpoint.
B.Host the website on Amazon S3 with static website hosting enabled, and use Amazon CloudFront with an AWS Certificate Manager (ACM) certificate for the custom domain.
C.Host the website on AWS Elastic Beanstalk with a load-balanced environment, and configure HTTPS using a self-signed certificate.
D.Host the website on Amazon EC2 instances behind an Application Load Balancer, and use an ACM certificate for HTTPS termination.
AnswerB

S3 static website hosting serves the files without any servers, and CloudFront caches content at edge locations worldwide for low latency. ACM provides a free public certificate for the custom domain, which can be associated with the CloudFront distribution. This combination meets the global low-latency, cost, no-server, and HTTPS requirements.

Why this answer

A static website on S3 with CloudFront provides serverless hosting, global edge caching for low latency, and cost efficiency. ACM issues a free certificate for the custom domain, enabling HTTPS on the CloudFront distribution. This combination meets all requirements without managing servers and is the standard AWS solution for static websites.

Exam trap

The trap here is assuming that an S3 static website endpoint itself can serve content over HTTPS with a custom domain.

282
MCQhard

A company is designing a disaster recovery solution for a critical database using Amazon RDS Multi-AZ. However, they also need to protect against regional failures. Which additional AWS service should they use?

A.RDS Multi-AZ in the same region
B.RDS Cross-Region Read Replicas
C.Amazon S3
D.AWS Database Migration Service
AnswerB

RDS Cross-Region Read Replicas asynchronously copy data to a different Region, providing a standalone database that can be promoted during a regional outage. This satisfies the protection-against-regional-failures constraint that Multi-AZ, confined to one Region, cannot address.

Why this answer

RDS Multi-AZ provides high availability within a single region by synchronously replicating data to a standby instance in a different Availability Zone. To protect against a regional failure, you need a cross-region disaster recovery solution. RDS Cross-Region Read Replicas asynchronously replicate data to a different AWS Region, allowing you to promote the replica to a standalone primary database in the event of a regional outage.

Exam trap

The trap here is that candidates confuse Multi-AZ (which is high availability within a region) with cross-region disaster recovery, assuming Multi-AZ alone provides regional protection.

How to eliminate wrong answers

Option A is wrong because RDS Multi-AZ in the same region only protects against Availability Zone failures, not regional failures; it does not replicate data across AWS Regions. Option C is wrong because Amazon S3 is an object storage service and cannot serve as a direct disaster recovery target for a relational database; it lacks native database replication and failover capabilities. Option D is wrong because AWS Database Migration Service (DMS) is designed for one-time or ongoing migrations, not for automated, low-RPO disaster recovery with automatic failover; it requires manual intervention to promote a target database.

283
MCQhard

A company is designing a new data lake solution on AWS using Amazon S3 as the storage layer. The data lake will be used by multiple teams for analytics and machine learning. The company needs to enforce fine-grained access control at the object level, enable auditing of data access, and ensure that sensitive data is masked for unauthorized users. Which combination of AWS services should be used?

A.Use S3 bucket policies and S3 access logs for auditing.
B.Use Amazon Macie to discover sensitive data and apply S3 bucket policies to restrict access.
C.Use IAM policies with condition keys and enable AWS CloudTrail for auditing.
D.Use AWS Lake Formation for fine-grained access control and auditing, and Amazon S3 Object Lambda to mask data on the fly.
AnswerD

AWS Lake Formation enforces column-, row- and cell-level permissions at the table level, satisfying the fine-grained access and audit requirements, while Amazon S3 Object Lambda intercepts GET requests to redact or mask sensitive fields before delivery, meeting the masking constraint without duplicating data.

Why this answer

AWS Lake Formation provides fine-grained access control at the column, row, and cell level for data in S3, and it integrates with AWS CloudTrail for auditing data access. Amazon S3 Object Lambda can transform data on the fly, such as masking sensitive fields, before returning it to the requester, meeting the requirement to mask data for unauthorized users.

Exam trap

The trap here is that candidates often assume IAM policies or S3 bucket policies alone can achieve fine-grained access control, but they lack the column/row-level granularity and dynamic data masking that Lake Formation and S3 Object Lambda provide.

How to eliminate wrong answers

Option A is wrong because S3 bucket policies alone cannot enforce fine-grained access control at the object level (e.g., column or row level), and S3 access logs provide basic request logging but lack the granular auditing and data masking capabilities required. Option B is wrong because Amazon Macie discovers sensitive data but does not enforce access control or mask data; S3 bucket policies are too coarse for fine-grained control and cannot mask data on the fly. Option C is wrong because IAM policies with condition keys can restrict access based on attributes like tags or IP, but they cannot provide column/row-level permissions or mask sensitive data; AWS CloudTrail logs API calls but does not enable real-time data masking.

284
MCQhard

A company is migrating a legacy monolithic application to a microservices architecture on AWS. The application has a relational database with complex queries. The team wants to minimize changes to the existing codebase. Which database migration strategy should be recommended?

A.Use Amazon RDS for MySQL or PostgreSQL with read replicas.
B.Use Amazon Aurora Serverless to reduce management.
C.Store data in Amazon S3 and use Athena for queries.
D.Migrate to Amazon DynamoDB for scalability.
AnswerA

RDS for MySQL or PostgreSQL preserves the relational schema and complex SQL, so the application's queries and drivers continue working with minimal code changes. Read replicas offload reporting traffic, and the engine choice matches the existing codebase rather than forcing a rewrite.

Why this answer

Using Amazon RDS with the same database engine (MySQL or PostgreSQL) minimizes code changes, as the application can connect via standard SQL drivers. Read replicas can help with read scaling without altering the codebase. Option B is wrong because Aurora Serverless may require configuration changes and does not necessarily minimize code changes.

Option C is wrong because S3 and Athena are not suitable for transactional relational queries and would require significant architectural changes. Option D is wrong because DynamoDB would require schema redesign and application changes to use NoSQL.

285
MCQmedium

A healthcare company is designing a new application that must store protected health information in Amazon DynamoDB. The compliance team requires that all data be encrypted at rest with a customer-managed AWS KMS key so that key rotation and access can be audited centrally. The application runs on Amazon EC2 instances in a private subnet and must access the table over a private network path. The solutions architect needs to configure encryption and network access. Which combination of steps should the architect take?

A.Create a DynamoDB table with a customer-managed KMS key, and create a gateway VPC endpoint for DynamoDB; attach an endpoint policy that restricts access to the specific table.
B.Create a DynamoDB table with a customer-managed KMS key, and create an interface VPC endpoint for DynamoDB; attach an endpoint policy allowing access to the table.
C.Create a DynamoDB table with a customer-managed KMS key, and configure the application to use the DynamoDB Accelerator (DAX) cluster in the VPC for private access.
D.Create a DynamoDB table with an AWS owned key, and create a VPC endpoint for DynamoDB; use the default endpoint policy.
AnswerA

A customer-managed KMS key satisfies the audit and rotation requirement, and a gateway VPC endpoint provides private connectivity from the VPC to DynamoDB without internet access. An endpoint policy can restrict access to the specific table, adding least-privilege control. This combination meets both encryption and network requirements.

Why this answer

Using a customer-managed KMS key for the DynamoDB table meets the compliance requirement for auditable, rotatable encryption. A gateway VPC endpoint for DynamoDB provides private connectivity from the VPC, and an endpoint policy can restrict access to the specific table, satisfying the private network requirement without exposing traffic to the internet.

Exam trap

The trap here is confusing DynamoDB VPC endpoint types and selecting an interface endpoint, when DynamoDB uses gateway endpoints.

286
MCQhard

A company is designing a new application that will process sensitive financial data. They need to ensure that data at rest is encrypted using customer-provided encryption keys (SSE-C) in Amazon S3. Which action is required to enable this?

A.Use AWS KMS to generate a key
B.Enable default encryption on the bucket
C.Provide the encryption key in the request headers
D.Configure a bucket policy to require SSE-C
AnswerC

SSE-C requires the customer to supply the encryption key with every request rather than storing it in S3; S3 uses the key to encrypt or decrypt the object and then discards it. Passing the key via request headers satisfies the stem's customer-provided-key constraint without AWS retaining it.

Why this answer

SSE-C requires the customer to provide the encryption key in the request headers when uploading or accessing objects. Amazon S3 uses the provided key to encrypt data at rest and then discards the key; the customer is responsible for managing the key lifecycle. This is the only way to enforce customer-provided encryption keys at the object level.

Exam trap

The trap here is that candidates confuse SSE-C with SSE-KMS or SSE-S3, assuming that a bucket policy or default encryption alone can enforce customer-provided keys, when in fact SSE-C requires the key to be explicitly supplied in every request.

How to eliminate wrong answers

Option A is wrong because AWS KMS generates AWS-managed or customer-managed keys (SSE-KMS), not customer-provided keys (SSE-C) that are supplied per request. Option B is wrong because enabling default encryption on the bucket applies SSE-S3 or SSE-KMS automatically, not SSE-C, which requires the key to be sent with each request. Option D is wrong because a bucket policy can require SSE-C (e.g., via a condition key like s3:x-amz-server-side-encryption-customer-algorithm), but it does not enable SSE-C itself; the key must still be provided in the request headers.

287
MCQmedium

A company is designing a new solution to host a static website on AWS. The website content is stored in an Amazon S3 bucket. The company wants to use a custom domain name (e.g., www.example.com) and enforce HTTPS. Which combination of AWS services should the company use?

A.Configure the S3 bucket for static website hosting and attach a custom SSL certificate using AWS Certificate Manager.
B.Use Amazon CloudFront with an SSL certificate from AWS Certificate Manager and point the CloudFront distribution to the S3 bucket.
C.Use Amazon Route 53 with an alias record pointing to the S3 bucket and enable DNSSEC.
D.Use an Application Load Balancer in front of the S3 bucket and attach an SSL certificate from AWS Certificate Manager.
AnswerB

CloudFront terminates HTTPS at the edge using the ACM certificate, then fetches content from the S3 bucket origin. ACM certificates cannot be attached directly to S3 static website endpoints, so CloudFront is required to enforce HTTPS on the custom domain.

Why this answer

Amazon CloudFront can terminate HTTPS at the edge using an SSL certificate from AWS Certificate Manager (ACM), and it can be configured with an origin pointing to an S3 bucket configured for static website hosting. This combination allows the use of a custom domain name (e.g., www.example.com) via a CloudFront alternate domain name (CNAME) and enforces HTTPS for all client connections, which S3 static website hosting alone cannot natively support.

Exam trap

The trap here is that candidates assume S3 static website hosting can directly serve HTTPS with a custom domain and SSL certificate, but S3 does not support SSL termination or custom certificates on its website endpoint, making a CDN like CloudFront mandatory for HTTPS enforcement.

How to eliminate wrong answers

Option A is wrong because S3 static website hosting does not support attaching a custom SSL certificate directly; S3 only serves HTTP on the bucket's website endpoint, and HTTPS is not available without a front-end service like CloudFront. Option C is wrong because Route 53 with an alias record pointing to an S3 website endpoint does not provide HTTPS termination; DNSSEC only secures DNS queries, not the HTTP connection, and the S3 website endpoint itself does not support HTTPS. Option D is wrong because an Application Load Balancer (ALB) cannot be placed directly in front of an S3 bucket as an origin; ALBs require targets such as EC2 instances, IP addresses, or Lambda functions, not S3 buckets.

288
MCQmedium

A company is designing a new application that will run on Amazon ECS with Fargate. The application needs to output logs to CloudWatch Logs. Which configuration should be used to send logs from the container to CloudWatch?

A.Use the awslogs log driver in the task definition and specify the log group.
B.Install and configure the CloudWatch agent in the container image.
C.Output logs to stdout/stderr and use a Lambda function to push them.
D.Configure a sidecar container running the CloudWatch agent.
AnswerA

The awslogs log driver, configured in the Fargate task definition, streams container stdout and stderr directly to a specified CloudWatch Logs log group. This satisfies the requirement without sidecar containers or host-level agents, which Fargate does not permit, since each task runs on isolated, managed infrastructure.

Why this answer

The awslogs log driver is the native, built-in mechanism for Amazon ECS tasks using the Fargate launch type to send container logs directly to CloudWatch Logs. By specifying the 'awslogs' log driver in the task definition and providing the log group name, ECS automatically streams stdout and stderr from the container to the specified CloudWatch log group without requiring any additional agents or infrastructure.

Exam trap

The trap here is that candidates often over-engineer the solution by thinking a separate agent or sidecar is required for log shipping, when in fact the awslogs log driver is the simplest and most efficient native integration for ECS with Fargate.

How to eliminate wrong answers

Option B is wrong because installing the CloudWatch agent inside the container image is unnecessary and adds complexity; the awslogs log driver handles log shipping natively at the container runtime level. Option C is wrong because using a Lambda function to push logs from stdout/stderr is an overly complex, non-standard approach that introduces latency and potential data loss, whereas the awslogs driver streams logs in real time. Option D is wrong because a sidecar container running the CloudWatch agent is redundant and consumes additional resources; the awslogs log driver is the recommended and simpler method for Fargate tasks.

289
Multi-Selectmedium

A company is building a new application that requires a relational database with high availability across multiple Availability Zones. The database must automatically failover with minimal downtime. Which two AWS services or features meet these requirements?

Select 2 answers
A.Amazon Aurora DB cluster with multiple Availability Zones
B.Amazon RDS Multi-AZ deployment
C.Amazon RDS Single-AZ deployment with automated backups
D.Amazon DynamoDB with global tables
E.Amazon RDS Read Replica
AnswersA, B

An Aurora DB cluster provisions writer and reader instances across multiple Availability Zones, with automatic failover to a reader if the writer fails. Storage is replicated across AZs, meeting the high availability and minimal downtime requirements.

Why this answer

Option A is correct because an Amazon Aurora DB cluster stores data across multiple Availability Zones and automatically fails over to an Aurora Replica (typically within 30 seconds or less) if the primary instance fails, providing high availability with minimal downtime. Option B is correct because an Amazon RDS Multi-AZ deployment maintains a synchronous standby replica in a different Availability Zone and automatically performs a DNS failover to the standby in the event of a primary failure, again with minimal downtime. Option C is incorrect because a Single-AZ deployment has no standby to fail over to; automated backups only enable point-in-time recovery, not automatic failover.

Option D is incorrect because DynamoDB is a NoSQL key-value/document database, not a relational database, even though global tables provide multi-Region replication. Option E is incorrect because RDS Read Replicas are used for read scaling and are asynchronous; they do not provide automatic failover for high availability.

Exam trap

The trap here is that candidates may overlook the 'relational database' requirement and select DynamoDB (a NoSQL service) or assume that RDS Read Replica provides automatic failover, when in fact it requires manual promotion and does not meet the minimal downtime requirement.

290
MCQeasy

A company is building a serverless application using AWS Lambda. The Lambda function needs to process files uploaded to an S3 bucket. The function should be triggered as soon as a new object is created. How should the architect configure this?

A.Configure S3 to send event notifications to the Lambda function directly
B.Configure S3 to send event notifications to an SNS topic, which triggers the Lambda function
C.Configure S3 to send event notifications to an SQS queue, and have the Lambda function poll the queue
D.Configure S3 to send event notifications to Amazon CloudWatch Events, which triggers the Lambda function
AnswerA

S3 event notifications natively push s3:ObjectCreated events to Lambda through a resource-based policy, invoking the function the moment an object lands. This direct integration satisfies the requirement for immediate, serverless triggering without polling or intermediary services.

Why this answer

Amazon S3 can directly invoke an AWS Lambda function via event notifications when a new object is created. This is the simplest and most direct integration, requiring no intermediate services. S3 publishes an event to Lambda, which then executes the function synchronously, ensuring near-real-time processing of uploaded files.

Exam trap

The trap here is that candidates may overcomplicate the solution by introducing intermediate services like SNS or SQS, not realizing that S3 can directly invoke Lambda with no additional components, which is the simplest and most cost-effective design.

How to eliminate wrong answers

Option B is wrong because while S3 can send notifications to an SNS topic, and SNS can trigger Lambda, this adds unnecessary complexity and latency; the direct S3-to-Lambda integration is simpler and more efficient for this use case. Option C is wrong because S3 can send notifications to an SQS queue, but Lambda would need to poll the queue, introducing polling overhead and potential delays; the requirement is for immediate triggering, not polling. Option D is wrong because S3 does not natively send event notifications to Amazon CloudWatch Events (now Amazon EventBridge); while EventBridge can receive S3 events via CloudTrail or S3 event notifications, this is an indirect path and not the standard configuration for triggering Lambda directly from S3 object creation.

291
MCQeasy

A company is building a new application that will run on AWS Lambda. The application needs to store and retrieve user preferences in a key-value format. The data is accessed frequently and must be highly available. The company expects low latency for reads and writes. Which AWS service should be used as the data store?

A.Amazon S3
B.Amazon ElastiCache for Memcached
C.Amazon RDS for PostgreSQL
D.Amazon DynamoDB
AnswerD

Amazon DynamoDB delivers single-digit millisecond latency for key-value reads and writes, satisfying the low-latency requirement. Its serverless, multi-AZ design provides the high availability the stem demands, and it scales without managing servers, matching Lambda's operational model. Unlike relational stores, its partition-key access pattern suits frequent preference lookups directly.

Why this answer

Amazon DynamoDB is a fully managed, highly available key-value and document database that delivers single-digit millisecond latency at any scale. It is the natural fit for storing user preferences accessed frequently by Lambda functions, with built-in replication across multiple AZs for high availability.

Exam trap

The trap is that candidates pick ElastiCache for low latency, but ElastiCache is a cache, not a durable data store, and the question requires storing and retrieving preferences persistently.

How to eliminate wrong answers

Option A is wrong because Amazon S3 is object storage, not a low-latency key-value store; it has higher latency and is not designed for frequent small reads/writes. Option B is wrong because ElastiCache for Memcached is an in-memory cache, not a durable data store, and Memcached does not provide persistence or high availability by itself. Option C is wrong because Amazon RDS for PostgreSQL is a relational database that requires provisioning and management, and it does not offer the same seamless key-value scalability and low-latency performance as DynamoDB for this use case.

292
Multi-Selecthard

Which THREE design patterns can help a microservices application achieve loose coupling and independent deployability? (Choose three.)

Select 3 answers
A.Shared database schema across services
B.Circuit breaker pattern to handle service failures
C.Synchronous RESTful HTTP calls between services
D.Event-driven communication using Amazon SNS and SQS
E.API Gateway as a facade for service endpoints
AnswersB, D, E

Circuit breakers isolate failures, allowing services to degrade gracefully without impacting others.

Why this answer

The circuit breaker pattern (B) prevents cascading failures by monitoring for failures and opening the circuit to stop calls to an unhealthy service, allowing it time to recover. This supports loose coupling because the caller does not need to know the internal state of the downstream service, and it enables independent deployability by isolating failures during deployment or scaling events.

Exam trap

The trap here is that candidates often confuse synchronous RESTful calls (C) as a valid pattern for loose coupling, but in reality, synchronous calls create tight temporal coupling and reduce independent deployability, whereas event-driven and facade patterns (D and E) are the correct approaches.

293
MCQeasy

A company wants to deploy a new web application on AWS that uses a microservices architecture. The company expects rapid growth and wants to decouple services to allow independent scaling and development. The team wants to use Docker containers for consistency across environments. Which solution should a Solutions Architect recommend?

A.Use Amazon Lightsail containers to deploy each microservice as a container service.
B.Deploy each microservice on separate EC2 instances behind an Application Load Balancer.
C.Use Amazon ECS with Fargate to run each microservice as a separate task definition, with service auto scaling.
D.Use AWS Elastic Beanstalk with Docker platform to deploy each microservice as a separate environment.
AnswerC

ECS with Fargate runs each microservice as a separate task definition, giving independent scaling and deployment without managing EC2 instances. Fargate provides serverless container hosting, and service auto scaling handles rapid growth, satisfying the Docker consistency and decoupling requirements.

Why this answer

Amazon ECS with Fargate allows running containers without managing servers, and each microservice can be defined as a separate task definition with its own scaling policies. This decouples services, supports independent scaling, and provides container consistency across environments. Fargate eliminates infrastructure management, making it ideal for rapid growth and microservices.

Exam trap

The trap is assuming that any container service (like Lightsail or Beanstalk) is suitable for microservices; candidates may overlook that ECS/Fargate provides the orchestration and scaling needed for independent services.

How to eliminate wrong answers

Option A is wrong because Amazon Lightsail containers are simplified and not designed for complex microservices architectures with independent scaling and orchestration. Option B is wrong because deploying on EC2 instances requires managing servers and does not provide the same level of decoupling or ease of scaling as ECS/Fargate. Option D is wrong because Elastic Beanstalk with Docker is more monolithic and less suited for independent microservice scaling; it manages environments as units, not individual services.

294
Multi-Selecteasy

A company is designing a new application that will run on Amazon EC2 instances behind an Application Load Balancer (ALB). The application must be highly available and fault-tolerant across multiple Availability Zones. Which TWO actions should be taken to achieve this? (Choose two.)

Select 2 answers
A.Use an Auto Scaling group to launch instances only in one Availability Zone.
B.Use a Network Load Balancer instead of ALB for better performance.
C.Launch EC2 instances in at least two Availability Zones.
D.Configure the ALB to be internet-facing and register instances from multiple AZs.
E.Launch all EC2 instances in a single Availability Zone for low latency.
AnswersC, D

Multiple AZs provide fault tolerance if one AZ fails.

Why this answer

Launching EC2 instances in at least two Availability Zones (AZs) ensures that if one AZ fails, the application continues to run from the other AZ, providing fault tolerance and high availability. Option D is correct because configuring the ALB to be internet-facing and registering instances from multiple AZs allows the ALB to distribute incoming traffic across healthy instances in different AZs, automatically rerouting traffic if an AZ becomes impaired.

Exam trap

The trap here is that candidates often think a single AZ with Auto Scaling is sufficient for high availability, but true fault tolerance requires distributing resources across multiple AZs to survive an AZ-level failure.

295
MCQeasy

A company wants to decouple a web application frontend from a backend processing service. The frontend sends jobs that are processed asynchronously. Which AWS service is best suited for this decoupling?

A.Amazon SQS
B.Amazon SNS
C.Amazon Kinesis
D.AWS Step Functions
AnswerA

Amazon SQS queues messages between the frontend and backend, so the frontend enqueues jobs and returns immediately while workers poll and process asynchronously. This satisfies the decoupling requirement, absorbing traffic spikes and isolating failures between tiers.

Why this answer

Amazon SQS is the best choice for decoupling a web application frontend from a backend processing service because it provides a fully managed message queue that allows the frontend to send jobs (messages) asynchronously without waiting for the backend to process them. The backend can poll the queue at its own pace, ensuring reliable, scalable, and fault-tolerant communication between the two components. SQS supports standard queues for high throughput and FIFO queues for exactly-once processing, making it ideal for decoupling asynchronous workloads.

Exam trap

The trap here is that candidates often confuse SNS (push-based pub/sub) with SQS (pull-based queue) for decoupling, failing to recognize that asynchronous job processing requires the backend to pull messages, not receive pushes, and that SNS alone does not provide a buffer for unprocessed jobs.

How to eliminate wrong answers

Option B (Amazon SNS) is wrong because SNS is a pub/sub messaging service that pushes messages to multiple subscribers, not a queue; it does not provide the decoupling needed for asynchronous job processing where the backend pulls messages at its own pace. Option C (Amazon Kinesis) is wrong because Kinesis is designed for real-time streaming data ingestion and processing (e.g., logs, metrics), not for decoupling discrete job requests between a frontend and backend; it introduces complexity and cost overhead for simple job queues. Option D (AWS Step Functions) is wrong because Step Functions is a serverless orchestration service for coordinating multiple AWS services into workflows, not a message queue; it is used for stateful workflows, not for decoupling frontend and backend via asynchronous message passing.

296
MCQmedium

A company is designing a new solution that uses Amazon S3 to store large amounts of archival data. The data must be retained for 7 years and then automatically deleted. Which S3 feature should they use?

A.S3 Replication
B.S3 Versioning
C.S3 Object Lock
D.S3 Lifecycle policies
AnswerD

S3 Lifecycle policies automate object transitions and expiration, satisfying the seven-year retention constraint by permanently deleting objects once the rule's expiration threshold is reached. Unlike manual deletion or versioning alone, lifecycle rules run without intervention, ensuring archival data is removed automatically at the defined interval.

Why this answer

S3 Lifecycle policies allow you to define rules that automatically expire objects after a specified period, such as 7 years. This directly meets the requirement to retain archival data for a fixed duration and then delete it without manual intervention.

Exam trap

The trap here is that candidates often confuse S3 Object Lock's retention period with automatic deletion, not realizing that Object Lock only prevents deletion during the retention window and requires a separate lifecycle rule to actually remove the objects afterward.

How to eliminate wrong answers

Option A is wrong because S3 Replication is used to copy objects across buckets for redundancy or compliance, not to manage retention or deletion based on time. Option B is wrong because S3 Versioning preserves multiple versions of an object and does not provide automatic deletion after a set period; it can actually increase storage costs if not combined with lifecycle rules. Option C is wrong because S3 Object Lock is designed to prevent object deletion or overwrites for a fixed retention period (compliance or governance mode), but it does not automatically delete objects after that period ends—it only prevents premature deletion, and objects remain until manually removed or a lifecycle rule is applied.

297
MCQmedium

A company is migrating a legacy three-tier application to AWS. The application servers run on Amazon EC2 instances behind an Application Load Balancer, and the database is a self-managed MySQL instance on an EC2 instance. The company requires that database credentials never be stored in application code or configuration files, and that credentials be automatically rotated every 30 days without application restarts. Which solution meets these requirements with the LEAST operational overhead?

A.Store the credentials in AWS Systems Manager Parameter Store as SecureString parameters. Use an AWS Lambda function triggered by Amazon EventBridge to rotate the credentials every 30 days, and update the application to read the parameters at startup.
B.Use AWS Identity and Access Management (IAM) database authentication for MySQL. Configure the application to generate an authentication token using the EC2 instance role, and connect to the database using that token.
C.Store the credentials in an encrypted Amazon S3 bucket. Use an EC2 user data script to download and decrypt the credentials at instance launch, and rotate them manually every 30 days by updating the S3 object and restarting the application servers.
D.Store the database credentials in AWS Secrets Manager and configure automatic rotation. Grant the EC2 instance role permission to retrieve the secret, and update the application to fetch credentials from Secrets Manager at startup and on connection failure.
AnswerD

AWS Secrets Manager natively supports automatic rotation for supported databases, including self-managed MySQL on EC2, using a Lambda rotation function. It integrates with IAM roles for EC2, so no static credentials are stored in code or configuration. The application can retrieve credentials via the Secrets Manager API when needed, enabling rotation without restarts.

Why this answer

AWS Secrets Manager is designed to securely store and automatically rotate database credentials for supported databases, including self-managed MySQL on EC2, using a Lambda rotation function. It integrates with IAM roles, eliminating hardcoded credentials, and allows applications to retrieve credentials on demand, so rotation occurs without application restarts. This meets the requirements with minimal operational effort.

Exam trap

The trap here is assuming that AWS Systems Manager Parameter Store provides automatic rotation for database credentials, when it only stores parameters and requires a custom rotation solution.

298
MCQmedium

A company is designing a new microservices application on AWS. Each microservice will be deployed as a containerized application using Amazon ECS with Fargate launch type. The company expects variable traffic patterns and needs to ensure that the application can scale automatically based on demand. Which scaling solution should be used?

A.Use Amazon EC2 Auto Scaling to add more Fargate tasks.
B.Configure Application Auto Scaling with a target tracking scaling policy based on average CPU utilization.
C.Use AWS Auto Scaling Plans with predictive scaling.
D.Manually adjust the desired count of tasks in the ECS service based on traffic analysis.
AnswerB

Application Auto Scaling with a target tracking policy on average CPU utilisation adjusts the ECS service's desired task count automatically as demand varies. It satisfies the stem's Fargate scaling requirement, since Fargate tasks scale at the service level rather than through EC2 Auto Scaling groups.

Why this answer

Amazon ECS with Fargate uses Application Auto Scaling to automatically adjust the desired count of tasks based on demand. A target tracking scaling policy based on average CPU utilization is the correct approach because it allows you to define a target value (e.g., 70% CPU) and Application Auto Scaling will add or remove tasks to maintain that target, matching the variable traffic patterns described.

Exam trap

The trap here is confusing EC2 Auto Scaling (which manages instances) with Application Auto Scaling (which manages ECS tasks), leading candidates to choose Option A despite Fargate being serverless and not requiring EC2 instance management.

How to eliminate wrong answers

Option A is wrong because Amazon EC2 Auto Scaling manages EC2 instances, not Fargate tasks; Fargate tasks are serverless and scaled via Application Auto Scaling, not EC2 Auto Scaling. Option C is wrong because AWS Auto Scaling Plans with predictive scaling is designed for recurring, predictable traffic patterns (e.g., based on historical data), not for variable, unpredictable traffic patterns as described in the question. Option D is wrong because manually adjusting the desired count of tasks does not meet the requirement for automatic scaling based on demand; it requires human intervention and analysis, which is not automated.

299
MCQeasy

A company is designing a new web application that will run on Amazon EC2 instances behind an Application Load Balancer. They need to offload SSL/TLS termination to reduce CPU usage on the instances. What should they do?

A.Install a self-signed certificate on each EC2 instance
B.Use a Network Load Balancer (NLB) with SSL pass-through
C.Configure the ALB with an SSL certificate
D.Use Amazon CloudFront for SSL termination
AnswerC

Terminating TLS at the Application Load Balancer using an ACM or imported certificate moves the cryptographic handshake and bulk decryption off the EC2 instances, directly satisfying the requirement to reduce their CPU usage while the ALB forwards plaintext HTTP to the targets.

Why this answer

An Application Load Balancer (ALB) can terminate SSL/TLS by installing a certificate on it, reducing CPU load on backend EC2 instances. Option A (self-signed certificate on each instance) does not offload SSL and is less secure. Option B (NLB with SSL pass-through) does not terminate SSL; it passes encrypted traffic through.

Option D (CloudFront) can terminate SSL but is a CDN service, not primarily for SSL offload in this architecture, and adds cost and complexity.

300
MCQhard

A company is migrating a monolithic application to a microservices architecture on AWS. The application uses a relational database with complex queries. The team wants to decouple the database layer and allow each microservice to own its data. Which design pattern should the team implement?

A.Implement an event-driven architecture using Amazon SQS and AWS Lambda with CQRS.
B.Deploy a read replica of the database for each microservice to offload queries.
C.Use a single Amazon RDS instance with multiple schemas for each microservice.
D.Use a database-per-service pattern with each microservice having its own Amazon DynamoDB table or RDS instance.
AnswerD

Database-per-service gives each microservice exclusive ownership of its schema, satisfying the decoupling constraint. Services choose DynamoDB for key-value access or RDS where complex relational queries persist, and integrate through APIs or events rather than shared tables. This removes the monolithic database as a coupling point and single point of contention.

Why this answer

The database-per-service pattern is the foundational microservices data management approach where each service owns its private datastore, exposing data only through its API. This gives each microservice independent schema evolution, technology choice (polyglot persistence), and failure isolation — directly satisfying the requirement that 'each microservice owns its data.' DynamoDB or a dedicated RDS instance per service enforces this boundary at the infrastructure level, preventing the shared-database anti-pattern that recreates the monolith's coupling.

Exam trap

SAP-C02 often tests whether candidates confuse 'decoupling' mechanisms (SQS, CQRS, read replicas) with actual data ownership — the exam wants you to recognize that only database-per-service removes the shared-schema coupling that blocks independent microservice evolution.

How to eliminate wrong answers

Option A is wrong because CQRS with SQS/Lambda addresses read/write model separation and asynchronous decoupling, not data ownership — services would still share the underlying database, so the coupling problem remains. Option B is wrong because read replicas only offload read traffic from a single primary; all replicas still contain the same schema and data, so services remain tightly coupled to one shared data model and writes still contend on the primary. Option C is wrong because multiple schemas on one RDS instance is the classic 'shared database' anti-pattern — services can still join across schemas, schema changes require coordinated deployments, and one service's heavy query can starve others on the same instance.

← PreviousPage 4 of 5 · 321 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Design for New Solutions questions.