Courseiva

AWS Certified Solutions Architect Professional SAP-C02 (SAP-C02) — Questions 676–750

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

Page 9

Page 10 of 14

Page 11
676
MCQhard

A company is migrating a large Oracle database to Amazon Aurora PostgreSQL using AWS DMS. The database is 5 TB and has frequent write operations. The migration must have minimal downtime. Which configuration should be used?

A.Use AWS DMS with full load and ongoing replication using CDC
B.Use AWS DataSync for the database files
C.Use AWS SCT to convert schema and then copy data manually
D.Use AWS DMS with full load only
AnswerA

AWS DMS full load copies the existing 5 TB dataset, then ongoing replication applies change data capture from the source transaction logs, continuously propagating writes to Aurora PostgreSQL. This keeps the target current until cutover, achieving the minimal downtime the migration demands.

Why this answer

AWS DMS with full load and ongoing replication using CDC allows continuous syncing after the full load, minimizing downtime. Option D (full load only) would cause downtime during migration. Option B (AWS DataSync) is for file-based data, not databases.

Option C (AWS SCT) is for schema conversion only, not data migration.

677
MCQeasy

A company wants to modernize a batch processing application that runs on EC2 instances using a cron job. The job processes files from an S3 bucket and takes about 2 hours. They want to reduce operational overhead. Which service should they use?

A.AWS Batch
B.Amazon ECS with Fargate
C.AWS Lambda
D.AWS Step Functions
AnswerA

AWS Batch manages the compute environment, queueing and scheduling, removing the cron and EC2 instance maintenance. It satisfies the reduced-operational-overhead constraint while handling the two-hour S3-sourced job, since Batch supports long-running jobs that AWS Lambda's fifteen-minute limit would preclude.

Why this answer

AWS Batch is purpose-built for batch computing workloads, automatically provisioning and managing compute resources (EC2 or Fargate) based on job requirements. It handles job queuing, scheduling, dependency management, and retries, eliminating the need to manage cron jobs or EC2 instances. The 2-hour runtime is well within Batch's capabilities, and it integrates natively with S3 for data input/output.

This reduces operational overhead by abstracting infrastructure management while providing cost-effective scaling.

Exam trap

SAP-C02 often tests the misconception that AWS Lambda can handle any duration if you just increase memory, but the 15-minute hard limit makes it unsuitable for long-running batch jobs; similarly, candidates may confuse Step Functions as a compute service when it only orchestrates.

How to eliminate wrong answers

Option B is wrong because Amazon ECS with Fargate is a container orchestration service that still requires you to manage task definitions, services, and scheduling (e.g., via CloudWatch Events or manual API calls) — it does not provide native batch job queuing, dependency handling, or automatic retries. Option C is wrong because AWS Lambda has a maximum execution timeout of 15 minutes, far short of the 2-hour processing time. Option D is wrong because AWS Step Functions is a serverless workflow orchestrator that coordinates multiple steps but does not itself run compute; you would still need to integrate with other services (like Lambda or ECS) and manage the underlying compute, adding complexity rather than reducing operational overhead for a single long-running batch job.

678
MCQhard

A company runs a stateless web application on an Auto Scaling group of Amazon EC2 instances behind an Application Load Balancer. The instances use a launch template with a base Amazon Machine Image and run a user data script that installs the application, which takes about 8 minutes. During a scale-out event, new instances fail the load balancer health checks for several minutes, causing 5xx errors. The company wants to reduce the time from instance launch to serving traffic without changing the application. Which solution will meet these requirements MOST cost-effectively?

A.Create a golden Amazon Machine Image with the application pre-installed and update the launch template to use it.
B.Increase the instance size in the launch template to a larger instance type.
C.Configure the Auto Scaling group to use a warm pool with a large number of pre-initialized instances.
D.Enable Elastic Load Balancing cross-zone load balancing and increase the health check interval.
AnswerA

A golden AMI eliminates the 8-minute installation during boot, so new instances pass health checks quickly. This is the most cost-effective fix because it requires no additional running services and directly addresses the slow bootstrap. Updating the launch template ensures all new instances use the pre-baked image, reducing scale-out latency.

Why this answer

Baking the application into a golden AMI removes the lengthy user data installation step, so new instances can pass health checks almost immediately after launch. This directly reduces scale-out latency and is the most cost-effective because it avoids ongoing costs of warm pools or larger instances. Other options either add cost or do not address the slow bootstrap.

Exam trap

The trap here is assuming that a warm pool is always the most cost-effective way to reduce launch time, when a golden AMI eliminates the bootstrap delay entirely without ongoing costs.

679
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.

680
MCQmedium

A company is migrating an on-premises monolithic application to AWS. The application uses a legacy database that cannot be easily refactored. The company wants to minimize changes to the application code while gaining scalability and high availability. Which migration strategy should the architect recommend?

A.Rehost the application on Amazon EC2 and use Amazon RDS for the database.
B.Replatform the application to use AWS Elastic Beanstalk and Amazon DynamoDB.
C.Refactor the application to use a microservices architecture with Amazon Aurora.
D.Retire the application and replace it with a SaaS solution.
AnswerA

Rehosting on Amazon EC2 preserves the application's existing code, satisfying the minimal-change constraint, while Amazon RDS supplies managed Multi-AZ high availability and read-replica scalability for the legacy database. Because the monolith cannot be refactored, lift-and-shift onto EC2 with a managed database engine avoids code rewrites yet still delivers the required resilience.

Why this answer

Rehosting (lift-and-shift) moves the application to Amazon EC2 and the legacy database to Amazon RDS with minimal code changes, satisfying the requirement to minimize application modifications. Amazon RDS provides managed high availability through Multi-AZ deployments and read scalability via read replicas, while EC2 offers the familiar environment the monolithic app expects. This strategy preserves the existing database engine compatibility (e.g., Oracle, SQL Server) so the application's connection strings and queries remain largely unchanged.

It directly addresses scalability and HA without forcing a refactor or replatform.

Exam trap

SAP-C02 often tests the trade-off between migration speed and optimization, tempting candidates to choose replatforming or refactoring when the requirement explicitly says 'minimize changes' — the trap is over-engineering the solution instead of selecting the simplest lift-and-shift.

How to eliminate wrong answers

Option B is wrong because replatforming to Elastic Beanstalk and DynamoDB requires significant code changes to replace relational database calls with NoSQL APIs, violating the 'minimize changes' constraint. Option C is wrong because refactoring to microservices with Aurora is a major architectural rewrite that contradicts the goal of minimal code changes and is unnecessary for a lift-and-shift migration. Option D is wrong because retiring and replacing with SaaS abandons the existing application entirely, which is not a migration strategy that preserves the legacy database or minimizes changes.

681
MCQmedium

A company runs a web application on Amazon EC2 instances in an Auto Scaling group. The application stores user session data in a local MySQL database on each instance, which has caused issues when instances are replaced. The company wants to make the application stateless and improve scalability. Which solution should a solutions architect recommend?

A.Store session data in an Amazon RDS for MySQL database with Multi-AZ.
B.Use Amazon S3 to store session data and have the application read/write to it.
C.Enable sticky sessions on the Application Load Balancer.
D.Move the session data to an Amazon ElastiCache for Redis cluster and configure the application to use it.
AnswerD

Storing session data in ElastiCache for Redis decouples session state from individual instances, making the application stateless. Redis provides high performance and scalability, and it is a managed service, reducing operational overhead. This allows the Auto Scaling group to scale in and out without losing session data, and it improves the application's ability to handle load.

Why this answer

To make the application stateless, session data must be externalized to a shared, scalable store. Amazon ElastiCache for Redis is an in-memory data store that provides low-latency access and high throughput, ideal for session management. It is a managed service, so it reduces operational overhead.

This allows instances to be added or removed without affecting user sessions, improving scalability and resilience.

Exam trap

The trap here is thinking that sticky sessions or storing session data in a database solves the statelessness problem, when in fact they either don't remove state from instances or introduce performance and scalability limitations.

682
Multi-Selectmedium

A company is designing a multi-account strategy using AWS Organizations. They want to enforce that no one can disable AWS CloudTrail in any account. Which TWO methods can achieve this?

Select 2 answers
A.Use AWS Trusted Advisor to alert when CloudTrail is disabled.
B.Attach a Service Control Policy (SCP) that denies disabling or deleting CloudTrail.
C.Use AWS Shield Advanced to protect CloudTrail.
D.Use AWS Config rules with auto-remediation to re-enable CloudTrail if disabled.
E.Use IAM permissions boundaries to restrict user permissions.
AnswersB, D

SCPs define the maximum permissions for principals in member accounts, so a deny statement for cloudtrail:StopLogging and DeleteTrail blocks the action at the Organizations level before IAM is evaluated, satisfying the requirement that no one in any account can disable CloudTrail.

Why this answer

Option B is correct because an SCP attached at the organization, OU, or account level in AWS Organizations can explicitly deny the CloudTrail actions that stop or delete a trail (for example cloudtrail:StopLogging, cloudtrail:DeleteTrail, and cloudtrail:UpdateTrail), which centrally prevents any principal in member accounts from disabling CloudTrail. Option D is correct because AWS Config can evaluate CloudTrail configuration with a managed rule such as cloudtrail-enabled and trigger automatic remediation (for example via SSM Automation) to re-enable logging if a trail is stopped or deleted, restoring the desired state. Option A is not correct because Trusted Advisor only provides advisory checks and alerts; it cannot enforce or prevent the disabling of CloudTrail.

Option C is not correct because AWS Shield Advanced is a DDoS protection service and has no role in controlling CloudTrail configuration. Option E is not correct because IAM permissions boundaries only limit the maximum permissions of an IAM entity and do not by themselves enforce organization-wide denial of CloudTrail changes across all accounts.

Exam trap

The trap here is that candidates often confuse IAM permissions boundaries or Trusted Advisor alerts as preventive controls, but only SCPs provide a true preventive guardrail that cannot be overridden by account administrators.

683
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.

684
MCQhard

A company is using AWS Migration Hub to track a server migration. The migration task has failed with the error shown in the exhibit. Which action should the solutions architect take to resolve the issue?

A.Change the migration port from 443 to 80.
B.Retry the migration using AWS CloudEndure instead of AWS MGN.
C.Increase the timeout value for the migration task.
D.Ensure the source server's SSL certificate is signed by a trusted Certificate Authority (CA).
AnswerD

Replacing the self-signed certificate with one issued by a trusted Certificate Authority satisfies the Migration Hub validation requirement, because the agent's TLS handshake to the service endpoint is rejected when the chain cannot be verified. A publicly trusted CA resolves that trust failure without altering network paths or agent configuration.

Why this answer

The migration task failed due to an SSL certificate validation error, which occurs when the source server presents a certificate not signed by a trusted Certificate Authority. AWS MGN (Application Migration Service) requires a valid, trusted certificate for the replication agent's TLS connection. Ensuring the source server's SSL certificate is signed by a trusted CA resolves the handshake failure.

Exam trap

SAP-C02 often presents SSL/certificate errors alongside network errors — candidates who see 'migration failed' reach for timeout or port changes, missing that the error text specifically indicates a certificate trust problem.

How to eliminate wrong answers

Option A is wrong because changing the migration port from 443 to 80 does not address a certificate validation error — port 80 is unencrypted HTTP and MGN replication uses TLS on 443; the error is about certificate trust, not port reachability. Option B is wrong because CloudEndure is the predecessor to MGN and switching tools does not fix an invalid certificate on the source server. Option C is wrong because increasing the timeout addresses slow connections, not TLS handshake failures caused by untrusted certificates.

685
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.

686
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.

687
Multi-Selecthard

A company is using AWS Organizations with a centralized networking account that hosts a transit gateway. The company wants to ensure that all traffic between VPCs in different accounts flows through the transit gateway. Which THREE steps are required to implement this architecture?

Select 3 answers
A.Attach the VPCs in member accounts to the transit gateway.
B.Update the route tables of the VPCs to point to the transit gateway for inter-VPC traffic.
C.Create VPC endpoints for the transit gateway in each VPC.
D.Create VPC peering connections between each VPC and the networking VPC.
E.Share the transit gateway with the member accounts using AWS Resource Access Manager.
AnswersA, B, E

Transit gateway attachments are the prerequisite for any VPC to send traffic through it. Each member-account VPC must be attached, either directly or via shared attachment, before route tables can reference the gateway as a target for inter-VPC traffic.

Why this answer

Option A is correct because each VPC that must send traffic through the transit gateway needs a transit gateway attachment in its own account (or a shared attachment), which is created by attaching the VPC to the transit gateway. Option B is correct because the VPC route tables must contain routes that direct inter-VPC traffic (for example, the remote VPC CIDR) to the transit gateway attachment; without these routes, traffic will not be forwarded to the transit gateway. Option E is correct because AWS Resource Access Manager (RAM) is used to share the transit gateway from the centralized networking account with the member accounts, allowing those accounts to create attachments to the shared transit gateway.

Option C is incorrect because VPC endpoints are for private connectivity to AWS services or VPC endpoint services, not for routing traffic through a transit gateway. Option D is incorrect because VPC peering creates direct VPC-to-VPC connectivity that bypasses the transit gateway, which contradicts the requirement that all inter-VPC traffic flow through the transit gateway.

Exam trap

The trap here is that candidates often confuse VPC endpoints (used for AWS service access) with transit gateway attachments, or mistakenly think VPC peering is required when the transit gateway already provides the necessary connectivity.

688
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.

689
MCQmedium

A company has a serverless application using AWS Lambda and Amazon API Gateway. The application experiences cold starts that cause latency spikes. Which solution would reduce the impact of cold starts?

A.Configure Provisioned Concurrency for the Lambda function.
B.Increase the Lambda function memory allocation.
C.Decrease the Lambda function timeout.
D.Use a VPC and enable Lambda to access resources in the VPC.
AnswerA

Provisioned Concurrency pre-initialises a specified number of Lambda execution environments, so invocations skip the init phase that causes cold-start latency. It directly satisfies the stem's requirement to reduce cold-start impact for the API Gateway-fronted function, unlike memory tuning or reserved concurrency, which do not pre-warm environments.

Why this answer

Provisioned Concurrency pre-initializes a specified number of Lambda execution environments so they are ready to respond immediately, eliminating cold starts for that concurrency level. This directly addresses latency spikes caused by cold starts. It is the purpose-built feature for latency-sensitive serverless workloads.

Exam trap

SAP-C02 often tests cold start mitigation — candidates pick 'increase memory' because it speeds execution, but memory tuning does not eliminate cold starts; only Provisioned Concurrency (or SnapStart for Java) directly addresses initialization latency.

How to eliminate wrong answers

Option B is wrong because increasing memory allocation speeds up execution and can slightly reduce init time, but it does not eliminate cold starts — new environments are still created on demand. Option C is wrong because decreasing the timeout makes the function fail faster, not start faster, and can cause more errors. Option D is wrong because placing Lambda in a VPC historically increased cold start duration due to ENI creation (now improved with Hyperplane ENIs), and it does not reduce cold starts — it can worsen them.

690
MCQhard

A company is migrating a legacy e-commerce application to AWS. The application includes a web tier, an application tier, and a MySQL database. The company wants to improve scalability and reduce operational overhead. The architect plans to use Amazon RDS for MySQL and refactor the application to use Auto Scaling for the web and application tiers. However, the application currently stores session state locally on the web servers. What should the architect do to address session state management in the new architecture?

A.Store session state in Amazon S3
B.Store session state in Amazon RDS for MySQL
C.Configure an Application Load Balancer with sticky sessions
D.Use Amazon ElastiCache for Redis to store session state
AnswerD

ElastiCache for Redis externalises session state into a shared, low-latency store, so any Auto Scaling web instance can read the same session regardless of which server handled the prior request. It satisfies the stem's constraint that locally stored sessions break horizontal scaling behind a load balancer.

Why this answer

Using ElastiCache for Redis provides a centralized, scalable session store that works with Auto Scaling. Using sticky sessions (ELB session stickiness) is a workaround but less scalable and not recommended for Auto Scaling. Storing sessions in RDS would add database load.

Storing in S3 is not suitable for low-latency session access.

691
MCQmedium

A company uses AWS CodePipeline to deploy a serverless application built with AWS SAM. The pipeline has a source stage from CodeCommit, a build stage using CodeBuild, and a deploy stage using CloudFormation. The team wants to ensure that the application is automatically tested in a staging environment before being deployed to production. The testing should include integration tests that simulate user interactions. Which solution should a solutions architect recommend to meet these requirements with minimal changes?

A.Add a manual approval action before the deploy stage and require testers to run integration tests locally before approving.
B.Use AWS CodeDeploy to manage the deployment and configure a pre-traffic hook that runs integration tests on the staging environment before shifting traffic to production.
C.Configure the existing deploy stage to deploy to a staging environment first, run tests using a Lambda function triggered by CloudFormation events, and then manually approve production deployment.
D.Add a new stage to the pipeline after the build stage that uses CodeBuild to run integration tests against a staging environment created by a separate CloudFormation stack.
AnswerD

Adding a test stage after build allows integration tests to run against a staging environment before production deployment. CodeBuild can execute test scripts, and a separate CloudFormation stack can provision the staging environment. This approach integrates seamlessly with CodePipeline and requires minimal changes to the existing pipeline structure, ensuring tests pass before production.

Why this answer

Adding a dedicated test stage after the build stage allows integration tests to run automatically against a staging environment before production deployment. CodeBuild can execute test scripts, and a separate CloudFormation stack can create the staging environment. This integrates cleanly with CodePipeline and requires minimal changes, ensuring tests are run automatically and consistently.

Exam trap

The trap here is assuming that CodeDeploy hooks or manual approvals can provide automatic integration testing, but they either require significant pipeline changes or do not automate the testing process.

692
MCQeasy

A company has a management account in AWS Organizations. It wants to delegate administration of AWS IAM Identity Center to a member account for user management. What is the correct way to achieve this?

A.Use AWS Resource Access Manager to share the IAM Identity Center instance with the member account.
B.Use the IAM Identity Center console to add the member account as a delegated administrator.
C.Use a service control policy to allow the member account to manage IAM Identity Center.
D.Create an IAM role in the management account and allow the member account to assume it.
AnswerB

IAM Identity Center supports delegated administration, letting the management account register a member account directly through the console. That member then manages users and permission sets without needing management account access, satisfying the delegation requirement natively.

Why this answer

AWS IAM Identity Center allows you to designate a member account as a delegated administrator directly from the IAM Identity Center console in the management account. This grants the member account the necessary permissions to manage users, groups, and permission sets without requiring cross-account roles or resource sharing.

Exam trap

The trap here is that candidates often confuse delegation with resource sharing via RAM or assume that SCPs can grant permissions, when in fact delegation is a specific AWS Organizations feature that must be configured through the IAM Identity Center console or API for that service.

How to eliminate wrong answers

Option A is wrong because AWS Resource Access Manager (RAM) is used to share resources like subnets or license configurations, not to delegate administrative control of IAM Identity Center; IAM Identity Center instances are not shareable via RAM. Option C is wrong because service control policies (SCPs) are used to restrict permissions across accounts in an organization, not to grant or delegate administrative capabilities; SCPs cannot enable a member account to manage IAM Identity Center. Option D is wrong because creating an IAM role in the management account for the member account to assume would provide access to the management account's IAM Identity Center configuration, but it does not delegate administration; the member account would still operate under the management account's context, not as a delegated administrator with its own management scope.

693
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.

694
MCQmedium

A company is migrating a high-traffic web application from on-premises to AWS. The application uses a shared file system for storing user uploads, and the company wants to ensure high availability and durability across multiple Availability Zones. The migration must be completed with minimal changes to the application code. Which AWS service should be used for the shared file system?

A.Amazon FSx for Lustre with a linked S3 bucket for durability.
B.Amazon FSx for Windows File Server with Multi-AZ deployment.
C.Amazon EFS with a mount target in each Availability Zone and a lifecycle policy to move infrequent access files to EFS IA.
D.Amazon S3 with a mounted file system using s3fs-fuse on each web server.
AnswerC

Amazon EFS provides a fully managed, scalable, and durable NFS file system that can be mounted on multiple EC2 instances across AZs. It requires no application code changes and supports high availability. The lifecycle policy optimizes cost by moving less frequently accessed files to EFS IA storage class.

Why this answer

Amazon EFS is a fully managed, elastic NFS file system that can be mounted on EC2 instances across multiple AZs, providing high availability and durability. It requires no application changes since it presents a standard file system interface. The lifecycle policy helps manage costs by moving infrequently accessed files to a lower-cost storage class.

Exam trap

The trap here is assuming that Amazon S3 can be used as a drop-in replacement for a shared file system without application changes, but S3 is object storage and requires code modifications to use its API.

695
MCQhard

A company is migrating a legacy CRM application from a colocation facility to AWS. The application uses a client-server architecture with a thick client installed on employee desktops. The company wants to reduce desktop administration and provide remote access. Which migration approach should the architect recommend?

A.Deploy the thick client on Amazon WorkSpaces and provide access to employees
B.Refactor the application into a web application using AWS App Runner
C.Rehost the application on Amazon EC2 and provide VPN access to employees
D.Retire the application and use a SaaS alternative
AnswerA

Amazon WorkSpaces delivers persistent virtual desktops, so the existing thick client runs unmodified on managed cloud-hosted Windows instances. This satisfies the reduced desktop administration and remote access constraints without refactoring the client-server application, unlike application-streaming or SaaS alternatives that would require code changes.

Why this answer

Amazon WorkSpaces is a fully managed Desktop-as-a-Service (DaaS) solution that hosts a Windows or Linux desktop in the AWS cloud. By deploying the thick client on WorkSpaces, the company eliminates the need to install and maintain the client on each employee's physical desktop, reducing desktop administration overhead. Employees can access their WorkSpaces from any device using a client or web browser, providing secure remote access without requiring a VPN.

This directly addresses both goals: reduced desktop administration and remote access.

Exam trap

SAP-C02 often tests the misconception that rehosting on EC2 with VPN is sufficient for remote access, but it fails to address the desktop administration reduction goal; candidates must recognize that DaaS solutions like WorkSpaces are designed for this exact scenario.

How to eliminate wrong answers

Option B is wrong because refactoring the application into a web app using AWS App Runner requires significant re-architecture and code changes, which is not a migration approach but a modernization effort that may be time-consuming and costly. Option C is wrong because rehosting on EC2 and providing VPN access still requires installing and managing the thick client on each employee's desktop, which does not reduce desktop administration. Option D is wrong because retiring the application and using a SaaS alternative is not a migration of the existing application; it may be a valid business decision but does not meet the requirement to migrate the legacy CRM application.

696
MCQmedium

A company is migrating a legacy application that uses SOAP web services to AWS. The application currently runs on a single on-premises server. The company wants to minimize changes and reduce operational overhead. Which approach should the company take?

A.Refactor the SOAP web services to RESTful APIs and deploy on Amazon API Gateway and AWS Lambda.
B.Containerize the application and deploy it on Amazon ECS using Fargate.
C.Rehost the application on Amazon EC2 using AWS Application Migration Service (MGN).
D.Use AWS Database Migration Service (DMS) to migrate the database and redeploy the application manually.
AnswerC

Rehosting on Amazon EC2 with AWS Application Migration Service lifts and shifts the SOAP application unchanged, satisfying the minimal-changes constraint. MGN replicates the existing server to AWS without refactoring, and EC2 keeps operational overhead lower than replatforming or rebuilding the legacy SOAP stack.

Why this answer

Rehosting the application on Amazon EC2 using AWS Application Migration Service (MGN) minimizes changes by lifting and shifting the entire on-premises server, including the SOAP web services, to AWS with minimal modification. This approach reduces operational overhead by automating server replication and cutover, avoiding the need to refactor or containerize the application, which aligns with the requirement to minimize changes.

Exam trap

The trap here is that candidates may assume modernizing to serverless or containers is always better, but the question explicitly requires minimizing changes, making rehosting the correct choice despite its perceived lack of modernization.

How to eliminate wrong answers

Option A is wrong because refactoring SOAP web services to RESTful APIs and deploying on Amazon API Gateway and AWS Lambda introduces significant changes to the application architecture and code, contradicting the requirement to minimize changes. Option B is wrong because containerizing the application and deploying on Amazon ECS using Fargate requires modifying the application to run in containers, which adds operational complexity and changes the deployment model, increasing rather than reducing overhead. Option D is wrong because using AWS Database Migration Service (DMS) only addresses database migration, not the application itself, and manually redeploying the application does not minimize changes or reduce operational overhead compared to a fully automated rehosting solution.

697
Multi-Selecthard

A company runs a critical application on EC2 instances in an Auto Scaling group. They want to ensure that during a patching cycle, the application remains available and no requests are dropped. Which TWO strategies should they implement? (Choose TWO.)

Select 2 answers
A.Increase the desired capacity of the Auto Scaling group before patching.
B.Stop all instances at the same time to apply patches consistently.
C.Perform a rolling update using a batch size of 50% with a pause time.
D.Use an Auto Scaling lifecycle hook to wait for a custom action before terminating instances.
E.Use Amazon Inspector to automatically patch instances.
AnswersC, D

A rolling update replaces instances in batches, so the remaining 50% of the Auto Scaling group continues serving traffic while each batch is patched. The pause time lets new instances pass health checks before the next batch begins, preventing dropped requests.

Why this answer

Option C is correct because a rolling update with a batch size of 50% and a pause time replaces instances in controlled waves, so the remaining healthy instances continue serving traffic and capacity never drops to zero, keeping the application available during patching. Option D is correct because an Auto Scaling lifecycle hook puts instances into a wait state (Terminating:Wait or Launching:Wait) so a custom action—such as draining connections, deregistering from the load balancer, or finishing in-flight requests—can complete before the instance is terminated, preventing dropped requests. Option A is not correct because simply raising desired capacity adds instances but does not orchestrate safe patching or connection draining, so requests can still be dropped when instances are replaced.

Option B is not correct because stopping all instances simultaneously causes an outage and drops all requests, directly violating the availability requirement. Option E is not correct because Amazon Inspector is a vulnerability assessment service that detects issues; it does not automatically patch EC2 instances.

Exam trap

SAP-C02 often tests whether candidates conflate vulnerability detection (Inspector) with automated remediation, or assume that scaling out alone guarantees availability during patching.

698
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.

699
Multi-Selecthard

A company is using AWS CloudTrail to log API activity. The security team wants to ensure that log files are tamper-proof and can be used for forensic analysis. Which TWO actions should the company take?

Select 2 answers
A.Enable S3 Object Lock on the CloudTrail S3 bucket.
B.Enable CloudTrail log file validation.
C.Use server-side encryption with AWS KMS managed keys (SSE-KMS).
D.Enable S3 Transfer Acceleration on the CloudTrail S3 bucket.
E.Set an S3 Lifecycle policy to transition logs to Amazon S3 Glacier.
AnswersA, B

S3 Object Lock enforces WORM protection at the object level, preventing deletion or modification of CloudTrail log files for a defined retention period. This directly satisfies the tamper-proof requirement, preserving log integrity so the files remain admissible for forensic analysis even if credentials are compromised.

Why this answer

Option A is correct because enabling S3 Object Lock on the CloudTrail S3 bucket (in compliance or governance mode with a retention period) uses WORM (write-once-read-many) semantics to prevent log files from being deleted or overwritten, which is essential for tamper-proof forensic evidence. Option B is correct because CloudTrail log file validation generates a digitally signed digest file for each log, allowing you to verify via the AWS CLI (aws cloudtrail validate-logs) that logs have not been altered or deleted after delivery. Option C is not correct here because SSE-KMS provides encryption at rest and access control but does not by itself prevent tampering or deletion of log files.

Option D is not correct because S3 Transfer Acceleration only speeds up uploads over long distances and has no bearing on log integrity. Option E is not correct because a Lifecycle policy transitioning logs to S3 Glacier changes storage class and could affect availability, but it does not make logs tamper-proof.

Exam trap

SAP-C02 often tests the misconception that encryption (SSE-KMS) equals tamper-proofing — candidates pick encryption when the question actually demands integrity and immutability controls like Object Lock and log file validation.

700
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.

701
MCQhard

A company runs a critical application on Amazon EC2 instances behind an Application Load Balancer (ALB). The application experiences intermittent latency spikes. The operations team has enabled detailed CloudWatch metrics and logs, but cannot identify the root cause. What is the MOST effective way to troubleshoot the latency issue?

A.Enable detailed ALB metrics and create a CloudWatch dashboard.
B.Migrate the application to AWS Lambda to eliminate EC2 overhead.
C.Replace the ALB with a Network Load Balancer (NLB) for lower latency.
D.Use AWS X-Ray to trace requests from the ALB to the application and downstream services.
E.Add more EC2 instances behind the ALB to distribute the load.
AnswerD

AWS X-Ray traces individual requests end-to-end, capturing segment timing from the ALB through the application to downstream calls. This pinpoints which component introduces the intermittent latency, satisfying the need to isolate a root cause that aggregate CloudWatch metrics and logs cannot attribute to a specific request path.

Why this answer

AWS X-Ray is the purpose-built distributed tracing service that follows a request as it flows from the ALB through the EC2 application and into any downstream services or AWS resources. It captures segment and subsegment timing data, so it can pinpoint exactly which hop (e.g., a slow database call, an external API, or application code) is introducing the latency spikes. Since the team already has detailed CloudWatch metrics and logs without identifying the cause, only request-level tracing can correlate the latency to a specific component.

Exam trap

SAP-C02 often tests the distinction between monitoring (CloudWatch metrics/logs) and distributed tracing (X-Ray) — candidates pick CloudWatch dashboards because they sound comprehensive, missing that only X-Ray can trace a single request across service boundaries.

How to eliminate wrong answers

Option A is wrong because detailed ALB metrics and dashboards only show aggregate load-balancer-level data (request counts, target response times, HTTP codes) and cannot isolate which internal call or downstream dependency is slow. Option B is wrong because migrating to Lambda is a re-architecture decision, not a troubleshooting step, and Lambda introduces its own cold-start and concurrency latency characteristics. Option C is wrong because NLB operates at Layer 4 and offers lower per-connection latency but provides no application-layer visibility, so it would not diagnose an application-level latency spike.

Option E is wrong because adding EC2 instances addresses capacity-driven latency but does nothing to identify the root cause, and the problem may not be load-related at all.

702
Multi-Selecthard

A company has an AWS Organizations environment with a management account, a central log archive account, and many workload accounts. The security team must prevent workload accounts from disabling AWS CloudTrail, deleting the central log bucket, or leaving the organization, while still allowing account administrators to manage their own resources. (Choose two.)

Select 2 answers
A.Enable AWS Config in every workload account and create a managed rule that flags noncompliant trails.
B.Enable Amazon GuardDuty in the management account to alert on attempts to disable logging.
C.Use IAM permissions boundaries on all roles in workload accounts to remove the ability to modify CloudTrail.
D.Create an S3 bucket policy on the central log bucket that denies s3:DeleteBucket and s3:DeleteObject to all principals except a tightly scoped log archive role.
E.Attach a service control policy to the workload OUs that denies cloudtrail:StopLogging, cloudtrail:DeleteTrail, and organizations:LeaveOrganization.
AnswersD, E

A resource-based bucket policy on the central log bucket restricts destructive S3 actions to a specific role, so workload accounts cannot delete the bucket or its objects even if their identity policies allow S3 access. This complements the organization-level controls by protecting the log destination itself.

Why this answer

Preventive guardrails require controls that block actions rather than merely detect them. Service control policies applied to the workload OUs deny trail modification and organization departure for all principals in those accounts, while an S3 bucket policy protects the central log bucket from deletion. Together they enforce the security team's requirements without removing account administrators' ability to manage other resources.

Exam trap

The trap here is choosing detective controls such as AWS Config rules or GuardDuty findings when the requirement is to prevent the actions from succeeding.

703
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.

704
MCQeasy

A company is migrating its on-premises VMware VMs to AWS using AWS MGN. After the test cutover, the migrated EC2 instance fails the health check. The source VM runs Windows Server 2016 with a static IP. What is the most likely cause?

A.The security group does not allow inbound RDP.
B.The EBS volume type is not gp3.
C.The source VM's static IP configuration was not changed to DHCP.
D.The instance type is not compatible with Windows Server 2016.
AnswerC

AWS MGN requires the migrated instance to use DHCP; a static IP carried over from the source VM prevents the EC2 instance from obtaining its network configuration, failing the post-cutover health check. Changing the source VM to DHCP before cutover satisfies this constraint.

Why this answer

When migrating a Windows VM with a static IP using AWS MGN, the source VM must be configured to use DHCP before migration, because AWS relies on DHCP for IP assignment. If the static IP configuration persists, the EC2 instance will not obtain an IP address, causing the health check to fail. Option A is incorrect because security groups do not affect DHCP-based IP assignment.

Option B is incorrect because the EBS volume type (e.g., gp3) does not impact health checks. Option D is incorrect because the instance type is not related to DHCP configuration; Windows Server 2016 is compatible with most current instance types.

705
MCQmedium

A solutions architect runs the above commands for an EC2 instance. The instance state is 'running' but the system status is 'impaired'. What should the solutions architect do to restore the instance?

A.Start the instance.
B.Stop and start the instance.
C.Modify the instance type.
D.Reboot the instance.
AnswerB

A system status check failure indicates the underlying host or hypervisor is impaired, not the guest OS. Stopping and starting migrates the instance to new hardware, clearing the fault; a reboot alone stays on the same impaired host.

Why this answer

When the system status check fails, it indicates a hardware issue. AWS recommends stopping and starting the instance to move it to new underlying hardware. Option A is incorrect because the instance is already running, so starting it does nothing.

Option C is incorrect because modifying the instance type does not resolve underlying hardware issues. Option D is incorrect because rebooting the instance does not change the underlying hardware and may not resolve the impairment.

706
MCQmedium

A company is migrating a web application to AWS. The application uses a three-tier architecture with a web server, application server, and MySQL database. The company wants to ensure high availability by deploying across multiple Availability Zones. The web and application servers are stateless. Which solution provides the HIGHEST availability with the LEAST administrative effort?

A.Deploy web and application servers on EC2 instances in an Auto Scaling group across two AZs with an Application Load Balancer. Use Multi-AZ Amazon RDS for MySQL.
B.Deploy web and application servers on EC2 instances in an Auto Scaling group in one AZ. Use Amazon Route 53 latency-based routing to another region.
C.Deploy web, application, and database on a single large EC2 instance in one AZ. Take snapshots every hour.
D.Deploy web and application servers on EC2 instances in two AZs with Elastic IP addresses. Use Amazon Route 53 with health checks to route traffic.
AnswerA

An Auto Scaling group spanning two AZs behind an Application Load Balancer removes single points of failure for the stateless tiers, while Multi-AZ Amazon RDS handles database failover automatically. This delivers the highest availability with the least administrative effort, as failover is managed by AWS.

Why this answer

Deploying web and application servers in an Auto Scaling group across two AZs behind an Application Load Balancer, and using Multi-AZ Amazon RDS for MySQL, provides high availability with minimal administrative effort. The ALB distributes traffic, Auto Scaling maintains capacity, and Multi-AZ RDS automatically fails over to a standby in another AZ. This is a fully managed, highly available architecture.

Exam trap

SAP-C02 often tests the difference between high availability (multi-AZ) and disaster recovery (multi-region), and candidates may choose cross-region routing or manual failover solutions that require more effort and do not provide automatic recovery.

How to eliminate wrong answers

Option B is wrong because deploying in one AZ and using Route 53 latency-based routing to another region does not provide high availability within the region; a single AZ failure would take down the application, and cross-region routing adds complexity. Option C is wrong because a single EC2 instance is a single point of failure, and hourly snapshots do not provide high availability; recovery would take time. Option D is wrong because using Elastic IP addresses with Route 53 health checks requires manual failover and does not automatically scale or replace failed instances; it also lacks a load balancer for distributing traffic across healthy instances.

707
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

708
MCQmedium

A company has a multi-account AWS environment with over 500 accounts. The security team uses AWS Config to evaluate resource compliance across all accounts. They have set up an AWS Config aggregator in the security account to collect configuration snapshots from all member accounts. Recently, the team noticed that some member accounts are not showing up in the aggregator. The accounts are active and have AWS Config enabled. What should the security team do to troubleshoot this issue?

A.Ensure that the member accounts have enabled AWS Config in the same region as the aggregator.
B.Check if the member accounts have exceeded the AWS Config resource limits.
C.Check if the AWS Config recorder in the member accounts is configured to record all resource types.
D.Verify that the AWS Config aggregator in the security account has the correct authorization to assume a role in each member account.
AnswerD

The aggregator needs a cross-account IAM role it can assume in every member account to read configuration data. If that role or its trust policy is missing or misconfigured, accounts silently fail to appear, so verify the authorisation first.

Why this answer

AWS Config aggregators require cross-account authorization to collect configuration data from member accounts. Even if AWS Config is enabled in member accounts, the aggregator in the security account must have the correct IAM role permissions (via an IAM role in each member account) to assume and retrieve configuration snapshots. Without this authorization, the aggregator cannot access the member accounts' data, causing them to not appear.

Exam trap

The trap here is that candidates assume enabling AWS Config in member accounts is sufficient, overlooking the critical cross-account authorization step required by the aggregator to pull data from those accounts.

How to eliminate wrong answers

Option A is wrong because AWS Config aggregators can collect data from multiple regions, and the issue is about accounts not showing up, not regions; the aggregator can aggregate across regions if configured correctly. Option B is wrong because exceeding AWS Config resource limits would cause errors or throttling, not a complete absence of accounts in the aggregator; the accounts are active and Config is enabled, so limits are not the likely cause. Option C is wrong because the AWS Config recorder configuration (recording all resource types or specific ones) affects what resources are recorded, not whether the account appears in the aggregator; the aggregator shows accounts regardless of the recorder's scope.

709
MCQmedium

A company is migrating a critical application from on-premises to AWS. The application uses a shared file system for user uploads and logs. The company wants a highly available, durable, and low-latency solution. Which AWS storage service should the company use?

A.Amazon EFS
B.Amazon EBS
C.Amazon FSx for Windows File Server
D.Amazon S3
AnswerA

Amazon EFS provides a shared, POSIX-compliant NFS file system that multiple EC2 instances across Availability Zones can mount concurrently, meeting the shared-uploads-and-logs requirement. Its regional, replicated design delivers the durability and high availability demanded, while general-purpose performance mode keeps latency low for file operations.

Why this answer

Amazon EFS is a fully managed, elastic NFS file system that can be mounted concurrently by multiple EC2 instances and containers across Availability Zones, providing high availability, durability (11 nines), and low-latency shared access. It is purpose-built for shared file workloads like user uploads and logs, and it scales automatically without provisioning. This matches the requirement for a highly available, durable, low-latency shared file system.

Exam trap

SAP-C02 often tests the confusion between block (EBS), file (EFS/FSx), and object (S3) storage — candidates who pick S3 for 'shared' workloads miss that S3 is not a POSIX file system and cannot be mounted natively.

How to eliminate wrong answers

Option B is wrong because Amazon EBS volumes attach to a single EC2 instance (except Multi-Attach io1/io2 in limited cases) and are Availability Zone-scoped, so they cannot serve as a shared, highly available file system across instances. Option C is wrong because FSx for Windows File Server is designed for Windows SMB workloads and Active Directory integration; it is not the default choice for a generic Linux/NFS shared file system and may be costlier or mismatched. Option D is wrong because Amazon S3 is object storage accessed via HTTP APIs, not a POSIX file system, so it cannot be mounted as a shared file system for low-latency random file operations without additional layers like Mountpoint for S3.

710
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

711
MCQmedium

A company has multiple AWS accounts and wants to centralize CloudTrail logs from all accounts into a single S3 bucket in the audit account. Which configuration is required?

A.Configure CloudWatch Events cross-account to forward logs to a central S3 bucket.
B.Create an organization trail in the management account that delivers logs to the central S3 bucket in the audit account, and set the bucket policy to allow CloudTrail from the organization.
C.Use AWS Organizations to automatically create a CloudTrail trail in the management account that logs all accounts.
D.Create a CloudTrail trail in each account that delivers logs to the central S3 bucket, with a bucket policy that grants write access to each account's CloudTrail service.
AnswerB

An organisation trail created in the management account automatically applies to every account in AWS Organizations and delivers events to the specified S3 bucket. The bucket policy must permit CloudTrail from the organisation so the audit account accepts logs, satisfying the centralised-logging requirement.

Why this answer

AWS Organizations allows you to create an organization trail in the management account that automatically applies to all accounts in the organization. By configuring the trail to deliver logs to a central S3 bucket in the audit account, and setting the bucket policy to grant CloudTrail service access from the organization, you centralize logging without needing per-account trails. This approach ensures that new accounts added to the organization are automatically covered.

Exam trap

The trap here is that candidates often assume they must create individual trails per account (Option D) or use CloudWatch Events (Option A), missing the simpler and more robust organization trail feature that automatically covers all accounts in the organization.

How to eliminate wrong answers

Option A is wrong because CloudWatch Events cross-account forwarding is not designed to aggregate CloudTrail logs into S3; it forwards events to targets like Lambda or SQS, not directly to S3, and would require custom processing. Option C is wrong because AWS Organizations does not automatically create a CloudTrail trail; you must explicitly create an organization trail in the management account. Option D is wrong because while it could work technically, it is not the simplest or most scalable solution; it requires configuring a trail in every account and managing individual bucket policies, which does not leverage the organizational trail feature that automatically includes all accounts.

712
MCQeasy

A solutions architect needs to design a network architecture for a multi-account AWS environment using AWS Transit Gateway. The company requires that all traffic between VPCs be inspected by a central security appliance. What is the MOST efficient way to achieve this?

A.Use AWS Direct Connect to connect all VPCs to a central on-premises firewall.
B.Use a Network Load Balancer in each VPC to forward traffic to a firewall instance.
C.Attach all VPCs to a Transit Gateway and route traffic through a central inspection VPC.
D.Create VPC peering connections between all VPCs and route traffic through a security VPC.
AnswerC

Attaching every VPC to the Transit Gateway and steering inter-VPC traffic through a central inspection VPC satisfies the mandated inspection constraint using native Transit Gateway route table segmentation. Appliance VPC attachments and separate route tables force all spokes through the security stack, avoiding complex peering meshes or per-VPC firewall deployments.

Why this answer

AWS Transit Gateway enables a hub-and-spoke architecture where all VPCs attach to a central Transit Gateway, and a dedicated inspection VPC (with the security appliance) acts as the central inspection point. By configuring route tables in the Transit Gateway to route all inter-VPC traffic through the inspection VPC, you achieve mandatory traffic inspection without complex peering or performance bottlenecks.

Exam trap

The trap here is that candidates may assume VPC peering is simpler or more direct, but they overlook that VPC peering lacks transitive routing, making it impossible to force all inter-VPC traffic through a single inspection point without a full mesh and complex routing.

How to eliminate wrong answers

Option A is wrong because AWS Direct Connect is a dedicated network connection to on-premises, not a mechanism to connect VPCs to each other or to a central firewall; it would introduce unnecessary latency and dependency on on-premises infrastructure for VPC-to-VPC traffic. Option B is wrong because a Network Load Balancer (NLB) operates at Layer 4 and cannot inspect or forward traffic for security purposes; it is designed for load balancing, not traffic inspection or routing. Option D is wrong because VPC peering does not support transitive routing, so you would need a full mesh of peering connections (which does not scale) and still cannot force all traffic through a central inspection VPC without complex routing and additional appliances.

713
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

714
MCQhard

A company has a multi-account strategy with a dedicated audit account. The audit account needs to have read-only access to all resources in all other accounts. The security team wants to use IAM roles. What is the MOST scalable way to set up this cross-account access?

A.Use AWS Single Sign-On (SSO) to grant the audit team access to each account.
B.Create an IAM user in the audit account and allow that user to assume a role in each account.
C.Manually create an IAM role in each account and attach a read-only policy.
D.Use AWS CloudFormation StackSets to deploy a stack containing an IAM role with the required trust and permissions.
AnswerD

CloudFormation StackSets deploy the IAM role with its trust policy and read-only permissions to every account simultaneously, satisfying the scalable cross-account access requirement. The audit account assumes the role in each target account, avoiding per-account manual role creation.

Why this answer

AWS CloudFormation StackSets allows you to deploy a consistent IAM role with a read-only policy and a trust policy that grants the audit account access across all target accounts in a single, automated, and scalable operation. This approach eliminates manual effort, ensures consistency, and scales to hundreds of accounts without requiring per-account configuration.

Exam trap

The trap here is that candidates often choose manual role creation (Option C) because it seems straightforward, but they overlook the scalability and automation benefits of StackSets, which is the most efficient solution for managing cross-account roles across many accounts in a multi-account strategy.

How to eliminate wrong answers

Option A is wrong because AWS Single Sign-On (SSO) is designed for federated user access to the AWS Management Console and does not provide a mechanism to grant programmatic cross-account IAM role access for a dedicated audit account; it also does not natively enforce read-only permissions across all resources. Option B is wrong because creating an IAM user in the audit account and allowing that user to assume roles in each account is not scalable—it requires manual creation of roles and trust policies in every account, and IAM users are a security anti-pattern for cross-account access compared to role-based access. Option C is wrong because manually creating an IAM role in each account with a read-only policy is not scalable for a multi-account environment with many accounts; it introduces human error, inconsistency, and operational overhead.

715
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

716
MCQmedium

A solutions architect is reviewing an application that writes millions of small records per hour to an Amazon DynamoDB table. The table uses a partition key of customer ID, and a few very large customers generate most of the traffic. During peak periods, the application receives ProvisionedThroughputExceededException errors even though total consumed capacity is below the provisioned amount. Which action will resolve the throttling MOST effectively?

A.Switch the table from provisioned capacity to on-demand capacity mode so DynamoDB automatically handles all traffic spikes.
B.Redesign the table to use a composite partition key that appends a random or calculated suffix to the customer ID, distributing writes across more partitions.
C.Create a global secondary index on the customer ID attribute and direct all reads and writes to the index instead of the base table.
D.Enable DynamoDB auto scaling to increase the provisioned read and write capacity units when consumed capacity approaches the limit.
AnswerB

Hot partitions occur when a single partition key value concentrates traffic. Adding a high-cardinality suffix spreads each large customer's writes across many partitions, each with its own throughput ceiling. This directly addresses the imbalance causing ProvisionedThroughputExceededException while keeping total capacity adequate. It is the standard DynamoDB remedy for skewed access patterns.

Why this answer

The throttling is caused by hot partitions, where a few high-traffic customer IDs exceed the per-partition throughput ceiling despite ample table-level capacity. Appending a random or calculated suffix to the partition key spreads each large customer's writes across many partitions, eliminating the bottleneck. Simply adding capacity, switching to on-demand, or moving to an index with the same skewed key does not redistribute the load.

Exam trap

The trap here is assuming ProvisionedThroughputExceededException always means total capacity is too low, when it frequently signals a hot partition caused by a low-cardinality or skewed partition key.

717
MCQmedium

A company is migrating a stateful web application to AWS. The application currently runs on a single on-premises server and uses local storage for session data. The company wants to make the application highly available and scalable. What should the solutions architect do?

A.Store session data in a Multi-AZ Amazon RDS database and use Route 53 with health checks
B.Use an Application Load Balancer with sticky sessions and an Auto Scaling group
C.Use a larger EC2 instance to handle all traffic and take regular snapshots
D.Migrate session data to Amazon ElastiCache or DynamoDB, then use an Auto Scaling group behind an ALB
AnswerD

Moving session state into ElastiCache or DynamoDB externalises it from the instance, so any instance in the Auto Scaling group can serve any request. The ALB distributes traffic, delivering the required high availability and horizontal scalability.

Why this answer

Moving session state to ElastiCache or DynamoDB makes the application stateless, enabling Auto Scaling. Sticky sessions on an ALB are a workaround but do not provide full statelessness. Using a larger instance does not provide high availability.

Multi-AZ RDS for session data is not ideal for high-frequency session access.

718
Multi-Selectmedium

A company is migrating a legacy application to AWS and wants to use a containerized architecture. The application requires persistent storage that can be shared across multiple containers in an Amazon ECS cluster. Which TWO storage solutions should the company consider? (Choose TWO.)

Select 2 answers
A.Amazon Simple Storage Service (S3)
B.Amazon Elastic File System (EFS)
C.Amazon FSx for Lustre
D.Amazon Elastic Block Store (EBS)
E.Amazon Relational Database Service (RDS)
AnswersB, C

Amazon EFS provides a shared, elastic NFS file system that multiple containers across an ECS cluster can mount concurrently, satisfying the persistent shared-storage requirement. It scales automatically and supports both EC2 and Fargate launch types.

Why this answer

Amazon EFS (B) is correct because it is a fully managed, elastic NFS file system that can be mounted simultaneously by multiple EC2 instances and ECS tasks across Availability Zones, providing the shared persistent storage the application needs. Amazon FSx for Lustre (C) is also correct because it is a high-performance, POSIX-compliant shared file system designed for compute-intensive workloads, and it can be mounted concurrently by many containers in an ECS cluster. Amazon S3 (A) is object storage accessed via HTTP APIs rather than a mountable shared file system, so it does not natively provide the shared persistent volume semantics required.

Amazon EBS (D) provides block storage that attaches to a single EC2 instance at a time and cannot be shared across multiple containers or hosts. Amazon RDS (E) is a managed relational database service, not a general-purpose shared storage layer for container file systems.

Exam trap

SAP-C02 often tests the misconception that EBS can be shared like a network file system across containers, when in fact EBS is single-instance block storage and only EFS/FSx provide true multi-attach shared file access.

719
MCQhard

Refer to the exhibit. A solutions architect is troubleshooting why EC2 instances launched in subnet-11111111 cannot access the internet. The subnet is in a VPC with an internet gateway attached. The route table for the subnet has a default route (0.0.0.0/0) pointing to the internet gateway. What is the MOST likely cause?

A.The subnet's auto-assign public IP setting is disabled
B.The internet gateway is not attached to the VPC
C.The subnet needs a NAT gateway for internet access
D.The subnet's route table does not have a route to the internet gateway
AnswerA

A subnet with a default route to an internet gateway still requires each instance to hold a public IPv4 address or elastic IP for NAT to occur. With auto-assign public IP disabled, instances receive only private addresses, so the internet gateway drops their traffic, satisfying the stem's connectivity failure.

Why this answer

The most likely cause is that the subnet's auto-assign public IP setting is disabled. Even though the subnet has a default route (0.0.0.0/0) pointing to an internet gateway, EC2 instances launched in that subnet will not receive a public IP address automatically unless the subnet's 'Auto-assign public IPv4 address' setting is enabled. Without a public IP (or an Elastic IP), the instance cannot communicate with the internet through the internet gateway, as the internet gateway requires a public IP for return traffic routing.

Exam trap

The trap here is that candidates often assume a route to an internet gateway is sufficient for internet access, overlooking the requirement that the instance must have a public IP address for the internet gateway to route traffic correctly.

How to eliminate wrong answers

Option B is wrong because the question explicitly states the VPC has an internet gateway attached, so this is not the issue. Option C is wrong because a NAT gateway is only needed for private subnets to access the internet; this subnet has a route to an internet gateway, indicating it is intended to be a public subnet, and a NAT gateway would not solve the lack of a public IP. Option D is wrong because the question states the route table for the subnet has a default route (0.0.0.0/0) pointing to the internet gateway, so the route is present.

720
MCQeasy

A company plans to modernize an existing .NET Framework 4.7 application running on Windows Server 2012 R2. The company wants to move to a containerized architecture on AWS with minimal code changes. Which service should the company use to meet these requirements?

A.AWS App2Container (A2C)
B.AWS Serverless Application Model (SAM)
C.AWS Copilot
D.AWS Migration Hub
AnswerA

App2Container discovers .NET applications running in IIS on Windows Server, or Java applications on Linux, analyses their dependencies, and builds a container image with a suitable base image, here a Windows container. It then generates ECS task definitions or EKS manifests, CloudFormation templates and optionally a CI/CD pipeline. That replatforms the application off an unsupported operating system with no code rewrite.

Why this answer

AWS App2Container (A2C) is specifically designed to containerize existing .NET Framework applications running on Windows Server with minimal code changes. It analyzes the application, generates Docker images, and produces CloudFormation templates for deployment on Amazon ECS or EKS, directly meeting the requirement to modernize a .NET Framework 4.7 application to a containerized architecture without significant refactoring.

Exam trap

The trap here is that candidates may confuse AWS App2Container with AWS Copilot or SAM, assuming any AWS container tool can handle existing .NET Framework applications, but only A2C provides the automated analysis and containerization of legacy Windows applications with minimal code changes.

How to eliminate wrong answers

Option B (AWS SAM) is wrong because it is a framework for building serverless applications using AWS Lambda and API Gateway, not for containerizing existing .NET Framework applications; it requires rewriting the application into a serverless architecture, which contradicts the 'minimal code changes' requirement. Option C (AWS Copilot) is wrong because it is a CLI tool for deploying containerized applications on Amazon ECS or App Runner, but it assumes the application is already containerized and does not provide analysis or containerization of existing .NET Framework binaries. Option D (AWS Migration Hub) is wrong because it is a tracking and monitoring service for migration progress across multiple tools, not a tool that performs containerization or code transformation.

721
Multi-Selectmedium

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

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

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

Why this answer

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

Exam trap

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

722
MCQeasy

A company is adopting AWS Organizations and wants a baseline set of IAM roles, a standard VPC, and a security agent deployed automatically into every new account the moment it is created. The operations team does not want to run scripts manually after each account creation. Which AWS service should they use to meet this requirement?

A.AWS Control Tower Account Factory for Terraform pipelines triggered per account.
B.AWS CloudFormation StackSets with automatic deployment enabled for the organization.
C.AWS Service Catalog portfolios shared with each organizational unit.
D.AWS Config conformance packs applied at the organization level.
AnswerB

StackSets deploy a CloudFormation template to many accounts and Regions from a single administration account, and with automatic deployment enabled, new accounts joining the organization receive the baseline stacks without manual intervention. It is the standard mechanism for provisioning consistent resources such as roles, VPCs, and agents across an organization.

Why this answer

AWS CloudFormation StackSets is designed for multi-account, multi-Region provisioning from a central administrator account. Enabling automatic deployment ties stack deployment to organization membership, so each newly created account automatically receives the baseline IAM roles, VPC, and security agent. This removes the need for manual or scripted post-creation steps.

Exam trap

The trap here is assuming AWS Config conformance packs or Service Catalog deploy resources, when they only evaluate compliance or offer on-demand products.

723
MCQhard

A company is using AWS DMS to migrate a SQL Server database to Amazon Redshift. The initial full load completed, but the ongoing replication task failed with the error shown. What is the MOST likely cause?

A.The DMS task is not configured to use a task log for troubleshooting.
B.The source SQL Server transaction log has not been backed up or truncated, causing it to become full.
C.The target Redshift table does not have a primary key defined for the DMS task to apply changes.
D.The DMS task is using a full LOB mode, which is not supported for Redshift targets.
AnswerB

A full transaction log halts SQL Server's ability to record further changes, so DMS change data capture cannot read new log records and the replication task fails. The stem's ongoing replication failure, following a successful full load, points to log growth from unbacked-up or untruncated logs rather than connectivity or permissions.

Why this answer

The error indicates that AWS DMS cannot read the source SQL Server transaction log to capture ongoing changes. This typically occurs when the transaction log is full because it has not been backed up or truncated, preventing DMS from reading new log records for continuous replication. DMS relies on the source database's transaction log for CDC (Change Data Capture), and a full log blocks this process.

Exam trap

The trap here is that candidates may confuse a target-side issue (like missing primary key or unsupported LOB mode) with a source-side transaction log problem, because the error message explicitly mentions 'transaction log' but test-takers often overlook the source database context.

How to eliminate wrong answers

Option A is wrong because the task log is used for debugging and monitoring, but its absence does not cause the replication task to fail with a transaction log error; the error message specifically points to a log read issue, not a missing log configuration. Option C is wrong because while a primary key is recommended for target tables in DMS tasks to support ongoing replication, its absence would cause a different error (e.g., 'No primary key defined') and not a transaction log failure. Option D is wrong because full LOB mode is supported for Redshift targets in DMS; the error is unrelated to LOB handling and instead points to a source-side transaction log problem.

724
Matchingmedium

Match each AWS database service to its characteristic.

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

Concepts
Matches

MySQL/PostgreSQL-compatible with high availability

Fully managed NoSQL key-value and document database

Petabyte-scale data warehouse for analytics

In-memory caching with Redis or Memcached

Managed relational database for multiple engines

Why these pairings

Each AWS database service targets specific use cases: RDS for relational workloads, DynamoDB for NoSQL, Redshift for analytics, and ElastiCache for caching. Common confusions include mixing up NoSQL with relational and caching with warehousing.

725
MCQhard

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

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

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

Why this answer

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

Exam trap

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

726
MCQeasy

A company wants to implement a data lake on AWS with data from multiple sources. They need to store data in its raw format and allow multiple teams to query it using different tools. Which service should be used as the central storage layer?

A.Amazon DynamoDB
B.Amazon Redshift
C.Amazon S3
D.Amazon RDS
AnswerC

Amazon S3 provides durable, schema-on-read object storage that keeps data in its native raw format, satisfying the requirement to preserve source fidelity. Its decoupling from compute lets Athena, Redshift Spectrum and EMR query the same objects independently, which no single-purpose analytics engine allows.

Why this answer

Amazon S3 is the correct choice because it provides a highly durable, scalable, and cost-effective object storage service that can store data in its raw, native format (e.g., CSV, JSON, Parquet, images). It supports multiple query engines like Amazon Athena, Amazon Redshift Spectrum, and AWS Glue, allowing diverse teams to query the same data using different tools without data movement.

Exam trap

The trap here is that candidates often confuse a data lake's raw storage layer with a data warehouse (Redshift) or a transactional database (RDS, DynamoDB), failing to recognize that a data lake requires schema-on-read, object storage, and multi-engine query support, which only S3 provides.

How to eliminate wrong answers

Option A is wrong because Amazon DynamoDB is a NoSQL key-value and document database designed for low-latency, transactional workloads, not for storing raw, schema-less data lake files or supporting SQL-based analytics at scale. Option B is wrong because Amazon Redshift is a petabyte-scale data warehouse that requires data to be loaded and transformed into a structured, columnar format; it is not designed to store raw, unprocessed data from multiple sources. Option D is wrong because Amazon RDS is a relational database service that enforces a fixed schema and is optimized for OLTP workloads, making it unsuitable for storing diverse raw data formats and supporting ad-hoc queries from multiple analytics tools.

727
Multi-Selectmedium

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

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

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

Why this answer

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

Exam trap

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

728
Drag & Dropmedium

Drag and drop the steps to troubleshoot an EC2 instance that is unreachable via SSH in the correct order.

Drag or tap steps into the slots.

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

Why this order

Start with security groups, then network ACLs, then public IP, then system status, and finally console output.

729
Multi-Selectmedium

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

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

Lambda can poll SQS queues and process events.

Why this answer

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

Exam trap

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

730
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

731
Multi-Selectmedium

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

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

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

Why this answer

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

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

732
MCQmedium

A Lambda function logs are being retained for 30 days. The company wants to reduce costs by deleting logs older than 7 days. What should they do?

A.Export the logs to S3 and delete the log group.
B.Use the put-retention-policy command to set retentionInDays to 7.
C.Configure an S3 Lifecycle policy on the log group's underlying storage.
D.Create a CloudTrail trail to capture log events and expire them after 7 days.
AnswerB

Setting a CloudWatch Logs retention policy of 7 days via `put-retention-policy` directly satisfies the stem's cost constraint, since CloudWatch automatically deletes log events once they exceed the configured `retentionInDays` value. This is the native, serverless mechanism for lifecycle management, requiring no custom deletion code or scheduled Lambda invocations.

Why this answer

CloudWatch Logs retention is controlled per log group via the PutRetentionPolicy API (aws logs put-retention-policy), which sets retentionInDays to a value such as 7. This automatically deletes log events older than the specified period, directly reducing storage costs without changing the logging pipeline. It is the native, lowest-effort solution.

Exam trap

SAP-C02 often tests whether candidates know that CloudWatch Logs retention is set per log group via put-retention-policy, and distracts with S3 lifecycle policies — candidates who assume CloudWatch logs live in S3 pick the wrong option.

How to eliminate wrong answers

Option A is wrong because exporting logs to S3 and deleting the log group removes the ability to query logs in CloudWatch and does not set a retention policy — it is a migration, not a retention change. Option C is wrong because CloudWatch Logs does not expose an underlying S3 bucket to attach a lifecycle policy to; log groups are managed by CloudWatch, not S3. Option D is wrong because CloudTrail captures API activity, not Lambda function logs, and CloudTrail does not manage CloudWatch log retention.

733
MCQhard

A financial services company uses AWS Organizations with a central networking account. Workload accounts need to reach an on-premises data center over AWS Site-to-Site VPN, and the network team wants to enforce that all inter-VPC traffic flows through a central inspection VPC. Which combination of components should the network team deploy to route traffic through the inspection VPC while keeping the architecture scalable?

A.Create a VPC peering mesh between all workload VPCs and the inspection VPC, and attach a virtual private gateway to each workload VPC.
B.Use AWS PrivateLink endpoints in each workload VPC to reach the inspection VPC, and route on-premises traffic through the endpoints.
C.Create a transit gateway in each workload account and peer the transit gateways together, then attach the VPN to one of them.
D.Use AWS Transit Gateway with a central transit gateway in the networking account, attach the inspection VPC and workload VPCs to it, and use a separate route table per segment with the inspection VPC as the next hop.
AnswerD

A central transit gateway provides hub-and-spoke connectivity with transitive routing, and separate transit gateway route tables let the network team force traffic through the inspection VPC. Attaching the VPN to the transit gateway keeps on-premises access centralized while scaling to many workload accounts without per-pair peering.

Why this answer

A single central AWS Transit Gateway in the networking account, with workload VPC attachments and segment-specific route tables pointing to the inspection VPC, delivers scalable hub-and-spoke routing and centralized inspection. Attaching the Site-to-Site VPN to the same transit gateway keeps on-premises traffic in the same controlled path and avoids per-account VPN or peering sprawl.

Exam trap

The trap here is reaching for VPC peering or PrivateLink for general inter-VPC and on-premises routing when only a transit gateway provides transitive, centrally governed connectivity.

734
MCQmedium

A company uses AWS Organizations and wants to delegate administration of AWS IAM Identity Center (successor to AWS SSO) to a member account. Which step is required to set this up?

A.Use the management account to designate the member account as a delegated administrator for IAM Identity Center.
B.Enable AWS Organizations and create an admin role in the member account.
C.Create a new OU for the delegated administrator account.
D.Attach an SCP to allow IAM Identity Center actions in the member account.
AnswerA

Delegating IAM Identity Center administration requires the management account to register a member account as delegated administrator, which then gains administrative control over Identity Center. Without this organisation-level designation, the member account cannot manage Identity Center centrally.

Why this answer

To delegate administration of IAM Identity Center to a member account, you must use the AWS Organizations management account to register that member account as a delegated administrator for IAM Identity Center. This is done via the AWS Organizations console or API (RegisterDelegatedAdministrator), which grants the member account the necessary permissions to manage IAM Identity Center settings, users, and groups without requiring full management account access. Only the management account can designate delegated administrators, and this action is specific to IAM Identity Center within AWS Organizations.

Exam trap

The trap here is that candidates often confuse generic cross-account role delegation (like creating an IAM role in a member account) with the specific AWS Organizations delegated administrator feature, which requires explicit registration from the management account and is not achieved by simply creating roles or policies.

How to eliminate wrong answers

Option B is wrong because enabling AWS Organizations and creating an admin role in the member account is a generic step for cross-account access, but it does not specifically delegate IAM Identity Center administration; delegated administration requires explicit registration via the management account, not just role creation. Option C is wrong because creating a new OU for the delegated administrator account is not required; delegated administrators can be any member account in any OU, and OUs are for organizational structure and policy application, not for enabling delegation. Option D is wrong because attaching an SCP to allow IAM Identity Center actions in the member account is unnecessary and incorrect; SCPs are used to restrict permissions, not to grant them, and delegation is controlled by the management account's registration, not by SCPs.

735
MCQhard

A company is migrating a legacy .NET application to AWS. The application uses Windows authentication and has a dependency on a local file system. The company wants to minimize code changes. Which combination of services should be used?

A.Amazon EC2 Windows instances with Amazon EFS
B.AWS Elastic Beanstalk with Amazon EFS
C.Amazon Lightsail with local instance storage
D.Amazon EC2 Windows instances with Amazon FSx for Windows File Server
AnswerD

EC2 Windows instances preserve Windows authentication (Kerberos/NTLM) unchanged, while Amazon FSx for Windows File Server provides SMB shares with NTFS ACLs, replacing the local file system dependency. Together they satisfy the minimal-code-change constraint because the .NET application sees the same authentication and file path semantics.

Why this answer

The application uses Windows authentication and depends on a local file system, so the target must support native Windows ACLs and SMB. Amazon EC2 Windows instances provide the Windows OS, and Amazon FSx for Windows File Server provides a fully managed SMB file system with Active Directory integration, preserving Windows authentication and file semantics with minimal code changes.

Exam trap

SAP-C02 often tests the EFS-vs-FSx distinction — candidates pick EFS because it is the default managed file service, forgetting EFS is NFS-only and cannot serve Windows authentication.

How to eliminate wrong answers

Option A is wrong because Amazon EFS is a Linux NFS file system and does not support Windows ACLs or SMB, so Windows authentication and file permissions would break. Option B is wrong because Elastic Beanstalk with EFS still uses NFS and does not provide Windows authentication or SMB semantics. Option C is wrong because Lightsail with local instance storage is not a managed Windows file service, does not integrate with AD, and local storage is ephemeral and not shared across instances.

736
MCQmedium

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

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

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

Why this answer

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

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

Exam trap

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

How to eliminate wrong answers

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

737
MCQhard

A company runs a microservices application on Amazon ECS with the EC2 launch type. The application consists of multiple services that communicate over HTTP. The operations team wants to improve observability and reduce the time to diagnose performance issues between services. They have already enabled CloudWatch Logs and metrics. They want to trace requests as they flow through the services and identify latency bottlenecks. What should a solutions architect recommend?

A.Configure CloudWatch ServiceLens to automatically trace requests without code changes.
B.Enable AWS X-Ray tracing by instrumenting the application code and running the X-Ray daemon as a sidecar container in each ECS task.
C.Use AWS CloudTrail to log all API calls between services and analyze the logs in Amazon Athena.
D.Enable VPC Flow Logs on the ECS cluster's VPC and analyze the logs with Amazon QuickSight.
AnswerB

AWS X-Ray provides end-to-end tracing of requests as they travel through microservices. By instrumenting the application with the X-Ray SDK and running the X-Ray daemon as a sidecar in each ECS task, the daemon can collect trace data and send it to X-Ray. This allows visualization of service maps, latency analysis, and identification of bottlenecks. It integrates natively with ECS and is the recommended approach for distributed tracing in microservices.

Why this answer

AWS X-Ray is designed for distributed tracing of microservices. Instrumenting the application with the X-Ray SDK and running the X-Ray daemon as a sidecar in each ECS task enables the collection of trace data. This provides a service map, latency analysis, and error identification.

Other options do not capture application-level request flows or require code instrumentation.

Exam trap

The trap here is thinking that CloudWatch ServiceLens or VPC Flow Logs can provide tracing without code changes, but X-Ray requires instrumentation to generate the trace data that ServiceLens then visualizes.

738
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

739
MCQmedium

A company has an AWS Organizations structure with a management account and 40 member accounts grouped into four OUs. The security team wants a single AWS account to receive all Amazon GuardDuty findings from every account and to view them in one place. They also need new accounts created under any OU to be automatically enrolled. Which solution meets these requirements with the LEAST operational overhead?

A.Designate a delegated administrator for GuardDuty in AWS Organizations and enable GuardDuty with auto-enable for all existing and new member accounts.
B.Create an organization trail in AWS CloudTrail and use CloudTrail Lake to query GuardDuty findings across all accounts.
C.Enable GuardDuty in each member account and create an Amazon EventBridge rule in each account that forwards findings to a central Amazon SNS topic.
D.Enable GuardDuty only in the management account and use AWS Resource Access Manager to share the detector with all member accounts.
AnswerA

GuardDuty integrates natively with AWS Organizations. Designating a delegated administrator lets that account manage GuardDuty across the organization, and auto-enable ensures every current and future member account is protected and its findings are aggregated in the delegated administrator account with no per-account scripting.

Why this answer

GuardDuty's native AWS Organizations integration is the intended mechanism for multi-account security monitoring. A delegated administrator account manages the service centrally, and auto-enable covers both existing accounts and accounts created later under any OU. This avoids building and maintaining per-account EventBridge and SNS forwarding pipelines while still delivering a consolidated findings view.

Exam trap

The trap here is assuming GuardDuty detectors can be shared across accounts with AWS Resource Access Manager instead of using the built-in Organizations delegated administrator and auto-enable features.

740
MCQhard

A company is migrating a critical 3-tier application to AWS. The application consists of a web tier, an application tier, and a PostgreSQL database. The web and application tiers are stateless and run on Linux. The company has deployed the web tier on EC2 instances behind an Application Load Balancer (ALB) across two Availability Zones. The application tier is deployed on EC2 instances in an Auto Scaling group across two Availability Zones. The PostgreSQL database is migrated to Amazon RDS for PostgreSQL with Multi-AZ deployment. The application uses sticky sessions (session affinity) to maintain user sessions on the web tier. After migration, users report that they are frequently logged out and lose session data. The web tier logs show that requests are being routed to different web instances. What is the MOST likely cause of this issue?

A.The target group for the web tier does not have sticky sessions (session affinity) enabled
B.The ALB is configured to disable cross-zone load balancing, causing uneven traffic distribution
C.The idle timeout of the ALB is set too low, causing sessions to expire
D.The web tier should use a Network Load Balancer (NLB) instead of an ALB for sticky sessions
AnswerA

The ALB target group lacks stickiness, so the load balancer distributes each request independently across web instances. Without session affinity, users hit different instances and lose session state, matching the reported logouts and the stem's sticky-session requirement.

Why this answer

The most likely cause is that the ALB target group does not have sticky sessions enabled. Sticky sessions (session affinity) ensure that all requests from a user during a session are routed to the same target. Without it, the ALB distributes requests across multiple instances, causing session loss.

The application relies on sticky sessions, so this misconfiguration directly explains the symptoms.

Exam trap

The trap is blaming the load balancer type (ALB vs NLB) or timeout settings, when the core issue is a missing sticky session configuration on the target group; candidates often overlook that ALB supports sticky sessions natively.

How to eliminate wrong answers

Option B is wrong because disabling cross-zone load balancing affects traffic distribution across AZs but does not cause session loss if sticky sessions are enabled. Option C is wrong because idle timeout affects long-lived connections, but the symptom of frequent logouts across different instances points to session affinity, not timeout. Option D is wrong because ALB supports sticky sessions; NLB is not required and would not solve the issue if sticky sessions are not enabled.

741
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

742
MCQeasy

A company is planning a hybrid cloud migration and needs to establish a dedicated network connection between its on-premises data center and AWS with consistent low latency. Which AWS service should be used?

A.AWS Direct Connect
B.AWS Client VPN
C.AWS Transit Gateway
D.AWS Site-to-Site VPN
AnswerA

AWS Direct Connect provisions a dedicated private network link from on-premises equipment to an AWS location, bypassing the public internet. This delivers consistent low latency and predictable bandwidth, satisfying the hybrid migration requirement for a dedicated connection, unlike VPN tunnels that traverse shared internet paths.

Why this answer

AWS Direct Connect provides a dedicated private network connection from on-premises to AWS, offering consistent low latency. Option A is correct for this reason. Option B (AWS Client VPN) is incorrect because it is designed for individual remote clients, not a dedicated connection.

Option C (AWS Transit Gateway) is incorrect as it is a hub for connecting networks, not a direct connection method. Option D (AWS Site-to-Site VPN) is incorrect because it uses the public internet and does not provide dedicated bandwidth or consistent low latency.

743
Multi-Selecthard

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

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

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

Why this answer

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

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

Exam trap

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

744
MCQmedium

A company is migrating an on-premises application to AWS. The application requires persistent shared storage that can be accessed by multiple EC2 instances simultaneously with strong consistency. Which AWS storage solution should the company use?

A.Amazon S3 with S3 File Gateway.
B.Amazon S3 Glacier Deep Archive.
C.Amazon EBS with Multi-Attach enabled.
D.Amazon EFS
AnswerD

Amazon EFS provides a shared, POSIX-compliant NFS file system mountable concurrently by many EC2 instances across Availability Zones, with strong read-after-write consistency. This satisfies the simultaneous multi-instance access and strong consistency constraints that single-attach EBS volumes cannot meet.

Why this answer

Amazon EFS is a fully managed, scalable, shared file storage service for EC2 instances. It provides strong consistency and supports simultaneous access from multiple EC2 instances across multiple Availability Zones. It is designed for applications that require shared storage, making it the correct choice.

The other options do not provide persistent shared storage with strong consistency for multiple instances.

Exam trap

The trap is confusing EBS Multi-Attach with a shared file system. EBS Multi-Attach allows multiple instances to attach the same volume, but it does not provide a clustered file system, so concurrent writes can lead to data corruption.

How to eliminate wrong answers

Option A is wrong because S3 File Gateway provides a file interface to S3, but it does not offer strong consistency for shared access from multiple EC2 instances; it is primarily for backup and archival. Option B is wrong because S3 Glacier Deep Archive is an archival storage service with retrieval times of hours, not suitable for persistent shared storage. Option C is wrong because EBS with Multi-Attach allows a volume to be attached to multiple instances in the same Availability Zone, but it does not provide strong consistency for concurrent writes and is not a shared file system.

745
Multi-Selecthard

A company runs a microservices architecture on Amazon ECS with Fargate. The operations team observes that some services are experiencing high latency during peak hours. The team wants to identify the root cause. Which THREE approaches should the team use? (Choose THREE.)

Select 3 answers
A.Use AWS X-Ray to trace requests through the microservices
B.Enable AWS CloudTrail to log API calls
C.Enable VPC Flow Logs to analyze network traffic
D.Use Amazon CloudWatch ServiceLens to correlate metrics, logs, and traces
E.Enable Container Insights for Amazon ECS
AnswersA, D, E

X-Ray traces individual requests as they traverse microservices, revealing which downstream call adds latency during peak hours. This satisfies the stem's requirement to identify the root cause by exposing per-segment timing across the distributed request path.

Why this answer

Option A is correct because AWS X-Ray traces requests as they travel through the microservices, revealing which service or downstream call is introducing latency during peak hours. Option D is correct because CloudWatch ServiceLens combines traces from X-Ray with CloudWatch metrics and logs in a single view, making it possible to correlate latency spikes with specific services and resources. Option E is correct because Container Insights for Amazon ECS collects CPU, memory, network, and task-level metrics for Fargate tasks, helping pinpoint resource saturation that causes high latency.

Option B is not appropriate because CloudTrail records control-plane API activity, not application request latency. Option C is not appropriate because VPC Flow Logs capture IP-level traffic metadata and cannot trace application requests or identify which microservice is slow.

Exam trap

SAP-C02 often tests whether candidates pick auditing tools (CloudTrail) or network-layer tools (VPC Flow Logs) for application performance troubleshooting, confusing observability layers.

746
MCQmedium

A multinational corporation is deploying a multi-account AWS environment using AWS Organizations. The security team requires that all S3 buckets across all accounts be encrypted with a specific AWS KMS key managed by the security account. Which solution should the company implement to enforce this policy across the organization?

A.Create IAM policies in each account to enforce encryption
B.Attach a service control policy (SCP) to the root that denies S3 actions unless encryption conditions are met
C.Use AWS Config rules with auto-remediation in each account
D.Deploy a CloudFormation StackSet that creates S3 buckets with encryption
AnswerB

SCPs attached at the organisation root define the maximum permissions for every account, so a deny on S3 actions lacking the required KMS encryption condition blocks non-compliant bucket creation and uploads organisation-wide. This enforces the mandated key across all accounts without per-account policy management.

Why this answer

A service control policy (SCP) attached to the root of the AWS Organizations hierarchy can deny S3 PutObject or CreateBucket actions unless the request includes the specific KMS key ID (via the s3:x-amz-server-side-encryption-aws-kms-key-id condition key). This enforces encryption centrally across all accounts, as SCPs are inherited by all member accounts and cannot be overridden by IAM policies within those accounts.

Exam trap

The trap here is that candidates often choose AWS Config rules (Option C) thinking they provide preventive enforcement, but Config rules are detective and reactive, not preventive, whereas SCPs proactively block non-compliant API calls before the resource is created.

How to eliminate wrong answers

Option A is wrong because IAM policies in each account can be modified or bypassed by account administrators, and they do not provide centralized enforcement across the organization. Option C is wrong because AWS Config rules with auto-remediation are reactive (detect and fix non-compliant resources after creation) and do not prevent the initial creation of unencrypted buckets, plus they require per-account setup. Option D is wrong because a CloudFormation StackSet only creates buckets with encryption at deployment time but does not prevent users from creating unencrypted buckets outside of the StackSet, nor does it enforce encryption on existing or future buckets.

747
MCQeasy

A company has multiple AWS accounts and wants to centrally manage CloudWatch dashboards. Which solution should they use?

A.Use CloudWatch cross-account dashboards with a monitoring account.
B.Use AWS Config aggregator to view resources.
C.Use Amazon QuickSight with data sources from each account.
D.Use AWS CloudFormation StackSets to deploy dashboards in each account.
AnswerA

CloudWatch cross-account dashboards let a monitoring account display metrics from source accounts without duplicating resources, satisfying the centralised management requirement across multiple AWS accounts. Source accounts share data via CloudWatch cross-account observability, so dashboards remain unified while each account retains ownership of its own metrics.

Why this answer

CloudWatch cross-account dashboards allow you to create a single dashboard in a central monitoring account that displays metrics from multiple source accounts. This is the native AWS solution for centralized observability, requiring no additional data movement or custom code. The monitoring account uses the CloudWatch cross-account functionality to query metrics across accounts via IAM roles and the CloudWatch API.

Exam trap

The trap here is that candidates confuse AWS Config aggregator (which aggregates configuration data) with CloudWatch cross-account dashboards (which aggregate metric data), or assume CloudFormation StackSets provide a central view when they only replicate resources per account.

How to eliminate wrong answers

Option B is wrong because AWS Config aggregator is designed to aggregate resource configuration and compliance data, not CloudWatch metrics or dashboards; it cannot display time-series metric graphs. Option C is wrong because Amazon QuickSight is a business intelligence service for interactive dashboards and analytics, not a native CloudWatch dashboard viewer; it would require custom data pipelines to extract CloudWatch metrics into SPICE or S3, adding unnecessary complexity. Option D is wrong because AWS CloudFormation StackSets can deploy dashboard definitions across accounts, but each dashboard remains isolated in its own account; there is no central view or cross-account query capability, defeating the purpose of centralized management.

748
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

749
MCQmedium

A solutions architect is reviewing an existing three-tier application running on Amazon EC2 instances in an Auto Scaling group. The database tier uses Amazon RDS for MySQL with a single Availability Zone deployment. The business requires improved resilience and wants to minimize changes to the application. The RPO is 5 minutes and the RTO is 2 minutes. Which change should the architect recommend?

A.Convert the RDS instance to a Multi-AZ deployment with a standby replica in another Availability Zone.
B.Migrate the database to Amazon DynamoDB with global tables and modify the application to use the DynamoDB API.
C.Create a read replica in another Availability Zone and update the application to send writes to the read replica during a failure.
D.Enable automated backups with a 5-minute backup window and restore the database to a new instance if a failure occurs.
AnswerA

Multi-AZ creates a synchronous standby in a second Availability Zone and automatically fails over the DNS endpoint, typically within one to two minutes. It requires no application changes because the endpoint remains the same. This meets the 2-minute RTO and near-zero RPO for Availability Zone failure, making it the most appropriate resilience improvement for the existing database tier.

Why this answer

A Multi-AZ deployment provides synchronous standby replication and automatic failover to a second Availability Zone, meeting the 2-minute RTO without application changes. Read replicas, backup restores, and NoSQL migration either require manual steps, longer recovery, or significant code changes, so they do not satisfy the constraints.

Exam trap

The trap here is confusing read replicas with Multi-AZ standby replicas, assuming that a read replica can provide automatic failover for writes.

750
MCQhard

A company has a legacy monolithic application running on a single EC2 instance. The application stores customer data in an attached EBS volume. The company wants to modernize the application to improve scalability and availability. Which approach should a solutions architect recommend?

A.Use a larger EC2 instance with enhanced networking.
B.Configure multiple EC2 instances to share the same EBS volume using Multi-Attach.
C.Replace the EBS volume with an Aurora RDS database.
D.Refactor the application into microservices running on Amazon ECS with data stored in Amazon S3.
AnswerD

Refactoring into microservices on Amazon ECS removes the single-instance bottleneck, enabling horizontal scaling and multi-AZ availability. Moving data to Amazon S3 decouples storage from compute, satisfying the scalability and availability constraints that the monolithic EBS-attached design cannot meet.

Why this answer

Migrating to a containerized, stateless application decouples storage and allows scaling. Option A is wrong because a larger instance still has a single point of failure. Option B is wrong because Multi-Attach EBS volumes have limited support and multiple instances writing to the same volume can cause data corruption.

Option C is wrong because RDS is for databases, not for application data stored in files.

Page 9

Page 10 of 14

Page 11