Tüm alıştırma soruları

931 soru

Soru 1Soru

An enterprise is designing a centralized logging solution to aggregate VPC Flow Logs from 80 member accounts in an AWS Organization. A solutions architect is tasking with configuring the delivery of these flow logs to a single Amazon S3 bucket located in a dedicated Security account. The S3 bucket must be encrypted at rest. Which TWO of the following configurations are required to ensure the flow logs can be successfully delivered to the centralized S3 bucket?

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

Cevabı ve açıklamayı göster

Cevap: Configure the Amazon S3 bucket policy in the Security account to allow s3:PutObject and s3:GetBucketAcl actions for the delivery.logs.amazonaws.com service principal.; Encrypt the Amazon S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and update the KMS key policy to allow the delivery.logs.amazonaws.com service principal to use the key.

Cevap

Configure the destination S3 bucket policy to allow permissions for the delivery.logs.amazonaws.com service principal, and encrypt the bucket using a Customer Managed Key in AWS KMS with a key policy that allows the delivery.logs.amazonaws.com service principal to use the key.
For cross-account VPC Flow Logs delivery, the S3 bucket policy must allow the delivery.logs.amazonaws.com service principal to perform s3:PutObject and s3:GetBucketAcl actions. Furthermore, if the bucket is encrypted, a Customer Managed Key must be used because AWS managed KMS keys cannot be configured with custom policies to allow service principal access.

Adım Adım Çözüm

1
Configure S3 bucket policy permissions for log delivery
The S3 bucket in the Security account now accepts writes from the VPC Flow Logs delivery service.
Since VPC Flow Logs are delivered via a service principal rather than IAM roles, the bucket policy must explicitly permit the delivery.logs.amazonaws.com principal.
2
Create and configure a Customer Managed Key (CMK) in AWS KMS
A CMK is created with a key policy allowing the delivery.logs.amazonaws.com service principal to perform kms:GenerateDataKey*.
AWS-managed KMS keys do not support key policy modifications and cannot be shared. A Customer Managed Key is required to permit the cross-account log delivery service to write encrypted data to the bucket.

Anahtar Kavram

Centralized VPC Flow Logs delivery to a cross-account S3 bucket requires configuring the bucket policy and KMS key policy to permit the log delivery service principal.
Tahmini Süre:1m 30s
Soru 2Soru

A gaming platform is launching a new multiplayer architecture in the `us-west-2` Region. The platform architecture requires two application VPCs (`vpc-game-prod-a` and `vpc-game-prod-b`) and one administrative management VPC (`vpc-mgmt-prod`). The management VPC hosts a Route 53 Private Hosted Zone (PHZ) `backend.gaming.internal` containing service endpoints that the application VPCs must resolve privately. The application VPCs must also access the internet for software updates through a centralized egress VPC (`vpc-egress-prod`) to minimize costs, but the egress path must survive a single Availability Zone (AZ) outage without disrupting egress traffic from unaffected AZs. Additionally, the game VPCs and management VPC must communicate with an on-premises graphics rendering cluster via a 10 Gbps AWS Direct Connect connection. Which TWO options should the Solutions Architect implement to satisfy these networking and DNS requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway (`tgw-main`) and attach `vpc-game-prod-a`, `vpc-game-prod-b`, and `vpc-egress-prod`. In `vpc-egress-prod`, deploy a NAT Gateway in Availability Zone `us-west-2a` and another in `us-west-2b`. In the subnet route tables for the Transit Gateway attachment in `vpc-egress-prod`, configure the route for `0.0.0.0/0` to point to the NAT Gateway in the respective Availability Zone. Configure the Transit Gateway route table associated with the game VPCs to route `0.0.0.0/0` to the `vpc-egress-prod` attachment.; In the management account, create a cross-account VPC association authorization for `vpc-game-prod-a` and `vpc-game-prod-b` to the Private Hosted Zone `backend.gaming.internal`. In each game account, associate the respective game VPC with the Private Hosted Zone using the AWS CLI or API.

Cevap

Deploy an AWS Transit Gateway and establish a centralized egress VPC with redundant NAT Gateways configured with AZ-specific routing, combined with cross-account Private Hosted Zone VPC associations.
Centralizing outbound egress traffic using Transit Gateway requires deploying a NAT Gateway in each active Availability Zone of the egress VPC and ensuring the subnet route tables route traffic to the NAT Gateway in the same zone. This maintains AZ isolation and resilience. Sharing a Route 53 Private Hosted Zone across AWS accounts is most efficiently achieved by creating a cross-account VPC association authorization in the hosted zone owner's account and executing the association in the client VPCs' accounts.

Adım Adım Çözüm

1
Analyze egress requirements
Identified that a single NAT Gateway violates the high availability requirement across Availability Zones. Redundant NAT Gateways must be deployed in each active Availability Zone within the egress VPC, and subnets must route traffic based on their respective zone.
Ensures that a failure in one Availability Zone does not impact outbound traffic originating from or routed through other zones.
2
Analyze private DNS requirements
Determined that Route 53 Private Hosted Zones can be shared cross-account by generating a VPC association authorization from the owner account and accepting it from the consumer accounts.
Avoids the unnecessary deployment costs and management overhead of Route 53 Resolver Inbound and Outbound Endpoints for simple internal resolution.
3
Verify transitive routing constraints
Confirmed that Direct Connect Gateway alone does not support transitive routing between associated virtual private gateways. AWS Transit Gateway must be used for transit routing.
Adheres to AWS architectural constraints regarding the non-transitive nature of Direct Connect Gateway.

Anahtar Kavram

Designing highly resilient, cost-effective centralized egress topologies using AWS Transit Gateway and managing cross-account private DNS resolution without adding operational complexity.
Tahmini Süre:3m 0s
Soru 3Soru

An enterprise deploys its core e-commerce application on Amazon EC2 instances within an Auto Scaling group (ASG) using AWS CloudFormation. Recently, engineers manually modified several security groups associated with the ASG, leading to configuration drift and subsequent deployment failures during CloudFormation stack updates. Additionally, during a rapid scale-out event, the ASG launched multiple instances that were immediately added to the Application Load Balancer (ALB) target group before their local bootstrapping scripts finished installing required packages, resulting in transient HTTP 502 errors for clients. A Solutions Architect must design an automated solution to remediate the configuration drift and ensure newly launched instances do not receive traffic until bootstrapping completes successfully. 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: Configure an Auto Scaling group lifecycle hook for the EC2_INSTANCE_LAUNCHING transition. Modify the EC2 user data script to perform the bootstrapping tasks, and upon successful completion, execute the complete-lifecycle-action CLI command to transition the instance to the InService state.; Deploy the AWS Config managed rule cloudformation-stack-drift-detection-check to monitor the stack. Configure an Amazon EventBridge rule to detect non-compliant status events and trigger an AWS Systems Manager Automation runbook to remediate the drifted resources.

Cevap

To resolve these issues, configure an Auto Scaling lifecycle hook to pause the EC2_INSTANCE_LAUNCHING state while user data completes bootstrapping and signals completion, and utilize AWS Config stack drift detection integrated with Amazon EventBridge and AWS Systems Manager Automation to detect and remediate infrastructure resource drift.
The correct architecture uses an Auto Scaling lifecycle hook to hold the instance in a launching state, allowing the user data script to perform bootstrapping tasks and signal completion before the instance is marked healthy and registered with the ALB. Additionally, deploying AWS Config with drift detection rules and automating remediation through EventBridge and Systems Manager Automation ensures that any manual alterations to resources are detected and corrected automatically without human intervention.

Adım Adım Çözüm

1
Address the premature registration of instances by adding an EC2_INSTANCE_LAUNCHING lifecycle hook to the Auto Scaling group.
The instances will remain in the 'Pending:Wait' state rather than immediately moving to 'InService'.
This prevents the ALB target group from routing client traffic to the instance before it is fully configured.
2
Update the EC2 user data script to perform the configuration steps and then call the complete-lifecycle-action CLI command.
Upon successful completion of the bootstrap script, the instance transitions to 'InService' and begins serving traffic.
This guarantees that only fully bootstrapped and verified instances receive traffic.
3
Deploy the cloudformation-stack-drift-detection-check rule in AWS Config and configure a rule in Amazon EventBridge.
Configuration drift is monitored automatically, and EventBridge captures any non-compliant drift notifications.
AWS Config tracks whether resources managed by a stack have been manually altered.
4
Link the EventBridge rule to an AWS Systems Manager Automation runbook.
An automated workflow is triggered to revert manual alterations or run appropriate drift remediation steps.
This automates the continuous alignment of resources to their defined infrastructure-as-code baseline.

Anahtar Kavram

Continuous alignment of infrastructure states using automated drift remediation combined with safe scaling lifecycle boundaries.
Tahmini Süre:3m 0s
Soru 4Soru

A solutions architect is planning the heterogeneous migration of a production on-premises MySQL database to an Amazon Aurora PostgreSQL-Compatible Edition DB cluster. The migration must minimize downtime, and the database experiences high write activity. The solutions architect has already run the AWS Schema Conversion Tool (SCT) to convert the database schema. To complete the migration, AWS Database Migration Service (DMS) will be used with Change Data Capture (CDC) enabled.

Which two actions must the solutions architect perform to prepare the source database and ensure successful CDC replication? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the MySQL configuration file on the source database to set binlog_format to ROW and binlog_row_image to FULL.; Configure the source database to retain binary logs for a minimum of 24 hours to prevent data loss before AWS DMS processes them.

Cevap

To perform successful Change Data Capture (CDC) from an on-premises MySQL database to Amazon Aurora PostgreSQL, you must set the source parameters binlog_format to ROW and binlog_row_image to FULL. Additionally, the source database must be configured to retain its binary logs for at least 24 hours to prevent replication errors.
To successfully perform Change Data Capture (CDC) from an on-premises MySQL database using AWS DMS, row-based logging must be enabled by setting the binary log format to ROW and the binary log row image to FULL. Additionally, the source database must be configured to retain these binary logs for a sufficient duration (typically at least 24 hours) to prevent the log files from being purged before AWS DMS can read and apply the changes.

Adım Adım Çözüm

1
Configure source binary logging parameters
Setting binlog_format to ROW and binlog_row_image to FULL ensures the necessary row-level change detail is logged.
AWS DMS requires detailed row-level change information in the binary logs to perform CDC replication from MySQL.
2
Configure binary log retention policy on the source
Configuring the retention to at least 24 hours prevents logs from being purged before they are consumed by the DMS replication task.
High-write environments generate large amounts of logs; if the retention period is too short, DMS will miss changes, causing the task to fail.
3
Verify schema conversion and launch DMS task
The target schema is already converted via SCT, and the DMS task starts replicating data from the source to the target.
DMS requires the schema to be present on the target before replicating data, and then relies on the configured binlogs to perform ongoing replication.

Anahtar Kavram

Configuring MySQL source databases for Change Data Capture (CDC) replication using AWS DMS requires setting specific binary logging configurations (ROW format and FULL row image) and ensuring binary logs are retained long enough to prevent replication failures.
Tahmini Süre:2m 0s
Soru 5Soru

An enterprise needs to migrate 350 TB350\text{ TB} of data from an on-premises SMB file share to an Amazon FSx for Windows File Server file system. The company has a dedicated 150 Mbps150\text{ Mbps} internet connection. The migration must be completed within 2121 days. In addition, all transferred data must be encrypted at rest using an AWS KMS customer managed key (CMK). Any incremental updates made on-premises during the migration must be captured and synced to AWS. 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: Order AWS Snowball Edge Storage Optimized devices. Set the destination to an Amazon S3 bucket, and specify an AWS KMS customer managed key to encrypt the data on the devices.; Deploy AWS DataSync agents on-premises, and configure tasks to copy the imported bulk data from the Amazon S3 bucket to Amazon FSx, and subsequently sync the incremental changes from the on-premises SMB share to Amazon FSx.

Cevap

Order AWS Snowball Edge Storage Optimized devices using a customer managed key for encryption, and deploy AWS DataSync agents to manage the data replication to Amazon FSx and incremental synchronization from the on-premises SMB share.
The correct strategy combines offline data migration using AWS Snowball Edge to overcome network bandwidth limitations with online replication using AWS DataSync. Ordering AWS Snowball Edge Storage Optimized devices with a customer managed key satisfies the encryption requirement and timeline for the bulk of the data. Deploying AWS DataSync allows the organization to move the imported bulk data from S3 to Amazon FSx for Windows File Server and sync any subsequent changes from the on-premises SMB share over the network.

Adım Adım Çözüm

1
Calculate the transfer time for the initial load over the network.
The theoretical transfer time for 350 TB350\text{ TB} over 150 Mbps150\text{ Mbps} is approximately 216216 days (350×1012×8/150×10618,666,667350 \times 10^{12} \times 8 / 150 \times 10^6 \approx 18,666,667 seconds), which violates the 2121-day migration window.
Determines whether an online transfer is feasible or if an offline transfer mechanism (Snowball Edge) is required.
2
Determine the Snowball encryption requirements.
Specify an AWS KMS customer managed key (CMK) for the Snowball job.
AWS managed keys (such as `aws/s3`) cannot be used for Snowball Edge encryption because their policies cannot be modified to authorize the Snowball service.
3
Plan the ingestion from the Snowball destination to the target file system and the incremental sync.
Use AWS DataSync to copy the imported bulk data from the Amazon S3 bucket to Amazon FSx, and then sync any incremental changes from the on-premises SMB share directly to Amazon FSx.
AWS DataSync supports copying data between AWS storage services and syncing changes from on-premises sources over the network, which completes the migration and captures any modifications made during transit.

Anahtar Kavram

Selecting the optimal data transfer strategy based on dataset size, available network bandwidth, time constraints, and KMS security policies.
Soru 6Soru

A manufacturing company is modernizing its warehouse inventory tracking system by refactoring a legacy monolithic application into a serverless architecture on AWS. The system must process barcode scanning events from multiple warehouses globally. These scans are ingested via Amazon API Gateway and processed by an AWS Lambda function that updates a central Amazon Aurora PostgreSQL database situated in a private VPC subnet. The volume of scans fluctuates significantly throughout the day, peaking at thousands of events per second during shift changes. During initial load testing, the application encounters database connection exhaustion errors, and other critical business functions in the same AWS account experience throttling. Which of the following actions should the Solutions Architect recommend to address these issues and ensure a reliable, scalable architecture? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Establish an Amazon RDS Proxy endpoint within the VPC to pool and reuse database connections from the Lambda function to the Aurora PostgreSQL database.; Configure reserved concurrency for the Lambda function to limit its maximum concurrent executions, preventing it from exhausting the regional account concurrency pool.

Cevap

Establish an Amazon RDS Proxy endpoint within the VPC to pool database connections, and configure reserved concurrency for the Lambda function to limit its concurrent executions.
Establishing an Amazon RDS Proxy pools database connections, preventing the Lambda function from exhausting the PostgreSQL connection limit. Configuring reserved concurrency prevents the Lambda function from scaling unbounded and exhausting the regional concurrency limit, which would otherwise throttle other critical functions in the AWS account.

Adım Adım Çözüm

1
Address database connection exhaustion by introducing a database proxy.
Amazon RDS Proxy pools connections, shielding the Aurora PostgreSQL database from connection spikes caused by highly concurrent Lambda executions.
Lambda scales horizontally by creating new execution environments, each of which establishes a new database connection. RDS Proxy intercepts these and manages a pool of persistent connections.
2
Protect the regional concurrency pool from depletion during traffic surges.
Reserved concurrency limits the maximum instances of the Lambda function that can run concurrently, preventing it from consuming the entire account's concurrency limits.
Without concurrency limits, a spike in inventory scans could exhaust the default account limit of 1,000 concurrent executions, causing all other functions in the region to fail with throttling errors.

Anahtar Kavram

Serverless connection pooling and concurrency management are critical when modernizing legacy workloads to Lambda and API Gateway to protect downstream resources and account limits.
Soru 7Soru

A retail corporation is designing a new Point of Sale (POS) transaction processing pipeline across multiple accounts under AWS Organizations. The application tier runs on Amazon EC2 instances in a dedicated Ingestion VPC inside the Production Account (111122223333). These instances must upload transaction logs directly to an Amazon S3 bucket located in a centralized Compliance Account (444455556666). The compliance team requires that all uploaded logs be encrypted at rest using a Key Management Service (KMS) key managed exclusively by the compliance team. The ingestion application must be able to encrypt the logs during upload but must be strictly prevented from decrypting the logs once they are written. Furthermore, key administration must be restricted to the Compliance Account, and administrators in the Production Account must not have permissions to modify the key's configuration. Which combination of actions should the Solutions Architect take to design a compliant control structure? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the Compliance Account (444455556666), create a Customer Managed KMS key. Configure the key policy to grant the Production Account (111122223333) IAM role permission to perform the kms:GenerateDataKey and kms:DescribeKey actions, while omitting the kms:Decrypt permission for this role.; In the Compliance Account (444455556666), configure the S3 bucket policy to grant the Production Account (111122223333) IAM role permission for the s3:PutObject action, and enforce a condition requiring the s3:x-amz-server-side-encryption header to be set to aws:kms referencing the Customer Managed KMS key's Amazon Resource Name (ARN).

Cevap

To achieve secure cross-account logging with proper segregation of duties, the solutions architect must create a Customer Managed Key (CMK) in the Compliance Account and grant the Production Account's IAM role permissions to generate and describe data keys (but not decrypt). Additionally, the Compliance Account S3 bucket policy must grant s3:PutObject to the Production IAM role while enforcing the use of the specific Customer Managed Key ARN using policy condition keys.
The correct combination requires creating a Customer Managed Key (CMK) in the Compliance Account, since only CMKs support the key policy modifications required for cross-account delegation. The key policy must grant key generation and description permissions to the Production Account IAM role while omitting decryption permissions to enforce segregation of duties. Simultaneously, the S3 bucket policy in the Compliance Account must grant PutObject permissions to the Production IAM role and enforce compliance by requiring that all uploads use the specified key via request headers.

Adım Adım Çözüm

1
Determine the correct KMS key type for cross-account sharing.
Identify that a Customer Managed Key (CMK) must be created in the Compliance Account (444455556666) because AWS-managed keys (aws/s3) cannot be shared across accounts.
AWS-managed keys do not permit policy modification, meaning they cannot delegate cross-account access.
2
Enforce segregation of duties in the KMS key policy.
Configure the key policy of the CMK to grant kms:GenerateDataKey and kms:DescribeKey to the Production Account (111122223333) IAM role, but omit kms:Decrypt.
This allows the ingestion application to write and encrypt logs but prevents it from reading or decrypting logs once uploaded.
3
Configure S3 bucket boundary controls.
Write an S3 bucket policy in the Compliance Account allowing s3:PutObject for the Production role with a condition requiring s3:x-amz-server-side-encryption-aws-kms-key-id to match the CMK ARN.
Enforces that all uploaded objects must use the designated compliance key, blocking unencrypted or incorrectly encrypted uploads.

Anahtar Kavram

Cross-account KMS key sharing and S3 bucket access control design
Tahmini Süre:3m 0s
Soru 8Soru

An enterprise is modernizing a legacy, high-volume batch processing and reporting workload by migrating it to a serverless architecture on AWS. The solution uses an Amazon API Gateway Regional REST API backed by AWS Lambda functions that read from and write to an Amazon Aurora PostgreSQL database. During peak load tests, the Lambda functions throttle other critical applications in the same AWS region, and outbound calls from Lambda to external verification APIs occasionally fail due to NAT gateway availability issues in a single Availability Zone. Which combination of architectural modifications will resolve these issues while maintaining high availability and security best practices? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure reserved concurrency on the high-volume batch processing Lambda function to limit its maximum concurrent executions and protect other critical applications.; Deploy NAT Gateways in multiple Availability Zones and update the route tables of the private subnets containing the Lambda functions to route outbound traffic through the local NAT Gateway in each zone.

Cevap

Configure reserved concurrency on the high-volume batch processing Lambda function to limit its concurrent executions, and deploy NAT Gateways across multiple Availability Zones to ensure redundant egress paths.
Configuring reserved concurrency on the high-volume batch processing function establishes a hard limit on the number of concurrent executions it can consume. This prevents the function from exhausting the regional concurrency pool, ensuring that other critical functions in the same region remain operational. Additionally, deploying NAT Gateways in multiple Availability Zones and configuring the corresponding subnet route tables ensures high availability and redundancy for outbound connections to external APIs, preventing single-AZ failures from disrupting egress traffic.

Adım Adım Çözüm

1
Analyze the cause of regional function throttling.
The high-volume Lambda function dynamically scales to consume the shared regional concurrency limit (default 1,000), which starves other critical applications.
A hard limit must be set using reserved concurrency to isolate and protect the shared regional execution pool.
2
Evaluate the egress networking path for outbound API calls.
Egress calls fail when a single NAT Gateway experiences issues or its Availability Zone is degraded.
To ensure reliable external API communication, NAT Gateways must be distributed across multiple Availability Zones, and route tables must be updated accordingly.
3
Assess key policy permissions for environment encryption.
AWS-managed keys do not permit key policy edits for cross-account access delegation.
This rules out the option attempting to modify the policy of the aws/lambda key, confirming that customer-managed keys are required for custom policies.

Anahtar Kavram

Mitigating resource exhaustion through Lambda reserved concurrency, and ensuring outbound network redundancy using multi-AZ NAT Gateways.
Soru 9Soru

An electric vehicle (EV) charging network provider is designing a new global charging session management system. The system must process real-time telemetry and session initialization requests from 200,000200,000 charging stations. At the start of peak operational hours, session initialization requests spike from 2,0002,000 requests per second to 60,00060,000 requests per second within a 11-minute window. The system must process these requests with sub-100ms latency, validate the user's account status, verify charger availability, and persist session records. The read-to-write ratio is 4:14:1.

The architecture uses Amazon Route 53, an Application Load Balancer (ALB), and Amazon ECS on AWS Fargate for the API layer. The database layer is Amazon Aurora PostgreSQL.

Which two actions should the Solutions Architect recommend to ensure the platform scales efficiently and meets the performance requirements during peak traffic? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Request AWS Support to pre-warm the Application Load Balancer (ALB) to the expected peak throughput before the scheduled start of peak hours, and configure Amazon ECS Scheduled Scaling to scale out the Fargate tasks to the anticipated capacity prior to the spike.; Implement Amazon ElastiCache for Redis to cache charger availability and user account status, and configure Amazon Aurora Auto Scaling to scale read replicas horizontally while maintaining a minimum replica count sufficient to absorb the initial burst.

Cevap

Request AWS Support to pre-warm the Application Load Balancer and configure ECS Scheduled Scaling before the event, and implement Amazon ElastiCache for Redis along with a pre-configured minimum replica count for Aurora Read Replicas.
To support a sudden 30-fold increase in traffic within a single minute, reactive scaling mechanisms are insufficient. Pre-warming the Application Load Balancer (ALB) ensures that AWS scales the load balancer's capacity ahead of time, preventing dropped connections at the start of the peak. Similarly, configuring Amazon ECS Scheduled Scaling ensures that Fargate tasks are fully provisioned and ready to accept traffic before the spike starts. To optimize the database layer, implementing Amazon ElastiCache for Redis offloads the frequent read operations (charger availability and account status) from the database. For the remaining reads, setting a high minimum count for Aurora Read Replicas ensures that read capacity is already in place to absorb the initial query spike.

Adım Adım Çözüm

1
Analyze the workload characteristics and scaling limits.
The traffic spikes 30-fold from 2,000 rps2,000\text{ rps} to 60,000 rps60,000\text{ rps} within 11 minute. Standard reactive scaling mechanisms (ALB auto-scaling, ECS target tracking, and Aurora Auto Scaling) have latency in spawning resources and will fail to absorb the sudden burst.
This establishes that proactive scaling strategies are required at the entry and compute layers to prevent performance degradation.
2
Address the load balancing and compute provisioning layers.
Pre-warming the ALB configures the load balancer for the target peak throughput beforehand. ECS Scheduled Scaling pre-allocates Fargate tasks to match the target capacity right before the peak hours begin, eliminating startup delay.
This guarantees that incoming connections are not dropped at the ingress point and that sufficient backend container capacity exists immediately.
3
Optimize the database layer for read and write loads.
Amazon ElastiCache for Redis caches the read-heavy transactions (charger availability and account status). Setting a high minimum reader count for Aurora Read Replicas pre-warms the database scaling pool for any uncached reads.
This isolates the primary database instance from write starvation and read latency spikes, adhering to AWS database best practices.

Anahtar Kavram

Proactive scaling and caching strategies are required to handle rapid, massive traffic spikes that exceed the response times of reactive auto-scaling policies.
Tahmini Süre:3m 0s
Soru 10Soru

A company wants to consolidate application logs from Amazon CloudWatch Logs across multiple AWS accounts in an AWS Organization into a centralized Amazon S3 bucket located in a dedicated Security account. The security team wants to stream these logs in near-real-time using Amazon Kinesis Data Firehose in the Security account, and they need to ensure secure cross-account delivery. Which two steps must the solutions architect take to configure this cross-account log aggregation topology? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the Security account, create a CloudWatch Logs destination that points to the Kinesis Data Firehose delivery stream and references an IAM role that allows CloudWatch Logs to write to the stream. Configure a destination policy on the CloudWatch Logs destination that grants the member accounts permission to perform the logs:PutSubscriptionFilter action.; In each member account, create a CloudWatch Logs subscription filter on the target application log groups, specifying the Amazon Resource Name (ARN) of the CloudWatch Logs destination in the Security account as the target.

Cevap

The correct configurations involve creating a CloudWatch Logs destination in the Security account that points to the Kinesis Data Firehose delivery stream, configuring a destination policy allowing the source accounts to execute logs:PutSubscriptionFilter, and creating a subscription filter on the target log groups in the member accounts referencing the Security account's destination ARN.
Setting up a CloudWatch Logs destination in the Security account with a resource policy allowing logs:PutSubscriptionFilter, along with configuring local subscription filters in the source accounts targeting the destination's ARN, correctly implements the cross-account subscription filter architecture. The destination is associated with an IAM service role that authorizes CloudWatch Logs to write to Kinesis Data Firehose.

Adım Adım Çözüm

1
Set up the target ingestion stream in the centralized Logging/Security account.
Create an Amazon Kinesis Data Firehose delivery stream configured to write to the destination S3 bucket.
This provides the ingestion pipeline for incoming streaming log data from all organization accounts.
2
Establish cross-account trust and log destination properties in the Security account.
Create a CloudWatch Logs destination referencing the Kinesis Data Firehose stream and an IAM role with a trust policy for logs.amazonaws.com. Attach a destination policy using PutDestinationPolicy to allow source accounts logs:PutSubscriptionFilter access.
This creates the endpoint that source accounts can target and authorizes cross-account access securely.
3
Configure log groups in the source member accounts to forward events.
Create a CloudWatch Logs subscription filter in each member account's target log groups pointing to the central destination ARN.
This establishes the active forwarding mechanism to stream local CloudWatch log events to the central destination.

Anahtar Kavram

Cross-account log aggregation with CloudWatch Logs requires establishing a CloudWatch Logs Destination in the receiving account, securing it via a resource-based destination policy, and creating local subscription filters targeting that destination in the sending accounts.
Soru 11Soru

A media streaming company manages a multi-account environment containing 6060 AWS accounts under a single AWS Organization. The security operations team requires all VPC Flow Logs from all member accounts to be consolidated into a single Amazon S3 bucket located in a dedicated Security account. The logs must be encrypted at rest using a customer managed key (CMK) in AWS Key Management Service (AWS KMS) to satisfy compliance guidelines. The solution must minimize administrative overhead and enforce least privilege.

Which TWO configurations must a Solutions Architect implement to achieve this goal?

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

Cevabı ve açıklamayı göster

Cevap: In the Security account, configure the S3 bucket policy to grant s3:PutObject and s3:GetBucketAcl permissions to the delivery.logs.amazonaws.com service principal, and restrict access using the aws:PrincipalOrgID condition key.; In the Security account, configure the KMS key policy for the customer managed key to grant kms:GenerateDataKey* and kms:Decrypt permissions to the delivery.logs.amazonaws.com service principal, and restrict access using the aws:PrincipalOrgID condition key.

Cevap

The correct configurations are: configuring the S3 bucket policy in the Security account to grant permission to the log delivery service principal, and configuring the customer managed KMS key policy to grant the log delivery service principal permission to use the key, both restricted by the Organization ID.
To centralize VPC Flow Logs to an S3 bucket in a different account, the S3 Log Delivery service principal (delivery.logs.amazonaws.com) requires permissions to write the logs. The S3 bucket policy must allow s3:PutObject and s3:GetBucketAcl for this service principal, restricted by the AWS Organization ID using the aws:PrincipalOrgID condition. Additionally, if the bucket is encrypted with a KMS customer managed key (CMK), the KMS key policy must grant kms:GenerateDataKey* and kms:Decrypt to the same service principal, also restricted by the Organization ID, because AWS managed keys (aws/s3) cannot be shared across accounts.

Adım Adım Çözüm

1
Identify the service principal responsible for delivering VPC Flow Logs to Amazon S3.
The service principal is delivery.logs.amazonaws.com (S3 Log Delivery).
VPC Flow Logs are delivered by this managed AWS service principal rather than individual member account IAM roles or root principals.
2
Determine the required S3 bucket policy permissions and condition keys for cross-account organization-wide delivery.
The S3 bucket policy in the Security account must grant s3:PutObject and s3:GetBucketAcl to delivery.logs.amazonaws.com and restrict access using the aws:PrincipalOrgID condition.
This allows the S3 Log Delivery service to verify bucket ownership and write flow logs from any account in the AWS Organization while blocking external accounts.
3
Evaluate key management and encryption requirements for cross-account S3 log delivery.
The KMS key policy for the customer managed key must grant kms:GenerateDataKey* and kms:Decrypt to the delivery.logs.amazonaws.com service principal, restricted by aws:PrincipalOrgID.
AWS managed keys (aws/s3) cannot be used for cross-account log delivery because their policies cannot be modified. A customer managed key must be used, and the log delivery service principal needs permission to generate data keys to encrypt logs.

Anahtar Kavram

Centralized VPC Flow Logs ingestion using S3 Log Delivery and KMS Customer Managed Keys in a multi-account AWS Organization.
Soru 12Soru

An international media broadcasting company is designing a hybrid network architecture for its multi-account AWS environment. The environment consists of 50 spoke VPCs in a single AWS Region, which host various parts of a media processing pipeline. The company needs to establish a highly available, transitive connection between all VPCs and two on-premises sites: a primary production facility and a backup recovery center. The primary path must run over a 10 Gbps AWS Direct Connect connection. The backup path must use an IPsec VPN over the internet. The solution must minimize routing configuration complexity, automatically fail over to the backup path if the primary path is unavailable, and allow direct VPC-to-VPC communication. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway and attach all 50 spoke VPCs to it. Create a Direct Connect gateway, associate it with a transit virtual interface (transit VIF) on the Direct Connect connection, and attach the Direct Connect gateway to the Transit Gateway.; Create an AWS Site-to-Site VPN connection and terminate it on the AWS Transit Gateway. Advertise the same on-premises network prefixes over both the Direct Connect gateway and the VPN connection, using AS PATH prepending on the backup VPN connection to ensure the Direct Connect path is preferred.

Cevap

The correct solution is to deploy an AWS Transit Gateway to connect the 50 spoke VPCs, routing hybrid traffic through a Direct Connect gateway with a transit virtual interface (transit VIF), while establishing a Site-to-Site VPN terminating on the Transit Gateway with AS PATH prepending on the VPN connection to ensure the Direct Connect path is preferred.
The correct solution involves deploying an AWS Transit Gateway to consolidate connectivity for the 50 spoke VPCs. The primary 10 Gbps path is established using a transit virtual interface (transit VIF) associated with a Direct Connect gateway attached to the Transit Gateway. The backup path is configured using a Site-to-Site VPN attachment directly on the Transit Gateway. To ensure the Direct Connect path is preferred, the same routes are advertised on both connections, but with AS PATH prepending configured on the VPN path.

Adım Adım Çözüm

1
Select the hub-and-spoke connectivity pattern.
AWS Transit Gateway is selected to connect the 50 spoke VPCs, enabling scalable VPC-to-VPC and hybrid communications.
Standard VPC peering is difficult to scale for 50 VPCs, and virtual private gateways do not support transitive routing or sufficient associations.
2
Configure the primary hybrid path using AWS Direct Connect.
A transit virtual interface (transit VIF) is created on the Direct Connect connection, associated with a Direct Connect gateway, and attached to the Transit Gateway.
Transit VIFs are required when connecting Direct Connect to a Transit Gateway to enable hybrid routing to multiple VPCs.
3
Configure the backup hybrid path and path preference.
A Site-to-Site VPN connection is terminated on the Transit Gateway, and AS PATH prepending is configured on the VPN connection to make it less preferred than the Direct Connect path.
This guarantees high availability with automatic failover to the VPN while ensuring the Direct Connect connection is the primary path.

Anahtar Kavram

AWS Transit Gateway acts as a cloud router, enabling transitive routing between multiple VPCs and on-premises networks using transit VIFs for Direct Connect and Site-to-Site VPNs for failover.
Soru 13Soru

A technology enterprise is designing a centralized monitoring and auditing solution for its AWS Organization, which contains 4040 member accounts. The security team requires that VPC Flow Logs from all VPCs across all member accounts be consolidated into a single Amazon S3 bucket located in a dedicated Monitoring account. The logs must be encrypted at rest using an AWS KMS key, and the transmission of logs must be secure and isolated to the organization. Which TWO configurations are required to establish this centralized log delivery architecture?

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

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket policy in the Monitoring account to grant s3:PutObject and s3:GetBucketAcl permissions to the delivery.logs.amazonaws.com service principal.; Create a Customer Managed Key (CMK) in the Monitoring account, and configure its key policy to allow the delivery.logs.amazonaws.com service principal to use the kms:GenerateDataKey* and kms:Decrypt actions.

Cevap

Configure the S3 bucket policy to allow the log delivery service principal to write objects and read bucket ACLs, and use a Customer Managed Key (CMK) with a key policy that grants the log delivery service principal permissions to generate data keys and decrypt.
The correct architecture uses the S3 bucket policy to grant necessary permissions to the AWS Log Delivery service principal (delivery.logs.amazonaws.com). In addition, since the logs are delivered across accounts and must be encrypted, a Customer Managed Key (CMK) must be configured to allow the log delivery service to generate data keys for encryption.

Adım Adım Çözüm

1
Configure the destination Amazon S3 bucket policy in the Monitoring account.
The S3 bucket policy is updated to grant s3:PutObject and s3:GetBucketAcl permissions to the delivery.logs.amazonaws.com service principal, restricted by the Organization ID or source account IDs.
This allows the native AWS Log Delivery service to deliver the flow logs to the centralized bucket across account boundaries.
2
Create and configure a Customer Managed Key (CMK) in AWS KMS within the Monitoring account.
A Customer Managed Key is set up with a policy that allows the delivery.logs.amazonaws.com service principal to call kms:GenerateDataKey* and kms:Decrypt.
AWS-managed KMS keys do not support policy modification and cannot be used for cross-account log delivery encryption; thus, a Customer Managed Key must be used.

Anahtar Kavram

Centralized VPC Flow Logs delivery requires configuring permissions on both the S3 bucket and the KMS Customer Managed Key to allow the delivery.logs.amazonaws.com service principal to write and encrypt logs cross-account.
Soru 14Soru

An enterprise is designing a hybrid network architecture to connect 3030 spoke VPCs in a single AWS Region to its on-premises data center. The primary connectivity must be established over a 10 Gbps10\text{ Gbps} AWS Direct Connect connection, with a backup AWS Site-to-Site VPN connection over the public internet. All outbound internet traffic from the spoke VPCs must be routed through a centralized egress VPC for security inspection. The solution must minimize routing complexity, avoid single points of failure, and support transitive routing between the VPCs.

Which of the following configuration steps should the Solutions Architect implement to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Attach the Direct Connect Gateway (DXGW) to an AWS Transit Gateway using a Transit Virtual Interface (Transit VIF), and configure a backup AWS Site-to-Site VPN connection attached directly to the Transit Gateway.; In the Transit Gateway route table associated with the spoke VPCs, add a route for 0.0.0.0/00.0.0.0/0 pointing to the egress VPC attachment, and configure the spoke VPC subnet route tables with a default route pointing to the Transit Gateway.

Cevap

Attach the Direct Connect Gateway (DXGW) to an AWS Transit Gateway using a Transit Virtual Interface (Transit VIF), configure a backup AWS Site-to-Site VPN connection attached directly to the Transit Gateway, add a route for 0.0.0.0/00.0.0.0/0 in the Transit Gateway route table pointing to the egress VPC attachment, and configure spoke VPC subnet route tables to route default traffic to the Transit Gateway.
The correct solution involves deploying AWS Transit Gateway to handle both transitive VPC-to-VPC routing and centralized egress. The Direct Connect Gateway attaches to the Transit Gateway using a Transit VIF to scale hybrid bandwidth, while a backup AWS Site-to-Site VPN connection attaches directly to the Transit Gateway to provide a redundant path. Outbound internet traffic is centralized by directing spoke VPC default routes (0.0.0.0/00.0.0.0/0) to the Transit Gateway, and configuring the Transit Gateway's route tables to forward all 0.0.0.0/00.0.0.0/0 traffic to the egress VPC attachment.

Adım Adım Çözüm

1
Determine the routing architecture for hybrid connectivity.
Deploy AWS Transit Gateway as a central hub, attach it to a Direct Connect Gateway using a Transit Virtual Interface (Transit VIF) for primary traffic, and configure AWS Site-to-Site VPN as a backup.
This supports transitive VPC-to-VPC routing and high-bandwidth primary hybrid connectivity with a redundant backup path.
2
Configure routing for centralized egress.
Add a default route (0.0.0.0/00.0.0.0/0) in the Transit Gateway route table pointing to the centralized egress VPC attachment. Configure spoke VPC subnet route tables with a default route (0.0.0.0/00.0.0.0/0) pointing to the Transit Gateway.
This centralizes outbound traffic to the egress VPC for security inspection while minimizing routing complexity.

Anahtar Kavram

AWS Transit Gateway acts as a centralized cloud router that simplifies hybrid connectivity by supporting Transit VIFs on Direct Connect Gateways and Site-to-Site VPNs, and enables centralized egress architecture by routing default routes (0.0.0.0/00.0.0.0/0) across VPC attachments.
Tahmini Süre:2m 0s
Soru 15Soru

An organization has a multi-account AWS environment with 2525 VPCs deployed across two AWS Regions: `us-east-1` and `us-west-2`. The organization has established a hybrid network using two 10 Gbps10\text{ Gbps} AWS Direct Connect connections terminating at separate DX locations. To ensure resiliency, they want to configure a backup path using a Site-to-Site VPN over the internet. The Direct Connect connections terminate at an AWS Direct Connect Gateway associated with AWS Transit Gateways in each region. Under normal operating conditions, all hybrid traffic must use the Direct Connect connections. The Site-to-Site VPN should only be used if both Direct Connect connections fail. Which two routing configurations must the solutions architect implement on the on-premises router and within AWS to achieve this dynamic failover behavior?

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

Cevabı ve açıklamayı göster

Cevap: Configure the on-premises router to advertise the on-premises IP prefixes to AWS with a shorter AS path over the Direct Connect transit virtual interface than over the Site-to-Site VPN connections.; Configure the on-premises router to assign a higher BGP local preference to the AWS routes received over the Direct Connect transit virtual interface than those received over the Site-to-Site VPN connections.

Cevap

The solutions architect should configure the on-premises router to advertise the on-premises IP prefixes with a shorter AS path over the Direct Connect virtual interface, and configure the on-premises router to assign a higher BGP local preference to the AWS routes received over the Direct Connect interface.
To ensure the Direct Connect connection is used as the primary path and the VPN as the backup, routing preferences must be set for both directions of traffic. For traffic going from AWS to on-premises (outbound), the Transit Gateway evaluates the BGP AS path length. By advertising the on-premises prefixes with a shorter AS path over the Direct Connect transit virtual interface, AWS will prefer this path. For traffic going from on-premises to AWS (inbound), the customer gateway should prefer the Direct Connect path by assigning it a higher BGP local preference, which is processed locally on the router before other BGP path attributes.

Adım Adım Çözüm

1
Configure the outbound routing preference from AWS to on-premises by adjusting the AS path length advertised from the customer gateway.
The Transit Gateway receives routes for on-premises CIDRs over both Direct Connect and VPN, but prefers Direct Connect due to the shorter AS path length.
This guarantees that all outbound traffic from the AWS VPCs to the on-premises environment uses the Direct Connect path under normal operating conditions.
2
Configure the inbound routing preference from on-premises to AWS on the local router using BGP local preference.
The local router receives the AWS prefixes over both Direct Connect and VPN, and selects Direct Connect as the best path due to the higher local preference value.
This guarantees that all inbound traffic from the on-premises environment to AWS VPCs uses the Direct Connect path under normal operating conditions.

Anahtar Kavram

Using BGP attributes such as AS path length and local preference to establish symmetric routing preferences over hybrid network connections.
Soru 16Soru

An enterprise is designing a deployment pipeline for a legacy Java application hosted on Amazon EC2 instances within an Auto Scaling group behind an Application Load Balancer. The deployment must achieve zero downtime and allow for a 1-hour verification window where the old version remains active but receives no traffic, enabling rapid rollback if issues are detected. If the validation succeeds, the old instances must be automatically terminated. The deployment process must be fully managed with minimal custom configuration. Which two configurations should the Solutions Architect include in the AWS CodeDeploy deployment group to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the deployment group to copy the Auto Scaling group and use the Application Load Balancer target group to route traffic.; Configure the deployment group settings to reroute traffic immediately, and set the original Auto Scaling group instances to terminate after a waiting period of 60 minutes.

Cevap

Configure the deployment group to copy the Auto Scaling group and use the Application Load Balancer target group to route traffic, and configure the deployment group settings to reroute traffic immediately while setting the original Auto Scaling group instances to terminate after a waiting period of 60 minutes.
For an EC2 Auto Scaling deployment using CodeDeploy, a blue/green deployment requires copying the Auto Scaling group and using an Application Load Balancer target group to route traffic. Setting the deployment group to reroute traffic immediately and setting the original instances to terminate after a 60-minute wait time ensures that traffic shifts to the new version immediately while keeping the old instances running and deregistered from the load balancer. This provides a 1-hour window for verification and rapid rollback without downtime, followed by automated termination.

Adım Adım Çözüm

1
Determine the deployment type and environment configuration.
CodeDeploy Blue/Green deployment is chosen, configuring the deployment group to copy the original Auto Scaling group and swap traffic via the Application Load Balancer target group.
This establishes a fully managed blue/green setup where CodeDeploy handles the creation of the green environment automatically.
2
Configure the traffic rerouting and validation window.
Set the deployment group to reroute traffic immediately once the green instances pass health checks, and configure the original instances' termination wait time to 60 minutes.
This meets the requirement of keeping the old instances active but not receiving traffic (deregistered) for a 1-hour verification period to allow rapid rollback.

Anahtar Kavram

AWS CodeDeploy Blue/Green deployment configurations for EC2 Auto Scaling Groups
Soru 17Soru

A multinational financial enterprise is building a regulatory reporting data pipeline. The application tier runs on Amazon EC2 instances in an Application Account (Account A: 111122223333111122223333). The reporting logs must be delivered to an Amazon S3 bucket in a Centralized Security Account (Account B: 444455556666444455556666). The compliance requirements mandate that all logs must be encrypted at rest using a Key Management Service (KMS) key, and the Centralized Security Account must have full ownership of all uploaded objects to prevent access delegation issues. The application tier must only have permissions to write objects and must not be allowed to decrypt the logs once written. Which combination of actions must the solutions architect take to meet these security requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable S3 Object Ownership with the Bucket Owner Enforced setting on the S3 bucket in Account B, and configure the S3 bucket policy in Account B to grant s3:PutObject permissions to Account A's EC2 instance profile role.; Create a customer managed KMS key in Account B, configure its key policy to grant kms:GenerateDataKey permissions to Account A's EC2 instance profile role, and configure the S3 bucket in Account B to use this customer managed KMS key for default encryption.

Cevap

Enable S3 Object Ownership with the Bucket Owner Enforced setting on the S3 bucket in Account B, configure the bucket policy to grant s3:PutObject permissions to Account A's role, and use a customer managed KMS key in Account B with key policy permissions for kms:GenerateDataKey granted to Account A.
To support cross-account KMS encryption, a customer managed key (CMK) must be created in the destination account because AWS managed keys (such as aws/s3) do not support policy modification and cannot be shared across accounts. Granting the writing role `kms:GenerateDataKey` allows the application to encrypt files without requiring `kms:Decrypt` access. Additionally, disabling S3 ACLs using the Bucket Owner Enforced setting ensures that all objects uploaded to the bucket are automatically owned by the bucket owner (the security account), resolving potential ownership and permission delegation issues.

Adım Adım Çözüm

1
Address the cross-account encryption requirement by creating a customer managed key (CMK) in the destination security account (Account B).
A CMK is established which supports cross-account key policy delegation, unlike default AWS-managed KMS keys.
AWS-managed keys (e.g., aws/s3) cannot be shared across accounts as their policies are not editable.
2
Configure the key policy of the newly created CMK to allow Account A's EC2 instance profile role to generate data keys.
The application can perform encryption at write time by calling kms:GenerateDataKey without requiring decryption permissions.
Applying the principle of least privilege ensures the writing account cannot decrypt or read the logs once written.
3
Configure the destination S3 bucket in Account B with default encryption using the customer managed KMS key.
All objects uploaded to the bucket are automatically encrypted with the specified CMK.
Enforces compliance control for encryption at rest for all incoming reporting logs.
4
Enable the Bucket Owner Enforced setting under S3 Object Ownership on the bucket in Account B, and grant s3:PutObject permissions in the bucket policy to Account A's role.
S3 ACLs are disabled, and the Centralized Security Account (Account B) automatically owns all uploaded log objects.
Ensures that the security account maintains full control and ownership of the logs without relying on object ACLs from the writer account.

Anahtar Kavram

Designing cross-account security controls using KMS key policies and S3 Object Ownership (Bucket Owner Enforced) to maintain compliance and data ownership.
Soru 18Soru

A healthcare provider is designing a new digital medical imaging archive and diagnostic report system. The system must store structured patient metadata logs (OLTP workload) and unstructured medical images in DICOM format (Object storage). The metadata database must support high-volume write transactions and scale read traffic to handle sudden spikes from hospital clients. The disaster recovery requirements demand a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 11 minute. Additionally, for regulatory compliance, the medical images must be securely archived and replicated to a destination bucket in a secondary, isolated AWS account in a different AWS region, encrypted at rest using AWS KMS. Which of the following database and storage configurations should the solutions architect choose to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora global database with the primary cluster in the active region and a secondary cluster in the disaster recovery region, utilizing Aurora Replicas in both regions to handle database operations.; Store the medical images in Amazon S3, and configure S3 Cross-Region Replication (CRR) to a destination bucket in the disaster recovery region using a Customer Managed Key (CMK) in AWS KMS with appropriate cross-account key policies.

Cevap

Deploy an Amazon Aurora global database with the primary cluster in the active region and a secondary cluster in the disaster recovery region, and store the medical images in Amazon S3, configuring S3 Cross-Region Replication (CRR) using a Customer Managed Key (CMK) in AWS KMS with cross-account key policies.
Deploying an Amazon Aurora global database provides sub-second replication to the disaster recovery region, satisfying the strict RTO of 1515 minutes and RPO of 11 minute, while supporting read replicas for traffic scaling. For object storage, utilizing Amazon S3 with Cross-Region Replication (CRR) and a Customer Managed Key (CMK) configured with cross-account policies allows secure replication of medical images to a secondary AWS account, which is impossible with AWS-managed keys.

Adım Adım Çözüm

1
Evaluate the database tier for high performance, read scaling, and strict RTO/RPO targets.
Determine that Amazon Aurora Global Database satisfies the RTO of 1515 minutes and RPO of 11 minute via storage-based physical replication, while standard RDS snapshot replication fails the RPO target.
Aurora Global Database replicates data sub-second, allowing for near-zero RPO and rapid failover.
2
Assess the scalability and read routing configuration of the database options.
Eliminate the configuration routing read queries to the RDS standby instance because Multi-AZ standby instances do not accept read traffic.
RDS standby instances are purely passive; read scaling requires read replicas or Aurora replicas.
3
Evaluate S3 Cross-Region Replication (CRR) requirements for cross-account destination buckets.
Identify that the default AWS-managed KMS key (aws/s3) cannot be used because its policy cannot be modified to grant cross-account access.
A Customer Managed Key (CMK) is required to configure key policies allowing cross-account decryption and encryption.

Anahtar Kavram

Selecting and configuring highly available, secure, and compliant databases and storage with cross-region and cross-account capabilities to meet RTO/RPO constraints.
Soru 19Soru

A global online retailer is launching a flash sale platform for limited-edition merchandise drops. The system expects sudden, extreme traffic surges where active users scale from 5,0005,000 to over 1,500,0001,500,000 within 60 seconds60\text{ seconds} at the start of a sale. The current architecture consists of an Application Load Balancer (ALB), an Amazon ECS on AWS Fargate service, and an Amazon Aurora PostgreSQL database cluster. During testing, the sudden influx of connection requests led to HTTP 503503 Service Unavailable errors from the ALB, and database write latency spiked, causing the Fargate tasks to exhaust their connection pools. Which combination of architectural optimizations will best resolve these performance and scalability issues? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Submit an AWS Support ticket to pre-warm the Application Load Balancer (ALB) with the expected traffic profile and surge rates prior to the start of the drop event.; Decouple the write operations by routing order requests to an Amazon Kinesis Data Stream, and configure an AWS Lambda function to poll the stream and perform batch writes to the Amazon Aurora database.

Cevap

Pre-warm the Application Load Balancer (ALB) by contacting AWS Support, and decouple the database write operations using Amazon Kinesis Data Streams and AWS Lambda to process database updates in batches.
Contacting AWS Support to pre-warm the ALB ensures that the load balancer is provisioned with sufficient capacity before the flash sale starts, preventing HTTP 503 errors. Decoupling the write path using Amazon Kinesis Data Streams and AWS Lambda allows the system to ingest massive transaction volumes instantly and write to the Aurora database in controlled, batched operations, preventing database CPU exhaustion.

Adım Adım Çözüm

1
Analyze the bottleneck at the ingress layer (Application Load Balancer) during an instantaneous surge.
Dynamic auto-scaling policies cannot react quickly enough, causing HTTP 503 errors. Determine that ALB pre-warming via AWS Support is required.
ALBs scale gradually based on traffic trends, but a sudden flash spike from 5,000 to 1.5 million requests in 60 seconds will saturate the existing capacity before scaling completes.
2
Analyze the bottleneck at the database layer (Amazon Aurora PostgreSQL).
Determine that decoupling writes using a queuing/streaming ingestion tier is necessary to absorb the peak throughput.
Direct, concurrent database writes from scaled container tasks can exhaust database connection pools and CPU. Buffering updates in Amazon Kinesis and processing them in batches via AWS Lambda smooths out the database write load.
3
Evaluate the architectural validity of the distractors.
Identify that the options suggesting dynamic ALB auto-scaling, routing reads to a standby, and using replicated Memcached are invalid.
Aurora standby instances do not handle read scaling, Memcached does not support replication or persistence, and ALB dynamic scaling is too slow for flash spikes.

Anahtar Kavram

Architecting systems for extreme flash traffic spikes by pre-warming load balancers and decoupling database writes to manage scalability and performance.
Soru 20Soru

A digital advertising company is designing a real-time bidding (RTB) platform that processes ad auction requests from global ad exchanges. The system must handle a baseline of 100,000100,000 requests per second (RPS) and scale to support sudden spikes of up to 800,000800,000 RPS with sub-1515 millisecond response times. The current design proposes using an Application Load Balancer (ALB) routing traffic to Amazon ECS tasks running on AWS Fargate, with Amazon Aurora PostgreSQL as the persistent database.

Which two actions should the solutions architect take to meet the performance and latency requirements under peak traffic loads? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Request AWS Support to pre-warm the ALB to the expected peak traffic capacity of 800,000800,000 requests per second.; Configure Aurora Replicas in the database cluster and set up Auto Scaling to dynamically add replicas based on read load.

Cevap

The correct actions are to request AWS Support to pre-warm the Application Load Balancer (ALB) to the expected peak traffic capacity of 800,000800,000 requests per second, and to configure Aurora Replicas in the database cluster with Auto Scaling to dynamically handle the read load.
Pre-warming the Application Load Balancer (ALB) ensures that it has sufficient capacity provisioned beforehand to handle the massive, instantaneous 8-fold traffic spike without dropping connections. Utilizing Aurora Replicas with Auto Scaling allows the database layer to horizontally scale read capacity to handle the increased query volume, preserving sub-15ms response times.

Adım Adım Çözüm

1
Analyze traffic characteristics and scaling limitations of the load balancing tier.
The application faces an immediate 8-fold traffic surge from 100,000100,000 to 800,000800,000 requests per second. Under default behavior, the ALB will fail to scale quickly enough, resulting in dropped packets and increased latency.
Requesting pre-warming for the ALB is necessary to prepare the balancer's capacity ahead of time for the peak spike.
2
Evaluate the database read-scaling capabilities of Amazon Aurora.
Dynamic read-scaling is achieved by adding Aurora Replicas to the cluster and configuring Auto Scaling based on metrics such as CPU utilization.
This offloads read operations from the primary writer node to the horizontally scaled reader nodes.
3
Eliminate incorrect configurations for databases and caches.
Multi-AZ standby instances cannot receive read queries. Amazon ElastiCache for Memcached does not offer replication or persistent failover features.
Identifying invalid database replication architectures and cache engine features helps refine the solution to comply with best practices.

Anahtar Kavram

Handling sudden massive spikes requires pre-provisioning capacity on the entry layer (ELB pre-warming) and utilizing scalable read replicas at the database tier.
Tahmini Süre:2m 0s
Sayfa 1 / 47Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin