Tüm alıştırma soruları

1462 soru

Soru 581Soru

A company runs a production application on an Amazon RDS for PostgreSQL database instance. The database currently operates in a single Availability Zone. The Solutions Architect needs to modify the database configuration to ensure high availability with automatic failover in the event of an infrastructure failure or Availability Zone outage. Which configuration change will meet these requirements with the least operational effort?

Cevabı ve açıklamayı göster

Cevap: Modify the database instance to enable a Multi-AZ deployment

Cevap

Modify the database instance to enable a Multi-AZ deployment
Modifying the RDS instance to a Multi-AZ deployment is the correct answer. AWS automatically provisions a standby replica in a different Availability Zone, synchronously replicates data to it, and performs automatic failover in the event of an outage by updating the DNS record of the database endpoint.

Adım Adım Çözüm

1
Identify the primary requirement: high availability with automatic failover for an Amazon RDS database.
Limits the viable options to AWS services that support automatic DNS redirection and failover.
The scenario requires zero manual intervention during an outage.
2
Evaluate the difference between Multi-AZ deployments and Read Replicas.
Multi-AZ uses synchronous replication with automated failover, while Read Replicas use asynchronous replication for scaling reads.
Promoting a Read Replica requires manual promotion or complex scripting, which does not provide native automatic failover.
3
Select Multi-AZ deployment as the solution.
Enabling Multi-AZ achieves synchronous replication and automatic failover with the least operational effort.
AWS manages the replication and failover process natively without additional user configuration.

Anahtar Kavram

Amazon RDS Multi-AZ deployments for high availability and automatic failover
Soru 582Soru

A financial services company runs a critical transactional application backed by an Amazon RDS PostgreSQL DB instance. Currently, the database is deployed in a single Availability Zone (AZ). Due to compliance regulations, the database layer must be redesigned to ensure high availability. The solution must achieve a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of under two minutes in the event of an AZ failure. Which database configuration should a solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Modify the existing Amazon RDS DB instance to be a Multi-AZ deployment.

Cevap

Modify the existing Amazon RDS DB instance to be a Multi-AZ deployment.
Modifying the existing DB instance to a Multi-AZ deployment matches all criteria. It synchronously replicates database changes to a standby instance in a different Availability Zone, ensuring zero data loss (RPO = 0). If the primary instance fails, Amazon RDS automatically performs a failover by updating the database DNS CNAME record to point to the standby instance, which typically takes between one and two minutes (RTO < 2 minutes).

Adım Adım Çözüm

1
Analyze the requirements for high availability, specifically the RPO (Recovery Point Objective) of zero and RTO (Recovery Time Objective) of under two minutes.
Identified that the replication must be synchronous to ensure no data loss (RPO = 0), and the failover mechanism must be automatic and fast (RTO < 2 minutes).
This sets the baseline criteria to evaluate the available database configurations.
2
Evaluate the replication type of Amazon RDS options.
Multi-AZ deployments use synchronous replication to a standby instance in a different AZ, whereas Read Replicas use asynchronous replication.
Only synchronous replication can guarantee an RPO of zero (no data loss) during an unexpected primary node failure.
3
Evaluate the failover mechanisms of the proposed solutions.
Multi-AZ deployments perform automatic DNS failover to the standby replica, typically completing within 60-120 seconds. Promoting a read replica or cross-region warm standby is a manual process or requires complex custom scripting, which increases RTO.
Ensures that the configuration meets the RTO requirement of under two minutes.

Anahtar Kavram

Amazon RDS Multi-AZ deployments provide high availability, data redundancy, and automatic failover by utilizing synchronous replication to a standby instance in a different Availability Zone.
Soru 583Soru

An enterprise healthcare platform hosts its critical medical imaging application in the `us-east-1` Region. The application runs on Amazon EC2 instances distributed across three Availability Zones (AZs) and requires concurrent, POSIX-compliant read/write access to shared storage for active patient scans. Active scans must be immediately resilient to AZ-level failures. Scans older than 9090 days must be transitioned to a lower-cost tier to optimize costs, but must remain accessible within an emergency retrieval window of under 55 minutes. Additionally, a disaster recovery (DR) site in the `us-west-2` Region must be maintained using a pilot light strategy. The DR site has a target Recovery Point Objective (RPO) of 1515 minutes and a Recovery Time Objective (RTO) of 1010 minutes. Which storage architecture meets all of these requirements with the lowest operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy a Multi-AZ Amazon EFS file system in us-east-1 and configure an EFS Lifecycle policy to transition files to EFS Archive after 9090 days. Enable EFS Replication to copy data to a destination EFS file system in us-west-2. Deploy pilot light EC2 instances in us-west-2 that remain stopped until a failover event, at which point they are started and mount the replicated EFS file system.

Cevap

Deploy a Multi-AZ Amazon EFS file system in us-east-1, configure an EFS Lifecycle policy to transition files to EFS Archive after 90 days, enable EFS Replication to us-west-2, and use stopped EC2 instances in us-west-2 as pilot light recovery targets.
The correct architecture utilizes Multi-AZ Amazon EFS to support concurrent, POSIX-compliant writes across three Availability Zones. Transitioning to EFS Archive via EFS Lifecycle Management ensures cost optimization while preserving sub-second file retrieval speeds (well below the 55-minute RTO). EFS Replication continuously synchronizes data to a target EFS file system in the destination region, achieving an RPO of minutes (meeting the 1515-minute target). Finally, starting stopped EC2 instances (pilot light strategy) to mount the destination EFS file system can easily be completed in under 1010 minutes, meeting the RTO.

Adım Adım Çözüm

1
Select Multi-AZ EFS for us-east-1 storage.
Provides concurrent POSIX-compliant file system access across all three Availability Zones, ensuring immediate resilience to AZ failures.
Meets the requirement for active patient scans to have regional high availability and shared access.
2
Configure EFS Lifecycle Management to transition files to EFS Archive after 90 days.
Files are automatically moved to a lower-cost tier while maintaining sub-second retrieval times.
Satisfies the regulatory requirement for cost-efficient long-term storage while keeping access times under the 5-minute RTO.
3
Enable native EFS Replication to a destination EFS file system in us-west-2.
Replicates file modifications asynchronously with an RPO of minutes (typically under 15 minutes).
Satisfies the 15-minute RPO disaster recovery requirement.
4
Configure stopped EC2 instances in us-west-2 to mount the replicated EFS file system upon startup.
A pilot light disaster recovery target that can be fully active in under 10 minutes.
Satisfies the 10-minute RTO disaster recovery requirement with minimal cost.

Anahtar Kavram

Designing a multi-region, resilient storage architecture with EFS Multi-AZ, EFS Archive lifecycle tiering, EFS Replication, and pilot light EC2 compute failover.
Tahmini Süre:3m 0s
Soru 584Soru

A genomics research facility is migrating its high-performance computing (HPC) pipeline to AWS. The pipeline runs on a cluster of 3232 Amazon EC2 instances and requires concurrent, shared read and write access to a temporary scratch workspace. The storage system must deliver sub-millisecond latencies, support parallel I/O, and scale aggregate throughput linearly up to 15 GB/s15\text{ GB/s} during peak processing. Which two actions should a solutions architect take to meet these performance requirements at the lowest cost and operational complexity? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon FSx for Lustre file system using the Scratch-2 deployment type.; Mount the file system on the cluster nodes using the open-source Lustre client.

Cevap

Deploy an Amazon FSx for Lustre file system using the Scratch-2 deployment type and mount the file system on the cluster nodes using the open-source Lustre client.
The correct architecture utilizes Amazon FSx for Lustre in the Scratch-2 deployment configuration along with the native Lustre client. Lustre is a parallel file system designed for HPC workloads, allowing multiple EC2 instances to read and write to the same storage blocks concurrently with sub-millisecond latencies. The Scratch-2 model is ideal for temporary processing data because it minimizes cost by omitting replication. Mounting with the native Lustre client ensures that parallel I/O is achieved across all 32 nodes.

Adım Adım Çözüm

1
Analyze the workload requirements: temporary scratch workspace, 32 concurrent nodes requiring shared read/write, sub-millisecond latencies, parallel I/O, and up to 15 GB/s15\text{ GB/s} throughput.
Identified the need for a high-performance, parallel, and temporary shared file system.
HPC clusters performing genomic processing require scalable, highly parallel file systems that can handle concurrent client access without data corruption or bottlenecks.
2
Select the correct AWS storage service that provides native parallel file system capabilities and optimized scratch deployment.
Selected Amazon FSx for Lustre with the Scratch-2 deployment type.
Lustre is designed for high-performance computing, and its Scratch-2 model offers a cost-effective, high-throughput solution without replication overhead, perfect for temporary scratch files.
3
Determine the optimal client mounting protocol to leverage the file system's parallel architecture.
Chose the open-source Lustre client for mounting the file system.
Standard NFS clients do not support the distributed, parallel architecture of Lustre, whereas the native Lustre client enables parallel data paths from all 32 EC2 instances to the storage servers.

Anahtar Kavram

Amazon FSx for Lustre is purpose-built for high-performance computing (HPC) workloads requiring high throughput, low latency, and parallel file access across many compute nodes. For temporary workloads, Scratch-2 deployment provides the best cost-to-performance ratio.
Soru 585Soru

A media company is building a telemetry platform to ingest and transform clickstream data from its mobile application. The data stream averages 8 MB/s8\text{ MB/s} and spikes up to 25 MB/s25\text{ MB/s} during peak hours. The company requires that the data be converted from JSON to Apache Parquet format, partitioned by date, and stored in Amazon S3. The latency from ingestion to S3 must not exceed 5 minutes (300 seconds300\text{ seconds}). The architecture must be high-performing and require minimal operational overhead. Which two actions should a solutions architect recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Kinesis Data Firehose delivery stream to ingest the data, and enable data format conversion to Apache Parquet using the AWS Glue Data Catalog.; Configure the Kinesis Data Firehose delivery stream with a buffer interval of 300 seconds and direct the output to the destination Amazon S3 bucket.

Cevap

Create an Amazon Kinesis Data Firehose delivery stream to ingest the data and configure it to perform format conversion to Apache Parquet using AWS Glue, then set the buffer interval to 300 seconds to write the files to the target Amazon S3 bucket.
The correct solution involves creating an Amazon Kinesis Data Firehose delivery stream configured to perform inline conversion of incoming JSON data to Apache Parquet format using the AWS Glue Data Catalog. By setting the buffer interval to 300 seconds, the delivery stream ensures the transformed data is written to the destination S3 bucket within the required 5-minute latency window without manual operational management.

Adım Adım Çözüm

1
Select an ingestion service that supports automatic, serverless data format conversion.
Amazon Kinesis Data Firehose is selected because it can convert JSON payloads to Apache Parquet format on the fly using schemas from the AWS Glue Data Catalog, avoiding custom translation code or servers.
This minimizes operational overhead while maintaining high performance.
2
Configure the buffer settings to meet the latency requirement.
The buffer interval is set to 300 seconds (5 minutes).
This guarantees that data is flushed and written to S3 within the required 5-minute time window.
3
Evaluate and reject options that introduce throttling risks or lack ordering/cost efficiency.
Reject the options involving a single Kinesis shard (which throttles at 1 MB/s1\text{ MB/s}), SQS Standard (which does not guarantee ordering), and S3 Standard-IA (which charges a 30-day minimum duration penalty).
This ensures the final solution meets throughput, ordering, and cost constraints.

Anahtar Kavram

Serverless data ingestion and real-time transformation using Kinesis Data Firehose and AWS Glue.
Tahmini Süre:2m 0s
Soru 586Soru

An enterprise runs a critical transactional application backed by an Amazon RDS for PostgreSQL database instance in the us-east-1 Region. The database must sustain an Availability Zone outage with zero data loss (RPO = 0) and automatic failover in less than 60 seconds (RTO < 60s). The enterprise also requires a disaster recovery (DR) solution in the us-west-2 Region with an RPO of less than 5 minutes and an RTO of less than 15 minutes. Which two database configuration actions should the solutions architect take to meet these requirements with the least operational overhead?

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

Cevabı ve açıklamayı göster

Cevap: Modify the primary database instance to a Multi-AZ DB cluster deployment to support synchronous replication across three Availability Zones and automated failover.; Create an Amazon RDS cross-region read replica in the secondary region to asynchronously replicate data and serve as the promotion target for regional disaster recovery.

Cevap

Modify the primary database instance to a Multi-AZ DB cluster deployment, and create a cross-region read replica in the secondary region.
To achieve high availability with an RPO of 0 and an RTO of less than 60 seconds, the database must be configured with synchronous replication and automated failover. An Amazon RDS Multi-AZ DB cluster deployment provides synchronous replication across three Availability Zones and failover in under 35 seconds, satisfying the primary region HA goals. For cross-region disaster recovery, an Amazon RDS cross-region read replica replicates data asynchronously with very low replication lag (RPO < 5 minutes) and can be promoted to a primary database in the secondary region in under 15 minutes (RTO < 15 minutes) with minimal administrative overhead.

Adım Adım Çözüm

1
Evaluate the high availability and failover requirements within the primary region.
The requirements demand an RPO of 0 (no data loss) and an RTO of less than 60 seconds.
An Amazon RDS Multi-AZ DB cluster deployment replicates data synchronously across three Availability Zones, ensuring zero data loss (RPO = 0) and provides automated failover within 35 seconds, which satisfies the local high availability goal.
2
Evaluate the disaster recovery requirements in the secondary region.
The requirements demand an RPO of less than 5 minutes and an RTO of less than 15 minutes.
Creating a cross-region read replica replicates data asynchronously, keeping replication lag under a few seconds (RPO < 5 minutes). The replica can be promoted to a standalone primary database in under 15 minutes (RTO < 15 minutes), meeting the disaster recovery criteria.
3
Analyze and eliminate alternate database replication and recovery configurations.
Using custom promotion scripts for in-region replicas fails synchronous replication and failover RTO requirements. Re-provisioning from snapshots violates the 15-minute RTO. Route 53 latency routing is not supported for active-active writes on RDS PostgreSQL.
This leaves Multi-AZ DB cluster deployment and a cross-region read replica as the only options that satisfy both primary and secondary region constraints with minimal operational overhead.

Anahtar Kavram

Amazon RDS Multi-AZ DB clusters provide synchronous replication across three Availability Zones for zero data loss and automated sub-minute failovers, while cross-region read replicas provide asynchronous replication for multi-region disaster recovery with low replication lag and fast promotion capabilities.
Soru 587Soru

A company runs a high-performance media rendering application using Amazon ECS on AWS Fargate. The containerized application tasks run concurrently and must read from and write to a shared, POSIX-compliant filesystem. The workload is highly dynamic, with throughput requirements spiking up to 800 MB/s800\text{ MB/s} during peak rendering times. Which storage solution should a solutions architect recommend to meet these requirements with the highest performance and scalability?

Cevabı ve açıklamayı göster

Cevap: Amazon Elastic File System (Amazon EFS) configured with Elastic Throughput

Cevap

Amazon Elastic File System (Amazon EFS) configured with Elastic Throughput
Amazon Elastic File System (Amazon EFS) is a serverless, shared file system that is natively supported by Amazon ECS on AWS Fargate. It supports POSIX compliance, concurrent access from thousands of containers, and with Elastic Throughput, it automatically scales to meet dynamic throughput requirements up to the gigabytes-per-second range, making it the most suitable and performant choice for this scenario.

Adım Adım Çözüm

1
Identify the compute environment and sharing requirements.
The application runs on serverless Amazon ECS Fargate containers that require concurrent read/write access to a shared POSIX-compliant filesystem.
This requirement eliminates standalone Amazon EBS volumes as they cannot be natively shared across multiple serverless tasks concurrently.
2
Evaluate the throughput and scaling requirements of the workload.
The workload is highly dynamic and requires up to 800 MB/s800\text{ MB/s} of throughput during peak rendering times.
The storage solution must scale throughput dynamically without manual intervention or over-provisioning to maintain performance and control costs.
3
Select the storage service that natively supports serverless container integration, POSIX standards, and dynamic throughput scaling.
Amazon EFS with Elastic Throughput meets all requirements by natively integrating with ECS Fargate, supporting concurrent access, and scaling throughput automatically based on workload demands.
This provides the highest performance and scalability with minimal management overhead.

Anahtar Kavram

Selecting high-performing, scalable, and shared storage solutions suitable for serverless container workloads.
Tahmini Süre:1m 30s
Soru 588Soru

A financial auditing firm hosts a document management system on AWS where millions of PDF records are stored in an Amazon S3 bucket. The compliance team mandates a highly resilient storage architecture that protects against a total AWS Region outage. The disaster recovery plan dictates a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of under 15 minutes. Which storage strategy should a solutions architect implement to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon S3 Cross-Region Replication (CRR) to replicate objects to a destination S3 bucket in a secondary AWS Region, allowing the application to immediately access the replica bucket during a failover.

Cevap

Configure Amazon S3 Cross-Region Replication (CRR) to replicate objects to a destination S3 bucket in a secondary AWS Region, allowing the application to immediately access the replica bucket during a failover.
Amazon S3 Cross-Region Replication (CRR) replicates objects automatically and asynchronously to another AWS Region. This provides a low RPO (usually within seconds/minutes) and keeps the data in a standard S3 bucket, which allows immediate read access during a regional disaster (meeting the 15-minute RTO).

Adım Adım Çözüm

1
Analyze the disaster recovery constraints, specifically the 15-minute Recovery Time Objective (RTO) and 15-minute Recovery Point Objective (RPO) for object storage protection against a region outage.
Identified that the storage must be replicated across regions automatically (asynchronous replication) and the recovery destination must allow immediate read access without significant retrieval delays.
This narrows down the potential storage classes and replication modes to those that support automatic replication and immediate access.
2
Evaluate the replication mechanism of Amazon S3 Cross-Region Replication (CRR) against the constraints.
CRR continuously replicates new S3 objects to another region automatically (meeting low RPO) and stores them in a readable S3 bucket (allowing immediate access during a regional failover, meeting the 15-minute RTO).
This matches the objective of resilient and highly available cross-region storage.

Anahtar Kavram

Cross-Region Replication (CRR) provides automatic, asynchronous copying of S3 objects across AWS Regions to meet low RTO and RPO requirements for disaster recovery.
Soru 589Soru

A company is replicating large daily backups from their on-premises data center to Amazon S3. The data replication requires a consistent network throughput of at least 3 Gbps3\text{ Gbps} during peak transfer windows. Currently, the company uses a single AWS Site-to-Site VPN connection to AWS, but they are experiencing severe replication delays. Which solution should the solutions architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Establish a dedicated AWS Direct Connect connection with a capacity of 10 Gbps10\text{ Gbps} to route replication traffic directly to AWS.

Cevap

Establish a dedicated AWS Direct Connect connection with a capacity of 10 Gbps10\text{ Gbps} to route replication traffic directly to AWS.
Establishing an AWS Direct Connect connection provides a dedicated, private network connection from the on-premises data center to AWS. Direct Connect supports bandwidth options of 1 Gbps1\text{ Gbps}, 10 Gbps10\text{ Gbps}, or 100 Gbps100\text{ Gbps} (and sub-1 Gbps1\text{ Gbps} hosted connections), which easily accommodates the required 3 Gbps3\text{ Gbps} throughput without the overhead and limitations of the public internet or IPsec VPNs.

Adım Adım Çözüm

1
Identify the throughput requirement (3 Gbps3\text{ Gbps}) and the limitations of the current Site-to-Site VPN.
Recognized that a single VPN tunnel cannot support 3 Gbps3\text{ Gbps} due to its 1.25 Gbps1.25\text{ Gbps} throughput cap.
Determines why the current network setup is insufficient.
2
Evaluate alternative AWS hybrid networking solutions that support dedicated high-bandwidth throughput.
Identified AWS Direct Connect as a service that offers dedicated connections of 1 Gbps1\text{ Gbps}, 10 Gbps10\text{ Gbps}, or 100 Gbps100\text{ Gbps}.
Filters available services based on performance capabilities.
3
Select the configuration that meets the bandwidth requirement.
Choosing a 10 Gbps10\text{ Gbps} Direct Connect connection accommodates the 3 Gbps3\text{ Gbps} traffic comfortably with scalability for future growth.
Matches the workload requirements with the correct Direct Connect connection capacity.

Anahtar Kavram

AWS Direct Connect provides dedicated, high-throughput, private network connections to AWS, bypassing the internet and overcoming VPN bandwidth limits.
Soru 590Soru

A solutions architect is designing a solution to ingest real-time streaming data from web application logs and store the data in Amazon S3. The logs must be converted from JSON to Apache Parquet format before storage to optimize query performance in Amazon Athena. The architect wants to implement a fully managed, serverless solution with minimal operational overhead.

Which AWS service should the solutions architect use to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Amazon Data Firehose configured to deliver log data directly to Amazon S3 with data format conversion enabled.

Cevap

Amazon Data Firehose configured to deliver log data directly to Amazon S3 with data format conversion enabled.
The correct choice is the option that proposes Amazon Data Firehose with data format conversion. Amazon Data Firehose is a serverless, fully managed service designed to ingest streaming data and load it directly into Amazon S3. It natively supports converting incoming JSON data to Apache Parquet format using a schema defined in AWS Glue, without requiring any custom consumer applications or manual infrastructure scaling.

Adım Adım Çözüm

1
Identify the requirements for log data ingestion and storage.
The solution must ingest streaming data, store it in Amazon S3, transform JSON format to Parquet format, and require minimal operational overhead.
Understanding the core requirements helps eliminate solutions that require running custom server applications or manual infrastructure scaling.
2
Evaluate the capabilities of Amazon Data Firehose.
Amazon Data Firehose is serverless, fully managed, integrates with AWS Glue for schema-based format conversion (JSON to Parquet), and writes directly to Amazon S3.
This matches all criteria of high-performing ingestion, automated transformation, and minimal operational overhead.

Anahtar Kavram

Amazon Data Firehose provides serverless ingestion, transformation, and delivery of streaming data directly to destinations like Amazon S3, with built-in format conversion capabilities.
Soru 591Soru

A financial analytics platform runs a simulation engine on a fleet of 120 Linux EC2 instances. The simulation requires concurrent, shared access to a POSIX-compliant file system. The instances must read and write transient datasets simultaneously. During peak workloads, the simulation engine generates an aggregate write throughput of 6 GB/s6\text{ GB/s} (6,000 MB/s6,000\text{ MB/s}) and requires sub-millisecond metadata latencies. Which storage solution meets these performance requirements with the lowest operational complexity?

Cevabı ve açıklamayı göster

Cevap: Amazon FSx for Lustre scratch file system configured with the required capacity to deliver the target throughput, mounted on the instances using the Lustre client.

Cevap

Amazon FSx for Lustre scratch file system configured with the required capacity to deliver the target throughput, mounted on the instances using the Lustre client.
The correct answer is the Amazon FSx for Lustre scratch file system. Amazon FSx for Lustre is specifically engineered for high-performance computing (HPC) workloads and transient datasets, offering sub-millisecond latencies and the ability to scale throughput to tens of gigabytes per second. It provides a native POSIX-compliant interface and allows hundreds of Linux instances to access the shared data concurrently.

Adım Adım Çözüm

1
Analyze workload storage requirements.
Identify key requirements: concurrent read/write from 120 Linux instances, POSIX compliance, 6 GB/s6\text{ GB/s} write throughput, sub-millisecond latencies, and transient datasets.
Establishing the storage capabilities checklist eliminates non-conforming services.
2
Evaluate EBS Multi-Attach limitations.
EBS gp3 does not support Multi-Attach. EBS io1/io2 volumes support Multi-Attach but are restricted to 16 instances, failing the 120-instance requirement.
This rules out EBS-based block storage solutions.
3
Evaluate EFS throughput capabilities.
Amazon EFS write throughput caps out at 3 GiB/s3\text{ GiB/s} under Elastic Throughput mode, which is below the needed 6 GB/s6\text{ GB/s}.
This rules out Amazon EFS as a high-performance candidate for this write-heavy load.
4
Evaluate Amazon S3 mounting solutions.
Mountpoint for Amazon S3 is not a fully POSIX-compliant interface and lacks support for concurrent writes and file locking.
This rules out S3-based options for concurrent writing simulation nodes.
5
Select the correct FSx deployment.
Amazon FSx for Lustre scratch file systems are optimized for transient, high-performance workloads, supporting tens of GB/s of throughput and sub-millisecond latencies with POSIX compliance.
FSx for Lustre is the only solution that satisfies all throughput, latency, concurrency, and compliance requirements.

Anahtar Kavram

Selecting high-performance shared storage solutions based on throughput scale, protocol compliance, and concurrency constraints.
Soru 592Soru

A solutions architect is designing a storage system for a high-performance rendering application running on a cluster of Linux EC2 instances. The cluster requires concurrent read and write access to a shared file system that can scale throughput dynamically. Which storage options should the solutions architect recommend? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Amazon EFS configured with Provisioned Throughput mode; Amazon FSx for Lustre

Cevap

The correct configurations are Amazon EFS configured with Provisioned Throughput mode and Amazon FSx for Lustre.
The correct configurations are Amazon EFS with Provisioned Throughput mode and Amazon FSx for Lustre. Amazon EFS natively supports concurrent read and write access from multiple EC2 instances and allows users to provision throughput independently of the storage capacity. Amazon FSx for Lustre is explicitly designed for high-performance compute workloads like rendering, offering sub-millisecond latencies, massive throughput, and seamless integration with S3.

Adım Adım Çözüm

1
Identify the storage requirements
The application requires concurrent read/write access from a cluster of Linux EC2 instances, meaning a shared file system is needed.
Block storage like Amazon EBS cannot be natively mounted concurrently across multiple instances as a shared file system without complex clustering configurations or a dedicated file server.
2
Evaluate the sharing and scalability capabilities of the available options
Amazon EFS natively supports concurrent access and can scale throughput using Provisioned Throughput mode. Amazon FSx for Lustre is built specifically for high-performance workloads (like rendering) and concurrent access.
Both EFS and FSx for Lustre are designed as high-performing, scalable shared file systems.

Anahtar Kavram

Shared file systems with concurrent access and high performance
Tahmini Süre:1m 30s
Soru 593Soru

A healthcare provider is deploying a medical imaging application on Amazon EC2 instances across multiple Availability Zones in a primary AWS region. The application requires a shared file system that supports POSIX-compliant file operations and allows concurrent read and write access from all EC2 instances. Additionally, the provider requires a disaster recovery strategy to replicate this shared storage to a secondary AWS region with a Recovery Point Objective (RPO) of less than 15 minutes. Which combination of storage configurations will meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Elastic File System (Amazon EFS) file system in the primary region and mount it on the EC2 instances using EFS mount targets in each Availability Zone.; Enable Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary AWS region.

Cevap

The correct configuration is to create an Amazon EFS file system with mount targets in each Availability Zone in the primary region, and then configure Amazon EFS Replication to replicate file system data to a destination EFS file system in the secondary AWS region.
Creating an Amazon EFS file system in the primary region provides a scalable, highly available shared storage layer that can be concurrently mounted by EC2 instances across different Availability Zones. Configuring EFS Replication to a destination file system in the secondary region ensures automated cross-region replication that aligns with an RPO of less than 15 minutes.

Adım Adım Çözüm

1
Identify the file sharing and access requirements for the EC2 instances.
The application requires concurrent read and write access to a shared POSIX-compliant file system across multiple Availability Zones.
This points to Amazon EFS as the appropriate storage service, since standard block storage (Amazon EBS) does not support multi-AZ sharing, and object storage (Amazon S3) is not POSIX-compliant.
2
Select the cross-region disaster recovery mechanism that meets the RPO requirement.
The solution must replicate storage to a secondary region with an RPO of less than 15 minutes.
Amazon EFS Replication satisfies this by continuously replicating file system modifications to a destination EFS file system in the secondary region with a typical RPO of minutes.

Anahtar Kavram

Cross-region disaster recovery and high availability for shared file systems using Amazon EFS and EFS Replication.
Tahmini Süre:2m 0s
Soru 594Soru

A financial service provider is designing a real-time fraud detection and auditing solution. The solution must ingest transaction logs from millions of globally distributed POS terminals, with peak traffic reaching 15 MB/s15\text{ MB/s} and up to 15,00015,000 transactions per second. The transactions must be processed in the exact order they are received for each terminal to ensure accurate validation. The raw transactions must also be stored in Apache Parquet format on Amazon S3 with low operational overhead.

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

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

Cevabı ve açıklamayı göster

Cevap: Create an Amazon Kinesis Data Stream in Provisioned mode with 1515 shards, and write transactions using the terminal ID as the partition key.; Create an Amazon Data Firehose delivery stream with Amazon S3 as the destination, set the Kinesis Data Stream as the source, and enable data format conversion to Apache Parquet using an AWS Glue table.

Cevap

Create an Amazon Kinesis Data Stream in Provisioned mode with 1515 shards using the terminal ID as the partition key, and create an Amazon Data Firehose delivery stream using the Kinesis Data Stream as the source with inline conversion to Apache Parquet using AWS Glue.
To ingest transaction logs at a peak rate of 15 MB/s15\text{ MB/s} and 15,00015,000 transactions per second while maintaining strict order per terminal, an Amazon Kinesis Data Stream in Provisioned mode with at least 1515 shards is required. Using the terminal ID as the partition key ensures that records for each terminal are routed to the same shard in order. For the transformation and S3 delivery, Amazon Data Firehose can ingest from the Kinesis Data Stream and perform inline data format conversion to Apache Parquet using AWS Glue with minimal operational overhead.

Adım Adım Çözüm

1
Calculate the required ingestion throughput.
With a peak of 15 MB/s15\text{ MB/s} and 15,00015,000 transactions per second, and knowing that a single Kinesis shard supports 1 MB/s1\text{ MB/s} or 1,0001,000 records per second, the stream requires a minimum of 1515 shards.
Provisioning fewer shards will cause write throttling and data loss during peak times.
2
Ensure chronological order of transactions per terminal.
Using the terminal ID as the partition key ensures that all transactions from a specific terminal are sent to the same shard and processed in order.
A monotonically increasing timestamp key or generic keys would distribute the same terminal's transactions across multiple shards or cause hot shards, violating ordering.
3
Implement low-overhead transformation and delivery.
Configure Amazon Data Firehose with the Kinesis Data Stream as the source and S3 as the destination. Firehose automatically converts the incoming JSON data to Apache Parquet inline using an AWS Glue schema before writing to S3.
This serverless configuration scales dynamically and requires no custom code, minimizing operational overhead.

Anahtar Kavram

High-Performing Data Ingestion and Transformation Solutions
Soru 595Soru

A company wants to connect its on-premises corporate data center to an AWS VPC to support a database replication workload that requires a dedicated, private network bandwidth of 10 Gbps. The connection must completely bypass the public internet. 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: Establish a 10 Gbps AWS Direct Connect connection to the VPC.; Configure an AWS Direct Connect gateway to route traffic between the on-premises network and the VPC.

Cevap

Establish a 10 Gbps AWS Direct Connect connection to the VPC and configure an AWS Direct Connect gateway to route traffic between the on-premises network and the VPC.
To meet the 10 Gbps private bandwidth requirement while bypassing the public internet, AWS Direct Connect is the correct choice. Implementing a Direct Connect gateway allows routing of this connection to the target VPC.

Adım Adım Çözüm

1
Analyze the requirements for network connection type and bandwidth.
The requirement specifies a dedicated, private connection bypassing the public internet with a bandwidth of 10 Gbps.
This rules out AWS Site-to-Site VPN, which operates over the public internet and is limited to 1.25 Gbps per tunnel.
2
Select the appropriate connectivity service that supports the bandwidth.
AWS Direct Connect provides dedicated physical connections that support 10 Gbps configurations.
Direct Connect meets both the private connection requirement and the high-throughput bandwidth requirement.
3
Select the gateway component to connect the Direct Connect interface to the VPC.
An AWS Direct Connect gateway connects the Direct Connect location to the VPC.
A Direct Connect gateway is the standard architecture for routing traffic between the physical Direct Connect connection and the target VPC.

Anahtar Kavram

Bypassing the public internet with high-throughput hybrid connectivity using AWS Direct Connect and Direct Connect Gateway.
Soru 596Soru

A company wants to design a serverless data ingestion pipeline to collect real-time website clickstream data. The data must be transformed into a standardized format and stored in Amazon S3. The ingestion rate varies throughout the day, and the solution must scale automatically to handle traffic spikes with minimal operational overhead.

Which combination of AWS services should the company use to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Amazon Data Firehose to ingest the streaming data and load it into Amazon S3; An AWS Lambda function to perform data transformation within the delivery stream

Cevap

The combination of Amazon Data Firehose to ingest the streaming data and deliver it to Amazon S3, along with an AWS Lambda function to perform the inline data transformation.
The correct combination includes Amazon Data Firehose and AWS Lambda. Amazon Data Firehose provides a fully managed, automatically scaling streaming delivery service that writes directly to Amazon S3. By configuring Firehose to invoke an AWS Lambda function, you get a completely serverless, inline data transformation process with minimal operational overhead.

Adım Adım Çözüm

1
Select a serverless ingestion service that automatically scales to handle incoming stream data without manual shard management.
Amazon Data Firehose is selected because it is fully managed, scales automatically, and delivers directly to Amazon S3.
Firehose handles scaling and delivery natively with minimal operational overhead.
2
Select a serverless data transformation component that integrates with the ingestion stream.
AWS Lambda is selected because Firehose supports inline transformation via Lambda functions.
This allows for serverless format standardization before the data is written to the S3 bucket.

Anahtar Kavram

Serverless data ingestion and inline transformation with minimal operational overhead using Amazon Data Firehose and AWS Lambda.
Tahmini Süre:2m 0s
Soru 597Soru

A company is designing a highly resilient storage solution on AWS for its critical media assets. The assets must be protected against accidental deletion, and the architecture must ensure the assets are replicated to a secondary AWS Region to support a disaster recovery plan with a Recovery Time Objective (RTO) of less than 15 minutes. Which two configurations should a solutions architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure Amazon S3 Cross-Region Replication (CRR) to replicate objects to a bucket in the secondary AWS Region.; Enable Amazon S3 Versioning on the source and destination buckets.

Cevap

Configure Amazon S3 Cross-Region Replication (CRR) to replicate objects to a bucket in the secondary AWS Region, and enable Amazon S3 Versioning on the source and destination buckets.
To satisfy both requirements, the solutions architect must configure Amazon S3 Cross-Region Replication (CRR) and enable Amazon S3 Versioning. Versioning ensures that any deleted or overwritten files can be restored, while CRR automatically replicates the files to another AWS Region. Because the files are already copied, they are immediately accessible, keeping the Recovery Time Objective (RTO) well below 15 minutes.

Adım Adım Çözüm

1
Enable versioning on the S3 buckets.
S3 Versioning is active, protecting objects from being permanently deleted or overwritten accidentally by keeping historical versions of each object.
This directly satisfies the requirement to protect assets against accidental deletion.
2
Configure Cross-Region Replication (CRR) on the source bucket.
Automatic and asynchronous replication of newly uploaded media assets to the destination bucket in the secondary AWS Region is established.
This satisfies the cross-region disaster recovery requirement while maintaining low RTO because the files are pre-replicated and immediately accessible in the target region.

Anahtar Kavram

Designing highly available, durable, and cross-region resilient object storage with Amazon S3 Versioning and Cross-Region Replication (CRR).
Soru 598Soru

A smart utility company is designing a real-time data ingestion pipeline to monitor 500,000500,000 smart electricity meters. The meters transmit power consumption metrics every 1515 seconds, resulting in a total write throughput of 5 MB/s5 \text{ MB/s} and approximately 33,00033,000 records per second. The company has two requirements:

1. An anomaly detection application must process the incoming metrics and identify power spikes. To prevent false positives, the application must process the metrics from each individual meter in the exact order they were generated.
2. The raw data must be converted to Apache Parquet format and archived in Amazon S3 within 55 minutes of generation for historical analysis.

Which architecture should a solutions architect recommend to meet these requirements with the highest performance and the lowest operational overhead?

Cevabı ve açıklamayı göster

Cevap: Ingest the data into Amazon Kinesis Data Streams, using the smart meter ID as the partition key. Build the anomaly detection application to consume from the stream. Configure an Amazon Data Firehose delivery stream to read from the Kinesis Data Stream, use AWS Glue to convert the data format, and deliver the files to Amazon S3.

Cevap

Ingest the data into Amazon Kinesis Data Streams using the smart meter ID as the partition key, run the anomaly detection application as a consumer, and use Amazon Data Firehose with AWS Glue integration to deliver the data in Parquet format to Amazon S3.
Ingesting data into Amazon Kinesis Data Streams with the smart meter ID as the partition key ensures that all records for a specific meter are routed to the same shard, preserving the order of generation. The anomaly detection application can consume the ordered stream directly. Amazon Data Firehose can subscribe to the Kinesis Data Stream as a source, integrate with AWS Glue to convert JSON records to Parquet format, and batch-deliver them to Amazon S3 within the 5-minute requirement with minimal operational overhead.

Adım Adım Çözüm

1
Ensure ordered processing of events for each smart meter.
Using the smart meter ID as the partition key in Amazon Kinesis Data Streams ensures that all events for a specific meter are routed to the same shard, maintaining chronological order for that meter.
Kinesis Data Streams preserves ordering within a shard based on the partition key.
2
Select a high-throughput, near-real-time archiving mechanism to Amazon S3.
Configure Amazon Data Firehose to read from the Kinesis Data Stream and buffer data for delivery.
Firehose natively integrates with Kinesis Data Streams to batch and load data into S3 with minimal operational overhead.
3
Perform format conversion from JSON to Parquet during ingestion.
Integrate Amazon Data Firehose with the AWS Glue Data Catalog schema to automatically convert JSON records to Parquet before writing to S3.
This setup achieves the transformation requirement serverlessly, avoiding custom Lambda transformation overhead.

Anahtar Kavram

Partition keys in Amazon Kinesis Data Streams ensure message ordering per key while scaling throughput. Amazon Data Firehose can serverlessly transform stream data to Parquet using AWS Glue.
Tahmini Süre:2m 0s
Soru 599Soru

A company is designing a high-performance analytics ingestion pipeline for mobile application clickstream events. During peak hours, the application generates up to 50,00050,000 events per second, with an average event size of 1.5 KB1.5\text{ KB}. The events must be ingested with minimal latency, transformed from JSON to Apache Parquet format, partitioned by date and hour, and stored in Amazon S3 for query analysis using Amazon Athena. The solution must scale automatically to handle peak traffic spikes without manual intervention, ensure no data loss, and maintain an end-to-end delivery latency of under 55 minutes. Which two steps should the solutions architect recommend to implement this architecture?

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

Cevabı ve açıklamayı göster

Cevap: Ingest the incoming clickstream events using Amazon Kinesis Data Streams configured in On-Demand mode to automatically scale shard capacity in response to the peak throughput.; Configure Amazon Kinesis Data Firehose with the Kinesis Data Stream as the source, enable format conversion to Apache Parquet using an AWS Glue schema, and set the buffer interval to 300300 seconds before writing to Amazon S3.

Cevap

To build this high-performance ingestion and transformation architecture, the solutions architect should ingest the clickstream events using Amazon Kinesis Data Streams in On-Demand mode and configure Amazon Kinesis Data Firehose with the stream as the source to convert JSON to Parquet using AWS Glue with a 300300-second buffer interval.
The correct solution uses Amazon Kinesis Data Streams in On-Demand mode to handle the ingestion. Since peak throughput is 50,00050,000 events per second (75 MB/s75\text{ MB/s}), On-Demand mode is perfect as it automatically scales up to 200 MB/s200\text{ MB/s} and 200,000200,000 records per second. Amazon Kinesis Data Firehose can then be configured with the Kinesis Data Stream as its source, allowing it to natively convert the JSON payloads into Apache Parquet format using a schema from the AWS Glue Data Catalog. Setting the buffer interval to 300300 seconds guarantees that data is written to S3 within the 55-minute latency requirement.

Adım Adım Çözüm

1
Calculate the peak throughput requirement.
Peak traffic of 50,00050,000 events per second at 1.5 KB1.5\text{ KB} per event results in a write throughput of 75 MB/s75\text{ MB/s}.
Sizing the ingestion mechanism requires determining both the event rate and the aggregate bandwidth.
2
Evaluate Kinesis Data Streams capacity modes.
On-Demand mode is selected because it automatically scales up to 200 MB/s200\text{ MB/s} and 200,000200,000 records per second, handling the 50,00050,000 records/sec peak without manual shard provisioning.
Provisioned mode with static shard allocations (like 1515 shards) would throttle the stream, as 1515 shards support only 15,00015,000 records/sec.
3
Determine the transformation and destination mechanism.
Amazon Kinesis Data Firehose is configured to read directly from Kinesis Data Streams, transforming JSON payloads into Apache Parquet format using a schema from the AWS Glue Data Catalog before writing to Amazon S3.
Firehose provides serverless, inline format conversion, which eliminates the need to run custom compute tasks for data format transformation.
4
Configure the buffering configurations for the destination.
The buffer interval is configured to 300300 seconds.
This configuration ensures that data is written to S3 within the required 55-minute latency window while maximizing compression ratio.

Anahtar Kavram

High-throughput data ingestion using Kinesis Data Streams in On-Demand mode combined with serverless format transformation via Kinesis Data Firehose and AWS Glue.
Tahmini Süre:3m 0s
Soru 600Soru

A mobile gaming company uses Amazon CloudFront to deliver static game patch files to global users. The patch files are primarily served from an Application Load Balancer (ALB) backed by Amazon EC2 instances. To improve availability, the company has uploaded a backup copy of the patch files to an Amazon S3 bucket. The solutions architect must configure CloudFront to automatically serve files from the S3 bucket if the ALB is unavailable or returns 502 or 504 error codes.

Which two actions should the solutions architect take to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an origin group in the CloudFront distribution containing the Application Load Balancer as the primary origin and the Amazon S3 bucket as the secondary origin.; Configure the failover criteria in the CloudFront origin group to trigger on HTTP status codes 502 and 504.

Cevap

Create an origin group in the CloudFront distribution containing the Application Load Balancer as the primary origin and the Amazon S3 bucket as the secondary origin, and configure the failover criteria in the CloudFront origin group to trigger on HTTP status codes 502 and 504.
The correct solution involves creating a CloudFront origin group with the Application Load Balancer as the primary origin and the S3 bucket as the secondary origin. The failover criteria in the group must be configured to trigger on HTTP status codes 502 and 504. When CloudFront receives a 502 or 504 response from the ALB, it will transparently fail over to the S3 bucket to retrieve the content.

Adım Adım Çözüm

1
Identify the primary and secondary origins for the content delivery path.
The Application Load Balancer is identified as the primary origin, and the Amazon S3 bucket containing the backup files is identified as the secondary origin.
Establishing the roles of each origin is necessary before configuring failover mechanics.
2
Group the origins in the CloudFront distribution settings.
An origin group is created containing both the Application Load Balancer (primary) and the Amazon S3 bucket (secondary).
CloudFront requires origins to be grouped together to enable automatic failover behavior.
3
Specify the status codes that should trigger failover.
The failover criteria are configured to include 502 and 504 HTTP status codes.
This ensures that when the ALB returns these gateway errors, CloudFront redirects the request to the S3 bucket.

Anahtar Kavram

CloudFront Origin Failover using Origin Groups allows automatic redirection of client requests to a backup origin when the primary origin is unreachable or returns specified HTTP error status codes.
ÖncekiSayfa 30 / 74Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Associate | Examkin