All practice questions

1462 questions

Question 701Question

A content delivery application is hosted on a fleet of Amazon EC2 instances distributed across three Availability Zones. The instances require concurrent read and write access to a shared directory containing static assets. The storage system must deliver low-latency file operations and handle unpredictable throughput spikes of up to 2 GiB/s2\text{ GiB/s}, while experiencing prolonged periods of near-zero activity. Which storage solution should a solutions architect recommend to meet these requirements with the lowest operational overhead?

Show answer & explanation

Answer: Amazon EFS file system configured in General Purpose performance mode with Elastic throughput

Answer

Amazon EFS file system configured in General Purpose performance mode with Elastic throughput
The correct solution uses Amazon Elastic File System (Amazon EFS) configured in General Purpose performance mode and Elastic throughput. Amazon EFS is a shared, POSIX-compliant file system that can be concurrently mounted by instances across multiple Availability Zones. General Purpose performance mode is recommended for latency-sensitive applications like web hosting. Elastic throughput is ideal for workloads with unpredictable or spiky traffic patterns because it dynamically adjusts throughput up to 2 GiB/s2\text{ GiB/s} or higher, charging only for the data read and written, which avoids over-provisioning during idle periods.

Step-by-Step Solution

1
Analyze workload characteristics and requirements.
Shared read/write storage access across three Availability Zones with low-latency file operations and throughput spikes up to 2 GiB/s2\text{ GiB/s} followed by idle periods.
This helps narrow down the eligible AWS storage services that support multi-AZ concurrent mounts.
2
Evaluate multi-AZ shared storage options.
Amazon EFS supports cross-AZ shared access, whereas Amazon EBS (even with Multi-Attach) is restricted to a single Availability Zone.
Eliminates EBS-based solutions from consideration for this multi-AZ deployment.
3
Determine EFS performance and throughput modes.
General Purpose mode provides the lowest per-operation latency, and Elastic throughput accommodates unpredictable throughput spikes up to 2 GiB/s2\text{ GiB/s} without pre-provisioning or risk of credit depletion, charging only for throughput consumed.
Fits the latency, throughput scaling, and cost-effectiveness requirements.

Key Concept

Shared storage performance optimization on AWS
Question 702Question

A company wants to improve the resiliency and availability of its static website hosted on Amazon S3. The website experiences occasional origin availability issues during regional outages. Which two configurations should a solutions architect implement to build a resilient content delivery solution? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and an S3 bucket in a different AWS Region as the failover origin.; Configure CloudFront custom error pages to serve a maintenance page cached at the edge when the origin returns a 503 Service Unavailable error.

Answer

To build a resilient content delivery solution, the solutions architect should configure a CloudFront Origin Group with primary and secondary S3 buckets in different regions, and configure CloudFront custom error pages to serve a cached maintenance page during origin outages.
Configuring a CloudFront Origin Group provides automatic failover capability between a primary S3 bucket and a failover S3 bucket in a different region. Combining this with CloudFront custom error pages ensures that even if both origins fail or during transition periods, a friendly, cached maintenance page is served directly from edge locations, optimizing availability and user experience.

Step-by-Step Solution

1
Set up multi-region origin redundancy by creating a secondary S3 bucket in another AWS Region and replicating static assets to it.
Two identical sets of static assets exist in different regions.
Ensures a backup origin is available in case the primary region experiences an outage.
2
Create a CloudFront Origin Group containing both the primary S3 bucket and the secondary S3 bucket.
An Origin Group is established with the secondary bucket designated as the failover origin.
Allows CloudFront to automatically redirect requests when the primary origin is unreachable or returns designated error codes.
3
Configure CloudFront custom error pages for HTTP status code 503.
A custom error page pointing to a static maintenance file is cached at edge locations.
Ensures that even during failover transitions or complete origin failures, users receive a friendly cached response directly from the edge.

Key Concept

Leveraging CloudFront Origin Groups and Custom Error Pages to build resilient content delivery architectures that survive regional S3 origin outages.
Estimated Time:1m 30s
Question 703Question

A company runs a high-performance simulation platform on AWS. The application architecture has three primary workloads:

1. A front-end web portal and API gateway running on Amazon ECS with AWS Fargate. This has a constant, predictable baseline demand of 15 vCPUs15\text{ vCPUs} and 30 GB30\text{ GB} of memory 24/724/7, with brief, unpredictable spikes up to 60 vCPUs60\text{ vCPUs} during peak daytime hours.
2. A cluster of backend worker nodes running simulation jobs on Amazon EC2. These jobs are stateless, run for 44 to 66 hours, can be interrupted and resumed at any time, and are triggered dynamically based on queue depth.
3. An Amazon RDS for MySQL database that stores application state and runs continuously.

Which two strategies should a solutions architect recommend to optimize the compute and database costs for this platform? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Purchase a Compute Savings Plan to cover the baseline usage of the ECS Fargate tasks.; Configure an EC2 Auto Scaling group using Spot Instances for the simulation worker nodes.

Answer

To optimize the costs of this architecture, the company should purchase a Compute Savings Plan to cover the baseline usage of the ECS Fargate tasks and configure an EC2 Auto Scaling group using Spot Instances for the simulation worker nodes.
Purchasing a Compute Savings Plan covers the constant, predictable baseline usage of the ECS Fargate tasks at a significantly discounted rate. Using Spot Instances for the simulation worker nodes is highly cost-effective because the workloads are stateless, queue-driven, and can tolerate interruptions, allowing the company to leverage up to 90%90\% discounts compared to On-Demand pricing.

Step-by-Step Solution

1
Analyze the workload characteristics of each compute tier to identify baseline vs. variable usage.
The ECS Fargate web tier has a continuous, predictable baseline of 15 vCPUs15\text{ vCPUs} and 30 GB30\text{ GB} of memory 24/724/7. The simulation worker nodes are stateless, run for 44 to 66 hours, and are queue-driven, meaning they can tolerate interruption.
Understanding the compute characteristics and resilience of each tier is necessary to match them to the correct AWS pricing models.
2
Select the optimal purchasing model for the continuous, predictable baseline of the ECS Fargate tasks.
Select a Compute Savings Plan, which applies to ECS Fargate, AWS Lambda, and Amazon EC2 usage. This commitment-based model provides substantial discounts over On-Demand rates for the steady-state baseline.
Compute Savings Plans are flexible, apply automatically to Fargate across any region, and lower the cost of continuous container workloads.
3
Select the optimal purchasing model for the stateless, queue-driven backend simulation worker nodes.
Configure an EC2 Auto Scaling group using Spot Instances to run the backend worker nodes.
Since the simulation jobs are stateless and run from a queue, they are highly tolerant of EC2 instance reclamation. Spot Instances offer the lowest cost (up to 90%90\% savings over On-Demand) for interruptible workloads.

Key Concept

Selecting the most cost-effective compute purchasing strategies based on workload predictability, duration, and fault tolerance.
Question 704Question

A company runs a collaborative data analytics application on a fleet of Amazon EC2 instances. The application requires a high-performance, shared storage solution that supports concurrent read and write access from all instances simultaneously. The storage solution must also scale capacity automatically as the dataset grows.

Which AWS storage service should the company use to meet these requirements?

Show answer & explanation

Answer: Amazon EFS

Answer

Amazon EFS
Amazon EFS provides a fully managed, serverless, and elastic file system that can be mounted concurrently by thousands of Amazon EC2 instances. It supports standard POSIX permissions and automatically scales its storage capacity up or down as files are added or removed, matching the high-performance and shared access requirements of the analytics application.

Step-by-Step Solution

1
Identify that the application requires a shared file system that can be accessed concurrently by a fleet of Amazon EC2 instances.
Limits the options to network-attached storage systems that support multi-instance mount configurations.
Block storage systems like Amazon EBS are restricted to single-instance mounting in standard operational patterns.
2
Evaluate the requirement for the storage capacity to scale automatically as the dataset grows.
Points to elastic storage solutions that grow and shrink dynamically without manual provisioning.
This rules out Amazon EBS volumes, which require manual API calls or configurations to resize.
3
Select the service that natively supports concurrent multi-instance POSIX-compliant access and elastic auto-scaling.
Amazon EFS is selected.
Amazon EFS is designed to serve as a serverless network file system that scales storage dynamically and supports concurrent access.

Key Concept

Shared, elastic file storage with Amazon EFS
Estimated Time:45s
Question 705Question

A financial modeling firm is designing a high-performance compute (HPC) environment on AWS to run tightly-coupled risk simulations. The workload uses Message Passing Interface (MPI) and requires node-to-node network latency of less than 1010 microseconds. The cluster must dynamically scale between 2020 and 8080 compute-optimized EC2 instances based on queue depth. During load testing, the team observes that scaling out the Auto Scaling group incrementally results in frequent launch failures with `InsufficientInstanceCapacity` errors, and the network performance between newly launched instances does not meet the low-latency SLA.

Which architecture should a Solutions Architect recommend to resolve the capacity errors and maintain the required low-latency performance?

Show answer & explanation

Answer: Deploy the EC2 instances in a single Cluster Placement Group within a single Availability Zone. Use a Launch Template that specifies an Elastic Fabric Adapter (EFA) enabled instance type, and associate the Auto Scaling group with an On-Demand Capacity Reservation targeted for the placement group to guarantee that the maximum capacity of 8080 instances is pre-allocated.

Answer

Deploy the EC2 instances in a single Cluster Placement Group within a single Availability Zone, using a Launch Template that specifies an Elastic Fabric Adapter (EFA) enabled instance type, and associate the Auto Scaling group with an On-Demand Capacity Reservation targeted for the placement group.
Tightly-coupled HPC workloads using MPI require ultra-low latency, which is achieved by deploying EC2 instances in a Cluster Placement Group in a single Availability Zone and using Elastic Fabric Adapter (EFA). Launching instances incrementally into a cluster placement group often leads to capacity fragmentation and `InsufficientInstanceCapacity` errors if the underlying physical rack lacks contiguous capacity. Creating an On-Demand Capacity Reservation (ODCR) targeted for the cluster placement group ensures that the required slot of 8080 instances is pre-allocated, resolving the launch failures during scale-out events.

Step-by-Step Solution

1
Identify latency and communication requirements
Tightly-coupled HPC workloads using MPI require node-to-node latency of less than 1010 microseconds, which demands a Cluster Placement Group in a single Availability Zone combined with Elastic Fabric Adapter (EFA) for OS-bypass.
This establishes the baseline compute and network topology optimized for tightly-coupled workloads.
2
Analyze the cause of scale-out capacity failures
Launching instances incrementally in a Cluster Placement Group leads to capacity fragmentation. The physical rack containing the placement group may run out of contiguous slots, causing `InsufficientInstanceCapacity` errors.
This explains why standard Auto Scaling scale-out fails even if general regional capacity exists.
3
Select the correct mitigation strategy
By using an On-Demand Capacity Reservation (ODCR) targeted for the specific Cluster Placement Group, AWS reserves the maximum 8080 instance slots upfront, ensuring subsequent scale-out requests succeed without capacity errors.
This guarantees availability of the required compute slots inside the strict physical boundaries of the placement group.

Key Concept

Optimizing compute environments for tightly-coupled HPC workloads using Cluster Placement Groups, Elastic Fabric Adapter (EFA), and On-Demand Capacity Reservations.
Estimated Time:3m 0s
Question 706Question

A financial services company is developing a real-time market analysis application deployed on a fleet of Amazon EC2 instances. The application needs to process and store millions of small analysis reports. The storage solution must support over 18,00018,000 read requests per second and 12,00012,000 write requests per second with sub-millisecond API latency. The files must be accessible via standard HTTPS APIs from any instance in the fleet, and the storage layer must automatically scale to handle unpredictable traffic spikes without manual intervention or performance degradation.

Which combination of actions should the solutions architect recommend to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Store the reports in an Amazon S3 bucket, and distribute the objects across multiple distinct prefixes within the bucket.; Deploy an Amazon CloudFront distribution in front of the Amazon S3 bucket to cache read requests and serve them from edge locations.

Answer

Storing the reports in Amazon S3 distributed across multiple prefixes and caching read requests using Amazon CloudFront.
Amazon S3 supports up to 5,5005,500 GET/HEAD requests and 3,5003,500 PUT/POST/DELETE requests per second per prefix. By partitioning the reports across multiple prefixes within the bucket, the application can scale storage operations horizontally to support 18,00018,000 read requests and 12,00012,000 write requests. Deploying Amazon CloudFront in front of the bucket caches frequently accessed read requests at edge locations, reducing request loads on the S3 prefixes and providing sub-millisecond latencies.

Step-by-Step Solution

1
Analyze the request rate requirements of 18,00018,000 reads/sec and 12,00012,000 writes/sec.
Identified that a single prefix in Amazon S3 (which supports 5,5005,500 GET/HEAD and 3,5003,500 PUT/POST/DELETE requests per second) will be throttled.
This establishes the scale of partitioning needed to distribute the performance load.
2
Evaluate partitioning options to distribute requests across multiple prefixes in S3.
By using at least 4 prefixes for reads and 4 for writes, the application can scale to handle the request volume without throttling.
S3 automatically partitions and scales performance limits per prefix.
3
Determine the mechanism to achieve sub-millisecond read latency over HTTPS.
Integrating Amazon CloudFront in front of the S3 bucket allows caching of reports at edge locations.
CloudFront handles high read rates and serves cached content with sub-millisecond latency.
4
Evaluate alternative storage options like EBS Multi-Attach and EFS against the requirements.
Ruled them out due to protocol mismatch (block/NFS instead of HTTP/HTTPS) and lack of automatic performance scaling for unpredictable spikes.
EBS Multi-Attach and EFS do not meet the direct HTTP API access requirement or the automatic scaling envelope without manual provisioning.

Key Concept

Amazon S3 prefix-based request scaling limits and CloudFront caching for high-performance HTTP workloads.
Estimated Time:2m 30s
Question 707Question

A media company runs a transcoding application that generates output files of approximately 22 MB each. These files are accessed frequently by downstream users for exactly 1010 days, after which they are deleted. The company wants to minimize its storage costs on Amazon S3. Which storage strategy is the most cost-effective for these output files?

Show answer & explanation

Answer: Keep the files in Amazon S3 Standard for the entire 1010 days, and then delete them using an S3 Lifecycle expiration rule.

Answer

Keep the files in Amazon S3 Standard for the entire 1010 days, and then delete them using an S3 Lifecycle expiration rule.
Keeping the files in Amazon S3 Standard for the entire duration and deleting them via lifecycle policies is the most cost-effective option. Amazon S3 Standard does not charge retrieval fees and has no minimum storage duration. Since the files are deleted after 1010 days, any transition to S3 Standard-IA or Glacier classes would trigger minimum storage charges (3030 days for Standard-IA, 9090 days for Glacier), resulting in higher costs.

Step-by-Step Solution

1
Evaluate the data access pattern and retention period.
The files are accessed frequently for 1010 days and then deleted.
Understanding the lifecycle of the data determines which storage tiers can be used without penalties.
2
Analyze storage class constraints, specifically minimum storage duration.
Amazon S3 Standard has no minimum storage duration. Amazon S3 Standard-IA has a 3030-day minimum storage duration. Amazon S3 Glacier Flexible Retrieval has a 9090-day minimum storage duration.
Using Standard-IA or Glacier for data that is deleted after 1010 days will result in paying for unused storage (3030 days and 9090 days of billing, respectively).
3
Determine the most cost-effective option based on duration and access rules.
S3 Standard is the most cost-effective tier because it avoids early deletion charges for the 1010-day lifecycle.
Since the files are accessed frequently and deleted well before 3030 days, S3 Standard is cheaper than Standard-IA or Glacier classes.

Key Concept

Amazon S3 Storage Classes and Minimum Storage Durations
Estimated Time:50s
Question 708Question

A company is migrating its transactional application to Amazon RDS. To prevent downtime during an infrastructure failure or an Availability Zone outage, the solutions architect must configure the database for automatic failover to a standby instance in another Availability Zone with zero manual intervention. Which database configuration should the solutions architect recommend?

Show answer & explanation

Answer: An Amazon RDS Multi-AZ deployment

Answer

An Amazon RDS Multi-AZ deployment
The correct option is the Amazon RDS Multi-AZ deployment. Multi-AZ deployments provide high availability and failover support for DB instances. AWS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. In the event of a failure, the primary DB instance is failed over to the standby replica automatically, ensuring high availability with zero administrative overhead.

Step-by-Step Solution

1
Identify the high availability and recovery time objective requirements.
The company requires automated failover to a standby instance in a different Availability Zone with zero manual intervention.
This rules out solutions that require manual failover procedures or application-level reconfiguration.
2
Evaluate the failover and replication characteristics of the options.
RDS Multi-AZ uses synchronous replication to a standby replica in another AZ and performs automatic failover when the primary instance becomes unavailable. Read Replicas use asynchronous replication and require manual promotion.
Only RDS Multi-AZ satisfies the requirement for automatic, zero-intervention failover in another AZ.

Key Concept

Amazon RDS Multi-AZ deployments provide automatic failover and high availability by maintaining a synchronous standby replica in a different Availability Zone.
Question 709Question

A startup runs a steady-state transaction processing application on Amazon EC2 instances and AWS Fargate tasks. They also run a reporting database on Amazon RDS for PostgreSQL that operates 24/7. To minimize compute costs, the startup wants to commit to a 1-year term. Which combination of purchasing options provides the most cost-effective coverage for these resources?

Show answer & explanation

Answer: A Compute Savings Plan to cover the Amazon EC2 instances and AWS Fargate tasks, combined with an Amazon RDS Reserved Instance for the PostgreSQL database.

Answer

A Compute Savings Plan to cover the Amazon EC2 instances and AWS Fargate tasks, combined with an Amazon RDS Reserved Instance for the PostgreSQL database.
The correct option combines a Compute Savings Plan to cover the Amazon EC2 and AWS Fargate resources with an Amazon RDS Reserved Instance to cover the PostgreSQL database. Compute Savings Plans apply discounts to compute services (EC2, Fargate, and Lambda) based on a 1-year or 3-year commitment. Since database instances are not covered by Compute Savings Plans, the continuous database tier must be covered separately under Amazon RDS Reserved Instances to ensure cost optimization across all resources.

Step-by-Step Solution

1
Identify the compute resources running in a steady-state or continuous pattern.
The application layers run on Amazon EC2 instances and AWS Fargate tasks, and the database layer runs on Amazon RDS for PostgreSQL.
Before applying purchasing models, the architecture must be cataloged into compute hosting models.
2
Determine the appropriate cost-optimization model for the EC2 instances and AWS Fargate tasks.
A Compute Savings Plan is selected to cover both EC2 and Fargate tasks under a single 1-year commitment.
Compute Savings Plans provide the greatest flexibility to apply discounts automatically across different compute options, including both EC2 and AWS Fargate.
3
Determine the appropriate cost-optimization model for the Amazon RDS database instance.
An Amazon RDS Reserved Instance is selected for the PostgreSQL database.
Savings Plans do not cover Amazon RDS databases; therefore, an RDS Reserved Instance is required to secure a discount on the 24/7 database workloads.

Key Concept

Applying Compute Savings Plans to EC2 and Fargate workloads while utilizing RDS Reserved Instances for RDS database workloads.
Estimated Time:1m 0s
Question 710Question

A company is planning to deploy a new web application on AWS. The application will consist of a steady-state web server hosted on Amazon EC2 that must run continuously 24/7, and an Amazon RDS for MySQL database. The workload is highly predictable. Which combination of purchasing options should the company select to minimize compute costs for these resources most effectively? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Purchase an Amazon EC2 Instance Savings Plan for the EC2 web server; Purchase Amazon RDS Reserved DB Instances for the MySQL database

Answer

Purchase an Amazon EC2 Instance Savings Plan for the EC2 web server, and purchase Amazon RDS Reserved DB Instances for the MySQL database.
To minimize compute costs for a predictable, 24/7 web server, purchasing an Amazon EC2 Instance Savings Plan is the most cost-effective option. To minimize database costs for Amazon RDS, purchasing Amazon RDS Reserved DB Instances is the correct approach, as RDS is not covered by Compute Savings Plans.

Step-by-Step Solution

1
Analyze the web server requirement.
The web server runs 24/7 with predictable, steady-state usage, making it an ideal candidate for an EC2 Instance Savings Plan.
This strategy locks in lower rates for predictable EC2 workloads.
2
Analyze the database tier cost optimization.
The database uses Amazon RDS for MySQL. Purchasing RDS Reserved DB Instances is the correct method to lower steady-state database costs.
RDS does not benefit from Compute Savings Plans, so database-specific reservations are required.

Key Concept

Selecting cost-effective compute purchasing options based on resource types and predictability
Question 711Question

An automotive engineering firm is designing a disaster recovery solution for its on-premises computer-aided design (CAD) file server, which holds 40 TB40\text{ TB} of data. The firm has defined a Recovery Point Objective (RPO) of 4 hours4\text{ hours} and a Recovery Time Objective (RTO) of 2 hours2\text{ hours}. During normal operations, on-premises users must access these files with sub-millisecond local latency. In the event of a local site failure, the files must be immediately accessible from a highly available and resilient environment in AWS. Which storage architecture meets these requirements most cost-effectively?

Show answer & explanation

Answer: Deploy AWS Storage Gateway in cached volume mode on-premises. Cache frequently accessed files locally, store the full dataset in Amazon S3, and schedule volume snapshots every 4 hours4\text{ hours}. In a disaster recovery event, restore the snapshots as Amazon Elastic Block Store (Amazon EBS) volumes and attach them to Amazon EC2 instances.

Answer

Deploy AWS Storage Gateway in cached volume mode on-premises, storing the full dataset in Amazon S3, scheduling snapshots every 4 hours4\text{ hours}, and restoring these snapshots to Amazon EBS volumes attached to Amazon EC2 instances during a disaster.
The correct solution uses AWS Storage Gateway in cached volume mode to store the master dataset in Amazon S3 and cache active files locally for sub-millisecond access. Taking snapshots every 4 hours4\text{ hours} meets the 4-hour4\text{-hour} RPO, and restoring those snapshots to EBS volumes attached to EC2 instances in a disaster meets the 2-hour2\text{-hour} RTO.

Step-by-Step Solution

1
Analyze the local latency and storage architecture requirements.
The requirement for sub-millisecond local latency on-premises indicates that frequently accessed data must be cached locally. AWS Storage Gateway in cached volume mode fulfills this by storing the primary dataset in Amazon S3 and maintaining a local cache of active data.
This minimizes local latency while ensuring durability by storing the master copy in the AWS cloud.
2
Evaluate the Recovery Point Objective (RPO) constraint.
An RPO of 4 hours4\text{ hours} means that backup or replication frequency must occur at least every 4 hours4\text{ hours} to prevent losing more than 4 hours4\text{ hours} of data.
Scheduling volume snapshots every 4 hours4\text{ hours} directly satisfies this requirement.
3
Evaluate the Recovery Time Objective (RTO) constraint.
An RTO of 2 hours2\text{ hours} means the system must be restored and running within 2 hours2\text{ hours}. Restoring EBS snapshots and attaching them to EC2 instances takes minutes, which is well within the 2-hour2\text{-hour} window.
Using Standard retrieval from Glacier Flexible Retrieval (which takes 33 to 5 hours5\text{ hours}) is ruled out because it cannot meet this RTO.

Key Concept

AWS Storage Gateway cached volumes provide low-latency local access to frequently used data while securing the full dataset in Amazon S3, allowing rapid disaster recovery via EBS snapshots.
Estimated Time:1m 30s
Question 712Question

An enterprise is planning a high-performance hybrid network architecture to connect their on-premises data center with two AWS Regions: us-east-1 and us-west-2. The company has an existing on-premises network with a 10 Gbps10\text{ Gbps} dedicated line. The new setup must support a continuous data replication stream of at least 5 Gbps5\text{ Gbps} between the on-premises database and multiple Amazon VPCs in both regions, while minimizing latency and routing complexity. Which combination of AWS networking components should a solutions architect recommend to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Provision an AWS Direct Connect connection and configure a Direct Connect Gateway.; Create an AWS Transit Gateway in each region and associate them with the Direct Connect Gateway to connect the VPCs.

Answer

Establish an AWS Direct Connect connection associated with a Direct Connect Gateway, and configure AWS Transit Gateway in each region to connect the VPCs to the Direct Connect Gateway.
The correct solution combines AWS Direct Connect, Direct Connect Gateway, and AWS Transit Gateway. AWS Direct Connect provides the necessary physical network bandwidth (10 Gbps10\text{ Gbps}) to easily support the 5 Gbps5\text{ Gbps} replication stream. The Direct Connect Gateway enables connectivity to multiple VPCs across different AWS Regions, while AWS Transit Gateway simplifies the architecture by serving as a centralized hub to consolidate VPC routing within each region.

Step-by-Step Solution

1
Evaluate the throughput requirement of 5 Gbps5\text{ Gbps} against connection options.
AWS Site-to-Site VPN is ruled out as a primary link because a single tunnel is limited to 1.25 Gbps1.25\text{ Gbps}. A dedicated AWS Direct Connect link (10 Gbps10\text{ Gbps} port) is selected to meet the bandwidth and performance needs.
Direct Connect ensures dedicated, reliable, and high-throughput connectivity without internet congestion.
2
Determine the routing mechanism to connect multiple VPCs across two different AWS Regions.
Establish a Direct Connect Gateway and attach a Transit Gateway from each region (us-east-1 and us-west-2) to the Direct Connect Gateway.
Direct Connect Gateway allows a single Direct Connect connection to access VPCs across multiple regions. Transit Gateway simplifies the routing mesh by aggregating VPC connections within each region.

Key Concept

High-Performing and Scalable Hybrid Network Architectures using Direct Connect and Transit Gateway
Estimated Time:2m 0s
Question 713Question

A global manufacturing firm runs a quality-control imaging system across several physical factories. The local factory systems require low-latency access to raw imaging data generated during the last 30 days. After 30 days, the data must be archived in the cloud, where it must remain durable and highly available for regulatory audits, with a Recovery Time Objective (RTO) of 5 hours. To protect against a regional disaster, all cloud archives must be replicated to a secondary AWS Region with a Recovery Point Objective (RPO) of 15 minutes. Which combination of actions should a solutions architect recommend to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon S3 File Gateway at each physical factory to provide low-latency local access to the active files while automatically uploading the data to an Amazon S3 bucket in the primary Region.; Configure Amazon S3 Cross-Region Replication (CRR) to a secondary Region with S3 Replication Time Control (RTC) enabled, and apply S3 Lifecycle rules to transition objects to Amazon S3 Glacier Flexible Retrieval after 30 days.

Answer

Deploying an Amazon S3 File Gateway at the factories to provide local caching, and configuring Amazon S3 Cross-Region Replication with Replication Time Control enabled along with lifecycle rules to transition objects to Amazon S3 Glacier Flexible Retrieval after 30 days.
The correct options involve deploying an Amazon S3 File Gateway at the factories to provide low-latency local access to the active files while uploading data to S3, and configuring Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (RTC) enabled to meet the 15-minute RPO. Additionally, using S3 Lifecycle rules to transition objects to Amazon S3 Glacier Flexible Retrieval after 30 days is correct because standard retrieval takes 3-5 hours, which satisfies the 5-hour RTO limit.

Step-by-Step Solution

1
Analyze the local low-latency access requirement for files under 30 days old.
Local users need fast access to files. An Amazon S3 File Gateway provides local caching (NFS/SMB) at physical locations while keeping data backed up to Amazon S3.
Direct cloud access could introduce high latency and fail bandwidth constraints for large imaging files.
2
Evaluate the 15-minute RPO disaster recovery requirement for the cloud storage.
Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (RTC) enabled.
S3 RTC guarantees that 99.9% of uploaded objects are replicated to the destination Region within 15 minutes, fulfilling the strict 15-minute RPO.
3
Verify the RTO requirement of 5 hours for archived data.
Transition objects to Amazon S3 Glacier Flexible Retrieval after 30 days using S3 Lifecycle policies.
S3 Glacier Flexible Retrieval supports Standard retrievals within 3-5 hours, which satisfies the 5-hour RTO, whereas Glacier Deep Archive requires up to 12 hours.

Key Concept

Designing hybrid cloud storage systems using Amazon S3 File Gateway for local caching, combined with cross-region replication (RTC) and S3 Glacier Flexible Retrieval to meet strict RTO and RPO objectives.
Question 714Question

A fleet logistics company is migrating its real-time telemetry processing platform to AWS. The platform receives data updates from 2,500,0002,500,000 active vehicles globally. Each vehicle transmits updates every 1010 seconds, resulting in a write throughput of 250,000250,000 writes per second. Each update consists of GPS coordinates, speed, and engine metrics. The monitoring dashboard requires real-time access to the most recent coordinate updates per vehicle with sub-millisecond read latency. A solutions architect must design a high-performing database architecture that avoids partition throttling and supports this read/write workload. Which two configurations should the solutions architect implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Provision an Amazon DynamoDB table with a partition key of `VehicleID` and a sort key of `Timestamp` to distribute writes evenly across partitions.; Deploy an Amazon DynamoDB Accelerator (DAX) cluster to cache read requests and deliver microsecond response times for the dashboard coordinate lookups.

Answer

To support a write volume of 250,000250,000 writes per second and sub-millisecond read latency, the solutions architect should provision an Amazon DynamoDB table with `VehicleID` as the partition key and `Timestamp` as the sort key, and deploy an Amazon DynamoDB Accelerator (DAX) cluster to cache read requests.
To scale to 250,000250,000 writes per second, Amazon DynamoDB is the ideal database choice. Choosing `VehicleID` as the partition key is highly effective because there are 2,500,0002,500,000 unique vehicle identifiers, resulting in a well-distributed hash key structure that avoids write hot spots. To meet the dashboard requirement for sub-millisecond (microsecond) read latency for lookup operations, deploying Amazon DynamoDB Accelerator (DAX) is the best choice because it provides an in-memory caching tier that sits directly in front of the DynamoDB table.

Step-by-Step Solution

1
Analyze write throughput requirements and calculate partition key distribution.
A write throughput of 250,000250,000 writes per second requires a database that scales horizontally. Amazon DynamoDB scales dynamically, but to avoid throttling, the partition key must be highly distributed. Using a unique `VehicleID` (with 2,500,0002,500,000 possibilities) as the partition key distributes writes evenly across partitions.
Ensures writes do not bottleneck on a single partition.
2
Analyze read latency requirements.
The dashboard requires sub-millisecond read latency. Standard DynamoDB queries return data in single-digit milliseconds, but microsecond response times require an in-memory caching tier.
Reduces read response time to microseconds.
3
Evaluate caching options for DynamoDB.
Amazon DynamoDB Accelerator (DAX) is an in-memory cache specifically designed for DynamoDB. It integrates seamlessly without requiring application-level caching logic changes and handles heavy read volumes at microsecond latency.
Directly meets the sub-millisecond lookup requirement for the dashboard.

Key Concept

Designing high-performing, horizontally scalable database solutions in AWS using DynamoDB partitioning strategies and in-memory caching with DAX to prevent write hotspots and read latency bottlenecks.
Question 715Question

A company is designing a hybrid network architecture to connect its on-premises data center to three VPCs in the us-east-1 Region. The connection must support a database replication traffic load that peaks at 3.2 Gbps3.2\text{ Gbps}. The company's security policy dictates that all traffic traversing this hybrid connection must be encrypted in transit using IPsec. Which network architecture will meet these requirements while providing the highest performance and scalability?

Show answer & explanation

Answer: Create an AWS Transit Gateway and enable Equal-Cost Multi-Path (ECMP) routing. Establish multiple AWS Site-to-Site VPN connections from the on-premises data center to the Transit Gateway, and configure dynamic routing using Border Gateway Protocol (BGP) to distribute the traffic across the active VPN tunnels.

Answer

The correct architecture is to create an AWS Transit Gateway with ECMP enabled, establish multiple AWS Site-to-Site VPN connections from the on-premises data center to the Transit Gateway, and configure dynamic routing using BGP to distribute the traffic across the active VPN tunnels.
The correct option provides a highly scalable and performant design. By deploying an AWS Transit Gateway and enabling Equal-Cost Multi-Path (ECMP) routing, multiple AWS Site-to-Site VPN connections can be combined. Since each VPN tunnel is capped at 1.25 Gbps1.25\text{ Gbps}, using ECMP to route traffic across at least three active tunnels allows the architecture to exceed the limit and support the required 3.2 Gbps3.2\text{ Gbps} peak database replication traffic while ensuring all traffic is encrypted with IPsec.

Step-by-Step Solution

1
Analyze the business requirements and constraints.
The solution requires IPsec encryption, connection to three VPCs, and a minimum peak throughput of 3.2 Gbps3.2\text{ Gbps}.
This establishes the boundaries for acceptable architectures.
2
Evaluate standard VPN throughput limits.
A single AWS Site-to-Site VPN tunnel is limited to 1.25 Gbps1.25\text{ Gbps}.
To support 3.2 Gbps3.2\text{ Gbps}, multiple VPN tunnels must be aggregated.
3
Select the aggregation and routing mechanism.
AWS Transit Gateway can aggregate multiple VPN tunnels using Equal-Cost Multi-Path (ECMP) routing with BGP.
ECMP enables load sharing of traffic across multiple active tunnels, providing scale and high performance.

Key Concept

AWS Transit Gateway supports ECMP routing to aggregate the throughput of multiple AWS Site-to-Site VPN tunnels, enabling hybrid networks to exceed the 1.25 Gbps1.25\text{ Gbps} single-tunnel limit.
Estimated Time:2m 0s
Question 716Question

A financial analytics firm generates daily transaction summaries that are stored in an Amazon S3 bucket. The summaries are accessed frequently by downstream applications for the first 30 days30 \text{ days} after creation. After 30 days30 \text{ days}, access to the summaries drops to almost zero, but they must be retained for compliance purposes for a total of 45 days45 \text{ days} from creation. During the compliance retention period, the summaries must remain queryable within milliseconds. Which of the following lifecycle configurations represents the most cost-effective storage strategy for these summaries?

Show answer & explanation

Answer: Keep the transaction summaries in S3 Standard for the entire 45 days45 \text{ days}, then use a lifecycle rule to expire the objects.

Answer

Keep the transaction summaries in S3 Standard for the entire 45 days, then use a lifecycle rule to expire the objects.
Keeping the files in S3 Standard for the entire duration is the most cost-effective solution because the storage duration in the lower tier (15 days) is shorter than the minimum billing threshold of S3 Standard-IA (30 days) and S3 Glacier Instant Retrieval (90 days). The cost of paying the minimum storage duration penalty makes transitioning the objects more expensive than maintaining them in the standard tier.

Step-by-Step Solution

1
Calculate the storage cost of keeping the summaries in S3 Standard for the entire 45 days45 \text{ days}.
The cost is approximately $0.0345\$0.0345 per GB.
S3 Standard charges $0.023\$0.023 per GB-month. For 45 days45 \text{ days}, the prorated storage cost is 45 days×($0.023/30 days)=$0.034545 \text{ days} \times (\$0.023 / 30 \text{ days}) = \$0.0345 per GB.
2
Calculate the storage cost of transitioning the summaries to S3 Standard-IA at day 30 and expiring them at day 45.
The cost is approximately $0.0355\$0.0355 per GB plus transition request fees.
S3 Standard-IA has a minimum storage duration of 30 days30 \text{ days}. Transitioning at day 30 and deleting at day 45 means the objects spend only 15 days15 \text{ days} in S3 Standard-IA but are billed for 30 days30 \text{ days}. The cost is 30 days in S3 Standard (30×$0.023/30=$0.02330 \times \$0.023 / 30 = \$0.023) plus 30 days of S3 Standard-IA (30×$0.0125/30=$0.012530 \times \$0.0125 / 30 = \$0.0125), totaling $0.0355\$0.0355 per GB.
3
Evaluate S3 Glacier options against retrieval time constraints and minimum storage duration rules.
S3 Glacier Flexible Retrieval fails the millisecond query requirement. S3 Glacier Instant Retrieval meets retrieval times but incurs a 90 day90 \text{ day} minimum storage charge, leading to a substantial early deletion penalty.
Glacier Flexible Retrieval requires minutes or hours for retrieval, which does not meet the millisecond requirement. Glacier Instant Retrieval has a minimum storage duration of 90 days90 \text{ days}, so deleting at day 45 forces a 75 day75 \text{ day} early deletion charge (90 days×$0.004/30=$0.012090 \text{ days} \times \$0.004 / 30 = \$0.0120 for storage, bringing total cost to $0.0350\$0.0350 per GB plus high transition request charges).

Key Concept

Minimizing storage costs by understanding minimum storage duration charges and retrieval latency constraints across S3 storage tiers.
Question 717Question

A software provider is deploying a containerized real-time telemetry processing application on Amazon ECS using AWS Fargate. The ingestion microservice receives high-velocity TCP traffic on port 8082, while administrative health and readiness checks are exposed on port 9000. Once ingested, the raw telemetry is streamed to a downstream high-performance computing (HPC) cluster of Amazon EC2 instances located in a single Availability Zone. This HPC cluster runs tightly-coupled Message Passing Interface (MPI) simulations that require sub-millisecond node-to-node network latency and maximum throughput.

Which TWO configuration steps must a solutions architect implement to satisfy the performance and health-monitoring requirements for this architecture?

Select all that apply

Show answer & explanation

Answer: Deploy the EC2 instances within a cluster placement group and utilize instance types that support Elastic Fabric Adapter (EFA).; Configure the Network Load Balancer target group health checks to explicitly target port 9000 instead of the traffic port.

Answer

Deploying the EC2 instances in a cluster placement group with EFA, and configuring the NLB target group health checks to use port 9000.
Deploying instances in a cluster placement group packs instances close together inside an Availability Zone, enabling low-latency, high-throughput network performance. Utilizing EFA enables OS-bypass networking, which is critical for scaling MPI-based HPC applications. Furthermore, since the application health check metrics are exposed on port 9000 rather than the service traffic port (8082), the NLB target group health check port must be explicitly configured to port 9000.

Step-by-Step Solution

1
Analyze the high-performance computing network requirement.
The tightly-coupled MPI application requires sub-millisecond node-to-node network latency and maximum throughput.
This is achieved by deploying EC2 instances in a cluster placement group within a single Availability Zone and utilizing EFA-enabled instance types.
2
Analyze the containerized ingestion service health check requirement.
The application serves ingestion traffic on port 8082 but exposes health checks on port 9000.
To prevent tasks from being incorrectly marked as unhealthy, the NLB target group health check port must be explicitly configured to port 9000 instead of defaulting to the traffic port.

Key Concept

High-Performance Compute Placement and Elastic Load Balancing Health Checks
Question 718Question

A solutions architect is configuring an active-passive disaster recovery strategy in Amazon Route 53. The primary application runs on an Application Load Balancer (ALB), and the backup site is a static website hosted on Amazon S3. Which of the following Route 53 record configurations must the solutions architect create to implement this failover mechanism? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A Failover record pointing to the Application Load Balancer with the Failover Record Type set to Primary and Evaluate Target Health set to Yes; A Failover record pointing to the Amazon S3 bucket website endpoint with the Failover Record Type set to Secondary

Answer

The correct configurations are creating a Failover record pointing to the Application Load Balancer with the Failover Record Type set to Primary and Evaluate Target Health set to Yes, and creating a Failover record pointing to the Amazon S3 bucket website endpoint with the Failover Record Type set to Secondary.
To set up active-passive failover in Route 53, you must create a Primary record using the Failover routing policy pointing to the active resource (the ALB) and enable 'Evaluate Target Health'. You must also create a Secondary record using the Failover routing policy pointing to the standby resource (the S3 bucket website endpoint). When the primary resource is determined to be unhealthy, Route 53 automatically shifts DNS traffic to the secondary resource.

Step-by-Step Solution

1
Define the primary routing policy.
Create a Failover routing policy record for the primary Application Load Balancer (ALB) and set its Failover Record Type to Primary.
This establishes the ALB as the active resource under normal operating conditions.
2
Enable health monitoring on the primary record.
Set Evaluate Target Health to Yes on the primary record.
Route 53 uses this setting to monitor the ALB's health and trigger failover if the ALB becomes unhealthy.
3
Define the backup routing policy.
Create a second Failover routing policy record for the static Amazon S3 website endpoint and set its Failover Record Type to Secondary.
This establishes the static S3 website as the standby resource that Route 53 routes traffic to when the primary ALB is unhealthy.

Key Concept

Route 53 active-passive DNS failover configurations use Failover routing policies with defined Primary and Secondary records, where the Primary record evaluates the target's health to determine when to route traffic to the Secondary record.
Question 719Question

A company hosts a collection of static PDF user guides on an Amazon S3 bucket and distributes them globally using an Amazon CloudFront distribution. The company notices that despite using a Content Delivery Network (CDN), the S3 bucket is experiencing high request volumes, leading to unexpected data transfer costs. An engineer checks the CloudFront configuration and finds that edge locations are always requesting the PDF guides directly from the S3 bucket.

Which configuration issue is causing this behavior?

Show answer & explanation

Answer: The CloudFront distribution's cache behavior has its minimum, maximum, and default Time to Live (TTL) values configured to 00.

Answer

The CloudFront distribution's cache behavior has its minimum, maximum, and default Time to Live (TTL) values configured to 00.
Setting the Time to Live (TTL) values (Minimum TTL, Maximum TTL, and Default TTL) to 00 in the CloudFront cache behavior disables caching. CloudFront will forward every request directly to the origin S3 bucket, resulting in high S3 request volumes and increased data transfer fees.

Step-by-Step Solution

1
Analyze the problem where CloudFront is not caching static files and is sending all requests directly to the Amazon S3 origin.
Identify that the cache hit ratio is 0%0\% and origin requests equal total requests.
This indicates that CloudFront is bypassing the cache entirely for every request.
2
Review the cache settings of the CloudFront distribution's cache behavior.
Find that the TTL (Time to Live) values (minimum, maximum, and default TTL) are all set to 00.
A TTL of 00 explicitly instructs CloudFront to not cache the files at edge locations.

Key Concept

CloudFront TTL configuration for static content delivery
Question 720Question

A solutions architect is designing a highly resilient architecture for a web application. The application's static assets are stored in a primary Amazon S3 bucket in one AWS Region. The architect needs to ensure that the assets remain available even if the primary S3 bucket experiences an outage, by failing over to a backup S3 bucket in a different Region with minimal operational complexity. Which configuration will meet these requirements?

Show answer & explanation

Answer: Create an Amazon CloudFront origin group with the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin.

Answer

Create an Amazon CloudFront origin group with the primary S3 bucket as the primary origin and the backup S3 bucket as the secondary origin.
Creating a CloudFront origin group is the most efficient and native way to configure failover for static assets. By grouping the primary and secondary S3 buckets, CloudFront automatically reroutes incoming requests to the backup bucket when the primary bucket returns error codes indicating an outage.

Step-by-Step Solution

1
Identify the primary goal: Establish automatic failover of static content stored in Amazon S3 to a backup bucket in a different Region with minimal operational complexity.
Realized that a global content delivery network like Amazon CloudFront is the best practice for caching static assets and managing origin failover natively.
CloudFront natively supports origin failover using origin groups, which requires no custom code or complex DNS setups.
2
Configure a CloudFront distribution with two S3 bucket origins.
Created a primary origin pointing to the primary S3 bucket and a secondary origin pointing to the backup S3 bucket.
Both origins must be defined in the distribution configuration before they can be grouped.
3
Group the two origins into a CloudFront origin group.
Established an origin group where the primary S3 bucket is the primary origin, and the backup S3 bucket is the secondary origin, specifying the HTTP status codes that trigger failover.
This setup allows CloudFront to automatically redirect requests to the backup bucket if the primary bucket returns status codes like 500, 502, 503, or 504.

Key Concept

CloudFront Origin Groups and Origin Failover
PreviousPage 36 / 74Next
All practice questions — AWS Certified Solutions Architect - Associate | Examkin