Examkin

Tüm alıştırma soruları

1462 soru

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

A company has two VPCs in the same AWS Region: VPC A with CIDR block 10.0.0.0/1610.0.0.0/16 hosting client applications in a private subnet, and VPC B with CIDR block 192.168.0.0/16192.168.0.0/16 hosting a centralized directory service in another private subnet. A VPC Peering connection is active between VPC A and VPC B. The client applications in VPC A must query the directory service in VPC B on TCP port 389389. The security team requires a multi-layered security approach: network ACLs must secure the subnets (stateless), and security groups must secure the instances (stateful) to permit only this specific traffic. Which combination of actions will meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the network ACL for the client subnets in VPC A to allow outbound TCP port 389389 to the VPC B CIDR block, and allow inbound TCP traffic on ephemeral ports (1024−655351024-65535) from the VPC B CIDR block.; Configure the security group for the directory service instances in VPC B to allow inbound TCP port 389389 from the security group of the client applications in VPC A.

Cevap

Configure the network ACL for the client subnets in VPC A to allow outbound TCP port 389389 to the VPC B CIDR block, and allow inbound TCP traffic on ephemeral ports (1024−655351024-65535) from the VPC B CIDR block; and configure the security group for the directory service instances in VPC B to allow inbound TCP port 389389 from the security group of the client applications in VPC A.
The correct combination of actions consists of configuring the stateless network ACL in VPC A to permit outbound directory traffic on port 389389 and inbound return traffic on ephemeral ports (1024−655351024-65535), while setting the stateful security group on the destination instances in VPC B to accept inbound port 389389 connections from the clients.

Adım Adım Çözüm

1
Analyze the stateful nature of security groups at the instance level.
The directory service instances in VPC B require an inbound security group rule to permit TCP port 389389 from the client security group in VPC A. Since security groups are stateful, return traffic is allowed automatically.
Security groups operate at the instance level and automatically track connection state, allowing response traffic without explicit outbound rules.
2
Analyze the stateless nature of network ACLs at the subnet level.
The subnets in VPC A require a network ACL outbound rule to allow TCP port 389389 to VPC B, and an inbound rule to allow return traffic on ephemeral ports (1024−655351024-65535) from VPC B.
Network ACLs operate at the subnet level and are stateless, meaning return traffic must be explicitly permitted in the opposite direction.

Anahtar Kavram

VPC network security involves configuring stateful security groups at the instance level and stateless network ACLs at the subnet level, ensuring both inbound and return path traffic are appropriately allowed or denied.
Soru 102Soru →

A company serves its global API through Amazon EC2 instances behind Application Load Balancers (ALBs) in the us-east-1 and eu-west-1 Regions. Currently, Route 53 is configured with latency-based routing to distribute traffic across these regions. The company wants to establish an active-passive disaster recovery (DR) plan. If the application endpoints in both primary regions fail their health checks, Route 53 must automatically redirect all user traffic to a static maintenance webpage hosted in an Amazon S3 bucket in us-west-2. The recovery time objective (RTO) is under 10 minutes. Which Route 53 routing configuration should a solutions architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure latency-based alias records for a subdomain pointing to the ALBs in us-east-1 and eu-west-1, with 'Evaluate Target Health' set to Yes on both. Create a primary failover alias record for the primary domain pointing to the subdomain with 'Evaluate Target Health' set to Yes, and a secondary failover alias record pointing to the S3 static website endpoint.

Cevap

The correct configuration is to use nested Route 53 records where latency-based alias records for a subdomain point to the ALBs with 'Evaluate Target Health' set to Yes, combined with primary and secondary failover records at the apex domain level that propagate health check status.
The correct configuration uses nested records to combine active-active latency routing with active-passive failover routing. By pointing the primary failover alias record to the latency-based alias records, and enabling 'Evaluate Target Health' on both the parent failover record and the child latency records, Route 53 monitors the health of the ALBs. If the ALBs in both regions fail their health checks, Route 53 detects that the primary failover target is unhealthy and redirects traffic to the secondary failover record pointing to the S3 static website.

Adım Adım Çözüm

1
Identify the hybrid routing requirement.
The configuration requires active-active routing (latency-based) between the two active regions under normal operation, combined with active-passive failover to a static website on Amazon S3 during an outage.
This establishes the need for nested records because a single Route 53 record name cannot support both latency-based and failover routing policies simultaneously.
2
Design the active-passive failover record pair.
Create a primary failover alias record at the domain apex pointing to a nested subdomain, and create a secondary failover alias record pointing to the S3 static website endpoint.
This structures the DNS records so that traffic fails over to the backup S3 bucket only when the primary target group is deemed completely unhealthy.
3
Configure the nested active-active latency records with health check propagation.
Create latency-based alias records for the subdomain pointing to the respective regional ALBs, and enable 'Evaluate Target Health' on both the parent failover record and the child latency records.
Enabling 'Evaluate Target Health' on the child latency records ensures Route 53 monitors ALB health. Enabling it on the parent failover record ensures Route 53 checks the health of the subdomain targets and fails over to S3 if all underlying ALBs are unhealthy.

Anahtar Kavram

Route 53 active-passive failover can be configured over active-active latency-based routing by using nested alias records and enabling 'Evaluate Target Health' to propagate health status up the DNS record chain.
Soru 103Soru →

An energy utility company's smart grid platform processes real-time telemetry from millions of meters. The ingestion layer runs on a fleet of Amazon EC2 instances distributed across three Availability Zones. This tier requires a shared, highly available file storage layer that supports concurrent read/write access. Additionally, the company must retain raw data logs for 77 years to meet regulatory compliance, with an administrative requirement to retrieve any archived log within 1515 minutes.

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

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

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class to mount on the EC2 instances.; Store compliance logs in Amazon S3 and implement an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Instant Retrieval.

Cevap

The correct configurations are to mount an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class on the EC2 instances, and to store compliance logs in Amazon S3 with an S3 Lifecycle policy transitioning them to Amazon S3 Glacier Instant Retrieval.
The correct configurations involve using Amazon Elastic File System (Amazon EFS) and Amazon S3 Glacier Instant Retrieval. Amazon EFS provides a serverless, fully managed, shared file system that can be accessed concurrently by EC2 instances across multiple Availability Zones, ensuring high availability and resilience. For the archiving requirement, storing logs in Amazon S3 and transitioning them to Amazon S3 Glacier Instant Retrieval ensures the logs are cost-effectively stored for 77 years while maintaining the ability to retrieve them in milliseconds, meeting the RTO of 1515 minutes.

Adım Adım Çözüm

1
Analyze the file sharing requirement for the compute tier.
The EC2 fleet is distributed across three Availability Zones and requires concurrent read/write access to a shared file system.
This establishes that a regional shared file storage service like Amazon EFS is required, as standard EBS volumes cannot be shared across multiple Availability Zones.
2
Evaluate the compliance log retention and retrieval requirements.
Logs must be stored for 77 years with a retrieval time limit (RTO) of 1515 minutes.
This eliminates cold archive options like S3 Glacier Deep Archive standard retrievals, which take up to 1212 hours, and directs the solution toward S3 Glacier Instant Retrieval which offers millisecond access.
3
Verify service compatibility and limitations for the selected options.
Amazon EFS natively supports multi-AZ concurrent mounts. Amazon S3 Glacier Instant Retrieval satisfies both the long-term archiving requirement and the low RTO retrieval requirement.
This confirms that combining Amazon EFS and S3 Glacier Instant Retrieval provides a highly available, resilient, and compliant architecture.

Anahtar Kavram

Designing a resilient, multi-AZ shared file storage layer combined with a compliant, fast-retrieval archive solution.
Tahmini Süre:2m 0s
Soru 104Soru →

An enterprise company hosts its customer portal under the domain name portal.finance.example.com. The primary infrastructure consists of an Application Load Balancer (ALB) and EC2 instances in the us-east-1 region. The company wants to set up an active-passive disaster recovery strategy. If the primary region goes offline or if the primary database loses connectivity, traffic must automatically redirect to an Amazon S3 bucket in the us-west-2 region hosting a static maintenance page. A custom health-check script on the EC2 instances monitors the database connection status. Which two configurations should the solutions architect implement to achieve this goal? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB, set the routing category to Primary, enable Evaluate Target Health, and configure the ALB's target group health checks to monitor the custom health-check path.; Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2, set the routing category to Secondary, and configure the S3 bucket name to exactly match portal.finance.example.com.

Cevap

Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB (Primary with Evaluate Target Health enabled and target group health checks pointing to the custom path) and configure a Route 53 Failover record as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2 (Secondary with matching bucket name).
To implement active-passive failover, the architect should define a Route 53 Failover policy. The primary record is configured as an Alias record pointing to the Application Load Balancer (ALB) with 'Evaluate Target Health' enabled. This links Route 53's health decision to the ALB's target health status. The ALB's target group executes health checks against the custom script verifying database connectivity. The secondary record is also configured as a Failover Alias record pointing to the Amazon S3 static website endpoint. For Route 53 to resolve an Alias record directly to an S3 bucket, the S3 bucket name must match the domain name exactly.

Adım Adım Çözüm

1
Analyze the active-passive failover requirement and identify the correct Route 53 routing policy.
Determine that a Route 53 Failover routing policy is required, featuring a primary record for normal operations and a secondary record for the maintenance page.
Failover routing is the native Route 53 policy designed specifically for active-passive disaster recovery configurations.
2
Evaluate the health-checking requirement involving the primary application and the backend database.
Identify that enabling 'Evaluate Target Health' on the primary Route 53 Alias record will delegate health evaluation to the ALB. The ALB's target group must be configured to check the custom script path that verifies database connectivity.
If target instances fail the ALB's health check due to database loss, the ALB is marked unhealthy, causing Route 53 to failover to the secondary target.
3
Establish the secondary record pointing to the static maintenance site.
Configure a secondary Failover Alias record pointing to the Amazon S3 static website endpoint. Ensure the S3 bucket name matches the domain name exactly.
Route 53 requires the S3 bucket name to match the record name (portal.finance.example.com) for Alias record resolution to work correctly.

Anahtar Kavram

Amazon Route 53 DNS Failover and health check configuration for active-passive disaster recovery architectures.
Soru 105Soru →

A global logistics corporation runs a package tracking portal on AWS. The application serves static content (images, CSS, and JS files) stored in an Amazon S3 bucket, and dynamic tracking updates via an Application Load Balancer (ALB) that routes to an Amazon ECS cluster. During peak operations, the ECS cluster experiences high CPU utilization due to repetitive queries for identical, fast-changing tracking data. A solutions architect must design a high-performing content delivery and caching solution that minimizes latency for users globally while reducing the read load on both S3 and the ECS cluster. Which architecture should the solutions architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon CloudFront distribution with two cache behaviors. Route the path pattern for static assets to the Amazon S3 origin with a caching-optimized policy. Route the API path pattern to the ALB origin with caching enabled and a short Time-To-Live (TTL), using the package ID query string parameter as part of the cache key.

Cevap

Configure an Amazon CloudFront distribution with two cache behaviors: one routing static assets to the S3 origin with a caching-optimized policy, and another routing API requests to the ALB with caching enabled for a short duration using query string parameters.
The correct architecture uses Amazon CloudFront to optimize content delivery for both static and dynamic contents. By defining two cache behaviors, the solutions architect can apply a long, caching-optimized TTL for static assets stored in S3, and a short TTL (e.g., a few seconds) for the dynamic API requests directed to the ALB. Including the tracking package ID query parameter in the cache key ensures that requests for the same package are served from the cache, while requests for different packages generate distinct cache entries, reducing load on ECS.

Adım Adım Çözüm

1
Analyze the workload characteristics
The application serves two distinct traffic types: static web assets (images, CSS, JS) from S3, and dynamic queries (tracking updates) from an ECS backend via ALB.
Different traffic types require different caching policies to optimize hit ratios and prevent stale data.
2
Establish the edge caching layer using Amazon CloudFront
A single CloudFront distribution can target multiple origins (S3 for static assets and ALB for the API) using path-based behaviors.
Using CloudFront ensures global low-latency delivery by caching content at AWS edge locations close to users.
3
Configure the cache behavior for static assets
Map static paths to the S3 origin and apply a caching-optimized policy (long TTLs).
Static assets rarely change, so maximizing cache retention minimizes read requests to the origin S3 bucket.
4
Configure the cache behavior for dynamic tracking updates
Map API paths to the ALB origin. Enable caching with a short TTL (e.g., several seconds) and configure the package ID query string parameter to be included in the cache key.
A short TTL prevents stale tracking updates while absorbing high-concurrency spikes for identical package queries, drastically reducing CPU load on ECS.

Anahtar Kavram

Multi-tier caching using Amazon CloudFront cache behaviors for S3 and ALB origins to optimize performance and reduce backend load.
Tahmini Süre:2m 0s
Soru 106Soru →

An application developer is launching a new multiplayer gaming platform. The game must store player session states with single-digit millisecond read and write latency. The traffic is highly volatile and fluctuates throughout the day, experiencing sudden spikes during weekend tournaments. Which database configuration should a solutions architect recommend to support this workload while minimizing management overhead?

Cevabı ve açıklamayı göster

Cevap: Amazon DynamoDB configured with on-demand capacity mode and a high-cardinality partition key such as user ID

Cevap

Amazon DynamoDB configured with on-demand capacity mode and a high-cardinality partition key such as user ID
Amazon DynamoDB configured with on-demand capacity mode is ideal for workloads that are highly unpredictable and spiky, as it automatically scales read and write capacity in response to traffic. Using a high-cardinality partition key like user ID ensures that traffic is distributed evenly across multiple partitions, avoiding hot partitions and maintaining single-digit millisecond latency.

Adım Adım Çözüm

1
Analyze application requirements for latency and traffic patterns.
The application requires single-digit millisecond read/write latency with highly volatile and spiky traffic patterns.
This helps determine the database type (NoSQL/DynamoDB for single-digit millisecond performance) and the capacity scaling strategy.
2
Select the appropriate capacity mode for the unpredictable workload.
Amazon DynamoDB with on-demand capacity mode is chosen.
On-demand mode scales instantly to handle sudden spikes without manual intervention or risk of throttling.
3
Choose a partition key design to prevent performance bottlenecks.
A high-cardinality partition key like user ID is selected.
High-cardinality keys distribute read and write operations uniformly across partitions, avoiding performance-limiting hot partitions.

Anahtar Kavram

Designing high-performing, scalable NoSQL databases with Amazon DynamoDB by choosing the appropriate capacity mode and avoiding hot partition keys.
Soru 107Soru →

A financial company is deploying a distributed, high-throughput order matching engine on Amazon EC2 instances. The compute nodes require closely-coupled, low-latency node-to-node communication to synchronize order books. The matching engine application runs on a custom port of 8999. A Network Load Balancer (NLB) is configured to route client traffic to these nodes. The platform must scale dynamically while maintaining optimal network performance and ensuring the NLB accurately identifies healthy compute instances. 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: Launch the EC2 instances in a cluster placement group.; Configure the Network Load Balancer target group health check to use port 8999.

Cevap

Launch the EC2 instances in a cluster placement group, and configure the Network Load Balancer target group health check to use port 8999.
The correct options are launching the instances in a cluster placement group and configuring the health check port to 8999. A cluster placement group places instances physically close together within a single Availability Zone, enabling low-latency, 10 Gbps or 25 Gbps node-to-node throughput. Additionally, since the application runs on custom port 8999, the load balancer's target group health check must specifically target port 8999 to successfully determine instance health.

Adım Adım Çözüm

1
Analyze the network latency and throughput requirements between the EC2 compute nodes.
Identify that the distributed order matching engine requires closely-coupled, low-latency node-to-node communication.
This requirement points directly to placing the EC2 instances in a cluster placement group rather than spread or partition groups.
2
Determine the correct health check configuration for the load balancer.
Identify that the application runs on custom port 8999.
To prevent false negatives where healthy instances are marked unhealthy, the NLB target group health check must be explicitly configured to monitor port 8999 instead of default ports like 80.

Anahtar Kavram

High-performance EC2 configurations require cluster placement groups for low-latency node-to-node communication, and load balancer target group health check ports must match the application port.
Soru 108Soru →

A health technology company runs genomic analysis workloads. The pipeline generates intermediate workspace files averaging 800 MB800\text{ MB} in size. These files are written to an Amazon S3 bucket and accessed frequently by compute nodes for the first 1010 days. Between day 1010 and day 2424, the files are rarely accessed but must remain available for immediate verification. On day 2424, the files are completely obsolete and must be permanently deleted. Which of the following is the most cost-effective storage strategy for these files?

Cevabı ve açıklamayı göster

Cevap: Store the files in Amazon S3 Standard, and configure an S3 Lifecycle policy to delete the files after 2424 days.

Cevap

Storing the files in Amazon S3 Standard for the entire duration and configuring an S3 Lifecycle policy to delete them after 24 days is the most cost-effective strategy.
Storing the files in Amazon S3 Standard for the entire 2424-day duration is the most cost-effective option. Because the total lifespan of the files is less than 3030 days, any transition to S3 Standard-IA (either from the beginning or after 1010 days) triggers early deletion charges for the minimum storage duration requirement. Keeping the files in S3 Standard avoids retrieval fees, transition fees, and early deletion penalties.

Adım Adım Çözüm

1
Analyze the access pattern and retention requirements of the data.
The files are accessed frequently for the first 1010 days, rarely accessed for 1414 days, and must be deleted on day 2424. The total lifespan of the files is 2424 days.
This establishes the timeline and access patterns needed to evaluate storage class constraints.
2
Evaluate the constraints of Amazon S3 Standard-Infrequent Access (S3 Standard-IA) and S3 Glacier Flexible Retrieval.
S3 Standard-IA has a 3030-day minimum storage duration, and S3 Glacier Flexible Retrieval has a 9090-day minimum storage duration. Deleting files before these thresholds results in early deletion fees.
Understanding minimum storage durations is critical to calculating the real cost of transitioning short-lived data.
3
Calculate and compare the cost of keeping data in S3 Standard versus transitioning to S3 Standard-IA.
Keeping the data in S3 Standard for 2424 days is cheaper because transitioning to S3 Standard-IA on day 1010 and deleting on day 2424 triggers a 1616-day early deletion penalty (charging for 3030 days of IA storage total). This penalty, combined with transition fees, offsets the lower storage rate of S3 Standard-IA.
Mathematical comparison confirms that avoiding early deletion charges and transition fees makes the S3 Standard lifecycle policy the optimal choice.

Anahtar Kavram

Identifying early deletion charges and minimum storage duration constraints when designing S3 lifecycle policies.
Soru 109Soru →

A SaaS provider operates an analytics application on Amazon EC2 instances located in the private subnets of VPC A in the us-west-2 Region. The application performs two primary data transfer tasks: it writes approximately 10 TB10\text{ TB} of data per month to an Amazon DynamoDB table in the same Region, and it replicates 25 TB25\text{ TB} of processed analytics reports per month to a centralized database server in VPC B in the same Region. Currently, both traffic pathways are routed through NAT Gateways in VPC A, resulting in significant data processing charges. Which combination of architectural modifications will minimize data transfer costs? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a Gateway VPC Endpoint for Amazon DynamoDB in VPC A and associate it with the route tables of the private subnets.; Establish a VPC Peering connection between VPC A and VPC B, and configure the route tables to direct inter-VPC traffic over the peering connection.

Cevap

Creating a Gateway VPC Endpoint for Amazon DynamoDB in VPC A, and establishing a VPC Peering connection between VPC A and VPC B.
The correct options are to create a Gateway VPC Endpoint for Amazon DynamoDB and to establish a VPC Peering connection. Gateway VPC Endpoints are a free feature that allows private subnets to communicate with Amazon DynamoDB without traversing NAT Gateways, thus eliminating NAT Gateway data processing fees. VPC Peering allows direct network routing between VPC A and VPC B in the same Region without data processing fees, which is much more cost-effective than Transit Gateway routing.

Adım Adım Çözüm

1
Identify the current cost drivers in the network architecture.
The application is routing 10 TB10\text{ TB} of Amazon DynamoDB traffic and 25 TB25\text{ TB} of inter-VPC traffic through NAT Gateways, which charges high data processing fees of $0.045\$0.045 per gigabyte.
Understanding the cost breakdown of the current traffic path allows targeting the highest costs first.
2
Select the most cost-effective routing method for Amazon DynamoDB traffic.
Amazon DynamoDB supports Gateway VPC Endpoints, which route traffic privately without using NAT Gateways. Gateway VPC Endpoints are free of charge, whereas Interface VPC Endpoints (AWS PrivateLink) incur hourly and data processing fees of $0.01\$0.01 per gigabyte.
Using the free Gateway VPC Endpoint completely eliminates data processing fees for DynamoDB traffic.
3
Select the most cost-effective routing method for inter-VPC traffic between VPC A and VPC B in the same Region.
VPC Peering is direct and does not charge any data processing fees. AWS Transit Gateway charges $.06\$.06 per gigabyte of processed data, making it less cost-effective than VPC Peering for a simple two-VPC connection.
VPC Peering avoids the hourly and data processing overhead associated with Transit Gateways or NAT Gateways for regional inter-VPC traffic.

Anahtar Kavram

Cost-effective routing via Gateway VPC Endpoints and VPC Peering to avoid NAT Gateway and Transit Gateway data processing fees.
Soru 110Soru →

A genomic research institution hosts an analytics pipeline on Amazon EC2 instances in a private subnet of a VPC. The pipeline processes raw sequence data and uploads approximately 30 TB30\text{ TB} of processed datasets monthly to an Amazon S3 bucket within the same AWS Region. Currently, the subnet's route table routes all internet-bound and AWS service traffic through a NAT Gateway. The institution wants to significantly reduce its data transfer costs without making code changes to the pipeline or compromising the private status of the EC2 instances. Which architectural change will achieve the maximum cost reduction for this workload?

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.

Cevap

Create a Gateway VPC Endpoint for Amazon S3, and associate it with the route table of the private subnet.
Creating a Gateway VPC Endpoint for Amazon S3 is the most cost-effective solution. Gateway VPC Endpoints are available at no additional cost (no hourly charges and no data processing fees). By associating the endpoint with the private subnet's route table, traffic destined for S3 is routed directly through the AWS network using private IP addresses. This bypasses the NAT Gateway entirely, requires no changes to the application code, and maintains the private status of the EC2 instances.

Adım Adım Çözüm

1
Analyze the current data transfer route and the associated costs.
The private EC2 instances transfer 30 TB30\text{ TB} of data monthly to Amazon S3 through a NAT Gateway, which incurs a NAT Gateway data processing fee of 0.0450.045 USD per GB.
Identifying the root cause of the high data transfer costs requires analyzing the current network path.
2
Evaluate alternative private routing options for Amazon S3 traffic.
Gateway VPC Endpoints for Amazon S3 provide a direct, secure connection to S3 using private IP addresses. They do not charge hourly fees or per-GB data processing fees.
Choosing the most cost-effective alternative requires comparing the pricing models of NAT Gateway, Interface VPC Endpoints, and Gateway VPC Endpoints.
3
Configure the route table to redirect the traffic.
Associate the Gateway VPC Endpoint with the private subnet's route table. This adds a route pointing to the S3 prefix list with the Gateway Endpoint as the target.
Associating the endpoint with the route table ensures that all S3 traffic from the subnet bypasses the NAT Gateway automatically without requiring application code changes.

Anahtar Kavram

Gateway VPC Endpoints provide free, private routing to Amazon S3 and DynamoDB.
Soru 111Soru →

A security monitoring firm is designing an ingestion pipeline for 15,00015,000 smart security cameras. The cameras generate a combined peak of 6,0006,000 motion detection events per second, with each event payload being a 2.5 KB2.5\text{ KB} JSON object. The company requires that events from each camera be processed in the exact order they are generated to maintain a chronological timeline. The data must be transformed into Apache Parquet format and stored in Amazon S3 for ad-hoc querying via Amazon Athena. The ingestion latency from event generation to storage in Amazon S3 must be less than 55 minutes, and the solution should minimize operational management. Which architecture meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Ingest the data into an Amazon Kinesis Data Stream configured with On-Demand capacity, using the camera ID as the partition key. Configure Amazon Data Firehose to consume the data from the stream, convert the format to Apache Parquet using the AWS Glue Schema Registry, and write the output to Amazon S3 with a buffer interval of 300 seconds.

Cevap

Ingest the data into an Amazon Kinesis Data Stream configured with On-Demand capacity, using the camera ID as the partition key, and use Amazon Data Firehose to perform format conversion and delivery to Amazon S3 with a 300-second buffer interval.
The correct architecture uses Amazon Kinesis Data Streams with On-Demand capacity to ingest high-velocity data. Using the camera ID as the partition key ensures that all events for a given camera are mapped to the same shard, which guarantees in-order delivery. Amazon Data Firehose integrates directly with Kinesis Data Streams, scales automatically, performs native JSON-to-Parquet conversion using the AWS Glue Schema Registry, and writes to Amazon S3 within the 5-minute latency requirement, minimizing both operational overhead and infrastructure management.

Adım Adım Çözüm

1
Calculate the peak data throughput and record rate to determine scale requirements.
The total throughput is 6,000 records/sec×2.5 KB=15,000 KB/s6,000 \text{ records/sec} \times 2.5\text{ KB} = 15,000\text{ KB/s} (or 15 MB/s15\text{ MB/s}), with a total of 6,0006,000 records per second.
This calculation determines the necessary scaling capacity for the ingestion stream.
2
Choose the streaming ingestion service that supports scale and strict ordering.
Amazon Kinesis Data Streams with the camera ID as the partition key. Kinesis Data Streams On-Demand automatically scales up to 200 MB/s200\text{ MB/s} and 200,000200,000 records/sec, and partition keys guarantee ordering per camera.
Ensures that the pipeline does not throttle during peak traffic and preserves the required chronological sequence.
3
Select a serverless delivery and transformation mechanism.
Amazon Data Firehose with native AWS Glue schema conversion, configured with a 300-second buffer interval writing to Amazon S3.
Allows direct conversion of JSON to Parquet format without provisioning server resources, while adhering to the 5-minute ingestion latency window.

Anahtar Kavram

High-performing real-time data ingestion pipelines must dynamically scale to meet peak throughput while satisfying operational simplicity and strict message ordering constraints by using Amazon Kinesis Data Streams with partition keys coupled with Amazon Data Firehose for format transformation.
Soru 112Soru →

A company hosts a data processing application on Amazon EC2 instances in a private subnet. The application downloads 50 TB50\text{ TB} of raw data monthly from Amazon S3, processes the data, and writes the metadata to an Amazon DynamoDB table. The EC2 instances must also periodically access the public internet to download software updates. Currently, all outbound traffic from the private subnet routes through a NAT gateway. A solutions architect must optimize the network routing to reduce data transfer and processing costs. 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 a gateway VPC endpoint for Amazon S3 and associate it with the private subnet's route table.; Create a gateway VPC endpoint for Amazon DynamoDB and associate it with the private subnet's route table.

Cevap

The solutions architect should create a gateway VPC endpoint for Amazon S3 and a gateway VPC endpoint for Amazon DynamoDB, associating both with the private subnet's route table.
Creating gateway VPC endpoints for both Amazon S3 and Amazon DynamoDB and associating them with the subnet's route table is the most cost-effective solution. Gateway endpoints do not incur hourly or data processing charges, keeping the high-volume data transfers (50 TB50\text{ TB}) free. The NAT gateway is kept in place to handle low-volume outbound traffic for external software updates.

Adım Adım Çözüm

1
Analyze current network flow and identify cost bottlenecks.
All traffic to Amazon S3 (50 TB50\text{ TB}) and Amazon DynamoDB is flowing through the NAT gateway, incurring high data processing charges ($0.045 per GB).
Traffic to public AWS services from private subnets defaults to the NAT gateway if endpoints are not configured.
2
Identify cost-effective alternatives for internal AWS service communication.
Gateway VPC endpoints are free of charge and provide direct routing to Amazon S3 and Amazon DynamoDB within the same Region.
Gateway endpoints bypass NAT gateways and route traffic privately over the AWS network backbone, eliminating processing fees.
3
Evaluate the remaining internet traffic requirements.
EC2 instances still require the NAT gateway for software updates from external repositories.
Gateway VPC endpoints only route traffic to S3 and DynamoDB; other public internet traffic continues using the NAT gateway routing path.

Anahtar Kavram

Gateway VPC Endpoints for S3 and DynamoDB
Tahmini Süre:2m 0s
Soru 113Soru →

An e-commerce startup is launching a temporary promotional microservice that expects highly unpredictable, bursty traffic with long periods of zero activity. The development team wants to deploy a relational database and a non-relational database to support this microservice while minimizing costs. Which TWO of the following configurations are the most cost-effective database capacity choices for these workloads? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Amazon DynamoDB configured with on-demand capacity mode for the non-relational database; Amazon Aurora Serverless v2 for the relational database to scale capacity automatically based on database usage

Cevap

Amazon DynamoDB configured with on-demand capacity mode for the non-relational database, and Amazon Aurora Serverless v2 for the relational database to scale capacity automatically based on database usage.
For highly unpredictable workloads with long periods of zero activity, serverless options provide the best cost optimization. Amazon DynamoDB on-demand capacity mode eliminates the need to estimate throughput and does not charge for read/write capacity when there is no traffic. Amazon Aurora Serverless v2 dynamically scales capacity units in response to active database usage, minimizing costs during idle periods compared to running provisioned DB instances.

Adım Adım Çözüm

1
Analyze the workload characteristics and requirements.
The microservice has highly unpredictable, bursty traffic with long periods of zero activity, and requires both relational and non-relational databases.
Identifying the workload profile is necessary to choose the correct database capacity and scaling modes.
2
Evaluate the capacity options for the non-relational database.
Amazon DynamoDB on-demand capacity mode charges only for active read/write requests and has zero cost when idle.
Provisioned capacity mode (even with auto-scaling) incurs continuous baseline charges and cannot scale to zero, making it inefficient for this workload.
3
Evaluate the capacity options for the relational database.
Amazon Aurora Serverless v2 automatically scales capacity dynamically based on demand to reduce costs during low-use periods.
Provisioned RDS instances with read replicas maintain active compute instances that charge continuously, even during idle hours.

Anahtar Kavram

Selecting serverless capacity modes (DynamoDB On-Demand and Aurora Serverless) is the most cost-effective approach for highly unpredictable, bursty database workloads with periods of zero activity.
Soru 114Soru →

A research institute runs a weather forecasting engine that performs real-time computational fluid dynamics simulations on Amazon EC2. The compute nodes must communicate with each other using low-latency, high-throughput network paths. The simulation service listens on TCP port 8080, and the traffic is managed by a Network Load Balancer.

Which combination of configuration steps should a solutions architect perform? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the compute instances inside a cluster placement group; Set the Network Load Balancer target group health check port to 8080

Cevap

To meet the requirements, the solutions architect should deploy the compute instances inside a cluster placement group to achieve maximum network performance and low latency. Additionally, the solutions architect must set the Network Load Balancer target group health check port to 8080 to ensure health checks correctly monitor the application running on the custom port.
Deploying the compute instances inside a cluster placement group ensures that the instances are physically located close to each other on the underlying hardware, minimizing network latency and maximizing throughput. Additionally, setting the Network Load Balancer target group health check port to 8080 ensures that the health checks monitor the actual port where the simulation service is listening, preventing healthy instances from being incorrectly marked as unhealthy.

Adım Adım Çözüm

1
Analyze the network requirement
The application requires low-latency and high-throughput node-to-node communication, which is best achieved via a cluster placement group.
Cluster placement groups group instances close together within a single Availability Zone, providing high network bandwidth and low latency.
2
Analyze the application port configuration
The application listens on TCP port 8080, meaning health checks must query port 8080 to check service health.
If health checks are sent to the default port (80) where nothing is listening, the load balancer will mark all targets as unhealthy.

Anahtar Kavram

Selecting cluster placement groups for low-latency node-to-node networking, and matching ELB health check ports to custom application listening ports.
Soru 115Soru →

A digital real estate enterprise operates a property document management portal on AWS. The portal hosts critical PDF appraisal reports and legal deeds that require 99.999999999%99.999999999\% (11 nines) of data durability. These documents are frequently accessed during the first 3030 days of a listing. After this period, they are rarely accessed, but agents must be able to retrieve them in real-time (latency under 11 second) during client meetings, establishing a Recovery Time Objective (RTO) of less than 1010 seconds. The architecture must remain highly available (99.9%99.9\% availability) and resilient to the loss of an entire AWS Availability Zone (AZ). Which storage strategy meets these requirements most cost-effectively?

Cevabı ve açıklamayı göster

Cevap: Store the files in Amazon S3 Standard. Use an S3 Lifecycle policy to transition the files to Amazon S3 Glacier Instant Retrieval after 3030 days.

Cevap

Store the files in Amazon S3 Standard. Use an S3 Lifecycle policy to transition the files to Amazon S3 Glacier Instant Retrieval after 30 days.
Amazon S3 Glacier Instant Retrieval is designed for archiving data that is rarely accessed but requires millisecond retrieval times when requested. It provides the same 11 nines of durability and availability across multiple Availability Zones as S3 Standard, meeting all resilience and RTO constraints while optimizing costs.

Adım Adım Çözüm

1
Analyze durability, availability, and recovery requirements.
The system requires 99.999999999%99.999999999\% durability, 99.9%99.9\% availability, multi-AZ resilience, and real-time retrieval (latency under 11 second) after 3030 days.
This establishes the constraints for choosing the appropriate storage tier.
2
Evaluate Amazon S3 storage classes against RTO requirements.
Amazon S3 Standard and Amazon S3 Glacier Instant Retrieval both offer 99.999999999%99.999999999\% durability and multi-AZ resilience. S3 Glacier Instant Retrieval provides retrieval in milliseconds, satisfying the RTO.
Standard Glacier classes like Glacier Flexible Retrieval take hours to retrieve data and cannot meet the real-time access requirement.
3
Compare cost-effectiveness.
S3 Glacier Instant Retrieval has a lower storage cost than S3 Standard, making it the most cost-effective choice for rarely accessed documents that require immediate access.
Using S3 Lifecycle policies to automate the transition minimizes costs without manual intervention.

Anahtar Kavram

Selecting resilient and cost-effective AWS storage classes based on RTO and retrieval latency requirements
Tahmini Süre:1m 30s
Soru 116Soru →

A media company hosts a popular blogging platform on AWS. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). Static images are stored in an Amazon S3 bucket, and dynamic blog posts are stored in an Amazon RDS for MySQL database. During peak hours, the database experiences high CPU utilization due to a high volume of read queries for popular posts, and user page load times increase.

Which combination of actions will reduce the load on the primary database and improve content delivery performance? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon ElastiCache cluster to cache frequent query results from the Amazon RDS database.; Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin to cache static images.

Cevap

Deploy an Amazon ElastiCache cluster to cache frequent query results from the Amazon RDS database, and configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin to cache static images.
Deploying an Amazon ElastiCache cluster caches dynamic database query results in-memory, resolving the RDS database read bottleneck and lowering latency. In parallel, configuring an Amazon CloudFront distribution caches static images at edge locations, offloading traffic from S3 and improving global delivery speed.

Adım Adım Çözüm

1
Analyze the bottlenecks in the current architecture.
The application suffers from high CPU utilization on the RDS MySQL database due to repetitive read queries, and static image delivery from S3 needs acceleration.
Identifying the distinct database read bottleneck and static content delivery bottleneck allows for targeted caching strategies.
2
Select the caching solution for database queries.
Amazon ElastiCache is selected to cache frequent SQL query results.
By serving repetitive queries from in-memory cache, the primary RDS database is relieved of read load, lowering its CPU utilization.
3
Select the content delivery solution for static assets.
Amazon CloudFront is selected to cache and distribute the static images stored in S3.
CloudFront edge locations cache static images closer to users, improving load times and offloading traffic from S3.

Anahtar Kavram

Multi-tier caching using Amazon ElastiCache for database query results and Amazon CloudFront for static asset content delivery.
Soru 117Soru →

A digital media agency is building a collaborative video editing platform on AWS. The editing application runs on a fleet of Amazon EC2 instances distributed across multiple Availability Zones in a single AWS Region. The instances require concurrent read and write access to a shared file workspace with sub-millisecond latencies. Additionally, the agency must archive completed video projects to minimize storage costs. In the event of a disaster, the archived files must be fully recoverable within a Recovery Time Objective (RTO) of 10 minutes. Which combination of storage solutions should a solutions architect recommend?

Cevabı ve açıklamayı göster

Cevap: Use Amazon EFS for the active collaborative workspace. Store the archived projects in Amazon S3 Glacier Flexible Retrieval and use Expedited retrievals during disaster recovery.

Cevap

Use Amazon EFS for the active collaborative workspace. Store the archived projects in Amazon S3 Glacier Flexible Retrieval and use Expedited retrievals during disaster recovery.
Amazon EFS is a managed, shared file system that supports simultaneous read and write connections from multiple EC2 instances across multiple Availability Zones in a Region. It provides sub-millisecond latencies, which fits the active collaboration requirements. For the archival tier, Amazon S3 Glacier Flexible Retrieval using Expedited retrievals satisfies the 10-minute Recovery Time Objective (RTO) because it typically restores data within 1 to 5 minutes, while maintaining a lower storage cost relative to S3 Standard.

Adım Adım Çözüm

1
Analyze the active workspace storage requirements.
Identify that the storage must support concurrent read/write access from EC2 instances across multiple Availability Zones with sub-millisecond latency. Amazon EFS is a native POSIX-compliant shared file system that meets these requirements.
EBS volumes cannot be attached across multiple Availability Zones, and EBS Multi-Attach is limited to a single Availability Zone and only supported on io1/io2 volumes, not gp3.
2
Evaluate the archive storage retrieval options against the disaster recovery requirements.
The target RTO is 10 minutes. S3 Glacier Flexible Retrieval with Expedited retrievals recovers data in 1 to 5 minutes, which falls within the 10-minute threshold. Standard retrievals for Glacier Flexible Retrieval (3-5 hours) and Glacier Deep Archive (12 hours) are too slow.
Choosing the correct Glacier retrieval tier is critical to meeting strict RTOs while minimizing long-term archival costs.
3
Assess the cost optimization constraints.
Verify that deleting objects early in S3 Standard-IA is cost-prohibitive due to the 30-day minimum billing charge. EFS for hot data and S3 Glacier Flexible Retrieval with Expedited retrievals for cold data represents the most cost-effective and resilient architecture.
Avoiding S3 IA minimum duration penalties helps satisfy the requirement to minimize storage costs.

Anahtar Kavram

Selecting highly available and resilient shared storage (Amazon EFS) combined with fast-recovery archival solutions (S3 Glacier with Expedited retrievals) to satisfy concurrent access, Multi-AZ availability, and tight RTO limits.
Tahmini Süre:1m 30s
Soru 118Soru →

A telehealth provider runs a medical imaging and patient record application on AWS. The application tier runs on a fleet of Amazon EC2 instances distributed across multiple Availability Zones in a single AWS Region. The application requires a shared storage layer to host patient medical images. This storage layer must allow concurrent read and write access from all EC2 instances. The architecture must achieve high availability with a Recovery Point Objective (RPO) of 0 and a Recovery Time Objective (RTO) of less than 1 minute against an Availability Zone outage. For compliance, the images must also be replicated to a secondary AWS Region. In the event of a disaster in the primary Region, the secondary Region must be able to serve the images with a recovery time (RTO) of less than 5 minutes. Which two configurations should a solutions architect recommend to build a resilient storage solution? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Use an Amazon EFS file system configured with the EFS Regional storage class in the primary Region.; Configure Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary Region.

Cevap

The correct configurations are to use an Amazon EFS file system with the EFS Regional storage class in the primary Region, and to configure Amazon EFS Replication to replicate the file system to a destination EFS file system in the secondary Region.
The correct options are to use an Amazon EFS file system with the Regional storage class and to configure Amazon EFS Replication. EFS Regional storage class stores data redundantly across multiple Availability Zones in a single Region, ensuring that even if one Availability Zone fails, the file system remains online with no data loss (RPO = 0, RTO < 1 minute) and allows concurrent access from all application instances. Amazon EFS Replication replicates data across AWS Regions continuously in near real-time, allowing the destination file system to be immediately writable during a failover with a recovery time of less than 5 minutes.

Adım Adım Çözüm

1
Evaluate the requirement for shared, concurrent storage access across multiple Availability Zones in the primary Region.
Identify that Amazon EFS with the Regional storage class is designed for multi-AZ concurrent file access with high availability.
Amazon EFS Regional replicates data across multiple AZs and allows concurrent read/write from EC2 instances in different AZs, satisfying RPO=0 and low RTO.
2
Analyze the cross-Region disaster recovery requirements (RTO < 5 minutes).
Determine that Amazon EFS Replication continuously synchronizes EFS file systems across Regions with minimal latency.
EFS Replication provides a destination file system that is immediately ready during failover, satisfying the sub-5-minute RTO.
3
Examine the recovery time constraints of alternative storage tiers like S3 Glacier and EBS.
Eliminate options utilizing S3 Glacier Standard Retrieval due to hours-long retrieval delays, and eliminate EBS due to single-AZ limits and manual recovery times.
Meeting strict low RTO and RPO requirements necessitates active replication rather than slow restore processes or single-AZ block storage.

Anahtar Kavram

Implementing resilient, shared multi-AZ file storage using Amazon EFS with cross-Region replication to meet low RTO and RPO targets.
Soru 119Soru →

A company hosts a stateful transaction processing application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to set up an active-passive disaster recovery (DR) configuration using a secondary scaled-down environment behind an ALB in the eu-west-1 Region. The DR plan requires automatic failover to the secondary region if the primary region's application or its underlying database becomes unavailable. To avoid database write conflicts, the application in the secondary region must not receive traffic unless a failover is active. Which two configurations should a solutions architect implement to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Route 53 Failover routing alias records pointing to the ALB in each region, and set the Evaluate Target Health option to Yes on both records.; Configure the primary Application Load Balancer (ALB) target group health check to query a deep path (such as /health) that verifies database connectivity, so targets are marked unhealthy if the database is offline.

Cevap

The correct configurations are to set up Route 53 Failover routing alias records with Evaluate Target Health enabled, and to implement a deep health check endpoint on the primary Application Load Balancer target group to verify database availability.
To implement a resilient active-passive configuration, the solutions architect should use Route 53 Failover routing records. These records must be configured as Alias records pointing to the respective Application Load Balancers (ALBs) to support the Evaluate Target Health feature. Additionally, because the database status dictates the availability of this stateful application, a deep health check endpoint (like /health) must be configured on the primary ALB's target group. This ensures that a database failure marks the targets and the load balancer as unhealthy, prompting Route 53 to trigger failover.

Adım Adım Çözüm

1
Determine the routing policy that meets the active-passive constraint.
Route 53 Failover routing policy is the correct choice, as it ensures traffic is directed to the primary region and only switches to the secondary region if the primary becomes unhealthy. Policies like Latency routing are active-active and do not satisfy this requirement.
Active-passive routing is required to prevent write conflicts on a stateful database.
2
Select the correct DNS record type to enable Route 53 health monitoring of AWS resources.
Route 53 Alias records must be used because they natively support the 'Evaluate Target Health' option, which queries the ALB health. Standard CNAME records do not support this feature.
Ensuring the correct record type is used is critical for integrating DNS routing with resource health status.
3
Determine how Route 53 will detect database-level failures.
Configure the ALB target group health check to hit a '/health' endpoint that runs a query against the database. When the database is offline, the EC2 targets fail the check, the ALB becomes unhealthy, and Route 53 detects this via the Evaluate Target Health setting.
Standard ALB target group checks only verify if the web server is listening, which would miss database outages.

Anahtar Kavram

Route 53 active-passive failover requires Failover routing alias records combined with deep application health checks on the load balancer's targets.
Tahmini Süre:2m 0s
Soru 120Soru →

A sports media company is building a real-time leaderboard and voting system for a global event. The application needs to handle millions of concurrent users. The system must support sub-millisecond latency for retrieving leaderboard data, up to 50,00050,000 write operations per second during peak voting windows, and the ability to scale capacity dynamically to handle spiky workloads. The system must also mitigate write bottlenecks for highly popular candidates. Which TWO strategies should a solutions architect implement to design a high-performing database architecture? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon DynamoDB Accelerator (DAX) in front of the database table to cache read requests and offload query volume.; Implement write sharding by appending a random integer suffix to the candidate ID partition key when writing voting transactions to Amazon DynamoDB.

Cevap

The correct strategies are to deploy Amazon DynamoDB Accelerator (DAX) to cache read requests and implement write sharding by appending a random integer suffix to the candidate ID partition key when writing voting transactions.
The correct strategies are implementing DynamoDB Accelerator (DAX) and write sharding. Caching with DAX offloads read traffic and provides microsecond-level latency, meeting the sub-millisecond retrieval requirement. Write sharding by appending a random suffix to the candidate ID distributes the voting writes across multiple partitions, preventing a write bottleneck on the popular candidate keys.

Adım Adım Çözüm

1
Analyze the performance requirements for reads.
Reads require sub-millisecond latency. Standard database queries typically operate in the millisecond range.
DynamoDB Accelerator (DAX) is selected because it provides microsecond latency caching for read-heavy workloads.
2
Analyze the write requirements and key distribution.
Writes peak at 50,00050,000 operations per second, targeting popular candidates. This will cause hot partitions if using a standard candidate ID as the partition key.
Write sharding (appending a random suffix to the partition key) is required to distribute the write load across multiple partitions.
3
Evaluate and eliminate incorrect database options.
Monotonically increasing keys cause hot partitions; Aurora replicas do not scale writes; static provisioned capacity cannot handle spiky traffic efficiently.
Eliminating these options ensures the architecture remains performant, cost-effective, and aligned with AWS best practices.

Anahtar Kavram

Mitigating hot partitions via write sharding and caching read-heavy tables using DAX to achieve low-latency, high-throughput scaling.
ÖncekiSayfa 6 / 74Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Associate | Examkin