Tüm alıştırma soruları

1462 soru

Tüm türler1,462 Çoktan seçmeli739 Çoklu seçim723

An enterprise retail company wants to deploy a multi-region, active-active database configuration for its online shopping cart application. The database needs to support write operations in both the us-east-1 and us-west-2 Regions with sub-second replication latency. The solution must achieve a Recovery Point Objective (RPO) of under 1 second and a Recovery Time Objective (RTO) of near-zero in the event of a regional outage. The database must automatically handle replication and conflict resolution based on a last-writer-wins rule. Which two actions should a solutions architect take to configure the database to meet these resilience requirements? (Select two.)

Geçerli olan tümünü seçin

Enable Amazon DynamoDB Streams on the primary table in us-east-1 and set the stream view type to NEW_AND_OLD_IMAGES.

Add a replica of the table in us-west-2 to the DynamoDB table configuration to establish a global table.

Set up Amazon Route 53 Latency routing with active-passive failover checks to route database write queries, relying on DNS routing to manage write replication.

Deploy an Amazon RDS for PostgreSQL database in us-east-1 and configure a cross-region read replica in us-west-2, promoting the replica manually during a regional failover.

Configure an Amazon Aurora PostgreSQL Global Database and write a custom AWS Lambda script to execute a manual database failover using a pilot light disaster recovery strategy.

Cevabı ve açıklamayı göster

Cevap: Enable Amazon DynamoDB Streams on the primary table in us-east-1 and set the stream view type to NEW_AND_OLD_IMAGES.; Add a replica of the table in us-west-2 to the DynamoDB table configuration to establish a global table.

Cevap

The correct options are to enable Amazon DynamoDB Streams with the stream view type set to NEW_AND_OLD_IMAGES, and to add a replica of the table in the us-west-2 Region to establish a global table.

To support active-active writes in both us-east-1 and us-west-2 with an RPO of under 1 second and automatic conflict resolution, Amazon DynamoDB Global Tables is the ideal solution. Configuring a global table requires enabling DynamoDB Streams on the source table with the stream view type set to NEW_AND_OLD_IMAGES, and then adding the replica region to create the multi-region configuration.

Adım Adım Çözüm

Enable DynamoDB Streams with NEW_AND_OLD_IMAGES on the existing DynamoDB table in the primary region.

Creates a stream that captures all modifications (insert, update, delete) to the table data, which DynamoDB uses to replicate changes.

DynamoDB Streams is a mandatory prerequisite for setting up DynamoDB Global Tables.

Add the target replica region (us-west-2) to the DynamoDB table configuration.

Creates an identical table in the secondary region and enables bi-directional active-active replication between the regions.

This establishes a DynamoDB Global Table, which natively replicates updates with sub-second latency and automatically handles conflict resolution.

Anahtar Kavram

Amazon DynamoDB Global Tables provides a fully managed, multi-region, active-active database replication solution. To configure it, you must enable DynamoDB Streams with the NEW_AND_OLD_IMAGES view type on the source table and add replica regions to the table configuration.

Soru 442Soru →

A retail analytics company has deployed an application environment on AWS. The environment consists of the following components:

* A set of legacy data ingestion scripts that run continuously (24/7) on Amazon EC2 instances with stable CPU usage.
* A fleet of EC2 instances running a web application that experiences highly unpredictable traffic peaks throughout the day.
* A PostgreSQL database hosted on Amazon RDS that stores transactional data and operates around the clock.

The company wants to optimize compute costs for this environment with minimal administrative effort. Which purchasing strategy will meet these requirements most cost-effectively?

Purchase a Compute Savings Plan to cover the EC2 instances, and purchase Amazon RDS Reserved DB Instances for the PostgreSQL database.

Purchase a single Compute Savings Plan with a commitment level high enough to cover both the EC2 instances and the Amazon RDS PostgreSQL database.

Migrate the continuous 24/7 data ingestion scripts from EC2 to AWS Lambda to eliminate idle compute costs, and use On-Demand EC2 instances for the web application.

Migrate the PostgreSQL database to Amazon DynamoDB configured with Provisioned Capacity Mode to handle the unpredictable transaction peaks, and purchase EC2 Reserved Instances.

Cevabı ve açıklamayı göster

Cevap: Purchase a Compute Savings Plan to cover the EC2 instances, and purchase Amazon RDS Reserved DB Instances for the PostgreSQL database.

Cevap

Purchase a Compute Savings Plan to cover the EC2 instances, and purchase Amazon RDS Reserved DB Instances for the PostgreSQL database.

Purchasing a Compute Savings Plan is the most effective way to cover the EC2 instances since it applies automatically to any instance family, size, or region, accommodating both the stable data ingestion instances and the unpredictable web application instances. Because Amazon RDS is not covered under Compute Savings Plans, purchasing Amazon RDS Reserved DB Instances is the correct and most cost-effective way to reduce the PostgreSQL database's 24/7 running costs.

Adım Adım Çözüm

Analyze compute requirements for EC2 instances.

The EC2 instances include both stable 24/7 workloads and unpredictable spiky web workloads. A Compute Savings Plan is the most flexible choice as it automatically applies discounts to EC2 instance usage regardless of instance family, size, or region.

To ensure maximum flexibility and automated cost savings across diverse and variable EC2 workloads with minimal administrative overhead.

Evaluate the database tier cost optimization options.

The PostgreSQL database on Amazon RDS runs continuously 24/7. Compute Savings Plans do not cover Amazon RDS. Instead, RDS Reserved DB Instances must be purchased to reduce database compute costs.

RDS workloads require database-specific reservation plans since general compute savings plans do not apply to database engines.

Combine the optimized compute and database purchasing strategies.

A combination of Compute Savings Plans for EC2 and Reserved DB Instances for RDS yields the lowest total cost of ownership while keeping administrative effort low.

This aligns the correct discount vehicle with each resource type according to their respective scopes and billing rules.

Anahtar Kavram

Compute Savings Plans vs. Database Reservations

Tahmini Süre:1m 30s

Soru 443Soru →

A company hosts a dynamic web application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to improve the application's performance for global users by caching static content. Additionally, they need to ensure high availability by serving a static maintenance page from an Amazon S3 bucket in the us-west-2 Region if the ALB returns HTTP 502 or 504 errors. The solution must minimize latency for global users, automate the failover process, and minimize operational complexity. Which configuration should a solutions architect implement to meet these requirements?

Configure an Amazon Route 53 latency routing policy with health checks pointing to both the ALB in us-east-1 and the S3 bucket in us-west-2 to distribute traffic and fail over during outages.

Create an Amazon CloudFront distribution with the ALB as the origin. Configure an AWS WAF web ACL with custom rules to inspect response codes and redirect client requests to the S3 bucket when the ALB returns 502 or 504 status codes.

Create an Amazon CloudFront distribution. Configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin. Set the failover criteria to include status codes 502 and 504.

Create an Amazon CloudFront distribution with the ALB as the origin. Configure the Cache Behavior with a Minimum TTL and Default TTL of 0 seconds for all paths, and write a custom Lambda@Edge function to intercept origin response errors and redirect users to the S3 bucket.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution. Configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin. Set the failover criteria to include status codes 502 and 504.

Cevap

The correct answer is to create an Amazon CloudFront distribution and configure an Origin Group containing the ALB as the primary origin and the S3 bucket as the secondary origin, setting the failover criteria to include status codes 502 and 504.

The correct answer is to configure an Amazon CloudFront distribution with an Origin Group. CloudFront Origin Groups allow you to specify a primary origin and a secondary failover origin. When the primary origin returns specific HTTP status codes such as 502 or 504, CloudFront automatically routes traffic to the secondary origin (the S3 bucket) to serve the static maintenance page. This solution provides edge caching to reduce latency globally, implements automatic failover, and has low operational complexity.

Adım Adım Çözüm

Analyze the requirements for edge caching, latency reduction, and automatic failover.

Identify that Amazon CloudFront is the best service to reduce global latency through edge caching, and that failover must handle 502 and 504 error codes from the Application Load Balancer.

CloudFront caches content at edge locations globally, reducing latency, and native failover is required to handle origin errors.

Evaluate native high-availability features of Amazon CloudFront.

Determine that CloudFront Origin Groups allow setting up a primary origin (ALB) and a secondary origin (S3 bucket) with failover criteria for specific HTTP status codes.

Using native CloudFront Origin Groups eliminates the need for complex DNS-level failover or custom Lambda@Edge code, reducing operational complexity.

Select the correct configuration that combines caching and resilient origin failover.

Create an Origin Group with the primary origin pointing to the ALB and the secondary origin pointing to the S3 bucket, configuring failover for 502 and 504 status codes.

This configuration meets the performance requirements by caching content at the edge and satisfies the resiliency requirements by automatically serving a static maintenance page if the ALB is unhealthy.

Anahtar Kavram

Edge caching and resilient origin failover using Amazon CloudFront Origin Groups

Tahmini Süre:2m 0s

Soru 444Soru →

A financial data analysis application runs on Amazon EC2 instances in a private subnet. The application downloads $50\text{ TB}$ of financial market data monthly from an Amazon S3 bucket located in the same AWS Region. Currently, all outbound internet traffic from the private subnet is routed through a NAT Gateway. Which action should a solutions architect take to minimize the data transfer and processing costs most cost-effectively?

Deploy a Gateway VPC Endpoint for Amazon S3 in the VPC and update the private subnet's route table to direct S3 traffic to the endpoint.

Configure an Interface VPC Endpoint for Amazon S3 in the VPC and route all S3 traffic through it.

Keep the existing routing through the NAT Gateway and purchase a Compute Savings Plan to lower the NAT Gateway data processing fees.

Establish an AWS Transit Gateway, attach the VPC, and route the S3 traffic through a NAT Gateway managed by the Transit Gateway.

Cevabı ve açıklamayı göster

Cevap: Deploy a Gateway VPC Endpoint for Amazon S3 in the VPC and update the private subnet's route table to direct S3 traffic to the endpoint.

Cevap

Deploy a Gateway VPC Endpoint for Amazon S3 in the VPC and update the private subnet's route table to direct S3 traffic to the endpoint.

The correct solution is to deploy a Gateway VPC Endpoint for Amazon S3. This endpoint is configured in the VPC route table and routes S3 traffic directly through the AWS internal network. Because Gateway VPC Endpoints do not incur any hourly or data processing charges, this completely eliminates the

0.045 per \text{GB}

NAT Gateway processing fee for the

50\text{ TB}

of S3 traffic.

Adım Adım Çözüm

Analyze the current architecture and identify cost drivers.

The application transfers

50\text{ TB}

of data monthly from Amazon S3 through a NAT Gateway, which charges

0.045 per \text{GB}

for data processing, leading to significant monthly charges.

Before proposing an optimization, the current data transfer path and associated pricing model must be understood.

Evaluate alternative routing mechanisms for Amazon S3.

Amazon S3 supports both Gateway VPC Endpoints and Interface VPC Endpoints. Gateway VPC Endpoints are free of charge, whereas Interface VPC Endpoints cost

0.01 per \text{GB}

plus hourly fees.

Finding the lowest-cost routing path for S3 traffic avoids routing through public gateways.

Select the most cost-effective option and formulate the routing change.

Deploying a Gateway VPC Endpoint for Amazon S3 and updating the route table routes all S3 traffic directly over the AWS internal network for free, reducing the NAT Gateway processing costs to zero.

Updating route tables ensures that only S3 traffic is diverted to the endpoint, while other internet-bound traffic continues using the NAT Gateway.

Anahtar Kavram

Gateway VPC Endpoints for S3 and DynamoDB provide free, secure, private routing within the AWS network, bypassing NAT Gateways and eliminating data processing charges.

Tahmini Süre:1m 30s

Soru 445Soru →

A fintech company is designing a payment transaction system to receive webhooks from a payment gateway. The system must process these transactions in the exact order they are received. The webhook volume is highly unpredictable, experiencing sudden spikes of activity followed by hours of complete silence. The processing logic completes within 1.5 seconds per request. The company wants to minimize idle compute costs.

Which TWO options should a solutions architect recommend to build a cost-effective and compliant architecture? (Select TWO.)

Geçerli olan tümünü seçin

Use Amazon SQS FIFO queues to buffer incoming webhooks and guarantee first-in, first-out processing.

Use AWS Lambda to process messages from the queue, scaling to zero when no webhooks are present.

Use Amazon SQS standard queues to buffer incoming webhooks and ensure strict ordering.

Use an AWS Lambda function configured to run continuously to poll the queue for incoming webhooks.

Use an Amazon DynamoDB table in provisioned capacity mode with high write capacity limits to handle peak bursts.

Cevabı ve açıklamayı göster

Cevap: Use Amazon SQS FIFO queues to buffer incoming webhooks and guarantee first-in, first-out processing.; Use AWS Lambda to process messages from the queue, scaling to zero when no webhooks are present.

Cevap

Use Amazon SQS FIFO queues to buffer incoming webhooks and guarantee first-in, first-out processing, and use AWS Lambda to process messages from the queue, scaling to zero when no webhooks are present.

Using Amazon SQS FIFO queues ensures that webhook messages are delivered and processed in the exact order they are received. Coupling this queue with AWS Lambda to process messages on an event-driven basis allows the system to scale down to zero when no transactions are occurring, which eliminates idle compute costs.

Adım Adım Çözüm

Evaluate the ordering requirements for payment transactions.

Identify that strict ordering is required, ruling out standard message queues.

Payment transactions must be processed sequentially to prevent data corruption or incorrect balances.

Determine the compute strategy that minimizes idle costs for highly sporadic workloads.

Identify that AWS Lambda is the ideal compute option.

Since the logic runs for less than 1.5 seconds and volume scales down to zero for hours, AWS Lambda ensures no compute costs are incurred when idle.

Choose the correct queuing and scaling services that satisfy both requirements.

Combine Amazon SQS FIFO queues with event-driven AWS Lambda triggers.

SQS FIFO guarantees message order, and Lambda scales automatically based on SQS queue depth, minimizing idle resource costs.

Anahtar Kavram

Serverless architectures minimize idle compute costs by scaling resources down to zero during inactive periods, while FIFO queues guarantee message sequencing.

Soru 446Soru →

A company hosts a content-heavy financial news website on AWS using an Application Load Balancer (ALB) and an Auto Scaling group of Amazon EC2 instances as the origin. To reduce latency for its global audience, the company configured an Amazon CloudFront distribution. However, during peak traffic, the EC2 instances experience high CPU utilization due to a massive volume of requests for static images and stylesheets, causing slow page loads. A solutions architect reviews the CloudFront configuration and finds that the cache behavior for static assets has the Minimum TTL, Default TTL, and Maximum TTL all set to 0. Which configuration change should the solutions architect implement to resolve the performance issue on the origin EC2 instances?

Keep the TTL values at 0 in CloudFront to ensure content freshness, but enable CloudFront Origin Shield to cache the static assets at a centralized regional layer.

Migrate the static assets to an Amazon Elastic File System (EFS) volume mounted on all EC2 instances, and configure Provisioned Throughput to handle the high IOPS demands, while leaving the CloudFront TTL settings at 0.

Modify the static assets cache behavior to set the Minimum, Default, and Maximum TTLs to non-zero values, allowing CloudFront to serve the static content from edge caches without forwarding validation requests to the ALB.

Move the static assets to an Amazon S3 bucket, and route all data transfer from the EC2 instances to the S3 bucket through a NAT Gateway to ensure low-latency delivery to CloudFront, while keeping the CloudFront TTL settings at 0.

Cevabı ve açıklamayı göster

Cevap: Modify the static assets cache behavior to set the Minimum, Default, and Maximum TTLs to non-zero values, allowing CloudFront to serve the static content from edge caches without forwarding validation requests to the ALB.

Cevap

Modifying the cache behavior for static assets to use non-zero TTL values allows Amazon CloudFront to cache static files at edge locations. Once cached, subsequent requests from users are served directly from the edge cache, eliminating the need to forward validation requests to the origin Application Load Balancer and significantly reducing origin CPU utilization.

Adım Adım Çözüm

Identify the cause of origin CPU spikes and slow page load times.

The CloudFront cache behavior for static assets has Minimum, Default, and Maximum TTLs all set to 0.

A TTL of 0 prevents CloudFront from caching content at edge locations, forcing it to forward every request to the origin for validation, which overloads the ALB and EC2 instances.

Determine the correct caching configuration for static content.

Change the TTL settings in the cache behavior for static assets to non-zero values (e.g., Default TTL = 86400).

This allows CloudFront to cache the static assets at edge locations and serve them directly to clients, preventing requests from hitting the origin servers.

Evaluate and rule out sub-optimal solutions such as adding EFS provisioned throughput or routing through NAT Gateways.

Alternative solutions either do not resolve the lack of caching at the edge or introduce unnecessary costs and architectural complexity.

Caching at the edge is the standard best practice for optimizing static asset delivery and reducing origin load.

Anahtar Kavram

Configuring CloudFront TTL values to enable effective edge caching and reduce origin request load.

Tahmini Süre:1m 30s

Soru 447Soru →

An enterprise healthcare organization is designing a highly resilient storage and database architecture for its Picture Archiving and Communication System (PACS) imaging application. The system consists of a metadata catalog stored in Amazon RDS for PostgreSQL and raw DICOM medical images stored as objects. The disaster recovery (DR) strategy requires a Recovery Time Objective (RTO) of $15$ minutes and a Recovery Point Objective (RPO) of $15$ minutes across a secondary AWS Region. The primary region deployment must be highly available with $99.99\%$ availability and $99.999999999\%$ durability for the raw images. Additionally, radiologists at local clinics require low-latency local access to the most recently acquired medical images. Which architecture meets these requirements with the lowest operational overhead?

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure an S3 Lifecycle policy to transition objects immediately to the S3 Glacier Flexible Retrieval storage class in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 CRR with S3 RTC enabled to the secondary region. Implement a Pilot Light disaster recovery strategy in the secondary region by using AWS Backup to copy database backups across regions, restoring the RDS PostgreSQL database from these backups only after a regional disaster is declared.

Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 CRR with S3 RTC enabled to the secondary region. Deploy the RDS PostgreSQL database in a Single-AZ configuration in the primary region, and set up a cross-region read replica in the secondary region with Route 53 configured to automatically route write traffic directly to the replica if the primary instance fails.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon S3 File Gateway at local clinics to cache the most recent images. Store raw images in an Amazon S3 bucket in the primary region, and configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled to a destination bucket in the secondary region. Deploy the RDS PostgreSQL database in a Multi-AZ configuration in the primary region, and configure a cross-region read replica in the secondary region.

Cevap

Deploy an Amazon S3 File Gateway at the local clinics, store raw images in Amazon S3 in the primary region with S3 Cross-Region Replication (CRR) and S3 Replication Time Control (S3 RTC) enabled to the secondary region, and deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration in the primary region with a cross-region read replica in the secondary region.

The correct architecture uses Amazon S3 File Gateway to cache images locally for radiologists, satisfying the low-latency local access requirement. Amazon S3 Standard provides

99.99\%

availability and

99.999999999\%

durability. To meet the

15

-minute RPO and RTO for the objects, S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) is used, which guarantees that

99.9\%

of objects replicate within

15

minutes. For the database, RDS Multi-AZ provides high availability within the primary region, and a cross-region read replica provides continuous replication to the secondary region, allowing manual promotion within the

15

-minute RTO during a disaster.

Adım Adım Çözüm

Address the local access requirement by placing an Amazon S3 File Gateway on-premises at the local clinics to cache recently accessed DICOM images.

Radiologists receive low-latency local access to the most recently generated images.

S3 File Gateway provides a local cache for file-based access to objects stored directly in Amazon S3.

Address S3 data replication durability and RPO requirements by enabling S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC).

S3 objects are replicated to the secondary region with a SLA-backed

15

-minute replication time, meeting the

15

-minute RPO.

S3 RTC ensures

99.9\%

of objects are replicated within

15

minutes and provides CloudWatch metrics to monitor replication lag.

Address database high availability and disaster recovery requirements by configuring Amazon RDS for PostgreSQL in a Multi-AZ deployment in the primary region and setting up a cross-region read replica in the secondary region.

Synchronous replication across AZs provides local high availability, and asynchronous replication to the secondary region read replica satisfies the cross-region DR RPO.

Multi-AZ configuration handles local zone failures automatically, while the cross-region read replica allows quick manual promotion within the

15

-minute RTO during a regional disaster.

Anahtar Kavram

Designing highly resilient hybrid storage and database architectures using S3 Replication Time Control (RTC) and RDS cross-region replication to satisfy strict RTO and RPO objectives.

Tahmini Süre:2m 30s

Soru 448Soru →

A global financial technology enterprise is migrating its transaction auditing system to AWS. The system must run across two AWS Regions: us-east-1 as the primary region and us-west-2 as the disaster recovery region. The database layer must support high-performance local read operations in both regions while routing all write operations to us-east-1. The disaster recovery requirements dictate a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Which database configuration best meets these requirements with the least operational complexity?

Configure an Amazon RDS for PostgreSQL DB instance in us-east-1 with a cross-region read replica in us-west-2, and configure Amazon Route 53 to automatically promote the replica to primary if the primary region fails.

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Provision an Amazon RDS for PostgreSQL Multi-AZ DB instance in us-east-1 and a stopped pilot light DB instance in us-west-2, automating the startup and transaction log restoration from Amazon S3 upon failover.

Set up Amazon RDS for PostgreSQL Multi-AZ deployments in both us-east-1 and us-west-2, and use Amazon Route 53 latency-based routing with active health checks to synchronize write transactions across both regions.

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Cevap

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.

Deploying an Amazon Aurora PostgreSQL Global Database is the most resilient design for these requirements. It replicates data across regions at the storage tier using physical replication, keeping replica lag under 1 second to meet the RPO requirement. In a failover scenario, the secondary cluster can be promoted to primary in under 1 minute to meet the RTO requirement, while natively supporting high-performance local reads in both regions.

Adım Adım Çözüm

Analyze RPO, RTO, and multi-region read/write requirements.

Identify that the system needs storage-level cross-region replication with lag under 1 second and regional recovery orchestration under 1 minute.

Narrow down database architectures to those capable of meeting the strict high-availability and disaster recovery thresholds.

Evaluate the replication mechanics of Amazon Aurora Global Databases.

Confirm that Aurora physical replication operates at the storage layer with typical lag of less than 1 second (satisfying the RPO) and can be promoted to primary in under 1 minute (satisfying the RTO).

Ensure the selected configuration natively aligns with the target metrics.

Assess and eliminate alternative configurations that introduce lag, manual steps, or incorrect routing.

Identify that RDS read replica promotion is manual, pilot light startup is too slow, and Route 53 cannot replicate transactional writes.

Eliminate distractors that fail to meet either the performance or recovery requirements.

Anahtar Kavram

Using Amazon Aurora Global Databases to achieve multi-region read scaling, sub-second RPO storage-level replication, and sub-minute RTO failover capabilities.

Tahmini Süre:2m 30s

Soru 449Soru →

A financial services firm hosts a global portfolio analytics application on AWS. The application consists of a dynamic transaction API hosted on Application Load Balancers (ALBs) in two AWS Regions: eu-west-1 (primary) and ap-southeast-1 (standby). Additionally, the application generates static PDF reports that are stored in Amazon S3 buckets in both regions. The firm requires a resilient routing and edge caching strategy that minimizes latency for global users, guarantees automatic failover to the standby region for both dynamic APIs and static reports, and keeps operational overhead to a minimum.

Which TWO actions should a solutions architect take to meet these requirements?

Geçerli olan tümünü seçin

Configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin. Create a cache behavior for /reports/* that routes requests to this Origin Group.

Configure a CloudFront Origin Group with the primary ALB as the primary origin and the secondary ALB as the failover origin. Create a default cache behavior (*) routing to this Origin Group, and attach the Managed-CachingDisabled cache policy.

Configure Route 53 Latency Routing to route dynamic traffic directly to the two regional ALBs, bypassing CloudFront to ensure the lowest latency and automatic DNS failover for APIs without edge network routing.

Attach an AWS WAF Web ACL to the CloudFront distribution and configure a custom rule that intercepts 502 Bad Gateway responses from the primary ALB to redirect the request to the secondary ALB.

Create a single CloudFront cache behavior for all paths (*) pointing to a combined ALB and S3 origin, and set the default, minimum, and maximum Time to Live (TTL) values to zero to guarantee dynamic requests are not cached.

Cevabı ve açıklamayı göster

Cevap: Configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin. Create a cache behavior for /reports/* that routes requests to this Origin Group.; Configure a CloudFront Origin Group with the primary ALB as the primary origin and the secondary ALB as the failover origin. Create a default cache behavior (*) routing to this Origin Group, and attach the Managed-CachingDisabled cache policy.

Cevap

To meet the requirements, the solutions architect should configure a CloudFront Origin Group with the primary S3 bucket as the primary origin and the secondary S3 bucket as the failover origin with a cache behavior for static reports, and configure a separate CloudFront Origin Group for the ALB origins with a default cache behavior using a disabled caching policy.

The correct implementation requires establishing separate CloudFront Origin Groups for S3 and ALB endpoints. For the static reports path, a dedicated cache behavior directs traffic to the S3 Origin Group, ensuring low-latency delivery of cached reports and automatic standby-bucket failover. For the dynamic transaction path, a default cache behavior points to the ALB Origin Group with the Managed-CachingDisabled policy. This ensures transaction requests bypass the edge cache but benefit from edge routing failover and optimized network pathing.

Adım Adım Çözüm

Separate the static assets (/reports/*) from the dynamic transactions (*) in the CloudFront cache behavior settings.

Two distinct paths are configured to handle caching properties independently.

Static content should be cached at edge locations to minimize latency, while dynamic content must bypass the cache to ensure real-time query results.

Group the primary and standby S3 buckets into a CloudFront Origin Group.

High availability is configured for the static assets layer at the edge.

If the primary S3 bucket fails, CloudFront automatically routes requests to the failover bucket in the standby region.

Group the primary and standby ALBs into a second CloudFront Origin Group.

Edge-level failover is configured for the dynamic application layer.

This guarantees dynamic API requests failover automatically with minimal delay, leveraging the AWS global network for optimized latency.

Apply a CachingDisabled policy to the default cache behavior routing to the ALB Origin Group.

Dynamic content bypasses edge caching while maintaining routing resilience.

This prevents transactional payloads from being cached while still using CloudFront's persistent connections and Origin Group failover capabilities.

Anahtar Kavram

CloudFront Origin Groups and Path-Based Caching Profiles

Tahmini Süre:2m 0s

Soru 450Soru →

A media streaming company is designing a high-performing data ingestion and transformation pipeline to process user clickstream events from their mobile application. During live events, clickstream traffic experiences sudden, unpredictable spikes up to $8,000$ events per second, with an average event size of $1.5\text{ KB}$ . The processed data must be stored in Amazon S3 in Apache Parquet format for downstream analytics. The company wants to minimize administrative overhead and ensure that the pipeline scales automatically without manual intervention.

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

Geçerli olan tümünü seçin

Use Amazon Kinesis Data Streams in On-Demand capacity mode to ingest the clickstream events from the mobile application.

Configure Amazon Data Firehose with the Kinesis Data Stream as the source, and enable format conversion to Apache Parquet using an AWS Glue schema before delivering the data to Amazon S3.

Use Amazon Kinesis Data Streams in Provisioned capacity mode with 5 shards to ingest the incoming clickstream data.

Ingest the clickstream events using an Amazon SQS standard queue and deploy a fleet of Amazon EC2 instances to consume, order, and transform the events.

Configure Amazon Data Firehose to ingest data directly from the application and use a custom AWS Lambda function to perform the conversion to Apache Parquet.

Cevabı ve açıklamayı göster

Cevap: Use Amazon Kinesis Data Streams in On-Demand capacity mode to ingest the clickstream events from the mobile application.; Configure Amazon Data Firehose with the Kinesis Data Stream as the source, and enable format conversion to Apache Parquet using an AWS Glue schema before delivering the data to Amazon S3.

Cevap

The solutions architect should recommend ingesting the clickstream events using Amazon Kinesis Data Streams in On-Demand capacity mode, and then using Amazon Data Firehose with AWS Glue schema integration to convert the incoming JSON data to Apache Parquet format before delivering it to Amazon S3.

The correct solution uses Amazon Kinesis Data Streams in On-Demand capacity mode to ingest clickstream traffic, which automatically scales up to

200\text{ MB/sec}

to accommodate the calculated

12\text{ MB/sec}

peak traffic without manual shard calculations. It then uses Amazon Data Firehose with AWS Glue schema integration to natively transform the incoming JSON clickstream data into Apache Parquet format before writing it to Amazon S3. This architecture meets the requirements of auto-scaling, low administrative overhead, and high-performance ingestion and transformation.

Adım Adım Çözüm

Calculate the peak throughput requirement for the ingestion layer.

Multiply

8,000\text{ events/sec}

1.5\text{ KB/event}

to get

12,000\text{ KB/sec}

, which is equivalent to

12\text{ MB/sec}

of write throughput.

This establishes the minimum ingestion capacity that the solution must handle during peak traffic spikes.

Compare scaling options for the Kinesis ingestion layer.

Kinesis Data Streams in On-Demand mode automatically scales to handle up to

200\text{ MB/sec}

write throughput. A provisioned capacity stream with 5 shards only handles up to

5\text{ MB/sec}

Choosing On-Demand capacity mode ensures that the system handles unpredictable traffic spikes automatically without administrative overhead or throttling.

Identify the low-overhead conversion mechanism from JSON to Parquet.

Amazon Data Firehose can pull from the Kinesis Data Stream and convert JSON data to Parquet using an AWS Glue schema before writing to Amazon S3.

This avoids writing custom application code (such as in Lambda or on EC2) and minimizes administrative overhead.

Anahtar Kavram

High-performing data ingestion and serverless transformation using Kinesis Data Streams On-Demand capacity mode combined with Amazon Data Firehose and AWS Glue schema conversion.

Soru 451Soru →

A financial services company is launching a global trading dashboard. The application consists of dynamic JSON APIs hosted on Amazon ECS containers behind an Application Load Balancer (ALB) in the us-east-1 Region, and static web assets stored in an Amazon S3 bucket in the same Region. For disaster recovery and high availability, the company has deployed a replica of the ECS application and a replicated S3 bucket in the us-west-2 Region. The company wants to minimize latency for global users and ensure that both static and dynamic requests automatically fail over to the secondary Region with minimal downtime if the primary Region becomes unavailable.

Which combination of actions should a solutions architect take to meet these requirements? (Select two.)

Geçerli olan tümünü seçin

Configure an Amazon CloudFront distribution with two origin groups: one containing the primary and secondary S3 buckets, and another containing the primary and secondary ALBs, with failover criteria set for 5xx status codes.

Create two cache behaviors in the CloudFront distribution: one for static paths routing to the S3 origin group with caching enabled, and another for dynamic API paths routing to the ALB origin group with caching disabled (TTL set to 0).

Configure Amazon Route 53 latency-based routing policies pointing directly to the ALBs in both regions, and enable Route 53 health checks to route dynamic API requests during a regional outage.

Deploy AWS Global Accelerator to route dynamic API traffic to the ALB endpoints, and configure Route 53 with failover routing to switch CloudFront static traffic to the backup S3 bucket.

Create a single CloudFront origin group that combines both the primary ALB and the primary S3 bucket, and configure an AWS WAF rule to redirect traffic to the secondary Region.

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon CloudFront distribution with two origin groups: one containing the primary and secondary S3 buckets, and another containing the primary and secondary ALBs, with failover criteria set for 5xx status codes.; Create two cache behaviors in the CloudFront distribution: one for static paths routing to the S3 origin group with caching enabled, and another for dynamic API paths routing to the ALB origin group with caching disabled (TTL set to 0).

Cevap

The correct configurations are to set up an Amazon CloudFront distribution with two distinct origin groups (one for S3 buckets and one for Application Load Balancers) and configure two cache behaviors to route static traffic with caching enabled and dynamic API traffic with caching disabled (TTL set to 0) to their respective origin groups.

To achieve both sub-second global latency and high availability with fast failover, the solutions architect should use Amazon CloudFront with origin groups. By configuring separate origin groups for S3 and ALB origins, CloudFront can monitor the primary origin and instantly switch to the secondary origin if a 5xx error status code is returned. Creating separate cache behaviors ensures that static content is cached for performance, while dynamic API calls bypass caching (using a TTL of 0) but still benefit from edge optimizations and origin-level failover.

Adım Adım Çözüm

Analyze the requirements for latency minimization and regional failover for both static and dynamic contents.

Identify that CloudFront is required to minimize latency globally and that both static (S3) and dynamic (ALB) resources exist in two regions (primary us-east-1 and secondary us-west-2).

This establishes the scope of the solution which must handle two distinct traffic types and regional disaster recovery.

Select the appropriate failover mechanism at the edge layer.

Create two CloudFront origin groups (one for the S3 buckets and one for the ALBs) with us-east-1 as the primary origin and us-west-2 as the failover origin based on 5xx status codes.

CloudFront origin groups provide rapid, CDN-level failover without relying on DNS TTL propagation, meeting the minimal downtime requirement.

Configure caching behaviors for the static and dynamic paths.

Create a static cache behavior pointing to the S3 origin group with caching enabled, and a dynamic cache behavior pointing to the ALB origin group with TTL set to 0 to bypass caching.

This optimizes delivery by caching static assets at edge locations while ensuring dynamic API requests are always forwarded to the backend containers.

Anahtar Kavram

Amazon CloudFront Origin Groups and Cache Behaviors

Soru 452Soru →

An autonomous vehicle research company stores two telemetry datasets in a single Amazon S3 bucket:
- LiDAR Point Cloud Blocks: Average file size of $180\text{ MB}$ . These files are analyzed intensively for $14\text{ days}$ after upload. They must be preserved for compliance audits and can be deleted exactly $45\text{ days}$ after upload.
- CAN Bus Sensor Logs: Average file size of $3\text{ KB}$ . These files are queried sporadically for the first $10\text{ days}$ and must be retained indefinitely for long-term machine learning training.

Which combination of actions will result in the most cost-effective storage architecture that meets the retention requirements? (Select two.)

Geçerli olan tümünü seçin

Configure an S3 Lifecycle rule for the LiDAR Point Cloud Blocks to transition objects to S3 Standard-Infrequent Access (S3 Standard-IA) after

14\text{ days}

, and expire them after

45\text{ days}

Configure an S3 Lifecycle rule for the LiDAR Point Cloud Blocks to transition objects to S3 Glacier Instant Retrieval after

14\text{ days}

, and expire them after

45\text{ days}

Configure an S3 Lifecycle rule for the CAN Bus Sensor Logs that filters on object size (using ObjectSizeGreaterThan set to

128\text{ KB}

) to transition logs to S3 Standard-IA after

10\text{ days}

, leaving smaller logs in S3 Standard.

Configure an S3 Lifecycle rule for the CAN Bus Sensor Logs to transition all logs to S3 Standard-IA after

10\text{ days}

to lower active storage costs.

Configure an S3 Lifecycle rule for the CAN Bus Sensor Logs to transition all logs to S3 Intelligent-Tiering after

10\text{ days}

to automatically tier them to Archive Instant Access after

90\text{ days}

Cevabı ve açıklamayı göster

Cevap: Configure an S3 Lifecycle rule for the LiDAR Point Cloud Blocks to transition objects to S3 Standard-Infrequent Access (S3 Standard-IA) after $14\text{ days}$ , and expire them after $45\text{ days}$ .; Configure an S3 Lifecycle rule for the CAN Bus Sensor Logs that filters on object size (using ObjectSizeGreaterThan set to $128\text{ KB}$ ) to transition logs to S3 Standard-IA after $10\text{ days}$ , leaving smaller logs in S3 Standard.

Cevap

Configure an S3 Lifecycle rule to transition the large LiDAR files to S3 Standard-IA after

14\text{ days}

and expire them at

45\text{ days}

, and configure a separate S3 Lifecycle rule for the CAN Bus logs filtering by object size (greater than

128\text{ KB}

) before transitioning them to S3 Standard-IA after

10\text{ days}

Transitioning the LiDAR files to S3 Standard-IA after

14\text{ days}

and expiring them at day

45

results in a

31\text{-day}

storage period in the IA tier. Since S3 Standard-IA has a minimum storage duration of

30\text{ days}

, no early deletion penalty is applied. The large size of the LiDAR files (

180\text{ MB}

) also makes them ideal for S3 Standard-IA. For the small CAN Bus logs (

3\text{ KB}

), S3 Standard-IA's minimum billing size of

128\text{ KB}

makes direct transitions cost-ineffective. Filtering transitions to only affect objects larger than

128\text{ KB}

avoids this storage charge penalty.

Adım Adım Çözüm

Calculate the active storage duration in the transition tier for the LiDAR dataset.

The files spend

31\text{ days}

in the target Infrequent Access tier (

45\text{ days}

total retention minus

14\text{ days}

in S3 Standard).

This determines if the transition triggers early deletion charges in the target storage tier.

Verify target tier minimum duration constraints against the calculated storage duration.

S3 Standard-IA has a

30\text{ day}

minimum storage duration (

31 \geq 30

is valid with no penalty), whereas S3 Glacier Instant Retrieval has a

90\text{ day}

minimum (

31 < 90

incurs a pro-rated

59\text{ day}

penalty).

This step identifies the most cost-effective storage tier that aligns with the deletion window.

Evaluate the average file size of the CAN Bus Sensor Logs (

3\text{ KB}

) against minimum billing sizes.

S3 Standard-IA charges a minimum of

128\text{ KB}

per object, making a

3\text{ KB}

file transition highly cost-ineffective due to the

42.6\times

size overhead billing penalty.

This analysis prevents unintended cost inflation when tiering small files.

Select the S3 Lifecycle rule filters that selectively transition objects based on size criteria.

Apply an `ObjectSizeGreaterThan` filter set to

128\text{ KB}

to exclude small telemetry logs from transitioning, keeping them in S3 Standard.

This ensures only cost-effective objects are transitioned to the standard-IA tier.

Anahtar Kavram

Applying storage tiering lifecycle policies while accounting for minimum storage durations, early deletion penalties, and minimum object size billing constraints in Amazon S3.

Soru 453Soru →

A company is building a big data analytics solution that ingests large, multi-gigabyte datasets from various global research partners. The files are uploaded to an Amazon S3 bucket. The data transfer speed is currently slow and inconsistent due to high latency and network congestion over long geographic distances.

Which combination of solutions should a solutions architect implement to maximize the upload performance of these large files? (Choose two.)

Geçerli olan tümünü seçin

Use Amazon S3 Transfer Acceleration to leverage the AWS edge network for global uploads.

Use S3 Multipart Upload to upload the large files in parallel and parallelize the data transfer.

Provision an Amazon EFS file system with Provisioned Throughput to act as an ingestion staging area.

Configure S3 Lifecycle policies to immediately transition incoming data to S3 Standard-Infrequent Access (S3 Standard-IA).

Attach Amazon EBS gp3 volumes with Multi-Attach enabled to the source servers to increase local throughput.

Cevabı ve açıklamayı göster

Cevap: Use Amazon S3 Transfer Acceleration to leverage the AWS edge network for global uploads.; Use S3 Multipart Upload to upload the large files in parallel and parallelize the data transfer.

Cevap

Use Amazon S3 Transfer Acceleration to leverage the AWS edge network for global uploads, and use S3 Multipart Upload to upload the large files in parallel and parallelize the data transfer.

To maximize upload performance of large files from global locations, the solution requires optimizing the network path and parallelizing the upload process. The option recommending Amazon S3 Transfer Acceleration addresses network latency by routing uploads through AWS Edge Locations over the AWS internal network instead of the public internet. The option recommending S3 Multipart Upload allows the source clients to split large files and upload the parts in parallel, which optimizes network throughput and resilience.

Adım Adım Çözüm

Analyze the workload requirements and identify bottlenecks.

The requirements are: ingesting large multi-gigabyte files from geographically distributed global partners into Amazon S3 with slow, inconsistent internet speeds.

Understanding the core bottleneck (geographic distance and network latency for large file transfers) helps eliminate local storage configurations that do not address WAN performance.

Evaluate solutions designed to optimize wide area network (WAN) data transfer to Amazon S3.

Amazon S3 Transfer Acceleration is identified as the native AWS solution to route traffic through the nearest AWS edge location and over the optimized AWS global backbone network.

This directly reduces latency and routing hops across the internet for global users.

Evaluate S3 capabilities for handling large files to improve throughput and fault tolerance.

S3 Multipart Upload is identified as the native S3 feature designed to upload large files in parallel parts.

By splitting files into parts, network bandwidth is maximized via parallel uploads, and network failures are mitigated since only failed parts need to be re-uploaded.

Anahtar Kavram

High-performing S3 data ingestion involves combining network routing optimization (S3 Transfer Acceleration) and object upload parallelization (S3 Multipart Upload).

Soru 454Soru →

A financial technology company is launching a new ledger application that records transactions for millions of active accounts. The application requires a database tier that can handle a sustained write volume of $25,000$ transactions per second with a write latency of less than $10$ milliseconds. Additionally, the application must support read queries of account balances with a latency of less than $1$ millisecond for hot accounts during peak hours. The database must scale automatically to handle sudden spikes in traffic. Which of the following database design and caching configurations should a solutions architect implement to meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Design the Amazon DynamoDB table using a high-cardinality attribute, such as `AccountID`, as the partition key to distribute write requests evenly across partitions.

Deploy an Amazon DynamoDB Accelerator (DAX) cluster to cache read requests for hot accounts, reducing read response times to microseconds.

Design the Amazon DynamoDB table using `TransactionDate` as the partition key to store and query transactions chronologically.

Provision an Amazon RDS for PostgreSQL DB instance with a Multi-AZ deployment, and configure a Read Replica to serve as the primary automated failover target during database outages.

Configure the DynamoDB table with Provisioned Capacity Mode using fixed Write Capacity Units (WCUs) and Read Capacity Units (RCUs) calibrated for average load to minimize cost during traffic spikes.

Cevabı ve açıklamayı göster

Cevap: Design the Amazon DynamoDB table using a high-cardinality attribute, such as `AccountID`, as the partition key to distribute write requests evenly across partitions.; Deploy an Amazon DynamoDB Accelerator (DAX) cluster to cache read requests for hot accounts, reducing read response times to microseconds.

Cevap

To meet the requirements, the database must be designed with a high-cardinality partition key like the account identifier in Amazon DynamoDB to distribute writes, and a DynamoDB Accelerator (DAX) cluster must be deployed to provide microsecond read latency for hot accounts.

Designing the DynamoDB table with a high-cardinality partition key ensures writes are distributed evenly, avoiding partition bottlenecks. Deploying a DynamoDB Accelerator (DAX) cluster addresses the microsecond read latency requirement for hot accounts by serving read queries directly from an in-memory cache.

Adım Adım Çözüm

Analyze the write throughput and scalability requirements.

A sustained write load of

25,000

transactions per second requires a horizontally scalable database. Amazon DynamoDB can handle this workload, provided that data is distributed evenly.

Avoiding hot partitions is critical to preventing write throttling in DynamoDB.

Choose the optimal partition key for the DynamoDB table.

Selecting a high-cardinality attribute like the account identifier ensures write requests are evenly spread across multiple physical partitions.

Monotonically increasing keys or low-cardinality keys like dates will concentrate writes on a single partition, causing write bottlenecks.

Address the microsecond read latency requirement for hot accounts.

Deploy Amazon DynamoDB Accelerator (DAX) as an in-memory cache in front of the DynamoDB table.

DAX reduces read latency from single-digit milliseconds to microseconds, offloading read requests from the DynamoDB table for hot keys.

Anahtar Kavram

Scaling database write throughput via partition key design in Amazon DynamoDB and optimizing read latency for hot keys using DynamoDB Accelerator (DAX).

Soru 455Soru →

A meteorological modeling company runs daily simulations that generate two types of output files stored in an Amazon S3 bucket:

* Raw simulation data: Files average $1.5\text{ GB}$ in size.
* Summary reports: Files average $20\text{ KB}$ in size.

Both file types are accessed frequently by the simulation team during the first $10\text{ days}$ following creation. After $10\text{ days}$ , the files are rarely accessed. All files must be retained for a total of $25\text{ days}$ and can be deleted thereafter.

Which S3 lifecycle configuration is the most cost-effective for this scenario?

Configure a lifecycle rule to transition the raw simulation data to S3 Standard-IA after 10 days, and expire all files after 25 days.

Configure a lifecycle rule to expire all files after 25 days, keeping them in S3 Standard for their entire lifecycle.

Configure a single lifecycle rule to transition all files in the bucket to S3 Standard-IA after 10 days, and expire all files after 25 days.

Configure a lifecycle rule to transition the raw simulation data to S3 Glacier Instant Retrieval after 10 days, and expire all files after 25 days.

Cevabı ve açıklamayı göster

Cevap: Configure a lifecycle rule to expire all files after 25 days, keeping them in S3 Standard for their entire lifecycle.

Cevap

Configure a lifecycle rule to expire all files after 25 days, keeping them in S3 Standard for their entire lifecycle.

The correct option is to keep all files in S3 Standard and expire them after 25 days. Because the files are deleted after 25 days and transitioned after 10 days, they would only spend 15 days in the target storage class. S3 Standard-IA has a minimum storage duration of 30 days, meaning an early deletion fee for the remaining 15 days is applied. For the raw simulation data (

1.5\text{ GB}

), the combined cost of 10 days in S3 Standard and 30 days in S3 Standard-IA is higher than keeping them in S3 Standard for the full 25 days. Additionally, the

20\text{ KB}

summary reports are below the

128\text{ KB}

minimum billable size for S3 Standard-IA, which would result in paying for

128\text{ KB}

of storage per file.

Adım Adım Çözüm

Analyze the file sizes, access patterns, and retention requirements.

The files consist of large raw simulation data (

1.5\text{ GB}

) and small summary reports (

20\text{ KB}

). They are accessed for

10\text{ days}

and must be deleted after

25\text{ days}

, meaning they would spend at most

15\text{ days}

in any transitioned storage tier.

Understanding the actual residency time in any lower storage tier is critical to assessing whether transition penalties will apply.

Calculate the S3 Standard-IA storage cost compared to S3 Standard.

For the raw simulation data (

1.5\text{ GB}

), S3 Standard-IA has a minimum storage duration of

30\text{ days}

. Deleting the files after

15\text{ days}

in S3 Standard-IA results in paying for

30\text{ days}

of storage. The cost of

10\text{ days}

in S3 Standard +

30\text{ days}

in S3 Standard-IA is higher than keeping the files in S3 Standard for the entire

25\text{ days}

S3 Standard-IA has a 30-day minimum storage duration, and violating it leads to early deletion charges.

Evaluate the impact of minimum billable object size on the summary reports.

The summary reports are

20\text{ KB}

in size. The minimum billable object size for S3 Standard-IA is

128\text{ KB}

. Transitioning these files to S3 Standard-IA would result in paying for

128\text{ KB}

of storage per file, which is significantly more expensive than keeping them in S3 Standard.

S3 Standard-IA is not cost-effective for files smaller than

128\text{ KB}

due to the minimum object size billing threshold.

Evaluate the S3 Glacier Instant Retrieval option.

S3 Glacier Instant Retrieval has a minimum storage duration of

90\text{ days}

. Storing files there for

15\text{ days}

and deleting them incurs a

75\text{ day}

early deletion penalty, which is highly cost-inefficient.

Glacier tiers are designed for long-term archiving and carry severe cost penalties for short retention periods.

Anahtar Kavram

Understanding S3 lifecycle transitions, minimum storage durations, and minimum object size limits to optimize costs.

Soru 456Soru →

A digital security company stores video surveillance feeds and operational device telemetry logs in an Amazon S3 bucket.

* Video feeds: The files average $500\text{ MB}$ in size. They are accessed frequently during the first 15 days for automated threat detection. After 15 days, they are accessed only if a security incident is reported, which is rare. They must be retained for 60 days total for compliance, after which they can be permanently deleted.
* Device telemetry logs: The files average $15\text{ KB}$ in size. They are accessed frequently for the first 10 days for system health checks. After 10 days, access drops significantly, but they must be kept for 35 days total for operational troubleshooting before deletion.

Which two actions should a solutions architect configure in the S3 Lifecycle policy to meet these requirements in the most cost-effective manner?

Geçerli olan tümünü seçin

For the video feeds, configure a transition rule to move the objects to S3 Standard-Infrequent Access (S3 Standard-IA) after 15 days.

For the device telemetry logs, configure a transition rule to move the objects to S3 Standard-Infrequent Access (S3 Standard-IA) after 10 days.

For the device telemetry logs, configure a rule to expire the objects after 35 days without transitioning them to any Infrequent Access tier.

For the video feeds, configure a transition rule to move the objects to S3 Glacier Deep Archive after 15 days.

For the device telemetry logs, configure a transition rule to move the objects to S3 One Zone-Infrequent Access (S3 One Zone-IA) after 10 days.

Cevabı ve açıklamayı göster

Cevap: For the video feeds, configure a transition rule to move the objects to S3 Standard-Infrequent Access (S3 Standard-IA) after 15 days.; For the device telemetry logs, configure a rule to expire the objects after 35 days without transitioning them to any Infrequent Access tier.

Cevap

Configure a lifecycle rule to transition the video feeds to S3 Standard-IA after 15 days, and configure a rule to expire the device telemetry logs after 35 days without transitioning them to any Infrequent Access tier.

The correct strategy transitions the large video files (500 MB) to S3 Standard-IA after 15 days, since they are stored in S3 Standard-IA for 45 days (meeting the 30-day minimum duration) and are larger than 128 KB. For the telemetry logs, keeping them in S3 Standard and expiring them after 35 days is the most cost-effective action because transitioning them to S3 Standard-IA would trigger penalties for both the small file size (15 KB vs. 128 KB minimum billing size) and the short storage duration (25 days vs. 30-day minimum).

Adım Adım Çözüm

Analyze the file size and lifecycle duration of the video feeds.

The video feeds average 500 MB (greater than the 128 KB S3 Standard-IA minimum size limit) and will be stored in S3 Standard-IA for 45 days (60 days total minus 15 days frequent access, which is greater than the 30-day minimum storage duration limit).

To determine if transitioning the video feeds to S3 Standard-IA is cost-effective and compliant with S3 storage class billing constraints.

Analyze the file size and lifecycle duration of the telemetry logs.

The telemetry logs average 15 KB (smaller than the 128 KB minimum storage billing size for IA) and will be stored for only 25 days if transitioned after day 10 (less than the 30-day minimum storage duration for S3 Standard-IA).

To evaluate the cost impact of transitioning small, short-lived telemetry files to S3 Standard-IA.

Select the optimal lifecycle actions based on the analysis.

Transition the video feeds to S3 Standard-IA after 15 days because it avoids all penalties. Retain the telemetry logs in S3 Standard for their entire lifecycle and expire them at day 35 to avoid the 128 KB billing size minimum and the 30-day minimum storage duration penalty.

To achieve the most cost-optimized storage design by aligning file profiles with Amazon S3 storage class rules.

Anahtar Kavram

Amazon S3 lifecycle management requires aligning file size characteristics and retention periods with the constraints of storage classes like S3 Standard-IA (128 KB minimum object size and 30-day minimum storage duration) to avoid cost penalties.

Soru 457Soru →

A company runs its applications in a multi-account environment managed by AWS Organizations. A solutions architect needs to design a cost-monitoring solution that identifies sudden, unexpected spikes in daily spend across any account or service. The solution must minimize false positives, require no manual maintenance of static thresholds, and automatically publish alerts to an Amazon SNS topic for immediate triage. Which solution should the solutions architect recommend to meet these requirements?

Create an AWS Cost Anomaly Detection monitor for AWS services, and set up an alert subscription to publish anomaly notifications to an Amazon SNS topic.

Configure an AWS Budget with a dynamic threshold based on historical usage, and integrate it with Amazon CloudWatch Alarms to publish to an Amazon SNS topic.

Configure a daily AWS Cost Explorer report for anomalous spending patterns, write an AWS Lambda function to parse the report, and publish notifications to an Amazon SNS topic.

Establish an AWS Billing Conductor pricing rule to analyze multi-account billing datasets daily, and trigger an alert to an Amazon SNS topic when costs deviate from normal baselines.

Cevabı ve açıklamayı göster

Cevap: Create an AWS Cost Anomaly Detection monitor for AWS services, and set up an alert subscription to publish anomaly notifications to an Amazon SNS topic.

Cevap

Create an AWS Cost Anomaly Detection monitor for AWS services and set up an alert subscription to publish anomaly notifications to an Amazon SNS topic.

The correct answer proposes using AWS Cost Anomaly Detection. This service leverages advanced machine learning models to detect unusual spend patterns, adapting automatically without requiring manual baseline calculation or static threshold maintenance. By configuring an alert subscription, it can immediately push notifications to an Amazon SNS topic, minimizing false positives and administrative overhead.

Adım Adım Çözüm

Identify the primary requirement: automated detection of sudden cost spikes across multiple accounts with zero manual threshold tuning.

Requires a machine-learning-based tool designed for cost anomalies rather than a static threshold budgeting tool.

This rules out tools requiring manually configured limits, such as AWS Budgets, or tools designed for retrospective manual analysis.

Evaluate the capabilities of AWS Cost Anomaly Detection.

It uses machine learning to identify anomalous spend patterns, requires no manual thresholds, and supports Amazon SNS integrations out of the box.

This directly matches the technical and operational requirements of the company.

Eliminate billing customization tools (AWS Billing Conductor) and retrospective tools (AWS Cost Explorer) that do not support automated, near-real-time anomaly alerting.

AWS Cost Anomaly Detection is selected as the optimal architecture.

Ensures minimal administrative overhead and fast reaction time to unexpected cost changes.

Anahtar Kavram

Proactive Cost Monitoring and Anomaly Detection in AWS

Tahmini Süre:1m 30s

Soru 458Soru →

A company hosts a dynamic web application on Amazon EC2 instances behind Application Load Balancers (ALBs) in the us-west-2 and eu-west-1 Regions. The application is accessed by users globally. The company wants to improve application performance by minimizing transit path latency, packet loss, and jitter. Additionally, they must implement stateless network filtering to block a list of known malicious IP ranges at the subnet boundary before the traffic reaches the ALBs.

Which two options should the solutions architect choose to meet these requirements?

Geçerli olan tümünü seçin

Deploy AWS Global Accelerator and register the ALBs in both Regions as endpoints.

Configure Network ACLs on the subnets where the ALBs are deployed with deny rules for the malicious IP ranges.

Create Amazon Route 53 records with latency-based routing policies that point directly to the ALB in each Region.

Add inbound rules to the ALB security groups to explicitly deny traffic from the malicious IP ranges.

Establish a single AWS Site-to-Site VPN connection from the users' networks to the VPCs to route the application traffic.

Cevabı ve açıklamayı göster

Cevap: Deploy AWS Global Accelerator and register the ALBs in both Regions as endpoints.; Configure Network ACLs on the subnets where the ALBs are deployed with deny rules for the malicious IP ranges.

Cevap

Deploying AWS Global Accelerator to route traffic over the AWS backbone network and configuring Network ACLs on the ALB subnets to statelessly block malicious IP ranges.

The combination of deploying AWS Global Accelerator and configuring Network ACLs meets all constraints. AWS Global Accelerator improves application performance for global users by routing traffic over the optimized AWS global backbone, which minimizes latency, jitter, and packet loss. Network ACLs provide stateless network filtering at the subnet boundary, allowing the solutions architect to create deny rules to block the specified malicious IP ranges before the traffic reaches the Application Load Balancers.

Adım Adım Çözüm

Evaluate routing solutions for performance optimization.

AWS Global Accelerator is selected because it uses anycast IP routing over the congestion-free AWS private network to minimize packet loss, jitter, and latency compared to public internet routing.

Users globally access the application, and the public internet path introduces higher jitter and latency variance.

Evaluate traffic filtering requirements at the subnet boundary.

Network ACLs are selected because they operate at the subnet boundary and allow stateless deny rules.

The requirement calls for stateless filtering before traffic reaches the ALBs, which Security Groups cannot provide as they are stateful and allow-only.

Anahtar Kavram

Combining AWS Global Accelerator for optimized global routing with Network ACLs for stateless edge subnet security filtering.

Soru 459Soru →

A financial services company hosts a transaction processing workload on Amazon EC2 instances in the private subnets of VPC A in the us-east-1 Region. The instances upload $50\text{ TB}$ of data monthly to an Amazon S3 bucket. In addition, the instances replicate $30\text{ TB}$ of transaction logs monthly to a database cluster in VPC B within the same AWS Region. Currently, VPC A and VPC B are connected via an AWS Transit Gateway. All outbound S3 traffic from the private subnets in VPC A is routed through a NAT Gateway. The company wants to optimize the network design to reduce data transfer costs without compromising security. Which two actions should a solutions architect take to meet these requirements most cost-effectively? (Select TWO.)

Geçerli olan tümünü seçin

Create a gateway VPC endpoint for Amazon S3 in VPC A, and associate it with the route tables of the private subnets.

Establish a VPC peering connection between VPC A and VPC B, and route the compliance replication traffic through the peering connection instead of the Transit Gateway.

Deploy an interface VPC endpoint for Amazon S3 in VPC A, and update the application configuration to use the PrivateLink DNS name.

Deploy an AWS Site-to-Site VPN connection between VPC A and VPC B over the Transit Gateway to secure and optimize the replication traffic.

Replace the NAT Gateway in VPC A with a self-managed NAT instance running on a configured Amazon EC2 instance to route the S3 and replication traffic.

Cevabı ve açıklamayı göster

Cevap: Create a gateway VPC endpoint for Amazon S3 in VPC A, and associate it with the route tables of the private subnets.; Establish a VPC peering connection between VPC A and VPC B, and route the compliance replication traffic through the peering connection instead of the Transit Gateway.

Cevap

Create a gateway VPC endpoint for Amazon S3 in VPC A, and establish a VPC peering connection between VPC A and VPC B to route compliance replication traffic.

The correct architecture uses a gateway VPC endpoint for Amazon S3 in VPC A, which is free of charge and routes S3 traffic privately, eliminating NAT Gateway processing fees. It also uses a VPC peering connection instead of the Transit Gateway to connect VPC A and VPC B, avoiding the Transit Gateway's data processing fee.

Adım Adım Çözüm

Analyze S3 traffic cost optimization options

Determine that routing

50\text{ TB}

of S3 traffic through a NAT Gateway incurs massive data processing fees. Implementing a Gateway VPC Endpoint for S3 in VPC A redirects this traffic directly to S3 privately with no data processing or hourly charges.

Gateway VPC endpoints are the most cost-effective way to access Amazon S3 from private subnets because they are completely free.

Analyze inter-VPC traffic cost optimization options

Determine that routing

30\text{ TB}

of replication traffic through AWS Transit Gateway incurs processing fees of

\$0.02

per

\text{GB}

. Establishing a VPC Peering connection between VPC A and VPC B and routing traffic through it avoids these processing fees.

VPC Peering does not charge for data processing within the same Region, making it more cost-effective than Transit Gateway for high-volume inter-VPC data transfer.

Anahtar Kavram

Minimizing data transfer costs in AWS by selecting the correct private connectivity options, specifically preferring Gateway VPC Endpoints for S3/DynamoDB over NAT Gateways/Interface Endpoints, and VPC Peering over Transit Gateway for high-volume intra-region traffic.

Tahmini Süre:3m 0s

Soru 460Soru →

A multinational enterprise manages its development environments across 50 separate AWS accounts consolidated under a single organization in AWS Organizations. The cloud engineering team is tasked with implementing a cost management solution that will automatically detect unexpected, erratic spikes in daily data transfer fees and instance usage within 24 hours of occurrence. Due to the highly variable workloads in each developer account, the solution must use machine learning to establish a dynamic baseline and adaptively alert on spend anomalies rather than relying on fixed, static thresholds. Which approach will satisfy these requirements with the lowest administrative effort?

Create an AWS Cost Anomaly Detection monitor for all member accounts within the organization, define an alert subscription with a threshold based on the daily dollar impact, and configure notifications to be sent to an Amazon Simple Notification Service (Amazon SNS) topic.

Establish daily cost budgets in AWS Budgets for each account, set the budgeted amount to match the average historical spend of the previous month, and configure an email notification to trigger when actual costs exceed 110% of the budgeted amount.

Create a custom Python script running on a daily Amazon EventBridge cron schedule that calls the AWS Cost Explorer API to query the previous day's usage, performs statistical standard deviation checks on the retrieved data, and sends alerts to an Amazon SNS topic.

Configure AWS Billing Conductor to define custom billing groups for each development account, set up billing rules to filter out standard usage patterns, and configure a CloudWatch alarm to trigger when the pro forma billing data deviates from the baseline.

Cevabı ve açıklamayı göster

Cevap: Create an AWS Cost Anomaly Detection monitor for all member accounts within the organization, define an alert subscription with a threshold based on the daily dollar impact, and configure notifications to be sent to an Amazon Simple Notification Service (Amazon SNS) topic.

Cevap

The correct option is the one proposing AWS Cost Anomaly Detection. AWS Cost Anomaly Detection is a fully managed service that uses machine learning to continuously monitor cost and usage, detect unusual spend patterns, and minimize false alerts by adapting to historical usage trends. It natively integrates with AWS Organizations to monitor all member accounts, and notifications can be routed via Amazon SNS within 24 hours of anomaly detection with zero custom scripting.

Adım Adım Çözüm

Analyze the requirements for cost monitoring: dynamic baseline (machine learning), detection within 24 hours, multi-account scoping under AWS Organizations, and lowest administrative effort.

Identify that static threshold tools like AWS Budgets do not satisfy the dynamic ML requirement, while custom scripting on AWS Cost Explorer violates the low operational effort requirement.

This narrows down the potential native AWS services designed specifically for automated anomaly detection.

Evaluate AWS Cost Anomaly Detection capabilities against the selected constraints.

AWS Cost Anomaly Detection natively uses machine learning to establish dynamic baselines and adjusts to variable patterns. It supports AWS Organizations out-of-the-box and integrates with Amazon SNS for alerting.

This confirms AWS Cost Anomaly Detection as the optimal tool for the scenario.

Configure the detection monitors and alert subscriptions.

Set up a monitor type for Member Accounts and link it to an SNS topic with threshold preferences.

This delivers the proactive notifications required by the cloud engineering team.

Anahtar Kavram

AWS Cost Anomaly Detection leverages machine learning to dynamically baseline usage and alert on spend anomalies with low operational overhead.

Tahmini Süre:2m 0s

ÖncekiSayfa 23 / 74Sonraki

Tüm alıştırma soruları

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram