Courseiva

CCNA Design for New Solutions Questions

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

151
MCQmedium

A media company is designing a new application that ingests large video files uploaded by users. The files must be stored durably and then processed by a compute fleet that runs for several hours per file. The company wants to minimize compute costs and ensure that processing can resume if interrupted. Which architectural approach should a solutions architect recommend?

A.Store files in Amazon S3 and use Amazon ECS with Fargate tasks that run for up to 24 hours.
B.Store files in Amazon S3 and use AWS Lambda with a 15-minute timeout to process each file.
C.Store files in Amazon S3 and use AWS Batch with managed compute environments to run processing jobs.
D.Store files in Amazon EBS and use a single large EC2 instance to process files sequentially.
AnswerC

AWS Batch is designed for batch computing workloads and can run jobs for hours or days. It manages compute resources dynamically, which can reduce costs by using Spot Instances and scaling down when not needed. AWS Batch also supports job queues and retries, allowing processing to resume if interrupted, and integrates with S3 for input and output.

Why this answer

AWS Batch is purpose-built for batch computing, supporting long-running jobs and managed compute environments that can use Spot Instances to reduce costs. It provides job queues, retries, and dependency management, enabling processing to resume after interruptions. Storing files in Amazon S3 ensures durability and accessibility for the compute fleet.

This combination meets the requirements for cost minimization and resiliency.

Exam trap

The trap here is assuming that AWS Lambda or Fargate can handle multi-hour processing without considering their timeout limits or the lack of built-in batch orchestration.

152
MCQmedium

A company is designing a new real-time bidding platform that must handle sudden bursts of traffic up to 100,000 requests per second. The application runs on Amazon EC2 instances behind an Application Load Balancer and stores bid data in Amazon DynamoDB. The company wants to minimize latency and cost while ensuring the database can scale automatically. Which solution meets these requirements?

A.Use Amazon RDS for MySQL with Multi-AZ and read replicas, and implement a caching layer using Amazon ElastiCache.
B.Use DynamoDB with provisioned capacity mode and set up Auto Scaling with a target utilization of 70%.
C.Use DynamoDB with on-demand capacity mode and enable DynamoDB Accelerator (DAX) for read-heavy workloads.
D.Use Amazon Aurora Serverless v2 with auto-scaling and enable Aurora Global Database for low-latency reads.
AnswerC

On-demand capacity mode automatically scales to handle sudden bursts without capacity planning, and DAX provides microsecond read latency for read-heavy workloads like real-time bidding. This combination minimizes latency and cost because you pay only for what you use, with no need to over-provision. It directly addresses the unpredictable traffic and low-latency requirements.

Why this answer

The correct solution uses DynamoDB on-demand mode to handle unpredictable bursts without capacity planning, and DAX to provide microsecond read latency for read-heavy operations. This combination ensures automatic scaling, low latency, and cost efficiency for a real-time bidding platform. Other options either require manual scaling, introduce bottlenecks, or are not optimized for the required throughput and latency.

Exam trap

The trap here is assuming that provisioned capacity with Auto Scaling can react quickly enough to sudden bursts, but it cannot match the instant scalability of on-demand mode.

153
MCQhard

Refer to the exhibit. An architect is troubleshooting an EC2 instance that is not responding to health checks from an Application Load Balancer. The instance is in the 'running' state. Which of the following is the most likely cause?

A.The security group is blocking the health check traffic.
B.The instance is in a stopped state.
C.The instance is impaired due to an AWS issue.
D.The instance has exhausted its CPU credits.
AnswerA

A security group that omits the load balancer's health check port or source blocks the probe packets, so the target never receives them and is marked unhealthy despite the instance running. Allowing the health check port from the ALB security group or subnet CIDR resolves it.

Why this answer

The most likely cause is that the instance's security group is not allowing inbound traffic from the ALB's security group on the health check port. ALB health checks originate from the load balancer's ENIs, so the target's security group must explicitly permit that traffic; otherwise the instance appears healthy at the OS level but fails ALB checks.

Exam trap

SAP-C02 often tests the misconception that a running instance with a healthy OS is automatically reachable by the ALB, when security group and NACL rules on the health check path are the usual culprits.

How to eliminate wrong answers

Option B is wrong because the question states the instance is in the 'running' state, so a stopped state is contradicted by the scenario. Option C is wrong because an AWS-side impairment would typically affect many resources and is not the first thing to check; it is a rare cause compared to misconfigured security groups. Option D is wrong because CPU credit exhaustion on a T-family instance degrades performance but does not by itself cause health check failures unless the instance becomes completely unresponsive, which is far less likely than a security group misconfiguration.

154
MCQmedium

A healthcare company is designing a new multi-tenant SaaS application on AWS. Each tenant requires a separate encryption key, and the company must be able to audit key usage per tenant and automatically rotate keys annually. The keys must be stored in a hardware security module (HSM) that is validated to FIPS 140-2 Level 3. Which solution meets these requirements with the LEAST operational overhead?

A.Use AWS Secrets Manager to store encryption keys per tenant, enable automatic rotation every year, and use AWS CloudTrail to audit access.
B.Use AWS Certificate Manager (ACM) to issue a separate certificate per tenant, store the private keys in ACM, and enable automatic renewal.
C.Use AWS Key Management Service (KMS) with a customer managed key per tenant, enable automatic annual rotation, and use AWS CloudTrail to audit key usage.
D.Deploy AWS CloudHSM clusters in each AWS Region, create a separate key for each tenant, and configure automatic rotation using a custom Lambda function.
AnswerC

AWS KMS provides FIPS 140-2 Level 3 validated HSMs, supports customer managed keys with automatic annual rotation, and logs all key usage to CloudTrail for auditing. Creating one customer managed key per tenant isolates encryption and enables per-tenant audit trails. This approach requires minimal operational effort because AWS manages the HSM infrastructure and rotation.

Why this answer

AWS KMS customer managed keys provide tenant-specific encryption with FIPS 140-2 Level 3 validated HSMs, and automatic key rotation can be enabled with a single setting. CloudTrail captures all API calls related to the keys, enabling per-tenant auditing. This solution offloads HSM management and rotation to AWS, minimizing operational overhead while meeting security and compliance requirements.

Exam trap

The trap here is assuming that AWS CloudHSM is necessary for FIPS 140-2 Level 3 compliance, when AWS KMS already meets that standard and requires far less management effort.

155
MCQhard

A company is designing a disaster recovery solution for a critical application that runs on Amazon EC2 instances in a single AWS Region. The application uses an Amazon RDS for MySQL database. The company wants to achieve a recovery point objective (RPO) of 5 seconds and a recovery time objective (RTO) of 15 minutes. Which solution should the company use?

A.Configure an RDS Multi-AZ DB cluster with a standby instance in another Region.
B.Use EC2 Auto Scaling to launch new instances in another Region and use an Application Load Balancer.
C.Take automated snapshots of the RDS instance every 5 seconds and copy them to another Region.
D.Deploy RDS Read Replicas in another Region and promote them during a disaster.
AnswerD

Correct. Cross-Region Read Replicas use asynchronous replication, typically achieving an RPO of seconds, and can be promoted to primary within minutes, meeting both RPO and RTO requirements.

Why this answer

Cross-Region Read Replicas for Amazon RDS MySQL use asynchronous replication, so they do not guarantee a 5-second RPO; replication lag can vary from seconds to minutes. However, among the options provided, D is the closest fit because the read replica can be promoted to a standalone primary database, and the other options fail to meet the RPO/RTO or are invalid. A strict 5-second RPO would be better served by Amazon Aurora Global Database, but D is the best available choice.

Option A is invalid because RDS Multi-AZ DB clusters do not support a standby instance in another Region for MySQL. Options B and C do not meet the RPO/RTO requirements.

Exam trap

The trap is that candidates assume Multi-AZ DB clusters support cross-Region standby instances, but Multi-AZ is limited to a single Region. They may also overlook that cross-Region Read Replicas use asynchronous replication and therefore cannot guarantee a 5-second RPO.

How to eliminate wrong answers

Option B is wrong because EC2 Auto Scaling and an Application Load Balancer address compute recovery but do not replicate the RDS database, failing to meet the RPO of 5 seconds and RTO of 15 minutes for the database tier. Option C is wrong because automated snapshots cannot be taken every 5 seconds (minimum interval is 5 minutes for automated snapshots, and manual snapshots are limited to once per 5 minutes per API), and copying snapshots to another Region introduces latency that exceeds the 5-second RPO. Option D is wrong because RDS Read Replicas in another Region use asynchronous replication, which can have a replication lag of several seconds to minutes, failing to guarantee a 5-second RPO; promotion is also not automatic, potentially exceeding the 15-minute RTO.

156
MCQeasy

A company wants to store application logs in Amazon S3 with a lifecycle policy that moves objects to S3 Glacier Instant Retrieval after 30 days and deletes them after 1 year. The logs are accessed frequently in the first 30 days but rarely after. Which storage class should the company use for the first 30 days?

A.S3 Standard
B.S3 Standard-IA
C.S3 One Zone-IA
D.S3 Glacier Flexible Retrieval
AnswerA

S3 Standard is appropriate for frequently accessed data. It has no retrieval fees, making it cost-effective for logs accessed multiple times in the first 30 days. The lifecycle transition to Glacier Instant Retrieval after 30 days is seamless.

Why this answer

S3 Standard is the correct choice because the logs are accessed frequently during the first 30 days. Standard provides low-latency access with no retrieval fees, and the lifecycle policy can transition objects to S3 Glacier Instant Retrieval after 30 days. For data that is accessed multiple times within a short retention period, Standard is more cost-effective than Standard-IA, which incurs retrieval fees and a 30-day minimum storage charge.

Exam trap

The common trap is selecting S3 Standard-IA (Option B) due to its lower storage cost, but failing to account for retrieval fees and the 30-day minimum charge. For frequently accessed data with short retention, S3 Standard is more cost-effective.

How to eliminate wrong answers

Option A (S3 Standard) is wrong because it is designed for frequently accessed data with no cost savings for infrequent access patterns; using it for the first 30 days would incur higher storage costs than necessary since the logs are not accessed constantly. Option C (S3 One Zone-IA) is wrong because it stores data in a single Availability Zone, which does not provide the durability and availability required for application logs that may need to be recovered after a zone failure; the question does not indicate tolerance for such risk. Option D (S3 Glacier Flexible Retrieval) is wrong because it is intended for long-term archival with retrieval times ranging from minutes to hours, not for data that is accessed frequently within the first 30 days; it would introduce unacceptable latency for the initial frequent access pattern.

157
MCQhard

A company is building a high-performance computing (HPC) cluster on AWS for genomics research. The compute nodes require low-latency inter-node communication. Which networking solution should be used?

A.Elastic Fabric Adapter (EFA)
B.Enhanced Networking (ENA)
C.VPC Peering
D.AWS Direct Connect
AnswerA

Elastic Fabric Adapter provides kernel-bypass and OS-bypass capabilities, enabling tightly coupled HPC applications to communicate with far lower latency than standard TCP/IP over Elastic Network Adapter. It satisfies the stem's low-latency inter-node requirement, supporting MPI and NCCL collective operations essential for genomics workloads distributed across many compute nodes.

Why this answer

Elastic Fabric Adapter (EFA) is a network interface that enables HPC and machine learning applications to achieve low-latency inter-node communication by bypassing the operating system kernel and providing OS-bypass capabilities via the Libfabric library. This is essential for tightly coupled HPC workloads like genomics research, where MPI (Message Passing Interface) jobs require microsecond-level latency and high throughput between compute nodes.

Exam trap

The trap here is that candidates confuse Enhanced Networking (ENA) with Elastic Fabric Adapter (EFA), assuming both provide similar low-latency benefits, but only EFA offers OS-bypass for HPC inter-node communication, while ENA still relies on kernel processing.

How to eliminate wrong answers

Option B (Enhanced Networking with ENA) is wrong because while it provides higher bandwidth and lower jitter than standard networking, it still operates through the kernel network stack and does not support OS-bypass, so it cannot achieve the ultra-low latency required for tightly coupled HPC inter-node communication. Option C (VPC Peering) is wrong because it is a logical connection between VPCs used for routing traffic, not a physical network adapter or interface; it does not reduce latency or provide OS-bypass for compute nodes within the same cluster. Option D (AWS Direct Connect) is wrong because it establishes a dedicated network connection from on-premises to AWS, not between compute nodes within a VPC; it is irrelevant to inter-node communication latency inside an HPC cluster.

158
MCQmedium

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

A.Manual scaling by operations team
B.Simple scaling with a cooldown period
C.Scheduled scaling based on historical data
D.Target tracking scaling policy
AnswerD

Target tracking scaling adjusts capacity automatically to hold a chosen metric, such as average CPU utilisation or request count per target, at a target value. It responds to sudden traffic spikes without manual intervention, unlike scheduled or simple step policies that need predefined thresholds.

Why this answer

Target tracking scaling policy is the correct choice because it automatically adjusts the number of EC2 instances to maintain a specified target metric (e.g., average CPU utilization or request count per target) without manual intervention. This policy uses a built-in metric and dynamically calculates the required capacity to handle sudden traffic spikes, aligning with the requirement for automatic scaling under unpredictable load.

Exam trap

The trap here is that candidates often confuse 'scheduled scaling' (which works for predictable patterns) with 'dynamic scaling' (which handles unpredictable spikes), and may overlook that target tracking is the only fully automated policy that continuously adjusts capacity based on a real-time metric without manual cooldown tuning.

How to eliminate wrong answers

Option A is wrong because manual scaling requires human intervention to add or remove instances, which cannot respond to sudden spikes in real time. Option B is wrong because simple scaling with a cooldown period uses a single step adjustment and then locks scaling actions during the cooldown, which can delay response to rapid traffic changes and cause under- or over-provisioning. Option C is wrong because scheduled scaling relies on predictable patterns from historical data and cannot react to unexpected spikes that deviate from the schedule.

159
MCQeasy

A company is designing a new application that will process streaming data from IoT devices. The data must be ingested in real-time and stored in Amazon S3 for long-term analytics. Which AWS service should be used to ingest the streaming data?

A.Amazon Simple Notification Service (SNS)
B.Amazon Simple Queue Service (SQS)
C.AWS Database Migration Service (DMS)
D.Amazon Kinesis Data Streams
AnswerD

Kinesis Data Streams ingests records in real time with low latency and durable, ordered shards, then supports delivery into Amazon S3 via Firehose or consumers. This satisfies the stem's real-time ingestion and long-term S3 storage requirements.

Why this answer

Amazon Kinesis Data Streams is designed for real-time data ingestion and can stream data directly to Amazon S3. Option A is wrong because SNS is a pub/sub messaging service, not intended for real-time data ingestion. Option B is wrong because SQS is a message queue service, not optimized for streaming ingestion.

Option C is wrong because AWS DMS is used for database migration, not for ingesting streaming data.

160
MCQeasy

A company wants to provide temporary, limited-privilege credentials to its application running on an EC2 instance so that the application can access an S3 bucket. What is the BEST practice for achieving this?

A.Use an S3 bucket policy to allow access from the EC2 instance's public IP
B.Create an IAM user and store the credentials in the EC2 instance user data
C.Store AWS access keys in the application code
D.Create an IAM role with the necessary permissions and attach it to the EC2 instance
AnswerD

An IAM role attached to the instance delivers temporary credentials through the instance metadata service, which the AWS SDK and CLI retrieve and rotate automatically. This satisfies the limited-privilege, temporary-credential requirement without embedding long-lived access keys on the instance.

Why this answer

The best practice is to use an IAM role, which provides temporary security credentials via the EC2 instance metadata service (IMDS). The application automatically retrieves these credentials without hardcoding secrets, and the credentials are rotated automatically by AWS. This approach follows the principle of least privilege and eliminates the security risks of long-term access keys.

Exam trap

The trap here is that candidates may think storing credentials in user data or code is acceptable for automation, but AWS explicitly prohibits this in favor of IAM roles for EC2 to avoid long-term credential exposure.

How to eliminate wrong answers

Option A is wrong because restricting access by EC2 instance public IP is not secure (IPs can change, and other AWS services or instances could share the same IP) and does not provide temporary credentials. Option B is wrong because storing IAM user credentials in EC2 user data exposes long-term access keys, which can be compromised and require manual rotation. Option C is wrong because hardcoding AWS access keys in application code is a severe security risk, as the keys are static, can be exposed in version control, and violate the principle of least privilege.

161
MCQhard

A company is migrating a monolithic application to a serverless architecture using AWS Lambda. The application reads and writes to an Amazon RDS for PostgreSQL database. The database connection pool is exhausted during peak traffic. Which design change should a solutions architect recommend to avoid connection exhaustion?

A.Use Amazon SQS to buffer write requests to the database.
B.Use DynamoDB Accelerator (DAX) as a caching layer.
C.Use Amazon RDS Proxy to pool and share database connections.
D.Increase the max_connections parameter in the RDS parameter group.
AnswerC

Lambda's per-invocation concurrency opens many direct PostgreSQL connections, exhausting the pool. RDS Proxy maintains a shared pool and multiplexes Lambda connections onto it, so the constraint of connection exhaustion at peak traffic is removed without changing application logic.

Why this answer

Amazon RDS Proxy sits between the Lambda function and the RDS database, managing a pool of database connections and reusing them across multiple invocations. This prevents the Lambda function from exhausting the database connection pool during traffic spikes, as each Lambda instance does not need to open its own connection. RDS Proxy also handles connection multiplexing and reduces the overhead of establishing new connections.

Exam trap

The trap here is that candidates often think increasing max_connections or using a queue (SQS) is sufficient, but they overlook that Lambda's concurrent execution model requires connection pooling at the database layer, which RDS Proxy uniquely provides.

How to eliminate wrong answers

Option A is wrong because Amazon SQS buffers write requests but does not address the root cause of connection exhaustion; it only decouples the write path, leaving read operations and other direct database interactions still vulnerable to connection pool exhaustion. Option B is wrong because DynamoDB Accelerator (DAX) is an in-memory cache for DynamoDB, not for Amazon RDS for PostgreSQL, and it cannot pool or manage database connections. Option D is wrong because increasing the max_connections parameter only raises the limit, but does not prevent Lambda from opening too many connections; it can lead to resource contention and still exhaust database resources under high concurrency.

162
MCQeasy

A company needs to provide a global content delivery solution with low latency. Which AWS service should they use?

A.Amazon S3
B.Amazon EC2
C.Amazon Route 53
D.Amazon CloudFront
AnswerD

Amazon CloudFront caches content at edge locations worldwide, delivering objects from the point of presence nearest each user. This directly satisfies the low-latency requirement by shortening the network path, rather than serving every request from a single regional origin. It also integrates with AWS Shield and AWS WAF for protection at the edge.

Why this answer

Amazon CloudFront is a global content delivery network (CDN) that caches content at edge locations worldwide, reducing latency by serving data from the nearest edge to the user. It integrates with origins like S3, EC2, or on-premises servers and supports both static and dynamic content acceleration, making it the correct choice for low-latency global delivery.

Exam trap

The trap here is that candidates often confuse Amazon S3's static website hosting or Route 53's latency-based routing with actual content delivery, but neither provides the edge caching and global distribution that CloudFront offers for low-latency delivery.

How to eliminate wrong answers

Option A is wrong because Amazon S3 is an object storage service, not a content delivery network; it stores data in a single region and does not provide global edge caching or low-latency distribution on its own. Option B is wrong because Amazon EC2 is a compute service that runs virtual servers in specific regions; it lacks built-in global edge caching and would require manual scaling and additional services to achieve low-latency delivery worldwide. Option C is wrong because Amazon Route 53 is a DNS and traffic management service; it resolves domain names to IP addresses but does not cache or deliver content, so it cannot reduce latency for content delivery.

163
Multi-Selecthard

A company is designing a new multi-tier application on AWS. The application will use an Application Load Balancer (ALB) to distribute traffic to Amazon EC2 instances in an Auto Scaling group. The company requires that the application be highly available across multiple Availability Zones and that it can scale automatically based on demand. The company also wants to ensure that the application can handle sudden spikes in traffic without manual intervention. Which two actions should a solutions architect recommend to meet these requirements? (Choose two.)

Select 2 answers
A.Enable cross-zone load balancing on the ALB and configure the Auto Scaling group to use a single Availability Zone.
B.Use a Network Load Balancer (NLB) instead of an Application Load Balancer (ALB) to improve performance.
C.Create a target tracking scaling policy based on average CPU utilization to automatically adjust the number of instances.
D.Configure the Auto Scaling group to use multiple Availability Zones and set the minimum capacity to at least two instances.
E.Configure a scheduled scaling policy to add instances at predicted peak times.
AnswersC, D

A target tracking scaling policy automatically scales the Auto Scaling group to maintain a target metric, such as average CPU utilization. This handles sudden spikes in traffic by adding instances as needed, and scales in during low demand, providing automatic scaling without manual intervention.

Why this answer

To achieve high availability, the Auto Scaling group must span multiple Availability Zones with a minimum capacity of at least two instances. To handle sudden spikes automatically, a target tracking scaling policy based on a metric like CPU utilization dynamically adjusts capacity. Together, these actions provide both resilience and elasticity without manual intervention.

Exam trap

The trap here is assuming that a Network Load Balancer or cross-zone load balancing alone can provide high availability, when in fact the Auto Scaling group must be configured across multiple AZs with sufficient minimum capacity.

164
Matchingmedium

Match each AWS cost management tool to its use.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Visualize and explore cost and usage data

Set custom cost and usage budgets with alerts

Recommendations for cost optimization, performance, security

Flexible pricing model for compute savings

Recommend optimal compute resources based on usage

Why these pairings

Correct matches: Cost Explorer visualizes costs, Budgets set alerts, Trusted Advisor recommends optimizations, and CUR provides detailed data. Common confusions involve mixing tool capabilities.

165
Multi-Selecthard

A company is migrating a legacy application to AWS. The application consists of several components that communicate via TCP. The solutions architect must design a solution that minimizes operational overhead and provides high availability. Which TWO strategies should be used?

Select 2 answers
A.Use instance store volumes for data persistence.
B.Use managed services like Amazon RDS and Amazon ElastiCache to reduce operational overhead.
C.Use Spot Instances for all compute resources.
D.Use VPC Peering to connect components.
E.Use an Application Load Balancer to distribute traffic across multiple EC2 instances.
AnswersB, E

Managed services reduce overhead and provide HA out-of-the-box.

Why this answer

Using managed services like Amazon RDS and Amazon ElastiCache offloads administrative tasks such as patching, backups, and replication setup, significantly reducing operational overhead. Option E is correct because an Application Load Balancer (ALB) distributes incoming TCP traffic across multiple EC2 instances in different Availability Zones, providing high availability and fault tolerance for the application components.

Exam trap

The trap here is that candidates may confuse high availability with data persistence, incorrectly choosing instance store volumes (Option A) for persistence, or assume that Spot Instances (Option C) can be used for all compute resources despite their interruption risk, overlooking the need for reliable TCP communication in a production migration.

166
MCQhard

A company runs a high-traffic web application on Amazon EC2 instances behind an Application Load Balancer. The application experiences intermittent latency spikes during peak hours. Analysis shows that the latency spikes correlate with high CPU utilization on the EC2 instances. The company wants to reduce latency without over-provisioning. Which solution is MOST cost-effective and scalable?

A.Add Amazon ElastiCache to cache database queries.
B.Use Spot Instances to reduce costs and scale horizontally.
C.Increase the EC2 instance size to handle peak loads.
D.Configure an Auto Scaling group with a target tracking scaling policy based on average CPU utilization.
AnswerD

Target tracking adjusts desired capacity dynamically against average CPU utilisation, matching the observed correlation between CPU load and latency. It scales out only when demand rises, satisfying the no-over-provisioning constraint while remaining elastic and cost-effective during peak hours.

Why this answer

A target tracking scaling policy based on average CPU utilization automatically adjusts the number of EC2 instances in the Auto Scaling group to maintain a target CPU utilization level. This directly addresses the latency spikes caused by high CPU utilization during peak hours by scaling out horizontally, while scaling in during low traffic to avoid over-provisioning, making it both cost-effective and scalable.

Exam trap

The trap here is that candidates may confuse addressing the symptom (high CPU) with vertical scaling (Option C) or cost-saving measures (Option B), rather than recognizing that horizontal auto-scaling with a target tracking policy is the most cost-effective and scalable solution for handling intermittent latency spikes caused by CPU utilization.

How to eliminate wrong answers

Option A is wrong because caching database queries with ElastiCache reduces database load and query latency, but does not directly address high CPU utilization on the EC2 instances themselves, which is the root cause of the latency spikes. Option B is wrong because Spot Instances are cost-effective but can be interrupted with a two-minute warning, making them unsuitable for a high-traffic web application that requires consistent availability and low latency during peak hours. Option C is wrong because increasing the EC2 instance size (vertical scaling) is less cost-effective and scalable than horizontal scaling, as it leads to over-provisioning during off-peak hours and has a hard limit on instance size, failing to handle unpredictable traffic spikes efficiently.

167
Multi-Selecthard

A company is deploying a new financial application on AWS that requires strict compliance with PCI DSS. The application will store sensitive cardholder data in an Amazon S3 bucket. The security team needs to ensure that data is encrypted at rest and that access is audited. They also need to be able to prove that encryption keys are rotated annually. Which two actions should be taken to meet these requirements? (Choose two.)

Select 2 answers
A.Enable default encryption on the S3 bucket using SSE-KMS with a customer managed key.
B.Enable versioning on the S3 bucket to protect against accidental deletion.
C.Enable default encryption on the S3 bucket using SSE-S3.
D.Configure AWS CloudTrail to log S3 data events for the bucket.
E.Enable S3 server access logging to a separate bucket.
AnswersA, D

SSE-KMS with a customer managed key allows you to control the key policy, enable automatic annual rotation, and audit key usage with AWS CloudTrail. This meets the requirements for encryption at rest, key rotation, and auditing. You can also use KMS grants to control access.

Why this answer

To meet encryption at rest with provable key rotation, use SSE-KMS with a customer managed key, which allows you to enable automatic annual rotation and audit key usage. To audit access to the data, enable CloudTrail data events for the S3 bucket, which logs object-level operations and KMS key usage. Together, these provide the necessary encryption and auditing controls.

Exam trap

The trap here is assuming that SSE-S3 provides sufficient key management control to prove annual rotation, when in fact only customer managed KMS keys allow you to demonstrate rotation to auditors.

168
MCQmedium

A company is designing a serverless application using AWS Lambda. The function needs to access a VPC resource. What is the correct way to configure this?

A.Attach an Internet Gateway to the VPC
B.Assign the Lambda function to the VPC and configure a security group
C.Set up a VPC peering connection
D.Configure a NAT Gateway in the public subnet
AnswerB

Attaching the function to the VPC places its elastic network interfaces in specified subnets, and the security group controls outbound and inbound traffic to the VPC resource. This satisfies the requirement to reach a private VPC resource.

Why this answer

Lambda functions must be attached to a VPC and assigned a security group to access resources within the VPC, such as an RDS database or an Elasticache cluster. This configuration creates an elastic network interface (ENI) in the VPC, allowing the function to communicate with VPC resources via private IP addresses. The security group acts as a virtual firewall to control inbound and outbound traffic for the Lambda function.

Exam trap

The trap here is that candidates often confuse external connectivity (Internet Gateway, NAT Gateway) with internal VPC access, mistakenly thinking those components are required for a Lambda function to reach resources within the same VPC.

How to eliminate wrong answers

Option A is wrong because an Internet Gateway enables communication between a VPC and the internet, not direct access to VPC resources from a Lambda function; Lambda already uses a VPC-attached ENI for private connectivity. Option C is wrong because VPC peering connects two separate VPCs, but the Lambda function needs to be directly attached to the target VPC, not rely on a peering connection. Option D is wrong because a NAT Gateway allows outbound internet access from private subnets, but it does not enable a Lambda function to access VPC resources; the function must be attached to the VPC with appropriate security group rules.

169
MCQhard

A financial services company is designing a new application that will store sensitive customer data in Amazon S3. The company must encrypt the data at rest and ensure that the encryption keys are rotated annually. The security team requires that the company retains full control over the key rotation and can audit key usage. The solutions architect needs to recommend an encryption solution that meets these requirements with minimal operational effort. Which solution should the architect recommend?

A.Use client-side encryption with a custom encryption library and store the keys in AWS Secrets Manager.
B.Use SSE-S3 with default encryption and enable S3 bucket key.
C.Use SSE-KMS with a customer managed key (CMK) and enable automatic key rotation.
D.Use SSE-KMS with an AWS managed key and enable automatic key rotation.
AnswerC

SSE-KMS with a customer managed key allows the company to control key rotation, audit key usage via AWS CloudTrail, and define key policies. Enabling automatic key rotation rotates the key annually, meeting the requirement with minimal operational effort. This solution provides the necessary control and auditability while being fully managed.

Why this answer

SSE-KMS with a customer managed key provides the company with full control over the encryption keys, including the ability to enable automatic annual rotation. It also integrates with AWS CloudTrail for auditing key usage. This solution is fully managed, requiring minimal operational effort.

Other options either do not provide the required control or require more management overhead.

Exam trap

The trap here is confusing AWS managed keys with customer managed keys, and assuming that AWS managed keys support automatic rotation and auditing.

170
MCQmedium

A company is designing a new application that processes sensitive healthcare data. The application runs on Amazon ECS with Fargate and uses an Application Load Balancer. The company must ensure that all data in transit is encrypted. Which step should be taken?

A.Configure the target group to use HTTP protocol.
B.Configure the security group to only allow inbound traffic from approved IPs.
C.Use HTTP on port 80 and rely on VPC network ACLs.
D.Configure the ALB listener to use HTTPS (port 443) with an SSL certificate.
AnswerD

Terminating TLS at the ALB listener encrypts traffic between clients and the load balancer, satisfying the in-transit encryption requirement. An SSL certificate on port 443 ensures HTTPS from the internet to the ALB, covering the external leg of the data path.

Why this answer

To encrypt data in transit between clients and the Application Load Balancer (ALB), you must configure the ALB listener to use HTTPS (port 443) with an SSL/TLS certificate. This ensures that all traffic between the client and the load balancer is encrypted using TLS, meeting the requirement for encrypted data in transit for sensitive healthcare data.

Exam trap

The trap here is that candidates often confuse network-level controls (security groups, NACLs) with encryption, or assume that using HTTP on the backend is sufficient, forgetting that the client-to-ALB leg must also be encrypted to satisfy 'data in transit' requirements.

How to eliminate wrong answers

Option A is wrong because configuring the target group to use HTTP protocol does not encrypt traffic between the client and the ALB; it only affects the backend connection, and the client-to-ALB leg remains unencrypted if the listener is HTTP. Option B is wrong because restricting inbound traffic to approved IPs controls network access but does not encrypt the data in transit; encryption requires TLS/SSL, not IP filtering. Option C is wrong because using HTTP on port 80 and relying on VPC network ACLs provides no encryption; network ACLs are stateless packet filters and do not provide any cryptographic protection for data in transit.

171
MCQhard

A global e-commerce company is designing a new order-processing system that must survive the failure of an entire AWS Region. The system uses an Amazon Aurora MySQL database and must provide a recovery point objective (RPO) of 1 minute and a recovery time objective (RTO) of 5 minutes. The company wants to minimize operational overhead and avoid managing replication instances. Which solution should the solutions architect recommend?

A.Configure Aurora MySQL with a cross-Region read replica using binary log replication, and promote the replica on failure.
B.Create an Aurora global database with the primary cluster in one Region and a secondary cluster in another Region; configure the application to fail over using the secondary cluster's endpoint.
C.Take automated snapshots of the Aurora cluster and copy them to another Region; restore from the copied snapshot on failure.
D.Deploy Aurora MySQL with a Multi-AZ configuration across three Availability Zones in a single Region; rely on automatic failover for disaster recovery.
AnswerB

Aurora global database replicates at the storage layer with typical lag under one second, meeting the 1-minute RPO, and allows promotion of a secondary cluster in under a minute, meeting the 5-minute RTO. It is fully managed, so no replication instances are needed, minimizing operational overhead. This directly satisfies all requirements.

Why this answer

Aurora global database replicates data across Regions with sub-second typical latency, enabling an RPO well within one minute, and allows a secondary cluster to be promoted in under a minute, meeting the five-minute RTO. Because it is a managed feature with no replication instances to operate, it also minimizes operational overhead.

Exam trap

The trap here is treating Aurora Multi-AZ or cross-Region read replicas as equivalent to an Aurora global database for Region-wide disaster recovery with strict RPO and RTO.

172
MCQeasy

A company wants to share a large dataset stored in Amazon S3 with a partner who has their own AWS account. The partner needs to access the data using their own account credentials. Which approach should the company use?

A.Use S3 cross-region replication.
B.Grant the partner's AWS account access via a bucket policy.
C.Create a pre-signed URL for the partner.
D.Provide the partner with an IAM user in the company's account.
AnswerB

A bucket policy grants cross-account access directly to the partner's AWS account principal, letting them use their own credentials without sharing keys. This satisfies the requirement for account-to-account sharing of a large S3 dataset, unlike IAM users or presigned URLs, which are tied to the source account or expire.

Why this answer

A bucket policy can grant cross-account access to the partner's AWS account by specifying the partner's AWS account ID as the principal. This allows the partner's IAM users or roles to access the S3 bucket directly using their own credentials, without needing to share access keys or create users in the company's account. The bucket policy must explicitly allow the necessary actions (e.g., s3:GetObject) and the partner must also have an IAM policy that permits the same actions.

Exam trap

The SAP-C02 exam often tests the misconception that pre-signed URLs are the only way to grant temporary access, but the question explicitly requires the partner to use their own account credentials, which only a bucket policy (or an S3 access point with a policy) can achieve.

How to eliminate wrong answers

Option A is wrong because S3 cross-region replication is used to automatically replicate objects to a different AWS region for data redundancy or compliance, not to grant cross-account access to a partner. Option C is wrong because a pre-signed URL grants temporary access to a specific object using a URL that embeds credentials, but it does not allow the partner to use their own AWS account credentials; it also expires and is not suitable for ongoing or large-scale access. Option D is wrong because providing an IAM user in the company's account would require the partner to use that user's credentials (access key and secret key) instead of their own account credentials, violating the requirement that the partner uses their own account credentials.

173
MCQmedium

A company is designing a new application that will use Amazon API Gateway and AWS Lambda. The application must authenticate users using an existing OpenID Connect (OIDC) identity provider. The company wants to minimize the amount of custom code required and ensure that only authenticated users can invoke the API. Which authentication method should be used?

A.Use AWS Lambda authorizer with a custom authorizer function that validates JWT tokens.
B.Use API Gateway resource policies to restrict access based on IP range.
C.Use API Gateway native OpenID Connect authorization with a JWT authorizer.
D.Use Amazon Cognito user pools with an OIDC identity provider.
AnswerC

API Gateway supports native OpenID Connect authorization with a JWT authorizer. You can configure it to validate tokens from your OIDC provider without writing any custom code. It automatically validates the token signature, issuer, and audience. This minimizes custom code and ensures only authenticated users can invoke the API.

Why this answer

API Gateway native OpenID Connect authorization with a JWT authorizer allows you to validate tokens from an OIDC provider without writing custom code. It automatically validates the token's signature, issuer, and audience, and only allows authenticated users to invoke the API. This meets the requirements with minimal custom code.

Exam trap

The trap here is assuming that a Lambda authorizer is required to validate JWT tokens, when API Gateway now supports native JWT authorizers for OIDC.

174
MCQmedium

A company is designing a new solution to process and analyze large volumes of log data. The data is generated continuously by thousands of IoT devices and must be ingested in near real-time. The company needs to perform simple transformations and aggregations on the data before storing it in Amazon S3 for long-term analysis. The solution must be highly available, scalable, and require minimal operational overhead. Which AWS service should the solutions architect use to ingest and transform the data?

A.Amazon Managed Streaming for Apache Kafka (Amazon MSK) with a Kafka Connect S3 sink connector.
B.Amazon Kinesis Data Firehose with an AWS Lambda function for transformation.
C.Amazon Kinesis Data Streams with an AWS Lambda function for transformation and an Amazon S3 destination.
D.AWS Glue with a scheduled job to process data from an Amazon S3 bucket.
AnswerB

Amazon Kinesis Data Firehose is a fully managed service that can ingest streaming data, transform it using AWS Lambda, and deliver it to Amazon S3. It automatically scales to handle varying throughput and requires no ongoing administration. It provides near real-time delivery and can buffer data before delivering to S3, making it ideal for this scenario.

Why this answer

Amazon Kinesis Data Firehose is a fully managed service that ingests streaming data, applies transformations via AWS Lambda, and delivers to Amazon S3. It scales automatically and requires no server management, providing near real-time processing with minimal operational overhead. This meets the requirements for continuous ingestion, transformation, and storage.

Exam trap

The trap here is assuming that Kinesis Data Streams with Lambda is equivalent to Firehose, but Data Streams requires managing shards and custom consumers, increasing operational overhead.

175
MCQhard

A company is designing a new application that requires low-latency access to a shared dataset across multiple EC2 instances in the same AWS Region. The dataset is updated frequently. Which storage solution should the company use?

A.Amazon S3
B.Amazon EBS with Provisioned IOPS
C.Amazon S3 Glacier
D.Amazon EFS
AnswerD

Amazon EFS provides a shared, elastic NFS file system mountable concurrently by many EC2 instances in one Region, with low-latency access to frequently updated data. This satisfies the shared-dataset constraint that instance-attached EBS volumes cannot meet.

Why this answer

Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently by multiple EC2 instances across different Availability Zones within the same AWS Region. It offers low-latency access and supports frequent updates through its standard storage class, making it ideal for shared datasets that require consistent, low-latency performance.

Exam trap

The trap here is that candidates often confuse block storage (EBS) with shared file storage, assuming EBS can be attached to multiple instances simultaneously, or they overlook the latency and protocol differences between object storage (S3) and file storage (EFS) for shared, low-latency workloads.

How to eliminate wrong answers

Option A is wrong because Amazon S3 is an object storage service accessed via HTTP/S APIs, not a file system; it introduces higher latency and does not support low-latency file-level locking or concurrent NFS-style access required by multiple EC2 instances. Option B is wrong because Amazon EBS volumes are block-level storage that can only be attached to a single EC2 instance at a time (except for multi-attach EBS, which is limited to specific instance types and is not designed for shared, frequently updated datasets across many instances). Option C is wrong because Amazon S3 Glacier is designed for archival and long-term backup with retrieval times ranging from minutes to hours, making it completely unsuitable for low-latency, frequently updated access.

176
Multi-Selecthard

A company is designing a new solution to host a static website with global low latency. The website content is stored in an S3 bucket and must be secured with HTTPS. Which three services or features should be used together to meet these requirements?

Select 3 answers
A.Application Load Balancer
B.S3 bucket configured as an origin with Origin Access Control (OAC)
C.Amazon Route 53
D.AWS Certificate Manager (ACM) to provision a custom SSL certificate
E.Amazon CloudFront
AnswersB, D, E

Restricts direct access to S3, ensuring content is served only through CloudFront.

Why this answer

Origin Access Control (OAC) allows CloudFront to securely access the S3 bucket without making the bucket public, enforcing that all requests come through CloudFront. This is the modern replacement for Origin Access Identity (OAI) and supports HTTPS between CloudFront and S3.

Exam trap

The trap here is that candidates often think an Application Load Balancer is needed for HTTPS termination, but CloudFront handles HTTPS natively with ACM, and ALB is unnecessary for static S3 content.

177
MCQhard

A company is designing a new hybrid cloud solution that requires low-latency access to on-premises data from AWS. The connection must be highly available and encrypted. The company has multiple VPCs and on-premises locations. Which combination of services meets these requirements?

A.AWS Site-to-Site VPN and VPC Endpoints
B.AWS Transit Gateway and AWS Direct Connect with VPN backup
C.VPC Peering and AWS Site-to-Site VPN
D.AWS Client VPN and VPC Peering
AnswerB

Transit Gateway provides a hub-and-spoke model for multiple VPCs and on-premises networks. Direct Connect offers dedicated low-latency connections with encryption, and VPN provides a backup.

Why this answer

AWS Transit Gateway acts as a central hub to interconnect multiple VPCs and on-premises networks, simplifying the hybrid architecture. AWS Direct Connect provides a private, low-latency, and consistent network path, while a Site-to-Site VPN over the Direct Connect link (or as a separate backup) adds encryption and high availability. This combination meets all requirements: low latency (Direct Connect), encryption (VPN), high availability (dual connections or failover), and support for multiple VPCs and on-premises locations (Transit Gateway).

Exam trap

The trap here is that candidates often assume a single VPN or Direct Connect alone is sufficient, but the question requires both low latency (Direct Connect) and encryption (VPN) across multiple VPCs and on-premises sites, which only Transit Gateway with Direct Connect and VPN backup fully satisfies.

How to eliminate wrong answers

Option A is wrong because VPC Endpoints are used for private access to AWS services (e.g., S3, DynamoDB) and do not provide connectivity to on-premises data centers; they also do not offer encryption or high availability for hybrid connectivity. Option C is wrong because VPC Peering does not support transitive routing (it is a one-to-one connection) and cannot connect multiple VPCs to multiple on-premises locations without a hub; additionally, it does not inherently provide encryption or low-latency guarantees for hybrid links. Option D is wrong because AWS Client VPN is a remote access VPN for individual clients (not site-to-site) and VPC Peering again lacks transitive routing and cannot aggregate multiple on-premises connections.

178
MCQeasy

A company wants to design a cost-effective solution to store infrequently accessed log files for 7 years. The logs are generated daily and must be available for retrieval within 24 hours. Which Amazon S3 storage class should be used?

A.S3 One Zone-Infrequent Access
B.S3 Intelligent-Tiering
C.S3 Glacier Deep Archive
D.S3 Standard
AnswerC

S3 Glacier Deep Archive offers the lowest storage cost for long-term retention and supports standard retrieval within 12 hours, satisfying the 24-hour availability constraint across the 7-year period. It is designed precisely for rarely accessed compliance archives.

Why this answer

Amazon S3 Glacier Deep Archive is the most cost-effective storage class for infrequently accessed data that must be retained for 7 years, with retrieval times of up to 12 hours (within the 24-hour requirement). It offers the lowest storage cost among S3 classes, making it ideal for long-term archival of log files that are rarely accessed.

Exam trap

The trap here is that candidates often confuse retrieval time requirements with access frequency, assuming that any 'Infrequent Access' class (like S3 One Zone-IA or S3 Standard-IA) is the best choice for archival, when in fact S3 Glacier Deep Archive is designed specifically for long-term, cost-effective archival with retrieval times that still meet the 24-hour window.

How to eliminate wrong answers

Option A is wrong because S3 One Zone-Infrequent Access is designed for data that is accessed infrequently but requires rapid retrieval (milliseconds), and it stores data in a single Availability Zone, which does not provide the durability needed for a 7-year retention period; its cost is higher than Glacier Deep Archive for long-term archival. Option B is wrong because S3 Intelligent-Tiering automatically moves data between access tiers based on usage patterns, but it is not optimized for purely archival data that will almost never be accessed; it incurs monitoring and automation fees that make it less cost-effective than Glacier Deep Archive for data that will be stored for 7 years with infrequent access. Option D is wrong because S3 Standard is designed for frequently accessed data with millisecond retrieval and is the most expensive storage class, making it unsuitable for cost-effective long-term archival of infrequently accessed logs.

179
MCQmedium

A media company is deploying a new video transcoding pipeline on AWS. The pipeline will process thousands of small input files stored in Amazon S3, and each file must be transcoded independently. The transcoding jobs are short (under 5 minutes) and stateless. The company wants a solution that scales automatically, minimizes operational overhead, and provides near-real-time processing. Which design should a solutions architect recommend?

A.Use AWS Lambda functions triggered by S3 event notifications to process each file as it is uploaded.
B.Use AWS Step Functions to orchestrate a fleet of Amazon EC2 instances that poll an Amazon SQS queue for new files.
C.Use AWS Batch with a managed compute environment to run transcoding jobs on Amazon EC2 Spot Instances.
D.Use Amazon Kinesis Data Firehose to stream the video files to Amazon Elastic Transcoder for processing.
AnswerA

AWS Lambda is ideal for short, stateless, event-driven tasks. S3 event notifications can invoke a Lambda function synchronously when an object is created, enabling near-real-time processing. Lambda automatically scales with the number of events, and there is no infrastructure to manage. This matches the requirements for low operational overhead and automatic scaling for small, independent transcoding jobs.

Why this answer

The requirement for near-real-time processing of small, independent files with minimal operational overhead points to a serverless, event-driven architecture. AWS Lambda integrates natively with S3 event notifications, allowing each uploaded file to trigger a function immediately. Lambda scales automatically and eliminates server management.

Other options introduce polling, orchestration overhead, or unsuitable services, failing to meet the low-latency and low-ops goals.

Exam trap

The trap here is assuming that any scalable compute service (like AWS Batch or Step Functions with EC2) is equally suitable, overlooking the need for event-driven, near-real-time processing and minimal operational overhead.

180
MCQeasy

A company is migrating a legacy on-premises application to AWS. The application requires a shared file system that can be mounted on multiple Amazon EC2 instances across multiple Availability Zones. The file system must be highly available, durable, and support POSIX permissions. The company wants a fully managed solution. Which AWS service should a solutions architect recommend?

A.Amazon S3 with a file gateway deployed on each EC2 instance.
B.Amazon Elastic Block Store (Amazon EBS) with Multi-Attach enabled.
C.Amazon Elastic File System (Amazon EFS).
D.Amazon FSx for Windows File Server.
AnswerC

Amazon EFS is a fully managed, elastic NFS file system that can be mounted on multiple EC2 instances across multiple Availability Zones. It provides high availability and durability by storing data redundantly across Availability Zones. It supports POSIX permissions and is designed for shared access, making it the ideal solution for this legacy application requiring a shared file system.

Why this answer

Amazon Elastic File System (Amazon EFS) is a fully managed, scalable, and elastic NFS file system for Linux-based workloads. It can be mounted on multiple EC2 instances across multiple Availability Zones simultaneously, providing high availability and durability. It supports POSIX permissions and is designed for shared access, making it the correct choice for a legacy application requiring a shared file system.

Exam trap

The trap here is confusing Amazon EBS Multi-Attach with a shared file system; Multi-Attach is limited to a single Availability Zone and does not support POSIX-compliant shared access.

181
MCQeasy

A company is designing a solution to capture changes from an Amazon RDS database and stream them to a data lake. Which AWS service should be used to capture database changes in real time?

A.AWS Glue with streaming ETL
B.AWS Lambda with database polling
C.Amazon Kinesis Data Streams with a custom producer
D.AWS Database Migration Service (DMS) with change data capture (CDC)
AnswerD

AWS DMS with change data capture reads the database's transaction logs (or redo logs) and streams row-level inserts, updates and deletions continuously, satisfying the real-time capture requirement. Unlike batch exports, CDC propagates changes as they commit, feeding the data lake with minimal latency.

Why this answer

AWS DMS with change data capture (CDC) is the correct service because it is specifically designed to capture ongoing changes from source databases (including Amazon RDS) in near real time and replicate them to targets like Amazon S3 (data lake). DMS reads the database transaction logs (e.g., MySQL binlog, PostgreSQL WAL) to capture inserts, updates, and deletes without requiring application-level polling or custom code, making it the most appropriate managed solution for streaming database changes to a data lake.

Exam trap

The trap here is that candidates often confuse AWS DMS with other streaming services like Kinesis or Glue, not realizing that DMS is the only AWS service that natively captures database transaction log changes without requiring custom code or polling.

How to eliminate wrong answers

Option A is wrong because AWS Glue with streaming ETL is designed for processing streaming data from sources like Amazon Kinesis or Kafka, not for capturing changes directly from an RDS database; it lacks native CDC capabilities to read database transaction logs. Option B is wrong because AWS Lambda with database polling requires custom code to repeatedly query the database for changes, which introduces latency, increased load on the database, and is not a real-time streaming solution; it also does not capture deletes or changes efficiently without additional logic. Option C is wrong because Amazon Kinesis Data Streams with a custom producer requires you to build and manage your own application to poll the RDS database and push changes to Kinesis, adding operational overhead and complexity; it does not provide native CDC integration with database transaction logs.

182
MCQeasy

A company is designing a new solution to store and analyze large amounts of log data from multiple sources. The logs must be retained for 90 days for recent analysis, and then archived to a more cost-effective storage class for an additional 5 years. The solution must support SQL-based queries. Which combination of AWS services should the company use?

A.Amazon Redshift with data sharing to retain logs for 5 years.
B.Amazon S3 with lifecycle policies to transition objects to S3 Glacier Deep Archive after 90 days, and Amazon Athena for SQL queries.
C.Amazon OpenSearch Service with UltraWarm storage to archive logs after 90 days.
D.Amazon RDS for PostgreSQL with automated backups to retain logs for 5 years.
AnswerB

S3 lifecycle policies automatically transition objects to Glacier Deep Archive after 90 days, meeting the 5-year archival cost constraint. Athena queries S3 directly using standard SQL, so no separate database or ETL pipeline is needed for the recent-analysis requirement.

Why this answer

Amazon S3 with lifecycle policies can automatically transition log objects from S3 Standard to S3 Glacier Deep Archive after 90 days, meeting the 90-day retention for recent analysis and the 5-year archival requirement at the lowest cost. Amazon Athena allows SQL-based queries directly on the log data stored in S3, without needing to load data into a separate database, making it a serverless and cost-effective solution for ad-hoc analysis.

Exam trap

The trap here is that candidates often confuse Amazon OpenSearch Service's UltraWarm storage as a long-term archival solution, but it is actually a warm tier for less-frequently accessed data within the same cluster, not a cost-effective cold archive like S3 Glacier Deep Archive, and it does not support SQL queries natively.

How to eliminate wrong answers

Option A is wrong because Amazon Redshift is a data warehouse optimized for structured, frequently queried data, not for storing large volumes of raw log data over long periods; using data sharing does not provide a cost-effective archival tier like S3 Glacier Deep Archive, and retaining logs for 5 years in Redshift would be prohibitively expensive. Option C is wrong because Amazon OpenSearch Service with UltraWarm storage is designed for near-real-time search and analytics on log data, but it does not support SQL-based queries natively (it uses its own query DSL) and UltraWarm is not a long-term archival tier; it also lacks the cost efficiency of S3 Glacier Deep Archive for 5-year retention. Option D is wrong because Amazon RDS for PostgreSQL is a relational database service intended for transactional workloads, not for storing and analyzing large volumes of log data; automated backups are for point-in-time recovery, not for long-term archival, and storing logs for 5 years in RDS would incur high storage costs and performance issues.

183
MCQhard

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

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

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

Why this answer

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

Exam trap

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

184
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

185
Multi-Selecthard

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

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

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

Why this answer

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

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

Exam trap

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

186
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

187
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

188
Multi-Selectmedium

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

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

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

Why this answer

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

Exam trap

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

189
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

190
MCQhard

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

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

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

Why this answer

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

Exam trap

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

191
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

192
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

193
Multi-Selectmedium

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

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

Read replicas offload read traffic from the primary database.

Why this answer

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

Exam trap

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

194
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

195
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

196
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

197
Multi-Selectmedium

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

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

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

Why this answer

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

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

Exam trap

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

198
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

199
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

200
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

201
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

202
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

203
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

204
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

205
Multi-Selectmedium

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

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

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

Why this answer

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

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

Exam trap

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

206
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

207
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

208
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

209
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

210
Multi-Selecteasy

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

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

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

Why this answer

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

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

Exam trap

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

211
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

212
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

213
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

214
MCQhard

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

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

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

Why this answer

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

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

215
MCQeasy

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

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

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

Why this answer

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

216
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

217
MCQmedium

A developer ran the AWS CLI command shown in the exhibit. The instance has an attached EBS volume with 'DeleteOnTermination' set to false. The instance will be started again soon. What will happen to the EBS volume when the instance is stopped?

A.The EBS volume is detached but the data is preserved.
B.The EBS volume is deleted.
C.The EBS volume is deleted because the instance is stopped.
D.The EBS volume remains attached to the instance and the data persists.
AnswerD

Stopping an EBS-backed instance detaches nothing: the volume stays attached and its data persists. DeleteOnTermination only governs deletion when the instance terminates, so setting it false is irrelevant to a stop/start cycle. The volume simply reattaches on next start.

Why this answer

Stopping an EC2 instance does not affect the attached EBS volumes; they remain attached and their data persists. The 'DeleteOnTermination' attribute only controls behavior when the instance is terminated, not stopped. Since the instance will be started again soon, the volume stays attached with its data intact.

Exam trap

The trap here is that candidates confuse the 'stop' and 'terminate' actions, incorrectly assuming that 'DeleteOnTermination' applies to both, when in fact it only applies to termination.

How to eliminate wrong answers

Option A is wrong because stopping an instance does not detach the EBS volume; the volume remains attached and available when the instance is started again. Option B is wrong because the EBS volume is not deleted when the instance is stopped; deletion only occurs on instance termination if 'DeleteOnTermination' is set to true, which it is not. Option C is wrong because the volume is not deleted due to the instance being stopped; the 'DeleteOnTermination' attribute is irrelevant during a stop operation.

218
MCQhard

A healthcare company is designing a new system on AWS to store and analyze patient health records. The system must comply with HIPAA regulations. Data includes structured lab results and unstructured clinical notes. The company needs to run complex SQL queries on the structured data and perform natural language processing (NLP) on the unstructured data. The solution should be cost-effective and minimize administrative overhead. Which solution should a Solutions Architect recommend?

A.Store structured data in Amazon RDS for PostgreSQL, store unstructured data in S3, and use AWS Glue to run NLP jobs.
B.Store all data in S3, use Amazon Athena for SQL queries and Amazon Textract for NLP.
C.Store structured data in DynamoDB, store unstructured data in S3, use Amazon SageMaker to build custom NLP models.
D.Store structured data in Amazon Redshift, store unstructured data in S3, and use Amazon Comprehend Medical for NLP.
AnswerD

Redshift handles complex SQL analytics on structured lab results, S3 stores unstructured clinical notes cost-effectively, and Amazon Comprehend Medical provides HIPAA-eligible NLP for extracting medical entities. This combination meets the query, NLP, cost and low-administrative-overhead constraints within a compliant AWS architecture.

Why this answer

Amazon Redshift is a petabyte-scale, columnar data warehouse optimized for complex analytical SQL queries over structured data, which fits the lab results workload. Amazon Comprehend Medical is a HIPAA-eligible, purpose-built NLP service that extracts medical entities (medications, conditions, PHI) from unstructured clinical notes without requiring custom model training. Both services are fully managed, minimizing administrative overhead, and the combination is cost-effective for this mixed workload.

S3 provides durable, low-cost storage for the unstructured notes that Comprehend Medical reads directly.

Exam trap

SAP-C02 often tests whether candidates confuse general-purpose AI/ML services (Textract, Glue, SageMaker) with purpose-built, HIPAA-eligible medical NLP services like Comprehend Medical, leading them to pick a solution that technically 'processes text' but lacks medical entity extraction and compliance alignment.

How to eliminate wrong answers

Option A is wrong because AWS Glue is an ETL service, not an NLP engine — it cannot perform natural language processing on clinical notes; you would still need a separate NLP service like Comprehend Medical. Option B is wrong because Amazon Textract is an OCR/document-text-extraction service, not a medical NLP service; it extracts text from images/PDFs but does not derive medical insights from clinical notes, and Athena alone is not ideal for complex, high-concurrency analytical SQL at scale. Option C is wrong because DynamoDB is a NoSQL key-value store that does not support complex SQL queries, and building custom NLP models with SageMaker incurs significant ML engineering effort and cost, violating the minimize-administrative-overhead and cost-effective requirements.

219
MCQmedium

A logistics company is designing a new event-driven system to process shipment tracking updates. The system must ingest millions of events per second from thousands of IoT devices, retain the events for up to 7 days so multiple independent consumer applications can replay them, and deliver each event to consumers in the order it was received per device. Which AWS service should a solutions architect recommend as the ingestion and retention layer?

A.Amazon Simple Queue Service (Amazon SQS) FIFO queues with a message retention period of 7 days.
B.Amazon EventBridge with an event bus and archive and replay configured for 7 days.
C.Amazon Managed Streaming for Apache Kafka (Amazon MSK) with a topic retention of 7 days and a single partition per topic.
D.Amazon Kinesis Data Streams with a retention period of 7 days and partition keys based on device ID.
AnswerD

Kinesis Data Streams ingests high volumes of events and retains records for up to 365 days, with 7 days meeting the requirement. Multiple consumer applications can read the same stream independently and replay records within the retention window. Using the device ID as the partition key ensures all events from a given device land in the same shard and are delivered in order.

Why this answer

Kinesis Data Streams is built for high-throughput, ordered event ingestion with configurable retention, and it allows multiple independent consumers to read and replay the same records. Partitioning by device ID guarantees that all events from one device are processed in order by a single consumer. This directly meets the ingestion rate, 7-day retention, replay, and per-device ordering requirements.

Exam trap

The trap here is selecting Amazon SQS FIFO because it preserves order, while overlooking that SQS messages are deleted after consumption and therefore cannot be replayed by multiple independent consumer applications.

220
MCQmedium

A financial-services company is designing a new multi-tenant SaaS platform on AWS. Each tenant must be able to bring its own AWS KMS customer managed key (CMK) so that tenant data is encrypted with a key the tenant controls and can revoke at any time. The platform stores objects in a single Amazon S3 bucket shared by all tenants and must support per-tenant key revocation without redeploying the application. Which design meets these requirements with the LEAST operational overhead?

A.Use S3 server-side encryption with Amazon S3 managed keys (SSE-S3) and store a per-tenant envelope key in AWS Secrets Manager, encrypting each object client-side with that secret before upload.
B.Enable S3 default encryption with SSE-KMS using a single platform-owned CMK, and use S3 Access Points with a per-tenant access point policy to isolate tenant prefixes.
C.Use S3 server-side encryption with AWS KMS keys (SSE-KMS) and specify a tenant-specific CMK in the x-amz-server-side-encryption-aws-kms-key-id header on each PutObject request, granting the platform role kms:GenerateDataKey and kms:Decrypt on each tenant CMK.
D.Create a separate S3 bucket per tenant and configure each bucket with SSE-KMS using a tenant-owned CMK via a bucket key, then use S3 Inventory to track objects across buckets.
AnswerC

SSE-KMS accepts a per-request CMK identifier, so each tenant object is wrapped with that tenant's key. Revoking the tenant's CMK or the platform's kms:Decrypt grant immediately blocks decryption of that tenant's objects, satisfying per-tenant revocability. Granting kms:GenerateDataKey and kms:Decrypt to the platform role is the minimal IAM surface needed, and no infrastructure change is required when a tenant rotates or revokes a key.

Why this answer

Per-tenant customer managed keys in AWS KMS can be selected at PutObject time through the SSE-KMS key-id header, letting one shared S3 bucket hold objects encrypted under many tenant-controlled keys. Because decryption requires kms:Decrypt on the specific CMK, revoking that grant or disabling the tenant CMK instantly cuts off access to that tenant's objects without redeploying or restructuring storage, which is the lowest-overhead way to meet the bring-your-own-key and revocation requirements.

Exam trap

The trap here is assuming that prefix isolation or S3 Access Points provide tenant-controlled encryption, when key ownership and revocation can only come from a tenant-owned KMS customer managed key.

221
MCQmedium

A company is designing a new solution to process streaming data from IoT devices. The data must be ingested, processed in real-time, and stored in a data warehouse for analytics. The company expects millions of events per second. Which combination of AWS services should be used?

A.Amazon Kinesis Data Firehose for ingestion and delivery to Amazon S3, then use AWS Glue for ETL into Amazon Redshift.
B.Amazon DynamoDB Streams for ingestion, AWS Lambda for processing, and Amazon Redshift for storage.
C.Amazon SQS for ingestion, AWS Lambda for processing, and Amazon DynamoDB for storage.
D.Amazon Kinesis Data Streams for ingestion, Amazon Kinesis Data Analytics for real-time processing, and Amazon S3 as a staging area before loading into Amazon Redshift.
AnswerD

Kinesis Data Streams sustains millions of events per second with ordered, replayable ingestion, while Kinesis Data Analytics performs real-time SQL/Flink processing. S3 stages the processed output before Redshift's columnar load, satisfying the real-time processing and warehousing constraints without provisioning servers.

Why this answer

Amazon Kinesis Data Streams can ingest millions of events per second with durable, ordered shards, while Kinesis Data Analytics provides real-time SQL or Apache Flink processing on the stream. Amazon S3 acts as a staging layer before loading into Amazon Redshift via COPY or Redshift Spectrum, enabling scalable analytics without throttling the ingestion pipeline.

Exam trap

The SAP-C02 exam often tests the distinction between Kinesis Data Streams (real-time, sub-second) and Kinesis Data Firehose (near-real-time, minutes of latency), leading candidates to choose Firehose for real-time requirements.

How to eliminate wrong answers

Option A is wrong because Kinesis Data Firehose is a near-real-time delivery service with a minimum buffer interval of 60 seconds, which cannot meet the sub-second real-time processing requirement for millions of events per second. Option B is wrong because DynamoDB Streams are designed for change data capture from a DynamoDB table, not for direct ingestion of high-throughput streaming data from IoT devices, and DynamoDB Streams have a limited retention period (24 hours) and throughput constraints. Option C is wrong because Amazon SQS is a message queue with at-least-once delivery and no native ordering guarantees (unless using FIFO, which limits throughput to 300 TPS), making it unsuitable for high-velocity, ordered streaming data; DynamoDB is not a data warehouse optimized for complex analytics queries.

222
MCQmedium

A company is designing a new application that will process messages from an SQS queue. The messages must be processed in real-time with minimal latency, and the processing time per message varies from 100 ms to 5 seconds. The company wants to minimize cost and operational overhead. Which solution should the architect recommend?

A.Use Amazon Kinesis Data Streams and an AWS Lambda function
B.Use an SQS queue and an EC2 Auto Scaling group to poll and process messages
C.Use an SQS queue as an event source for an AWS Lambda function
D.Use SQS to send messages to Amazon SNS, which triggers a Lambda function
AnswerC

Lambda's SQS event source mapping polls the queue and invokes functions per batch, scaling automatically with no servers to manage. It handles variable 100 ms to 5 s processing and charges per invocation, meeting the real-time, low-latency, low-overhead and cost constraints.

Why this answer

Using an SQS queue as an event source for AWS Lambda enables real-time, low-latency processing of messages without any polling infrastructure to manage. Lambda automatically scales to handle variable processing times (100 ms to 5 seconds) and charges only for compute time used, minimizing both cost and operational overhead. This serverless approach eliminates the need for EC2 instances or Auto Scaling groups, aligning perfectly with the requirements for minimal latency and reduced management effort.

Exam trap

The trap here is that candidates often assume EC2 Auto Scaling is required for variable processing times, overlooking Lambda's native ability to scale instantly and cost-effectively for SQS-triggered workloads, or they mistakenly add unnecessary services like SNS or Kinesis that increase latency and cost without benefit.

How to eliminate wrong answers

Option A is wrong because Amazon Kinesis Data Streams is designed for streaming large volumes of data with shard-level throughput limits, not for individual message processing with variable latency, and it introduces higher cost and operational complexity compared to SQS-Lambda integration. Option B is wrong because using an EC2 Auto Scaling group to poll SQS adds significant operational overhead for managing instances, scaling policies, and polling logic, and it cannot match the sub-second scaling and cost efficiency of Lambda for variable processing times. Option D is wrong because adding Amazon SNS between SQS and Lambda introduces unnecessary latency and complexity; SQS can directly trigger Lambda without SNS, and SNS is typically used for fan-out to multiple subscribers, not for simple message processing.

223
MCQeasy

A retail company is designing a new order-processing workflow. When an order is placed, an Amazon API Gateway endpoint invokes an AWS Lambda function that must validate the order, then wait for a human fraud analyst to approve or reject it, and finally send a confirmation email. The approval can take up to three days, and the company wants to minimize operational overhead. Which design should the solutions architect use?

A.Use AWS Step Functions Express workflows with a wait state that polls Amazon DynamoDB for the analyst decision on a fixed interval.
B.Use an Amazon EventBridge rule that schedules a Lambda function every five minutes to check whether the analyst has approved the order.
C.Use AWS Step Functions Standard workflows with a Lambda task for validation, a callback pattern using a task token for the analyst decision, and a Lambda task to send the email.
D.Use a single long-lived Lambda function that polls an Amazon SQS queue for the analyst decision until it arrives or the function times out.
AnswerC

Standard workflows support long-running executions of up to one year and the callback task token pattern, which pauses the state machine until the analyst's decision is submitted. This models the human approval step directly, and Step Functions manages retries, state, and error handling so the team writes almost no orchestration code.

Why this answer

Step Functions Standard workflows run for up to a year and support the callback task token pattern, which is purpose-built for pausing a workflow until an external human or system responds. The analyst's approval action calls SendTaskSuccess or SendTaskFailure with the token, resuming the state machine, which then invokes the email step. Retries, timeouts, and state persistence are handled by the service.

Exam trap

The trap here is reaching for a polling loop, when the callback task token pattern exists precisely so a workflow can wait indefinitely for an external decision without polling.

224
Multi-Selectmedium

Which TWO design patterns help ensure data durability in Amazon S3?

Select 2 answers
A.Enable Cross-Region Replication (CRR).
B.Enable S3 Versioning.
C.Enable MFA Delete.
D.Use S3 Standard-IA storage class.
E.Configure lifecycle policies to transition to Glacier.
AnswersA, B

Cross-Region Replication asynchronously copies objects to a bucket in another AWS Region, so data survives a regional outage or account-level event. This directly satisfies the durability requirement by providing an independent replica outside the source Region.

Why this answer

Option A (Enable Cross-Region Replication) is correct because CRR automatically replicates objects to a destination bucket in a different AWS Region, so data survives a regional outage or the loss of the source bucket, directly improving durability. Option B (Enable S3 Versioning) is correct because it keeps multiple distinct versions of every object, so an overwrite or delete of the current version does not destroy the prior data, allowing recovery of earlier versions. Option C (MFA Delete) only adds an authentication requirement for deleting versions or changing versioning state; it is a protective control, not a durability mechanism.

Option D (S3 Standard-IA) is a cost-optimized storage class that changes retrieval pricing and availability characteristics, not the underlying durability of the data. Option E (lifecycle transition to Glacier) is a cost/archival management action that moves objects to cheaper storage, and does not by itself increase durability.

Exam trap

SAP-C02 often tests the distinction between durability (protecting data from loss) and availability/cost (storage classes, lifecycle) — the trap is selecting MFA Delete or Glacier transitions, which are security/cost controls, not durability patterns.

225
MCQhard

A company is migrating a legacy on-premises application to AWS. The application requires a fixed IP address for whitelisting by external partners. The solution must be highly available across multiple Availability Zones. Which design should they use?

A.Use an Application Load Balancer (ALB) with an Elastic IP address.
B.Use Amazon Route 53 with a weighted routing policy.
C.Use a Network Load Balancer (NLB) with an Elastic IP address.
D.Use a Classic Load Balancer (CLB) with an Elastic IP address.
AnswerC

A Network Load Balancer supports Elastic IP addresses per Availability Zone, giving external partners stable public IPs for whitelisting. Because the NLB spans multiple AZs, the fixed addresses remain reachable if one AZ fails, meeting the high availability requirement.

Why this answer

A Network Load Balancer (NLB) supports static IP addresses via Elastic IPs per Availability Zone, providing a fixed IP for partner whitelisting while maintaining high availability across multiple AZs. Unlike ALBs, NLBs operate at Layer 4 and can preserve the client IP, which is critical for IP-based whitelisting scenarios.

Exam trap

The trap here is that candidates often assume an ALB can use Elastic IPs because it is a modern load balancer, but ALBs are DNS-based and cannot be assigned static IPs, making the NLB the only correct choice for fixed IP whitelisting with high availability.

How to eliminate wrong answers

Option A is wrong because an Application Load Balancer (ALB) does not support Elastic IP addresses; it uses a DNS name and its IP addresses can change, making it unsuitable for fixed IP whitelisting. Option B is wrong because Amazon Route 53 with a weighted routing policy distributes traffic across multiple endpoints but does not provide a single fixed IP address for whitelisting; it relies on DNS resolution which can change. Option D is wrong because a Classic Load Balancer (CLB) can be assigned an Elastic IP, but it is a legacy service that does not support multiple Availability Zones natively and lacks the high availability and performance features of an NLB.

← PreviousPage 3 of 5 · 321 questions totalNext →

Ready to test yourself?

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