Tüm alıştırma soruları

1462 soru

Soru 421Soru

A logistics company is designing a hybrid network architecture to synchronize its on-premises telemetry processing system in Chicago with a critical analytics application deployed across multiple VPCs in the `us-east-1` and `us-west-2` Regions. The telemetry system requires a high-throughput, private connection that can support peak data transfer rates of up to 10 Gbps10 \text{ Gbps} with the lowest possible latency. Meanwhile, several regional distribution centers must upload transactional logs to the same VPCs. The regional logs require IPsec encryption and need a connection that can handle up to 2 Gbps2 \text{ Gbps} of aggregate traffic. Which network architecture will meet these requirements while optimizing throughput, securing data in transit, and minimizing routing complexity?

Cevabı ve açıklamayı göster

Cevap: Provision peered AWS Transit Gateways across both Regions. Attach the Chicago telemetry system to the Transit Gateways using an AWS Direct Connect connection with a Transit Virtual Interface (Transit VIF) attached to a Direct Connect Gateway. Connect the regional distribution centers using multiple AWS Site-to-Site VPN connections to the Transit Gateways with Equal-Cost Multi-Path (ECMP) routing enabled to aggregate tunnel throughput.

Cevap

The architecture that provisions peered AWS Transit Gateways with a Direct Connect Transit VIF and ECMP-enabled VPN connections is the correct choice.
The correct architecture uses peered AWS Transit Gateways across the target Regions to simplify routing to multiple VPCs. It leverages AWS Direct Connect with a Transit VIF and a Direct Connect Gateway to provide the required 10 Gbps10 \text{ Gbps} private, low-latency connection. To support the 2 Gbps2 \text{ Gbps} IPsec VPN bandwidth requirement, it implements AWS Site-to-Site VPN connections to the Transit Gateways with Equal-Cost Multi-Path (ECMP) routing enabled, which aggregates the throughput of multiple VPN tunnels to bypass the 1.25 Gbps1.25 \text{ Gbps} limit per tunnel.

Adım Adım Çözüm

1
Analyze connectivity and performance requirements.
The telemetry system requires 10 Gbps10 \text{ Gbps} of private, low-latency throughput. The regional distribution centers require encrypted paths supporting 2 Gbps2 \text{ Gbps} of aggregate traffic across multiple VPCs in two Regions.
This establishes the throughput thresholds and encryption constraints for both connection types.
2
Evaluate the primary Direct Connect configuration.
A Transit VIF associated with a Direct Connect Gateway connected to peered Transit Gateways is required to access multiple VPCs across two Regions at 10 Gbps10 \text{ Gbps}.
A Private VIF cannot connect to a Transit Gateway, which is necessary for scalable multi-VPC and multi-Region architectures.
3
Evaluate the Site-to-Site VPN throughput limitation.
A single VPN tunnel is limited to 1.25 Gbps1.25 \text{ Gbps} of throughput. To achieve 2 Gbps2 \text{ Gbps}, Equal-Cost Multi-Path (ECMP) routing must be enabled on the Transit Gateway to aggregate bandwidth over multiple VPN tunnels.
This overcomes the bandwidth limitation of a single VPN connection.
4
Assess security and routing options.
Stateless Network ACLs cannot track connection states, and Route 53 Latency routing does not provide secure IPsec tunnels.
Using peered Transit Gateways with ECMP-enabled VPN and Direct Connect with a Transit VIF is the only architecture that satisfies all constraints.

Anahtar Kavram

High-Performing and Scalable Hybrid Networks
Soru 422Soru

A media streaming platform needs to ingest user interaction telemetry during live broadcasts. The platform expects a baseline ingestion rate of 15 MB/s15\text{ MB/s}, which spikes rapidly to 120 MB/s120\text{ MB/s} during popular live events. The telemetry payloads are sent in JSON format and must be converted to Apache Parquet format and stored in Amazon S3 for long-term analytics. The solution must scale dynamically to handle the peaks without manual intervention or latency degradation, while minimizing operational overhead. Which architecture meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon Kinesis Data Stream in On-Demand mode to ingest the incoming telemetry data. Set up an Amazon Data Firehose delivery stream that references the Kinesis Data Stream as the source, uses AWS Glue to convert the JSON data to Apache Parquet, and delivers the formatted data to Amazon S3.

Cevap

Configure an Amazon Kinesis Data Stream in On-Demand capacity mode linked to an Amazon Data Firehose delivery stream that utilizes AWS Glue for serverless JSON-to-Parquet conversion before delivering the files to Amazon S3.
The correct answer combines Amazon Kinesis Data Streams in On-Demand capacity mode with Amazon Data Firehose. On-Demand mode automatically scales shard provisioning up to twice the previous peak rate to accommodate sudden bursts, avoiding ingestion throttling. Firehose then consumes from the stream and uses AWS Glue to convert the incoming JSON telemetry records into Apache Parquet format before saving them to S3, providing a serverless, low-overhead solution.

Adım Adım Çözüm

1
Select the correct ingestion ingestion layer for dynamic scaling.
Amazon Kinesis Data Streams in On-Demand mode is chosen because it dynamically manages shard count allocation to handle rapid traffic spikes up to 200 MB/s200\text{ MB/s} without manual administrative overhead or scaling lag.
To avoid ProvisionedThroughputExceededExceptions during sudden live broadcast traffic peaks, capacity must scale instantly.
2
Integrate with a serverless delivery and format transformation pipeline.
Connect Kinesis Data Streams to Amazon Data Firehose. Firehose natively integrates with AWS Glue Schema Registry to perform JSON-to-Parquet conversion inline before writing to S3.
This avoids the need to write and maintain custom AWS Lambda transformation code, minimizing both latency and operational overhead.
3
Configure the storage destination.
Amazon S3 serves as the durable destination for the query-ready Parquet data.
This establishes a high-performance, cost-effective data lake storage solution.

Anahtar Kavram

Serverless high-throughput ingestion and transformation architectures using Kinesis Data Streams On-Demand and Amazon Data Firehose.
Tahmini Süre:2m 30s
Soru 423Soru

A financial services company is deploying a critical online transaction processing (OLTP) application on AWS that requires a multi-region database architecture. The primary database cluster will be hosted in `us-east-1`, and the disaster recovery (DR) cluster will be located in `us-west-2`. The architecture must achieve a Recovery Point Objective (RPO) of less than 11 second and a Recovery Time Objective (RTO) of less than 11 minute. The database tier must support scaling read traffic in the secondary region while keeping the write path resilient to regional failures. Which two database configurations or actions should a solutions architect recommend to meet these requirements? (Select TWO.)

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

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.; Configure Aurora Auto Scaling for the reader instances in the us-west-2 secondary cluster to handle fluctuating read query workloads.

Cevap

To meet the requirements, the solutions architect should deploy an Amazon Aurora PostgreSQL Global Database across the primary and secondary regions, and configure Aurora Auto Scaling for the reader instances in the secondary region cluster.
Deploying an Amazon Aurora PostgreSQL Global Database ensures storage-level replication lag remains under 11 second, fulfilling the low RPO limit. If a regional outage occurs, the secondary cluster in the recovery region can be promoted to primary in under 11 minute, satisfying the RTO limit. Furthermore, configuring Aurora Auto Scaling on the reader instances in the secondary region allows the secondary cluster to handle dynamic read request volumes independently of the primary write path.

Adım Adım Çözüm

1
Select a multi-region database engine that supports low-latency replication.
Amazon Aurora Global Database provides storage-level asynchronous replication across AWS regions with typical latencies of less than 11 second.
This satisfies the strict RPO requirement of less than 11 second.
2
Ensure the disaster recovery failover capability fits the target recovery window.
Aurora Global Database secondary clusters can be promoted to a standalone primary cluster with full read-write capabilities in less than 11 minute.
This allows the database to meet the RTO requirement of less than 11 minute.
3
Configure scaling for the read workload in the secondary region.
Enable Aurora Auto Scaling on reader instances in the secondary region cluster.
This allows the reader endpoints to dynamically scale out or scale in based on query volume without affecting the primary cluster.

Anahtar Kavram

Resilient Database Configurations and High Availability
Soru 424Soru

A fintech company is designing a high-performing data ingestion and transformation pipeline for a mobile payment application to process real-time transaction logs. The pipeline must ingest a steady volume of 2 MB/s2\text{ MB/s} of JSON data, which can spike up to 10 MB/s10\text{ MB/s} during promotional events. The logs must be converted into Apache Parquet format and stored in Amazon S3 for near-real-time business intelligence queries. The architecture must minimize operational management and scale automatically to handle traffic spikes. Which ingestion and transformation solution should the company implement?

Cevabı ve açıklamayı göster

Cevap: Use Amazon Data Firehose to receive the transaction logs, configure native data format conversion using an AWS Glue schema to output Apache Parquet, and deliver the transformed logs directly to Amazon S3.

Cevap

Use Amazon Data Firehose to receive the transaction logs, configure native data format conversion using an AWS Glue schema to output Apache Parquet, and deliver the transformed logs directly to Amazon S3.
The correct solution uses Amazon Data Firehose to automatically scale up to 10 MB/s10\text{ MB/s} to handle promotional traffic spikes. It leverages Firehose's native integration with AWS Glue to convert JSON records into Apache Parquet format directly before writing them to Amazon S3. This eliminates the operational complexity of managing shards or writing custom ETL code in AWS Lambda.

Adım Adım Çözüm

1
Analyze scale and ingestion requirements.
The pipeline must handle steady ingestion at 2 MB/s2\text{ MB/s} and spikes up to 10 MB/s10\text{ MB/s} with minimal operational management.
This establishes that the solution must scale dynamically without manual intervention.
2
Evaluate data transformation overhead.
Converting JSON data to Apache Parquet can be done natively by Amazon Data Firehose using an AWS Glue schema, eliminating the need for custom transformation code in AWS Lambda.
Choosing native features minimizes custom code maintenance, CPU usage charges, and operational overhead.
3
Select the optimal architecture.
Amazon Data Firehose combined with AWS Glue for schema definition and Amazon S3 for destination is the most performant, self-scaling, and operationally simple design.
It addresses ingestion, transformation, and storage without provisioning shards or maintaining polling code.

Anahtar Kavram

Serverless real-time data ingestion and native schema-based format transformation using Amazon Data Firehose and AWS Glue.
Tahmini Süre:1m 30s
Soru 425Soru

A healthcare software provider is deploying a web application on AWS that uses an Amazon Aurora PostgreSQL database. The application has strict compliance requirements:

1. High availability within the primary region (us-east-1) with a Recovery Time Objective (RTO) of less than 3030 seconds and a Recovery Point Objective (RPO) of 00 (no data loss).
2. A cross-region disaster recovery (DR) site in us-west-2 with an RTO of less than 1515 minutes and an RPO of less than 55 minutes. The DR region must also support low-latency read operations during normal business hours to serve local reports.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL DB cluster in the primary region with one or more Aurora Replicas placed in different Availability Zones.; Create an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, and use the secondary cluster to serve local read traffic.

Cevap

Deploying an Amazon Aurora PostgreSQL DB cluster with replicas in different Availability Zones in the primary region, and creating an Amazon Aurora Global Database with a secondary cluster in the disaster recovery region.
Deploying an Amazon Aurora cluster with replicas across different Availability Zones guarantees high availability and automatic failover (RTO < 30 seconds) with zero data loss (RPO = 0) because Aurora replicates storage synchronously across three Availability Zones. Adding an Aurora Global Database to replicate asynchronously to us-west-2 provides an RPO of less than 1 second and can be promoted to primary in less than a minute, meeting the DR RTO/RPO requirements while allowing the secondary cluster to serve local read operations.

Adım Adım Çözüm

1
Evaluate the high availability requirement in the primary region (us-east-1).
Identify that an Amazon Aurora DB cluster with replicas in different Availability Zones provides automatic failover (RTO < 30 seconds) and synchronous replication across storage nodes (RPO of 0).
This configuration ensures that if the primary instance fails, a replica in another Availability Zone is promoted automatically with no data loss.
2
Evaluate the cross-region disaster recovery (DR) and read scaling requirements in us-west-2.
Identify that Amazon Aurora Global Databases replicate data asynchronously to a secondary region with an RPO of less than 1 second and an RTO of less than 1 minute when managed failover is used, while also allowing the secondary cluster to serve read traffic.
This satisfies the cross-region RTO (< 15 minutes) and RPO (< 5 minutes) limits and offloads reporting read traffic.
3
Eliminate configurations that do not support automatic failover or fail to meet the recovery objectives.
Reject using RDS read replicas for primary failover, setting up an EC2-based Pilot Light strategy with daily backups, and using Route 53 Latency routing for database failover.
These alternatives either lack automatic failover capabilities, exhibit recovery times and data loss exceeding the thresholds, or misapply DNS routing policies to database replication.

Anahtar Kavram

Amazon Aurora Multi-AZ and Global Databases provide high availability and cross-region disaster recovery by separating compute and storage replication layers.
Soru 426Soru

A logistics company is designing a high-performance data ingestion pipeline for real-time telemetry from 150,000150,000 active delivery vehicles. The peak ingestion rate is 45 MB/s45\text{ MB/s} with an average payload size of 3 KB3\text{ KB} per message. Telemetry data from each vehicle must be processed in the exact chronological order it was generated to calculate accurate velocity trends. The company wants to convert the telemetry from JSON to Apache Parquet format and store it in an Amazon S3 data lake within 5 minutes5\text{ minutes} of arrival. Which architecture meets these requirements with the highest performance and the lowest operational overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon Kinesis Data Streams in On-Demand capacity mode, utilizing the vehicle ID as the partition key. Configure Amazon Kinesis Data Firehose to consume from the stream, perform format conversion from JSON to Apache Parquet using AWS Glue Schema Registry, and deliver the output to the Amazon S3 data lake.

Cevap

Deploy Amazon Kinesis Data Streams in On-Demand capacity mode with the vehicle ID as the partition key, and use Amazon Kinesis Data Firehose with AWS Glue Schema Registry to convert the JSON data to Apache Parquet format before storing it in Amazon S3.
The correct architecture uses Amazon Kinesis Data Streams in On-Demand capacity mode alongside Amazon Kinesis Data Firehose. Kinesis Data Streams guarantees ordering per partition key (vehicle ID), and the On-Demand mode dynamically scales write throughput up to 200 MB/s200\text{ MB/s} or 200,000 records/s200,000\text{ records/s} without administrative intervention. Kinesis Data Firehose consumes from the stream, performs serverless format conversion to Apache Parquet using AWS Glue Schema Registry, and delivers the data to Amazon S3 within the required 5-minute buffering interval. This provides a highly performant and scalable solution with the lowest operational overhead.

Adım Adım Çözüm

1
Analyze ordering requirements
Vehicle telemetry requires strict chronological order per vehicle ID, meaning partition keys based on vehicle ID must be used to keep records on the same partition/shard.
Ensures that sequential messages from the same vehicle are processed in order.
2
Calculate ingestion throughput and shard capacity limits
Peak throughput is 45 MB/s45\text{ MB/s} and message rate is 15,000 records/s15,000\text{ records/s} (45 MB/s/3 KB45\text{ MB/s} / 3\text{ KB}). A single Kinesis shard supports 1 MB/s1\text{ MB/s} or 1,000 records/s1,000\text{ records/s}. This requires at least 4545 shards at peak.
Ensures the stream is sized correctly to prevent ProvisionedThroughputExceededException errors during peak loads.
3
Select ingestion stream capacity mode
Choose Kinesis Data Streams with On-Demand capacity mode to automatically scale throughput up to 200 MB/s200\text{ MB/s} and 200,000 records/s200,000\text{ records/s} without manual administrative effort.
Meets the requirement for minimum operational overhead while accommodating fluctuating traffic spikes.
4
Design the transformation and delivery tier
Use Amazon Kinesis Data Firehose to pull data from Kinesis Data Streams, perform serverless Parquet formatting via integration with AWS Glue Schema Registry, and write to S3 within a 5-minute5\text{-minute} buffering window.
Allows near-real-time transformation and ingestion into S3 without managing custom EC2 or ECS transformation nodes.

Anahtar Kavram

High-performing data ingestion and format transformation using Kinesis Data Streams On-Demand and Kinesis Data Firehose with minimal operational overhead.
Soru 427Soru

A financial technology company is deploying a global transactional platform across two AWS Regions: us-east-1 (primary) and us-west-2 (secondary). The application requires a relational database backend that can survive a complete regional outage with a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Read operations must be served locally in both regions to minimize latency, while write operations must be routed appropriately to avoid data divergence. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and enable write forwarding on the secondary cluster.; In the event of a primary regional outage, initiate a managed failover of the Aurora Global Database to promote the secondary DB cluster in us-west-2 to primary.

Cevap

Deploy an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and enable write forwarding on the secondary cluster. Also, in the event of a primary regional outage, initiate a managed failover of the Aurora Global Database to promote the secondary DB cluster in us-west-2 to primary.
Deploying an Amazon Aurora Global Database with write forwarding enabled ensures low-latency reads in both regions and coordinates writes to the primary cluster. During a regional outage, initiating a managed failover promotes the secondary cluster to primary with zero data loss, achieving an RPO of less than 1 second and an RTO of less than 1 minute.

Adım Adım Çözüm

1
Select a multi-region relational database engine that supports cross-region replication latency under 1 second.
Amazon Aurora Global Database is chosen because its physical replication lag is typically under 1 second.
This satisfies the Recovery Point Objective (RPO) requirement of less than 1 second.
2
Enable write forwarding on the secondary Aurora cluster.
Applications in the secondary region can read locally and send writes to the local cluster, which are forwarded to the primary region.
This allows reads to be served locally with low latency while avoiding split-brain data divergence.
3
Define the disaster recovery failover mechanism.
Managed failover is configured to promote the secondary cluster to primary during a disaster.
Aurora Global Database managed failover completes in less than 1 minute (meeting the RTO requirement of less than 1 minute) and guarantees zero data loss.

Anahtar Kavram

Amazon Aurora Global Database managed failover and write forwarding support cross-region high availability with RTO < 1 minute and RPO < 1 second.
Tahmini Süre:3m 0s
Soru 428Soru

A health insurance provider is migrating its transactional claims processing application to AWS. The application database requires a MySQL-compatible relational engine. The solutions architect must design a highly resilient database architecture that spans two AWS Regions in an active-passive setup. The design must achieve a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute for a regional disaster. Furthermore, the database must support automatic failover in the primary region within 60 seconds if an Availability Zone fails.

Which configuration meets these requirements with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora MySQL Multi-AZ cluster in the primary region, and configure an Amazon Aurora Global Database with a secondary cluster in the secondary region.

Cevap

Deploying an Amazon Aurora MySQL Multi-AZ cluster in the primary region and using Amazon Aurora Global Database to create a secondary cluster in the secondary region meets all constraints with the lowest operational overhead.
Deploying an Amazon Aurora MySQL Multi-AZ cluster in the primary region and using Amazon Aurora Global Database to create a secondary cluster in the secondary region meets all constraints with the lowest operational overhead. Aurora Multi-AZ clusters use shared storage and automatically fail over to a reader instance in another Availability Zone within 30 seconds, satisfying the local high availability requirements. For disaster recovery, Aurora Global Databases use storage-based, physical replication that operates asynchronously but has latency typically under 1 second (satisfying the Recovery Point Objective of less than 1 minute). In a disaster event, the secondary cluster can be promoted to a standalone primary cluster with read-write capabilities in under 10 minutes (satisfying the Recovery Time Objective of less than 15 minutes). This setup is managed natively by AWS, minimizing operational complexity.

Adım Adım Çözüm

1
Analyze the database engine and high availability (HA) constraints in the primary region.
The application requires a MySQL-compatible database that must survive an Availability Zone outage and fail over within 60 seconds.
This helps eliminate options that do not support rapid local auto-failover, such as Single-AZ deployments.
2
Evaluate the disaster recovery (DR) constraints for the secondary region.
The DR solution requires an RPO of less than 1 minute and an RTO of less than 15 minutes.
The RPO constraint requires near-real-time cross-region data replication, while the RTO constraint requires a fast, automated or highly streamlined database promotion process.
3
Compare the candidate architectures against AWS managed replication capabilities and operational complexity.
Amazon Aurora Global Database replicates storage blocks across regions in under 1 second (RPO < 1 second) and supports promotion in under 10 minutes (RTO < 15 minutes), meeting all criteria natively.
Choosing the architecture with the lowest operational overhead ensures compliance with the requirement of least operational complexity.

Anahtar Kavram

Amazon Aurora Global Database provides low-latency cross-region storage replication (RPO < 1 second) and fast managed failover/promotion (RTO < 10 minutes) for multi-region resilience, while Aurora Multi-AZ clusters handle rapid, automated local failovers (RTO < 30 seconds).
Soru 429Soru

A logistics company has migrated its inventory management systems to AWS, distributing the workload across 2020 VPCs in the us-west-2 Region. The company needs to establish private connectivity between these VPCs and its on-premises data center, which has an existing 10 Gbps10\text{ Gbps} AWS Direct Connect connection. The database synchronization process requires a minimum, consistent throughput of 3 Gbps3\text{ Gbps}. The solution must easily scale to accommodate up to 5050 VPCs in the future with minimal routing complexity and administrative overhead. Additionally, the network security policy mandates stateful traffic filtering at the instance level and stateless filtering at the subnet boundary. Which of the following network architectures meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Attach the 2020 VPCs to an AWS Transit Gateway. Connect the Transit Gateway to a Direct Connect Gateway using a Transit Virtual Interface (Transit VIF) on the Direct Connect connection. Configure Security Groups to statefully inspect traffic at the instance level and Network ACLs to statelessly filter traffic at the subnet boundary.

Cevap

The correct network architecture is to attach all VPCs to an AWS Transit Gateway, connect it to a Direct Connect Gateway using a Transit Virtual Interface (Transit VIF), and use Security Groups for stateful instance-level security and Network ACLs for stateless subnet-level security.
The correct architecture uses AWS Transit Gateway to act as a centralized cloud router, which supports up to 50 Gbps50\text{ Gbps} of throughput per VPC attachment and easily scales up to thousands of VPCs, meeting both the throughput and scalability requirements. Connecting the Transit Gateway to the 10 Gbps10\text{ Gbps} Direct Connect connection requires a Direct Connect Gateway and a Transit Virtual Interface (Transit VIF). To satisfy the security requirements, Security Groups are configured at the instance level for stateful filtering, and Network ACLs are configured at the subnet level for stateless filtering.

Adım Adım Çözüm

1
Analyze the scaling and routing complexity requirements for connecting 2020 (scaling to 5050) VPCs to an on-premises data center.
A full mesh VPC Peering scales poorly and lacks transitive routing. A Direct Connect Gateway associated with Virtual Private Gateways is limited to 1010 associations. AWS Transit Gateway provides a hub-and-spoke model that scales to thousands of VPCs.
To identify a network topology that supports the required scale and reduces routing complexity.
2
Evaluate the bandwidth and connection requirements (3 Gbps3\text{ Gbps} throughput over a 10 Gbps10\text{ Gbps} Direct Connect line).
A single Site-to-Site VPN tunnel is limited to 1.25 Gbps1.25\text{ Gbps}, which fails the requirement. Direct Connect with a Transit VIF to AWS Transit Gateway supports the full Direct Connect line speed, with Transit Gateway supporting up to 50 Gbps50\text{ Gbps} per VPC attachment.
To ensure the network path meets the database replication performance constraints.
3
Apply security rules for stateful instance-level and stateless subnet-level filtering.
Security Groups are stateful and apply to elastic network interfaces (instance level). Network ACLs are stateless and apply at the subnet boundary.
To satisfy the security policy requirements correctly using AWS native security components.

Anahtar Kavram

Scalable hybrid network design using AWS Transit Gateway, Direct Connect Gateway with Transit VIF, and stateful vs stateless traffic filtering.
Tahmini Süre:2m 30s
Soru 430Soru

A digital marketing agency maintains an on-premises file server containing active design assets and historical archives. The agency requires a hybrid storage solution that provides low-latency local read/write access to active assets while ensuring that all files are stored with high durability in the cloud. If the local data center suffers a catastrophic power failure, the agency must be able to resume file access for its designers within a Recovery Time Objective (RTO) of 1515 minutes, using either a secondary office or AWS-based compute instances. Which storage configuration meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.

Cevap

Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.
Deploying an AWS Storage Gateway (Amazon S3 File Gateway) on-premises allows designers to access files locally via NFS with low latency, while the master copy is stored in Amazon S3. In the event of a disaster, a new gateway VM can be quickly created on-premises at a secondary office or as an Amazon EC2 instance and pointed to the same S3 bucket. This restores file sharing capabilities in minutes, satisfying the 1515-minute Recovery Time Objective (RTO).

Adım Adım Çözüm

1
Analyze the requirements for a hybrid storage solution that offers local caching and high cloud durability.
Identify that AWS Storage Gateway (Amazon S3 File Gateway) fits this scenario by caching active data locally while storing the primary copy in Amazon S3.
S3 File Gateway provides NFS/SMB access to objects in S3 with a local cache for low-latency read/write operations.
2
Evaluate the disaster recovery failover strategy against the 1515-minute Recovery Time Objective (RTO).
Determine that recreating the gateway virtual machine (VM) and pointing it to the existing Amazon S3 bucket allows immediate retrieval of file metadata and data access.
Since the file data is preserved in the S3 bucket, a new gateway can be quickly provisioned on-premises or on an EC2 instance without waiting for lengthy data restores.

Anahtar Kavram

AWS Storage Gateway (S3 File Gateway) hybrid storage and disaster recovery failover mechanics.
Tahmini Süre:2m 0s
Soru 431Soru

An online multiplayer gaming studio is launching a new game server hosting platform in the us-west-2 Region. The gaming client applications require low-latency UDP communication with the server fleet. Additionally, the studio must establish a hybrid network link to their on-premises development office to transfer large game builds (up to 3 Gbps3\text{ Gbps} during peak hours) to private subnets in the VPC, while blocking specific external IPs known for malicious attacks at the subnet boundary. Which TWO actions should the solutions architect take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure AWS Global Accelerator to route client traffic to a Network Load Balancer (NLB) targeting the game servers.; Establish a 10 Gbps10\text{ Gbps} AWS Direct Connect connection to the VPC, and configure a Network Access Control List (NACL) with deny rules for the malicious IP addresses.

Cevap

Configure AWS Global Accelerator to route client traffic to a Network Load Balancer (NLB) targeting the game servers, and establish a 10 Gbps10\text{ Gbps} AWS Direct Connect connection to the VPC while configuring a Network Access Control List (NACL) with deny rules for the malicious IP addresses.
AWS Global Accelerator optimizes UDP routing by utilizing the AWS global network to route traffic to a Network Load Balancer (NLB) close to the game servers. AWS Direct Connect provides high, dedicated throughput (such as 10 Gbps10\text{ Gbps}) that easily accommodates the 3 Gbps3\text{ Gbps} build transfer requirement. Network Access Control Lists (NACLs) allow stateless deny rules to block specific malicious IP addresses at the subnet boundary.

Adım Adım Çözüm

1
Evaluate the incoming client traffic requirement (low-latency UDP).
AWS Global Accelerator supports UDP traffic and routes it through the AWS global backbone network to a Network Load Balancer (NLB), minimizing latency.
Traditional DNS-based routing or ALBs cannot optimize UDP path latency and connection stability as effectively as Global Accelerator.
2
Analyze the hybrid throughput requirement of 3 Gbps3\text{ Gbps} peak traffic.
AWS Direct Connect can support bandwidth rates up to 10 Gbps10\text{ Gbps} or 100 Gbps100\text{ Gbps} directly.
A single AWS Site-to-Site VPN tunnel is limited to 1.25 Gbps1.25\text{ Gbps} maximum bandwidth, making it insufficient for the 3 Gbps3\text{ Gbps} demand.
3
Determine how to block malicious IP addresses at the subnet boundary.
Configure Network Access Control Lists (NACLs) with deny rules.
Security Groups only support allow rules and cannot explicitly deny traffic, whereas NACLs are stateless and can define explicit deny rules at the subnet boundary.

Anahtar Kavram

Designing scalable, low-latency, and high-throughput hybrid network architectures using AWS Global Accelerator, Direct Connect, and VPC NACLs.
Soru 432Soru

An enterprise is designing a disaster recovery (DR) architecture for a critical web application. The primary infrastructure is located in the us-east-1 Region, consisting of an Application Load Balancer (ALB) and an Amazon Aurora PostgreSQL Global Database. The passive DR site is in the eu-west-1 Region, using a Pilot Light strategy where application servers are scaled to zero to minimize costs, and an Aurora read replica is maintained for data replication.

The Solutions Architect must configure Amazon Route 53 to implement automatic failover. Under normal operations, all client traffic must be routed to us-east-1. If the primary region's compute resources or database fail, Route 53 must redirect all traffic to eu-west-1. The architect must ensure that traffic is not routed to eu-west-1 before the pilot light resources are scaled up, and Route 53 does not route traffic to both regions simultaneously.

Which TWO configurations should the Solutions Architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure a Route 53 primary failover record pointing to the us-east-1 ALB with Evaluate Target Health set to Yes. Configure a secondary failover record pointing to the eu-west-1 ALB with Evaluate Target Health set to No.; Create a Route 53 metric-based health check linked to a CloudWatch alarm that monitors Aurora database health and database connection failures in us-east-1, and associate this health check with the primary Route 53 record.

Cevap

Configure the primary failover record pointing to the primary ALB with Evaluate Target Health set to Yes while setting Evaluate Target Health to No on the secondary failover record, and create a Route 53 metric-based health check linked to a CloudWatch alarm monitoring database health.
The correct configurations ensure robust active-passive DNS failover. First, the primary failover record must point to the primary ALB with target health evaluation enabled, while the secondary failover record pointing to the standby ALB must have target health evaluation disabled (set to No). This is because the standby region uses a Pilot Light DR pattern where application servers are scaled to zero. A target-health-check enabled secondary record would be seen as unhealthy by Route 53 due to zero healthy registered targets, causing Route 53 to route to both endpoints if the primary fails. Second, Route 53 health checks can be linked to CloudWatch alarms. Because standard ALB health checks do not monitor database status, creating a metric-based health check linked to a CloudWatch alarm that tracks database connectivity and write availability ensures Route 53 will fail over if the primary database cluster becomes unavailable.

Adım Adım Çözüm

1
Determine the correct Route 53 routing policy for an active-passive disaster recovery configuration.
Identify that a Failover routing policy must be used to ensure all traffic goes to the primary region (us-east-1) under normal conditions, and is redirected to the secondary region (eu-west-1) only during an outage.
Active-passive failover requires directing all traffic to the active site, unlike active-active policies such as Latency routing.
2
Analyze target health evaluation settings for both the primary and secondary ALB endpoints when using a Pilot Light strategy.
Primary failover record points to the primary ALB with Evaluate Target Health set to Yes. Secondary failover record points to the secondary ALB with Evaluate Target Health set to No.
Because the secondary region runs in a Pilot Light state with compute instances scaled to zero, the secondary ALB has no healthy targets and would fail health checks. Setting Evaluate Target Health to Yes on the secondary would cause Route 53 to see both regions as unhealthy and route traffic to both. Setting it to No ensures Route 53 always treats the secondary as healthy when the primary fails.
3
Integrate database health checks into Route 53 routing decisions.
Configure a CloudWatch alarm monitoring Aurora database health metrics (such as connection count or write availability) and link a Route 53 metric-based health check to this alarm, associating it with the primary failover record.
Standard Route 53 health checks and ALB target group health checks only evaluate compute target health, not database availability. A metric-based health check ensures Route 53 triggers a failover if the database layer fails while the web servers remain running.

Anahtar Kavram

Configuring Route 53 active-passive DNS failover in a Pilot Light DR scenario requires coordinating compute scaling states with Route 53's health evaluation mechanisms (Evaluate Target Health) and using CloudWatch alarm-based health checks to incorporate backend database health into the DNS failover decision.
Soru 433Soru

An organization is migrating its high-frequency financial ledger application to AWS. The system must meet two performance criteria: it must retrieve current transaction states with microsecond latency for active sessions, and it must write audit logs at a rate exceeding 80,00080,000 writes per second. The audit logs are queried chronologically by day. Which combination of database design and architectural strategies will meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Store transaction states in Amazon DynamoDB and deploy Amazon DynamoDB Accelerator (DAX) to cache reads.; For the audit log table, use a composite primary key consisting of a transaction UUID partition key and a timestamp sort key.

Cevap

The optimal strategy is to cache transaction state reads with DynamoDB Accelerator (DAX) to achieve microsecond latency, and to use a high-cardinality partition key (such as a transaction UUID) with a timestamp sort key for the audit logs to distribute write traffic evenly across DynamoDB partitions.
Caching transaction states using Amazon DynamoDB Accelerator (DAX) provides the required microsecond latency for active session lookups. Additionally, using a transaction UUID as the partition key and a timestamp as the sort key for the audit log table ensures write operations are evenly distributed across multiple physical partitions, preventing write bottlenecks while still supporting chronological queries.

Adım Adım Çözüm

1
Analyze read latency requirements.
Microsecond read latency requires an in-memory caching layer. Amazon DynamoDB Accelerator (DAX) provides microsecond latency for DynamoDB reads.
Standard DynamoDB queries operate in single-digit millisecond latency, which does not meet the microsecond requirement.
2
Analyze write scale and partition key design for the audit logs.
A rate of 80,00080,000 writes per second requires wide partition distribution to avoid hot keys.
DynamoDB partitions data based on the partition key. A sequential key (like a timestamp) routes all writes to a single partition, causing throttling.
3
Select partition and sort key strategies for chronological queries.
Use a transaction UUID as the partition key for write distribution, and the timestamp as the sort key for range-based chronological queries.
This allows query filters to run range operations on the sort key while maintaining uniform write distribution across partitions.

Anahtar Kavram

Designing high-performing AWS database architectures requires combining in-memory caching (such as DAX) for microsecond reads with proper partition key design (avoiding monotonically increasing attributes) to scale write throughput uniformly.
Soru 434Soru

A financial technology company is deploying a transaction processing system on AWS. The application uses an Amazon RDS for PostgreSQL database. To meet regulatory compliance, the database architecture must achieve a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of less than 35 seconds for any single Availability Zone failure within the primary AWS Region. The application also requires local read scaling within the primary Region to handle reporting queries without affecting write transaction throughput. Which database configuration satisfies these resilience and scalability requirements with the lowest RTO?

Cevabı ve açıklamayı göster

Cevap: Deploy the database as an Amazon RDS Multi-AZ DB cluster with one writer and two readable standby DB instances across three Availability Zones.

Cevap

Deploy the database as an Amazon RDS Multi-AZ DB cluster with one writer and two readable standby DB instances across three Availability Zones.
Deploying an Amazon RDS Multi-AZ DB cluster satisfies all constraints. It uses semi-synchronous replication to guarantee an RPO of zero (no data loss) if at least one standby acknowledges the write. Its architecture enables automatic failovers that typically complete in under 35 seconds, meeting the strict RTO target. Furthermore, it allows read traffic to be routed to the two standby DB instances, providing native local read scaling within the primary Region.

Adım Adım Çözüm

1
Analyze the RPO requirement.
An RPO of zero requires synchronous or semi-synchronous database replication so that no acknowledged transactions are lost during an Availability Zone failure.
Asynchronous replication mechanisms, such as standard RDS Read Replicas, can lead to data loss during failover and do not guarantee an RPO of zero.
2
Analyze the RTO requirement.
An RTO of less than 35 seconds requires an automated failover mechanism that promotes a backup instance immediately without manual intervention or script execution delays.
Standard Multi-AZ DB instance deployments typically failover in 60 to 120 seconds, which is too slow. Multi-AZ DB clusters feature transaction-routing mechanisms that achieve failovers in under 35 seconds.
3
Evaluate the read scalability requirement.
The configuration must support readable standby instances or replicas within the same Region to offload reporting queries.
A Multi-AZ DB cluster allows the two standby instances to serve read traffic, satisfying local read scaling natively, whereas standard Multi-AZ DB instances do not allow reading from the standby.

Anahtar Kavram

Amazon RDS Multi-AZ DB Cluster Deployments vs Multi-AZ DB Instance Deployments
Soru 435Soru

A financial technology enterprise is designing the storage architecture for its transactional auditing application. The application processes high-volume trade ledgers that must be stored with high availability and durability. The company requires that all ingested ledger files be replicated across two AWS Regions to support a disaster recovery strategy with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 5 minutes. Additionally, older historical ledger archives must be stored cost-effectively for 7 years; these archives are rarely accessed, but when an audit occurs, the data must be fully retrievable within a strict RTO of 2 hours.

Which combination of AWS storage configurations will meet these resilience and recovery requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled on the S3 buckets hosting the ledger files.; Transition the historical ledger archives to Amazon S3 Glacier Flexible Retrieval and utilize Expedited retrievals when accessing the data for audits.

Cevap

The correct configurations are configuring Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled on the primary bucket, and transitioning historical archives to Amazon S3 Glacier Flexible Retrieval with Expedited retrievals used during audits.
To achieve an RPO of 15 minutes for object replication between two AWS Regions, enabling Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) is necessary because S3 RTC provides a service level agreement (SLA) to replicate 99.9% of objects within 15 minutes. To retrieve archived files within a 2-hour RTO during audits, the data must be stored in a class that supports fast retrieval. Amazon S3 Glacier Flexible Retrieval supports Expedited retrievals, which complete within 1-5 minutes, fitting the 2-hour window.

Adım Adım Çözüm

1
Identify the replication RPO and RTO for active files.
The active ledger files must be replicated to a second region with an RPO of 15 minutes and an RTO of 5 minutes.
This establishes the performance boundaries for the replication technology selection.
2
Evaluate replication features for Amazon S3.
Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) replicates 99.9% of objects within 15 minutes.
S3 RTC provides the necessary SLA to meet the strict 15-minute RPO, and replication keeps the data available in the secondary region for immediate retrieval.
3
Analyze the retrieval RTO for historical archives.
Historical archives must be stored cost-effectively for 7 years and retrieved within a 2-hour window during audit events.
This defines the latency limits of the cold storage classes and retrieval tier.
4
Compare Glacier storage classes and retrieval options.
Amazon S3 Glacier Flexible Retrieval with Expedited retrievals restores data in 1 to 5 minutes.
Standard retrieval from Glacier takes 3 to 5 hours, and standard retrieval from Glacier Deep Archive takes 12 hours, meaning only Expedited retrieval meets the 2-hour RTO constraint.

Anahtar Kavram

Implementing resilient and highly available multi-region storage systems using S3 replication controls and optimizing lifecycle transitions based on recovery time objectives (RTO).
Tahmini Süre:2m 30s
Soru 436Soru

A media production agency needs to transfer large, uncompressed video files daily from their on-premises editing studio to Amazon S3 buckets inside their AWS VPC. The agency requires a network connection that guarantees a throughput of at least 5 Gbps5\text{ Gbps} and ensures that the traffic does not traverse the public internet.

Which steps should a solutions architect take to configure this network connection? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Provision a 10 Gbps10\text{ Gbps} AWS Direct Connect connection.; Create a private virtual interface (VIF) to connect to the VPC.

Cevap

To meet the requirements, the solutions architect must provision a 10 Gbps10\text{ Gbps} AWS Direct Connect connection and create a private virtual interface (VIF) to connect to the VPC.
To achieve a dedicated, private connection that does not traverse the public internet and meets the throughput requirement of at least 5 Gbps5\text{ Gbps}, the company must use AWS Direct Connect. A 10 Gbps10\text{ Gbps} connection satisfies the performance demand, while a private virtual interface (VIF) is required to establish private network connectivity directly to resources inside a VPC.

Adım Adım Çözüm

1
Evaluate the network throughput and public internet constraints.
The requirement demands a minimum of 5 Gbps5\text{ Gbps} throughput and specifies that the traffic must not traverse the public internet.
This rules out a standard AWS Site-to-Site VPN connection, which runs over the public internet and is limited to 1.25 Gbps1.25\text{ Gbps} per tunnel.
2
Select the appropriate hybrid connectivity service.
AWS Direct Connect provides dedicated, private physical network connections to AWS that bypass the public internet. A 10 Gbps10\text{ Gbps} connection is selected to support the 5 Gbps5\text{ Gbps} requirement.
Direct Connect supports standard port speeds of 1 Gbps1\text{ Gbps}, 10 Gbps10\text{ Gbps}, or 100 Gbps100\text{ Gbps}.
3
Determine the required virtual interface type for VPC resource access.
A private virtual interface (VIF) is created to connect the Direct Connect connection to the VPC.
A private VIF is required to access private resources within a VPC, such as EC2 instances or S3 VPC endpoints, via Direct Connect.

Anahtar Kavram

High-Performing and Scalable Network Architectures
Soru 437Soru

A logistics company monitors 5,000 container tracking devices that send temperature, humidity, and location telemetry every minute. The company wants to ingest, transform the coordinates into a standardized format, and load the data into Amazon Redshift in near-real-time. The telemetry must be processed in chronological order per container to ensure accurate tracking. The system must scale automatically to handle traffic spikes during peak shipping seasons and require minimal operational overhead. Which solution meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Kinesis Data Streams in On-Demand mode to ingest the telemetry using the container ID as the partition key. Use Amazon Data Firehose to read from the stream, invoke an AWS Lambda function to transform the coordinates, and deliver the data to Amazon Redshift.

Cevap

Configure Amazon Kinesis Data Streams in On-Demand capacity mode with the container ID as the partition key, and use Amazon Data Firehose integrated with AWS Lambda to transform and deliver the data directly to Amazon Redshift.
The correct answer provides a fully serverless, highly performant architecture. Setting Amazon Kinesis Data Streams to On-Demand capacity mode satisfies the scaling requirement without manual intervention. Partitioning the stream by container ID ensures strict chronological ordering per device. Amazon Data Firehose integrates natively with Kinesis Data Streams and AWS Lambda, allowing coordinates to be transformed in near-real-time before delivery to Amazon Redshift. This keeps operational overhead to a minimum.

Adım Adım Çözüm

1
Ensure ordered processing by container.
Using the container ID as the partition key in Amazon Kinesis Data Streams ensures that all telemetry payloads for a specific container are mapped to the same shard, which preserves their relative chronological order during ingestion.
Data within a single shard of a Kinesis Data Stream is ordered sequentially.
2
Select an auto-scaling, serverless ingestion layer.
Configuring Kinesis Data Streams in On-Demand mode allows the ingestion throughput to dynamically scale up or down based on incoming volume without manually managing shards.
This meets the requirement of handling traffic spikes automatically while minimizing operational overhead.
3
Integrate with a serverless delivery and transformation pipeline.
Connecting Amazon Data Firehose to the Kinesis stream enables serverless buffering and delivery to Amazon Redshift. Inlining an AWS Lambda function in the Firehose configuration allows data transformation (such as coordinate flattening) to occur during transit.
This workflow avoids the need to build, maintain, and scale custom consumer applications on EC2.

Anahtar Kavram

Serverless, ordered data ingestion and transformation using Amazon Kinesis Data Streams (On-Demand), Amazon Data Firehose, and AWS Lambda.
Tahmini Süre:2m 0s
Soru 438Soru

A media processing workload is hosted on Amazon EC2 instances in a private subnet. The application must regularly download large video files from an Amazon S3 bucket in the same Region, and it must also access a third-party software repository on the public internet to download package updates. The solutions architect must design a secure network routing architecture that minimizes data transfer costs and prevents direct internet exposure of the EC2 instances.

Which combination of configurations will meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a Gateway VPC endpoint for Amazon S3, and associate it with the route table of the private subnet.; Deploy a NAT Gateway in a public subnet, and configure the private subnet's route table to route traffic destined for 0.0.0.0/00.0.0.0/0 to the NAT Gateway.

Cevap

Create a Gateway VPC endpoint for Amazon S3 associated with the private subnet's route table, and deploy a NAT Gateway in a public subnet with a route for 0.0.0.0/00.0.0.0/0 in the private subnet's route table.
To satisfy the requirements securely and cost-effectively, a Gateway VPC endpoint should be created for Amazon S3 and associated with the private subnet's route table. This configuration keeps S3 traffic on the private AWS network and eliminates NAT Gateway data processing costs. Additionally, to allow the private EC2 instances to download updates from the public internet without direct exposure, a NAT Gateway should be deployed in a public subnet, with the private subnet's route table configured to send 0.0.0.0/00.0.0.0/0 traffic to it.

Adım Adım Çözüm

1
Analyze S3 traffic cost optimization and routing.
Determine that routing S3 traffic through a Gateway VPC Endpoint is free and routes traffic privately through the AWS internal network, avoiding NAT Gateway charges.
S3 Gateway Endpoints are the most cost-effective and secure method for private subnets to access S3.
2
Analyze external internet access for package updates.
Determine that outbound internet access requires a NAT Gateway placed in a public subnet with a route in the private subnet's route table targeting the NAT Gateway.
Private EC2 instances cannot access the internet directly; they require a NAT translation device in a public subnet.
3
Evaluate security and statefulness rules.
Confirm that Network ACLs are stateless and AWS WAF cannot be applied to subnets or NACLs.
This rules out distractors related to stateful Network ACLs and incorrect WAF deployments.

Anahtar Kavram

VPC Network Routing and Cost Optimization using VPC Endpoints and NAT Gateways
Soru 439Soru

A company runs a core transactional retail application on AWS. The application database is deployed on Amazon RDS for PostgreSQL in a Multi-AZ configuration using a 2 TB2\text{ TB} `io2` storage volume provisioned at 30,00030,000 IOPS. Database metric analysis shows that during normal operations (2525 days of the month), the workload is steady, consuming an average of 3,0003,000 write IOPS and 2,0002,000 read IOPS. During a 55-day monthly flash sale event, read queries scale dramatically, requiring up to 28,00028,000 read IOPS, while write IOPS remain steady at 3,0003,000 IOPS. The system must maintain high availability with automatic failover at all times. Which database design modification is the most cost-effective solution to handle this workload?

Cevabı ve açıklamayı göster

Cevap: Migrate the database to Amazon Aurora PostgreSQL. Deploy a Multi-AZ cluster consisting of one writer instance and one reader instance. Configure Aurora Auto Scaling for the reader instances to dynamically scale out up to five reader instances during the flash sale events, and scale back down to a single reader instance afterwards.

Cevap

Migrate the database to Amazon Aurora PostgreSQL. Deploy a Multi-AZ cluster consisting of one writer instance and one reader instance. Configure Aurora Auto Scaling for the reader instances to dynamically scale out up to five reader instances during the flash sale events, and scale back down to a single reader instance afterwards.
Migrating the database to Amazon Aurora PostgreSQL with a Multi-AZ cluster consisting of one writer and one reader instance, and configuring Aurora Auto Scaling for the reader instances, is the most cost-effective solution. Since Aurora's storage architecture automatically scales performance and storage space without requiring provisioned IOPS, the company avoids the high cost of provisioned `io2` storage. Because the flash sale spikes are read-heavy, Aurora Auto Scaling can dynamically provision additional reader instances to handle the 28,00028,000 read IOPS and scale them down when the event ends, aligning instance capacity and cost with actual demand while maintaining full Multi-AZ high availability.

Adım Adım Çözüm

1
Analyze the workload characteristics and requirements
The database requires high availability (Multi-AZ) and automatic failover. The workload is highly read-heavy (90%90\% reads) with a predictable 55-day spike of 28,00028,000 read IOPS, while the remaining 2525 days require only 3,0003,000 write IOPS and 2,0002,000 read IOPS.
Understanding the ratio of reads to writes and the predictability of the spikes allows for target capacity scaling of the correct database tier.
2
Evaluate storage and database options for handling IOPS dynamically
Amazon RDS PostgreSQL requires provisioning storage volumes like `io2` to guarantee high IOPS, which must be paid for 24/7. Amazon Aurora PostgreSQL decouples compute from storage; its storage auto-scales performance dynamically without provisioning IOPS. Furthermore, Aurora supports native Auto Scaling of reader instances to handle read-heavy spikes.
Comparing RDS and Aurora storage cost models identifies that Aurora eliminates the need to provision expensive `io2` storage for peak capacity.
3
Select the most cost-effective capacity scaling strategy
By deploying a baseline Aurora PostgreSQL Multi-AZ cluster (one writer, one reader) and enabling Auto Scaling for readers, the system automatically scales out reader instances to absorb the 28,00028,000 read IOPS during the 55-day flash sale. The instances scale back down to one reader for the other 2525 days, minimizing compute costs.
Aligning instance capacity with the database query patterns minimizes both compute and storage costs while maintaining the high availability SLA.

Anahtar Kavram

Cost-optimized database capacity planning leverages Aurora's decoupled storage and Auto Scaling read replicas to handle periodic read-heavy spikes, avoiding the high cost of provisioned database storage.
Soru 440Soru

A logistics company is designing an architecture to process telemetry data from its fleet of delivery vehicles. The telemetry data contains status updates that must be processed in the exact sequence they are generated per vehicle to ensure accurate route mapping. The ingestion volume is highly irregular, peaking during daytime deliveries and dropping to zero overnight. Each processing run involves executing a route optimization simulation that takes approximately 20 minutes to complete. The company wants a highly cost-efficient, serverless, and automated scaling solution that preserves message ordering, handles the database writes dynamically, and eliminates idle compute costs. Which architecture meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Ingest the telemetry data using Amazon API Gateway and write to an Amazon SQS FIFO queue. Process the queue using Amazon ECS tasks running on AWS Fargate Spot that scale dynamically based on the queue depth and scale down to zero when the queue is empty, storing the results in an Amazon DynamoDB table in On-Demand capacity mode.

Cevap

The architecture that uses Amazon API Gateway to ingest data, an Amazon SQS FIFO queue to preserve sequence, Amazon ECS on AWS Fargate Spot to process the 20-minute simulation with auto-scaling to zero, and Amazon DynamoDB in On-Demand capacity mode to handle spiky database writes.
The correct architecture uses Amazon SQS FIFO to ensure that telemetry status updates are processed in the exact sequence they are generated per vehicle (using the vehicle ID as the Message Group ID). Since each processing run takes 20 minutes, using AWS Fargate Spot is the most cost-effective and scalable compute option, as it supports long-running processes (unlike AWS Lambda's 15-minute execution limit) and saves up to 70% compared to standard Fargate tasks. Scaling the ECS service to zero when the queue is empty eliminates idle compute costs. Finally, Amazon DynamoDB in On-Demand capacity mode is ideal for highly irregular workloads with overnight idle periods, as there is no baseline capacity charge and it scales instantly to handle peak traffic.

Adım Adım Çözüm

1
Evaluate the execution duration requirement against serverless compute limits.
The simulation takes 20 minutes to execute. Since AWS Lambda has a maximum execution limit of 15 minutes, containerized execution on Amazon ECS (or AWS Batch) must be selected instead of Lambda to avoid timeouts.
AWS Lambda is not suitable for continuous, long-running processes exceeding 15 minutes.
2
Evaluate message ordering requirements.
The status updates must be processed in the exact sequence they are generated per vehicle. An Amazon SQS FIFO queue must be used, using the vehicle ID as the Message Group ID to ensure sequential processing for each vehicle while enabling parallel processing across different vehicles.
Amazon SQS Standard queues do not guarantee first-in, first-out (FIFO) ordering.
3
Evaluate compute cost efficiency for the highly irregular, zero-overnight traffic pattern.
Amazon ECS on AWS Fargate Spot should be used. The tasks should be configured to scale based on SQS queue metrics and scale down to zero when the queue is empty, avoiding compute charges during idle hours.
Fargate Spot offers up to a 70% discount compared to standard Fargate, and scaling to zero tasks when idle eliminates baseline compute costs.
4
Evaluate database capacity scaling and cost optimization.
Amazon DynamoDB should be configured in On-Demand capacity mode to automatically handle spikes in write traffic without manual capacity planning, and to avoid any baseline capacity costs when traffic drops to zero overnight.
DynamoDB Provisioned Capacity mode with Auto Scaling cannot scale down to zero and suffers from scaling delays, leading to either write throttling or excessive idle resource costs.

Anahtar Kavram

Decoupling and scaling serverless architectures cost-effectively for spiky, long-running, and ordered workloads.
Tahmini Süre:3m 0s
ÖncekiSayfa 22 / 74Sonraki