Tüm alıştırma soruları

1964 soru

Soru 241Soru

A financial services company manages 4545 member accounts within an AWS Organization. The security team is setting up an organization-wide AWS CloudTrail trail to log all API activity to a centralized Amazon S3 bucket located in a dedicated Security account. The S3 bucket must be encrypted using a Customer Managed Key (CMK) in AWS Key Management Service (AWS KMS) to comply with regulatory standards. Which combination of configuration steps will ensure that CloudTrail can successfully write logs from all member accounts to the central S3 bucket?

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket policy in the Security account to permit the CloudTrail service principal to write objects, restricted by the AWS Organization ID. Attach a key policy to the Customer Managed Key in the Security account that allows the CloudTrail service principal to generate data keys, restricted by the AWS Organization ID.

Cevap

Configure the S3 bucket policy in the Security account to permit the CloudTrail service principal to write objects, restricted by the AWS Organization ID. Attach a key policy to the Customer Managed Key in the Security account that allows the CloudTrail service principal to generate data keys, restricted by the AWS Organization ID.
The correct answer correctly addresses both S3 bucket access and KMS encryption. The S3 bucket policy in the target Security account must allow the CloudTrail service principal to write logs, and the KMS key policy for the Customer Managed Key must allow the same principal to generate data keys to encrypt those logs. Using the AWS Organization ID as a condition scope maintains security control across all member accounts.

Adım Adım Çözüm

1
Analyze bucket policy requirements for centralized S3 logging
The destination S3 bucket policy in the Security account must explicitly allow 's3:PutObject' and 's3:GetBucketAcl' for the CloudTrail service principal ('cloudtrail.amazonaws.com') to permit writes from all organization member accounts.
Since the bucket is in a different account than the member accounts, cross-account access must be configured via the S3 bucket policy.
2
Analyze KMS encryption requirements for cross-account CloudTrail logs
The Customer Managed Key (CMK) key policy must grant permissions for the CloudTrail service principal to perform 'kms:GenerateDataKey*' and 'kms:Decrypt' operations.
AWS-managed keys cannot be used for cross-account access because their key policies are not modifiable. A Customer Managed Key is required.
3
Apply organizational restrictions for security boundaries
Use conditions like 'aws:PrincipalOrgID' or 'aws:SourceArn' in both the S3 bucket policy and KMS key policy to restrict access to the specific AWS Organization.
This prevents unauthorized accounts outside the organization from writing to the bucket or using the key.

Anahtar Kavram

Centralized cross-account logging requires configuring both resource policies (S3 bucket policy) and KMS key policies to trust the AWS service principal, restricted by organizational boundaries.
Soru 242Soru

A healthcare enterprise is designing a new patient monitoring application. The application runs on Amazon ECS tasks inside a Data Ingestion account (Account 123456789012) and must write clinical telemetry files directly to an Amazon S3 bucket in a Centralized Analytics account (Account 987654321098). The S3 bucket is encrypted using server-side encryption with AWS KMS (SSE-KMS). To comply with HIPAA requirements, the encryption keys must be managed in the Centralized Analytics account. Which combination of configurations must the Solutions Architect implement to allow the ECS tasks to write to the S3 bucket?

Cevabı ve açıklamayı göster

Cevap: In the Centralized Analytics account, create a Customer Managed Key (CMK) and configure its key policy to grant the Data Ingestion account root principal (arn:aws:iam::123456789012:root) permissions for kms:GenerateDataKey and kms:Decrypt. In the Centralized Analytics account, configure the S3 bucket policy to allow the ECS task's IAM role s3:PutObject permissions. In the Data Ingestion account, attach an IAM policy to the ECS task's IAM role that grants permissions for s3:PutObject on the Centralized Analytics S3 bucket, and kms:GenerateDataKey and kms:Decrypt on the CMK.

Cevap

The configuration utilizing a Customer Managed Key (CMK) with a key policy delegating to the source account's root principal, an S3 bucket policy in the destination account allowing the write operations, and a local IAM policy in the source account granting the ECS task permissions to both the S3 bucket and KMS key.
The configuration utilizing a Customer Managed Key (CMK) with a key policy delegating to the source account's root principal, an S3 bucket policy in the destination account allowing the write operations, and a local IAM policy in the source account granting the ECS task permissions to both the S3 bucket and KMS key is correct. This configuration establishes a secure trust relationship that adheres to the two-way authorization model required for cross-account resource access in AWS.

Adım Adım Çözüm

1
Select the correct key type
Identify that a Customer Managed Key (CMK) must be used in the Centralized Analytics account because AWS managed keys (aws/s3) cannot be shared cross-account.
AWS managed keys have default policies that cannot be modified to grant access to external accounts.
2
Configure destination account policies
Create a KMS key policy that grants the source account root principal (arn:aws:iam::123456789012:root) access to the CMK for cryptographic operations, and configure the S3 bucket policy to allow the ECS task's IAM role to perform s3:PutObject.
KMS key policies must explicitly trust the external account to delegate permissions, and the S3 bucket policy must allow the cross-account write.
3
Configure source account policies
Attach an IAM policy to the ECS task's IAM role in the Data Ingestion account that grants s3:PutObject on the destination S3 bucket and kms:GenerateDataKey/kms:Decrypt on the CMK in the Centralized Analytics account.
Cross-account access requires explicit permission in the caller's local IAM policy, as resource-based policies alone cannot grant access across account boundaries without local authorization.

Anahtar Kavram

Cross-account access design with SSE-KMS requires co-ordination of three policy types: destination KMS key policies (using Customer Managed Keys), destination S3 bucket policies, and source IAM policies.
Tahmini Süre:2m 30s
Soru 243Soru

A financial technology organization is designing a hybrid network architecture for its AWS environment. The environment consists of 4040 spoke VPCs across multiple AWS accounts in the us-east-1 Region, along with a centralized Shared Services VPC. The organization needs to connect its AWS resources to an on-premises data center.

The connectivity design must meet the following requirements:
1. High-throughput hybrid connectivity must be established using a primary AWS Direct Connect connection, with a Site-to-Site VPN connection acting as a backup.
2. All traffic between the spoke VPCs and the on-premises network must be inspected by a cluster of third-party firewall appliances deployed in the Shared Services VPC.
3. The spoke VPCs must be able to resolve private on-premises domain names using Route 53 with minimal administrative overhead.
4. Egress traffic to the internet must be highly available and centralized through the Shared Services VPC.
5. Administrative overhead must be minimized, and the solution must scale automatically as new spoke VPCs are added.

Which of the following architectures satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway (TGW) and attach all spoke VPCs and the Shared Services VPC, enabling Transit Gateway Appliance Mode on the Shared Services VPC attachment. Create a Direct Connect Gateway (DXGW) associated with the TGW via a Transit VIF, and attach the Site-to-Site VPN directly to the TGW. Configure BGP with AS-path prepending on the VPN connection to ensure the Direct Connect path is preferred. Configure TGW route tables to route all spoke-to-on-premises and spoke-to-internet traffic to the Shared Services VPC. In the Shared Services VPC, deploy redundant NAT Gateways across multiple Availability Zones for internet egress. Deploy Route 53 Resolver outbound endpoints in the Shared Services VPC, configure a forwarding rule for the on-premises domain, and share it with all spoke VPCs using AWS Resource Access Manager (RAM).

Cevap

Deploy an AWS Transit Gateway (TGW) to connect all spoke VPCs and the Shared Services VPC (enabling Appliance Mode). Establish hybrid connectivity using a Direct Connect Gateway and Site-to-Site VPN directly attached to the TGW, with BGP AS-path prepending on the VPN. Centralize security using separate TGW route tables to direct traffic through firewall appliances in the Shared Services VPC. Use redundant NAT Gateways for internet egress and Route 53 Resolver outbound endpoints with shared forwarding rules via AWS RAM for DNS resolution.
The correct architecture uses a Transit Gateway with separate route tables to enforce traffic inspection through the Shared Services VPC. Enabling Transit Gateway Appliance Mode on the Shared Services VPC attachment guarantees traffic symmetry for stateful firewalls. Hybrid failover is achieved using BGP routing with AS-path prepending to prefer the Direct Connect link. Centralized internet egress is kept highly available by deploying redundant NAT Gateways across multiple Availability Zones. Lastly, DNS queries for the on-premises domain are forwarded via Route 53 Resolver outbound endpoints and shared forwarding rules via AWS RAM, minimizing administrative overhead.

Adım Adım Çözüm

1
Configure the Transit Gateway (TGW) and VPC attachments.
Attach all 4040 spoke VPCs and the Shared Services VPC to the TGW. Enable Transit Gateway Appliance Mode on the Shared Services VPC attachment to keep traffic flow symmetric through the third-party firewall appliances.
Appliance Mode ensures that the TGW forwards both forward and return traffic to the same firewall instance within the Shared Services VPC, preventing stateful firewall drop issues.
2
Set up hybrid connectivity with failover routing.
Associate the Direct Connect Gateway (DXGW) with the TGW using a Transit VIF, and create a Site-to-Site VPN attachment to the TGW. Advertise the same on-premises routes via BGP over both paths, prepending the AS-path on the VPN connection.
This establishes Direct Connect as the primary path due to a shorter AS-path (and default AWS routing preferences), while ensuring automatic failover to the VPN connection in case of Direct Connect failure.
3
Configure routing for security inspection and egress.
Set up separate TGW route tables (Spoke, Firewall, and Edge/Hybrid) to steer traffic. Direct all spoke-to-on-premises and spoke-to-internet traffic to the Shared Services VPC for inspection. Route outbound internet traffic through redundant NAT Gateways deployed across multiple Availability Zones in the Shared Services VPC.
Separate route tables prevent routing loops and ensure that all traffic is inspected by the firewalls. Redundant NAT Gateways across multiple AZs ensure high availability for egress traffic.
4
Implement hybrid DNS resolution.
Deploy Route 53 Resolver outbound endpoints in the Shared Services VPC. Create a forwarding rule for the on-premises domain pointing to the on-premises DNS servers, and share the rule with all spoke VPCs using AWS Resource Access Manager (RAM).
Sharing the Resolver forwarding rule via RAM allows all spoke VPCs to automatically resolve on-premises hostnames via the outbound endpoints without needing private hosted zone associations or individual endpoint configurations.

Anahtar Kavram

Centralized hybrid routing with inspection, high-availability egress, and shared DNS resolution in a multi-account AWS environment.
Soru 244Soru

A logistics company is designing a hybrid network architecture to connect its on-premises data center to its AWS environment. The environment consists of 12 spoke VPCs across two AWS Regions: us-east-1 and us-west-2. The company requires a highly available, private connection with a backup path. A 10 Gbps AWS Direct Connect (DX) connection has been established. To minimize costs while ensuring high availability, the company will use an IPsec VPN over the internet as a backup. The architecture must support dynamic routing and automatic failover. Which of the following configurations are required to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure an AWS Transit Gateway in each Region, and associate both Transit Gateways with a single AWS Direct Connect Gateway using transit virtual interfaces.; Establish BGP sessions for both the Direct Connect and VPN connections, and prepend the autonomous system (AS) path on the VPN connection to ensure AWS routes traffic via Direct Connect under normal operations.

Cevap

Configure an AWS Transit Gateway in each Region associated with a single AWS Direct Connect Gateway using transit virtual interfaces, and prepend the AS path on the VPN BGP session to ensure Direct Connect is preferred.
The correct configurations involve deploying an AWS Transit Gateway in each Region and associating them with a single AWS Direct Connect Gateway using transit virtual interfaces. This establishes the primary high-throughput path. For the backup path, dynamic routing via BGP is established over both Direct Connect and VPN. By prepending the AS path on the VPN connection, AWS is instructed to prefer the Direct Connect path because it has a shorter AS path, ensuring failover occurs automatically only when the Direct Connect path is unavailable.

Adım Adım Çözüm

1
Establish the primary connectivity model using AWS Transit Gateways and a Direct Connect Gateway.
Transit Gateways in us-east-1 and us-west-2 are associated with a single Direct Connect Gateway using transit virtual interfaces.
This supports multi-account, multi-region transit routing and allows the 12 spoke VPCs to communicate with each other and the on-premises data center.
2
Configure the backup IPsec VPN connection and enable dynamic routing using BGP.
Dynamic routing paths exist via both the Direct Connect Gateway and the IPsec VPN.
To allow automatic failover without manual routing table interventions.
3
Apply AS-path prepending on the VPN BGP session from the customer gateway.
The BGP route advertised over the VPN has a longer AS path than the route advertised over the Direct Connect connection.
This forces AWS to prefer the Direct Connect path for outbound traffic to the on-premises network under normal operating conditions.

Anahtar Kavram

Hybrid network connectivity design with Transit Gateway, Direct Connect, and VPN failover using BGP routing policies.
Tahmini Süre:2m 0s
Soru 245Soru

A media broadcasting company is planning a global live-streaming event that expects a massive flash crowd of 15,000,00015,000,000 concurrent viewers to authenticate, fetch metadata, and establish session states within a 55-minute window. The current architecture consists of an Application Load Balancer (ALB) routing requests to a containerized microservices fleet on Amazon Elastic Container Service (ECS) on AWS Fargate, and Amazon Aurora PostgreSQL for the database layer. Video metadata changes infrequently, but session states require sub-millisecond updates and must survive an Availability Zone outage. Which combination of architectural optimizations should the Solutions Architect implement to ensure the platform scales seamlessly and maintains performance during the initial traffic spike? (Select THREE.)

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 to the expected peak request rate and throughput before the event begins.; Implement an Amazon ElastiCache for Redis cluster with Multi-AZ replication to cache video metadata and store user session states.; Deploy Aurora Replicas in the database cluster and configure Aurora Auto Scaling to dynamically scale read operations.

Cevap

To optimize performance and scalability for the flash traffic event, the Solutions Architect must request AWS Support to pre-warm the Application Load Balancer, deploy Amazon ElastiCache for Redis in a Multi-AZ configuration to manage caching and persistent session state, and implement Aurora Replicas with Aurora Auto Scaling to scale read queries horizontally.
Pre-warming the Application Load Balancer ensures the proxy instances are scaled out before the traffic arrives. Amazon ElastiCache for Redis provides the required sub-millisecond latencies for metadata caching and session lookup, and its Multi-AZ replication ensures durability. Using Aurora Replicas with Aurora Auto Scaling provides the necessary read capacity scaling, offloading the database writer instance.

Adım Adım Çözüm

1
Address the load balancing layer scalability limitations for flash crowds.
Identify that automatic scaling of ALBs is reactive and slow for extreme spikes, requiring pre-warming by AWS Support to pre-allocate capacity.
Prevents immediate HTTP 502/504 errors when millions of requests hit the load balancer within a 5-minute window.
2
Select the correct caching engine for persistent, highly available session data.
Choose Amazon ElastiCache for Redis over Memcached because Redis supports replication, data structures, and multi-AZ configurations for high availability.
Ensures that user sessions survive node or AZ failures without requiring users to re-authenticate.
3
Implement database horizontal read scaling.
Configure Aurora Replicas and target them using the cluster reader endpoint, enabling Aurora Auto Scaling to adjust instance counts.
Enables the database to scale read operations dynamically, avoiding overload on the primary writer node.

Anahtar Kavram

Handling extreme flash traffic by pre-warming load balancers, selecting replication-capable in-memory data stores, and scaling database reads horizontally using active replica scaling.
Soru 246Soru

A logistics and supply chain enterprise is modernizing its fleet dispatching and tracking application by migrating its core API to a serverless architecture on AWS. The API must handle highly bursty and unpredictable transaction volumes, spiking up to 15,00015,000 requests per second. The backend logic runs on AWS Lambda and reads from an Amazon Aurora PostgreSQL database cluster deployed in a private VPC subnet. To protect the database from connection exhaustion, an Amazon RDS Proxy has been deployed. The API Gateway endpoint is private, accessible only from the company's corporate offices through an existing AWS Direct Connect connection. The architect must ensure that:

1. Bursty traffic spikes do not exhaust the regional Lambda concurrency limit, which would throttle other critical serverless workloads in the same AWS account.
2. The database credentials, stored in AWS Secrets Manager, are rotated automatically every 3030 days and encrypted using a KMS key that can be shared with a monitoring tool in a separate security audit account.
3. The serverless compute layer remains highly available and resilient to Availability Zone failures.

Which combination of actions 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: Configure a reserved concurrency limit on the Lambda function to control the maximum concurrent executions, preventing the function from consuming the entire regional account concurrency pool.; Store the database credentials in AWS Secrets Manager, enable automatic rotation, and encrypt the secret using a Customer Managed Key (CMK), configuring the KMS key policy to permit decryption by both the Lambda execution role and the cross-account security audit role.

Cevap

Configure a reserved concurrency limit on the Lambda function and use a Customer Managed Key (CMK) for encrypting the database credentials in Secrets Manager with cross-account access.
Configuring a reserved concurrency limit sets a ceiling on the Lambda function's parallel executions, which isolates its resource usage and protects other regional serverless applications from throttling. Storing the credentials in Secrets Manager and using a Customer Managed Key (CMK) allows full customization of the KMS key policy, making it possible to grant cross-account decryption rights to the audit monitoring tool.

Adım Adım Çözüm

1
Analyze the impact of high-volume bursty traffic on Lambda concurrency limits.
Unconstrained Lambda functions can scale rapidly and consume the entire account's regional concurrency pool.
Applying reserved concurrency guarantees a maximum execution limit for the specific function and prevents it from starving other workloads.
2
Evaluate KMS encryption options for Secrets Manager cross-account access.
AWS-managed KMS keys cannot have their key policies modified to delegate cross-account access.
A Customer Managed Key (CMK) must be used so that its key policy can be updated to trust the external security audit account's role.
3
Assess high availability and networking practices for serverless integrations.
Lambda functions must be mapped to multiple subnets across different Availability Zones with redundant NAT Gateways to avoid a single point of failure.
This guarantees execution resiliency in the event of an Availability Zone outage.

Anahtar Kavram

Serverless architectures require concurrency controls to protect shared account resources, and cross-account access to encrypted data requires Customer Managed Keys (CMKs).
Soru 247Soru

A telemetry collection system running on Amazon EC2 instances in Account A needs to publish environment alerts to an Amazon SNS topic in Account B. To meet internal security and compliance policies, the SNS topic must be encrypted at rest. The Solutions Architect needs to design a secure, least-privilege configuration to allow the instances in Account A to publish to the topic in Account B. Which configuration will allow the EC2 instances in Account A to publish to the SNS topic in Account B while maintaining encryption?

Cevabı ve açıklamayı göster

Cevap: Configure the SNS topic in Account B to use a Customer Managed Key (CMK). Update the KMS key policy in Account B to grant the EC2 instance profile role in Account A permissions for the kms:GenerateDataKey and kms:Decrypt actions. Update the SNS topic policy in Account B to allow the sns:Publish action for the EC2 instance profile role in Account A.

Cevap

Configure the SNS topic in Account B to use a Customer Managed Key (CMK), update the KMS key policy in Account B to grant the EC2 instance profile role in Account A permissions for the kms:GenerateDataKey and kms:Decrypt actions, and update the SNS topic policy in Account B to allow the sns:Publish action for the EC2 instance profile role in Account A.
The correct configuration uses a Customer Managed Key (CMK) in the target account (Account B) and updates its key policy to allow the publishing role in Account A to perform kms:GenerateDataKey and kms:Decrypt. Combined with updating the SNS topic policy to permit sns:Publish from the Account A role, this satisfies least-privilege and security requirements.

Adım Adım Çözüm

1
Select the correct encryption key type.
A Customer Managed Key (CMK) in Account B is chosen instead of the default AWS-managed KMS key.
AWS-managed keys do not support key policy modifications, making them unusable for cross-account access scenarios.
2
Configure the KMS key policy.
The key policy of the CMK in Account B is updated to grant kms:GenerateDataKey and kms:Decrypt to the IAM role from Account A.
The publisher in Account A needs to generate a data key to encrypt the messages before they are processed by SNS.
3
Configure the SNS topic policy.
The resource-based policy of the SNS topic in Account B is updated to allow sns:Publish for the Account A IAM role.
Cross-account access to Amazon SNS requires explicit permission in the destination resource policy.

Anahtar Kavram

Cross-account encryption permissions using KMS Customer Managed Keys
Soru 248Soru

A logistics company manages 120120 member accounts within an AWS Organization. The security team is setting up an organization-wide AWS CloudTrail trail to log all API activity to a centralized Amazon S3 bucket in a dedicated Logging account. The requirements state that all logs must be encrypted using an AWS KMS Customer Managed Key (CMK) and that access must follow the principle of least privilege. Which TWO configuration steps are required to achieve this goal?

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

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket policy in the Logging account to grant write permissions (s3:PutObject) to the AWS CloudTrail service principal (cloudtrail.amazonaws.com) for all log paths, with a condition matching the organization's ID using aws:PrincipalOrgID.; Create a customer managed key (CMK) in the Logging account, and configure its key policy to allow the CloudTrail service principal (cloudtrail.amazonaws.com) to perform kms:GenerateDataKey* and kms:DescribeKey operations, with a condition matching the organization's ID using aws:PrincipalOrgID.

Cevap

Configure the S3 bucket policy to grant write access to the CloudTrail service principal with a condition for the AWS Organization ID, and create a customer managed key (CMK) in the Logging account with a key policy allowing the CloudTrail service principal to generate data keys and describe the key, constrained by the Organization ID.
Centralizing CloudTrail logs in a multi-account setup requires configured bucket and key policies that allow the CloudTrail service principal (cloudtrail.amazonaws.com) to access resources in the Logging account. To ensure that only member accounts within the specific AWS Organization can deliver logs, the aws:PrincipalOrgID condition is used. S3-managed and AWS-managed KMS keys cannot be shared across accounts for CloudTrail logging, so a Customer Managed Key (CMK) must be created and configured with a key policy that delegates kms:GenerateDataKey* and kms:DescribeKey permissions to CloudTrail.

Adım Adım Çözüm

1
Set up the centralized S3 bucket policy.
The S3 bucket in the dedicated Logging account is configured to accept log delivery from the CloudTrail service principal across all accounts in the organization by using the aws:PrincipalOrgID condition.
CloudTrail is a service principal that writes logs to the bucket on behalf of the member accounts, so S3 bucket permissions must be granted to the service principal with organizational boundaries.
2
Configure the KMS customer managed key key policy.
A Customer Managed Key (CMK) is created with a key policy allowing cloudtrail.amazonaws.com to generate data keys and describe the key, restricted to the organization's accounts using the aws:PrincipalOrgID condition key.
AWS-managed keys cannot be shared cross-account, so a CMK is required. The key policy must allow CloudTrail to encrypt logs as they are written from any account in the organization.

Anahtar Kavram

Centralizing AWS CloudTrail logs in a multi-account environment requires delegating S3 write permissions and KMS decryption/encryption permissions to the CloudTrail service principal with organization-level scoping using the aws:PrincipalOrgID condition.
Tahmini Süre:2m 0s
Soru 249Soru

A financial services company is migrating its backend payment processing microservice to a serverless architecture using Amazon API Gateway and AWS Lambda. Due to strict compliance and risk mitigation guidelines, any deployment of a new code version must be exposed to production traffic gradually. Specifically, the new version must receive 10% of traffic initially, and then the remaining traffic must be routed in equal increments of 10% every 10 minutes. If the payment processing latency exceeds 500 ms or if the Lambda error rate exceeds 1% at any point during the deployment, the deployment must automatically and immediately roll back. Additionally, the Lambda function relies on a database connection pool that must be fully initialized and pre-warmed before the new version starts serving any production traffic to prevent connection timeout errors during the initial traffic shift. Which deployment strategy should the solutions architect implement to meet these requirements with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy the Lambda function using AWS CloudFormation and configure the AWS::Lambda::Alias resource with a DeploymentPreference type set to CodeDeployDefault.LambdaLinear10PercentEvery10Minutes. Associate the deployment with CloudWatch Alarms for function errors and latency. Define a BeforeAllowTraffic lifecycle hook in the AppSpec file to execute a validation Lambda function that pre-warms the database connection pool.

Cevap

Deploy the Lambda function using AWS CloudFormation with the AWS::Lambda::Alias DeploymentPreference set to CodeDeployDefault.LambdaLinear10PercentEvery10Minutes, configured with CloudWatch Alarms for rollback, and a BeforeAllowTraffic lifecycle hook to run a validation function that pre-warms the database connection pool.
The optimal solution uses AWS CloudFormation to manage the serverless deployment via AWS CodeDeploy. A linear shifting strategy (CodeDeployDefault.LambdaLinear10PercentEvery10Minutes) satisfies the requirement of routing traffic in equal 10% increments every 10 minutes. Using a BeforeAllowTraffic lifecycle hook allows a validation Lambda function to run and initialize the database connection pool before the actual traffic starts shifting, preventing latency or connection timeouts for the first users. Integrating CloudWatch Alarms with CodeDeploy provides automated rollback capabilities.

Adım Adım Çözüm

1
Analyze the traffic shifting requirement
Identify that the system requires shifting traffic in 10% increments every 10 minutes until completed, which matches a linear deployment configuration (CodeDeployDefault.LambdaLinear10PercentEvery10Minutes) rather than a canary configuration.
Choosing the correct deployment configuration configuration is essential for meeting compliance and risk mitigation guidelines.
2
Determine the proper lifecycle hook for database pre-warming
Identify that the database connection pool must be warm before the new version begins serving any production traffic, which requires the BeforeAllowTraffic lifecycle hook.
The BeforeAllowTraffic hook runs a validation Lambda function to pre-warm resources before any production traffic is shifted to the new alias. Using AfterAllowTraffic would execute too late, causing connection timeouts during the deployment.
3
Configure the automated rollback mechanism
Associate CloudWatch Alarms for Lambda error rate and latency to the CodeDeploy deployment group.
If any alarm triggers during the deployment, CodeDeploy will automatically stop the deployment and redirect 100% of traffic back to the original stable version, satisfying the rollback requirement.

Anahtar Kavram

AWS CodeDeploy Lambda Traffic Shifting and Lifecycle Hooks
Tahmini Süre:3m 0s
Soru 250Soru

A digital media company is hosting a live pay-per-view sporting event. Within a 55-minute window before the broadcast begins, the web portal is expected to experience a sudden surge in traffic from 500500 requests per second to 300,000300,000 requests per second. The application runs on Amazon ECS with AWS Fargate behind an Application Load Balancer (ALB) and performs read-heavy entitlement verifications against an Amazon Aurora MySQL database. Which two actions should the solutions architect take to ensure the architecture scales efficiently and handles the sudden traffic spike without performance degradation? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Aurora Auto Scaling to dynamically add Aurora Replicas to the cluster based on average CPU utilization, and configure the application to use the reader endpoint for entitlement queries.; Submit a request to AWS Support to pre-warm the Application Load Balancer (ALB) to handle the expected traffic volume of 300,000300,000 requests per second.

Cevap

The solutions architect should configure Aurora Auto Scaling to dynamically add Aurora Replicas to the cluster while pointing the application to the reader endpoint, and submit a support ticket to pre-warm the Application Load Balancer (ALB) for the expected surge.
Pre-warming the Application Load Balancer ensures it is scaled to the target capacity beforehand, avoiding initial packet drops due to the sudden surge. Dynamically scaling Aurora Replicas based on CPU utilization and routing queries to the reader endpoint allows the database layer to handle the load of the read-heavy entitlement checks.

Adım Adım Çözüm

1
Evaluate the database scaling requirements for read-heavy workloads.
Identify that Aurora Replicas can be scaled dynamically using Aurora Auto Scaling and that queries should be directed to the reader endpoint.
This offloads read traffic from the primary writer node and distributes the database read load.
2
Evaluate the load balancer's behavior during sudden, massive surges.
Determine that standard ALB scaling is too slow for a surge from 500500 to 300,000300,000 requests per second within 55 minutes.
Pre-warming the ALB ensures the load balancing layer is scaled beforehand to prevent connection timeouts and service failures.

Anahtar Kavram

Handling flash traffic surges and scaling read workloads in AWS requires pre-warming the load balancer and dynamically scaling database read replicas.
Soru 251Soru

A financial services company is designing a disaster recovery (DR) solution for a critical transaction auditing application. The application currently runs in the us-east-1 Region on Amazon ECS tasks using AWS Fargate behind an Application Load Balancer (ALB). The database tier uses a Multi-AZ Amazon Aurora PostgreSQL cluster. Outbound connections to external clearinghouses must go through NAT Gateways. The company needs to establish a DR site in the us-west-2 Region. The business requirements specify a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes, while minimizing infrastructure costs during normal operations. Which of the following architectures meets these requirements most cost-effectively?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the Amazon ECS application in both regions, but set the service desired task count to zero in us-west-2. Set up an ALB in each region, and deploy NAT Gateways in each Availability Zone in both VPCs. Configure Amazon Route 53 Failover routing policies with health checks pointing to the ALBs. In a failover scenario, promote the Aurora secondary cluster and scale up the ECS tasks in us-west-2.

Cevap

Configure Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the Amazon ECS application in both regions, but set the service desired task count to zero in us-west-2. Set up an ALB in each region, and deploy NAT Gateways in each Availability Zone in both VPCs. Configure Amazon Route 53 Failover routing policies with health checks pointing to the ALBs. In a failover scenario, promote the Aurora secondary cluster and scale up the ECS tasks in us-west-2.
The correct architecture uses Amazon Aurora Global Database to achieve near-instantaneous cross-region replication, matching the strict 5-minute RPO. Setting the Amazon ECS desired task count to zero in the disaster recovery region avoids compute costs during normal operations while allowing rapid scale-up (well within the 15-minute RTO) when Route 53 detects a failover condition. Deploying NAT Gateways in each Availability Zone satisfies the high availability requirements for outbound API calls.

Adım Adım Çözüm

1
Evaluate replication capability for RPO.
Amazon Aurora Global Database provides cross-region physical replication with latency typically under 1 second, fulfilling the 5-minute RPO requirement.
Choosing a replication technology with sub-second lag guarantees that data loss is minimized during regional failovers.
2
Determine compute tier configuration for RTO and cost.
Pre-deploy the ECS task definitions and services in the secondary region but scale the desired task count to zero.
This implements a warm standby/pilot light architecture that incurs no Fargate compute costs during normal operations, yet allows scaling up tasks within a few minutes to meet the 15-minute RTO.
3
Configure highly available outbound connectivity.
Deploy a NAT Gateway in each Availability Zone of the VPCs in both regions.
Deploying NAT Gateways per AZ ensures that the outage of a single AZ does not disrupt outbound traffic to external clearinghouses from the remaining AZs.
4
Establish global DNS routing and health checks.
Configure Route 53 Failover routing policy with health checks pointing to the ALBs.
Active-passive failover routing automatically routes user traffic to the secondary region ALB once the primary endpoint health check fails.

Anahtar Kavram

Disaster Recovery strategies (Warm Standby/Pilot Light) balancing RTO/RPO objectives with cost-effectiveness, combined with database cross-region replication and NAT Gateway high availability.
Soru 252Soru

A gaming company is designing a new multiplayer game. The backend requires a database for a NoSQL workload to store real-time player session states with sub-millisecond latency. It also requires an Object storage solution to store historical game telemetry logs for analytical processing, which must be replicated to a centralized security logging account in a secondary AWS Region. The key performance indicators (KPIs) include write latency under 10 ms10\text{ ms} for player state updates, 99.99%99.99\% availability, and a disaster recovery requirement of Recovery Time Objective (RTO) under 15 minutes15\text{ minutes} and Recovery Point Objective (RPO) under 5 minutes5\text{ minutes}. Encryption at rest is required for all data. Which two options should the solutions architect choose to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon DynamoDB with global tables enabled across two AWS Regions to store player session states, using on-demand capacity mode.; Configure Amazon S3 Cross-Region Replication (CRR) to copy telemetry logs to the centralized security account's S3 bucket, using a customer managed KMS key in the source region and authorizing replication in the destination key policy.

Cevap

Deploy Amazon DynamoDB with global tables enabled across two AWS Regions to store player session states, and configure Amazon S3 Cross-Region Replication (CRR) to copy telemetry logs to the centralized security account's S3 bucket, using a customer managed KMS key.
Deploying Amazon DynamoDB global tables provides multi-region active-active deployment, satisfying the RTO and RPO limits and providing sub-millisecond latencies. Replicating S3 telemetry logs to a centralized account across regions requires using a customer managed KMS key, as the default key policy of AWS-managed KMS keys cannot be modified to authorize cross-account actions.

Adım Adım Çözüm

1
Evaluate the database requirements for the player session NoSQL workload.
Amazon DynamoDB with global tables is selected because it offers active-active multi-region replication, sub-millisecond latency, and satisfies the RTO under 15 minutes15\text{ minutes} and RPO under 5 minutes5\text{ minutes} constraints.
Relational options like standard RDS Multi-AZ cannot serve read traffic from standby nodes, and manual backup replication models fail the RPO targets.
2
Evaluate the object storage replication and encryption requirements for telemetry logs.
Amazon S3 Cross-Region Replication (CRR) configured with a customer managed KMS key is selected.
Cross-account replication with KMS encryption requires a customer managed key because the default AWS-managed KMS key policy cannot be modified to grant cross-account access.

Anahtar Kavram

Designing highly available, low-latency cross-region architectures using Amazon DynamoDB global tables and secure cross-account Amazon S3 replication using customer managed KMS keys.
Tahmini Süre:3m 0s
Soru 253Soru

A financial services company is launching a new transaction reporting API on Amazon ECS using AWS Fargate. A Solutions Architect must design a deployment strategy that routes exactly 10% of production traffic to the new version of the API, holds it there for a 30-minute validation window, and then shifts the remaining 90% of traffic to the new version. The deployment must automatically roll back within minutes if target response times exceed acceptable thresholds or if HTTP 5XX error rates spike. The solution must minimize costs and avoid DNS caching issues.

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 AWS CodeDeploy deployment group with the production listener, a test listener, and two target groups, and select the CodeDeployDefault.ECSCanary10Percent30Minutes deployment configuration.; Create Amazon CloudWatch alarms to monitor the Application Load Balancer's 5XX count and target response time metrics, and configure the CodeDeploy deployment group to automatically roll back if these alarms are triggered.

Cevap

The correct actions are to configure an AWS CodeDeploy deployment group with the CodeDeployDefault.ECSCanary10Percent30Minutes deployment configuration, and to create Amazon CloudWatch alarms monitoring the Application Load Balancer's 5XX count and target response times to trigger automatic rollback in CodeDeploy.
The correct options implement a native AWS CodeDeploy canary deployment on Amazon ECS. Using the CodeDeployDefault.ECSCanary10Percent30Minutes configuration shifts exactly 10% of traffic to the new target group (green) and holds it for 30 minutes. To detect failures and automatically roll back, CloudWatch alarms for 5XX count and target response time must be associated with the CodeDeploy deployment group. The deployment shifts traffic by modifying Application Load Balancer target group weights, which avoids DNS caching issues.

Adım Adım Çözüm

1
Select a canary traffic routing pattern in AWS CodeDeploy.
Using the CodeDeployDefault.ECSCanary10Percent30Minutes deployment configuration ensures 10% of traffic is routed to the new target group for exactly 30 minutes before shifting the rest.
This satisfies the requirement to route exactly 10% of traffic to the new version and validate it for 30 minutes.
2
Set up Application Load Balancer routing via CodeDeploy.
CodeDeploy updates the listener rules of a single ALB to direct traffic to two target groups (blue and green), adjusting weights without DNS caching impacts.
This avoids DNS caching issues and minimizes load balancer infrastructure costs.
3
Configure CloudWatch Alarms and link them to CodeDeploy's automatic rollback.
CloudWatch alarms monitor the ALB's HTTPCode_Target_5XX_Count and TargetResponseTime. CodeDeploy is configured to automatically roll back the deployment if these alarms transition to the ALARM state during the deployment window.
This provides automated, fast rollback capability if application latency or error rates spike.

Anahtar Kavram

Canary deployments on Amazon ECS using AWS CodeDeploy and Application Load Balancers
Soru 254Soru

A medical device company is designing a high availability and disaster recovery architecture for its patient monitoring dashboard. The primary database runs on an Amazon Aurora PostgreSQL DB cluster in the us-east-1 Region. The system requires an RTO of 15 minutes and an RPO of 5 minutes. The architecture must span a secondary Region (us-west-2) for disaster recovery. The network design requires private connections from on-premises hospitals using AWS Direct Connect, routing through Transit Gateways in both Regions.

Which TWO network and database configuration designs should the Solutions Architect implement to meet the HA/DR requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database with a secondary DB cluster in the secondary Region, and use Route 53 Application Recovery Controller routing controls to manage traffic routing during failover.; Deploy a dedicated NAT Gateway in each Availability Zone of the private subnets' VPCs to ensure outbound connectivity remains highly available across all active zones.

Cevap

Configure Amazon Aurora Global Database with a secondary DB cluster using Route 53 Application Recovery Controller, and deploy a dedicated NAT Gateway in each Availability Zone of the private subnets' VPCs.
Implementing Amazon Aurora Global Database ensures sub-second asynchronous replication, which fits well within the 5-minute RPO constraint, while Route 53 Application Recovery Controller facilitates fast multi-region routing failovers to meet the 15-minute RTO. Additionally, placing a NAT Gateway in every Availability Zone guarantees that a failure in one zone does not disrupt egress traffic for instances located in other zones, preserving high availability.

Adım Adım Çözüm

1
Analyze database replication and failover mechanisms for multi-region DR.
Amazon Aurora Global Database provides the low-latency asynchronous replication required to achieve the 5-minute RPO, and using Route 53 Application Recovery Controller routing controls allows failover orchestration within the 15-minute RTO.
Traditional backups or snapshot-based replication cannot satisfy these aggressive recovery objectives due to copy frequencies and restoration times.
2
Evaluate NAT configuration for outbound high availability.
A dedicated NAT Gateway is placed in each Availability Zone so that outbound internet traffic from private subnets is resilient to a single-zone outage.
Sharing a single NAT Gateway across multiple Availability Zones introduces a single point of failure, violating high availability principles.
3
Ensure internal DNS resolution is fully functional in both the primary and disaster recovery Regions.
The Route 53 Private Hosted Zone must be associated with all active and recovery VPCs.
If the Private Hosted Zone is not associated with the secondary Region's VPCs, name resolution will fail upon disaster recovery activation.

Anahtar Kavram

High Availability and Disaster Recovery Design
Soru 255Soru

An enterprise needs to migrate 220 TB220\text{ TB} of legacy document archives from an on-premises NFS file system to an Amazon S3 bucket. The enterprise has a 500 Mbps500\text{ Mbps} internet connection, but to avoid impacting business operations, they can allocate a maximum of 150 Mbps150\text{ Mbps} of bandwidth for the migration, and only during a 10 hour10\text{ hour} daily off-peak window. The migration must be completed within 25 days25\text{ days}. Additionally, company compliance requires that the data be encrypted at rest using an AWS KMS key that is shared with a separate AWS audit account for security verification.

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

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

Cevabı ve açıklamayı göster

Cevap: Order multiple AWS Snowball Edge Storage Optimized devices to copy the data locally and ship them to AWS for import into the Amazon S3 bucket.; Create a KMS Customer Managed Key (CMK) in the target account, configure the key policy to grant the audit account decrypt permissions, and specify this key during the Snowball Edge job creation.

Cevap

The correct migration plan is to order multiple AWS Snowball Edge Storage Optimized devices for physical transfer and configure a KMS Customer Managed Key (CMK) with cross-account permissions in its key policy.
The correct strategy uses multiple AWS Snowball Edge Storage Optimized devices because transferring 220 TB220\text{ TB} of data over a 150 Mbps150\text{ Mbps} connection for only 10 hours10\text{ hours} per day would take more than 320 days320\text{ days}, which fails the 25 days25\text{ days} requirement. Additionally, a KMS Customer Managed Key (CMK) must be created to facilitate cross-account decryption permissions, as the key policy for the default AWS managed key cannot be updated to allow access to the audit account.

Adım Adım Çözüm

1
Calculate the time required for a network-based migration: 220 TB220\text{ TB} over 150 Mbps150\text{ Mbps} for 10 hours10\text{ hours} per day.
Daily transfer capability is 150 Mbps×36000 seconds=5.4 Terabits675 GB150\text{ Mbps} \times 36000\text{ seconds} = 5.4\text{ Terabits} \approx 675\text{ GB} per day. Transferring 220 TB220\text{ TB} would take approximately 326 days326\text{ days}.
To determine whether the online path (AWS DataSync) can meet the 25 days25\text{ days} requirement.
2
Evaluate the offline data transfer options based on the calculated timeline.
AWS Snowball Edge Storage Optimized devices must be used since shipping and importing the devices will take approximately 77 to 10 days10\text{ days}, well within the 25 days25\text{ days} limit.
To select the correct physical shipping mechanism for high-volume, time-constrained migration.
3
Address the cross-account KMS key sharing requirements.
Create a KMS Customer Managed Key (CMK) and grant decrypt access to the secondary audit account via key policy modifications.
AWS-managed keys (like aws/s3) cannot be shared cross-account as their key policies cannot be modified.

Anahtar Kavram

Selecting between AWS DataSync and Snowball Edge based on data size, available bandwidth, and transfer timeline, while utilizing Customer Managed Keys (CMKs) to satisfy cross-account key sharing compliance.
Soru 256Soru

A major ticketing platform is preparing for a global concert ticket launch. The platform expects an instantaneous traffic spike, surging from a baseline of 2,0002,000 requests per second to 600,000600,000 requests per second within 33 minutes (a 300×300\times increase). The current architecture consists of an Application Load Balancer (ALB) routing traffic to containerized microservices hosted on Amazon ECS using AWS Fargate. The microservices query an Amazon Aurora PostgreSQL database cluster for ticket inventory and real-time seat availability. The architecture must minimize latency, handle the massive flash traffic without dropping requests, and dynamically scale the read capacity of the database tier. Which of the following architectures meets these requirements with the highest performance and operational efficiency?

Cevabı ve açıklamayı göster

Cevap: Submit a support ticket to AWS to pre-warm the Application Load Balancer to handle the expected peak of 600,000600,000 requests per second. Configure a scheduled scaling policy on the Amazon ECS service to scale out Fargate tasks ahead of the launch. Enable Aurora Auto Scaling for the Aurora PostgreSQL database cluster to dynamically add Aurora Replicas based on CPU utilization to handle the read query load.

Cevap

Submit a support ticket to AWS to pre-warm the Application Load Balancer, configure a scheduled scaling policy on Amazon ECS to scale out Fargate tasks, and enable Aurora Auto Scaling for the Aurora PostgreSQL cluster.
The correct architecture combines pre-emptive scaling actions (ALB pre-warming and ECS scheduled scaling) to bypass the bootstrap latency of reactive scaling policies during an instantaneous flash crowd. For the database layer, it correctly leverages Aurora Replicas and Aurora Auto Scaling to distribute the read query load horizontally across multiple active endpoints.

Adım Adım Çözüm

1
Address the entry point scaling limitation.
The Application Load Balancer is pre-warmed by AWS Support to handle the target throughput of 600,000600,000 requests per second.
An ALB scales dynamically based on traffic, but a sudden 300×300\times surge within 33 minutes exceeds the rate at which the ALB can spawn new controller nodes, leading to connection timeouts and dropped packets.
2
Pre-provision compute resources for the microservices.
ECS Fargate tasks are scaled out prior to the event using a scheduled scaling policy.
Fargate tasks require time to pull container images, bootstrap, and pass health checks. Relying on reactive target tracking during an instantaneous spike results in a severe compute deficit during the critical initial minutes of the launch.
3
Scale the database read capacity horizontally.
Aurora Auto Scaling is enabled to dynamically provision Aurora Replicas based on CPU utilization.
Aurora supports up to 1515 reader replicas that share the same underlying storage volume with minimal replication lag (typically under 100 ms100\text{ ms}), providing a highly performant and scalable read tier.

Anahtar Kavram

Handling extreme flash traffic spikes requires pre-warming load balancers, scheduled compute scaling, and horizontal read scaling using database replicas instead of passive disaster recovery instances.

Alternatif Yöntem

Instead of relying on relational read replicas, the architecture could incorporate Amazon DynamoDB with DynamoDB Accelerator (DAX) if the data model is migrated to a key-value store, enabling microsecond read latencies and seamless horizontal scaling for high-frequency reads.
Tahmini Süre:3m 0s
Soru 257Soru

A major airline is preparing to launch a flash promotional event where discounted international flight tickets will be released at a specific second. The marketing department expects an immediate surge in traffic, with concurrent user connections scaling from fewer than 100100 to over 450,000450,000 within the first 6060 seconds of the launch. The backend application, running on Amazon ECS, queries flight availability from an Amazon Aurora PostgreSQL database (with a read-to-write ratio of 10:110:1). The system must also store transient flight search filters and user session data, which requires a caching solution that supports Multi-AZ replication and data persistence to survive cache node failures. Which architecture optimization strategy will handle the peak traffic spike while maintaining low latency and preventing request failures?

Cevabı ve açıklamayı göster

Cevap: Request AWS Support to pre-warm the Application Load Balancer to the expected traffic volume, scale the Aurora database reads horizontally by configuring Aurora Auto Scaling with Aurora Replicas, and use Amazon ElastiCache for Redis with Multi-AZ enabled to store the persistent user session state.

Cevap

The strategy that pre-warms the Application Load Balancer, utilizes Aurora Auto Scaling with Aurora Replicas for read scaling, and deploys Amazon ElastiCache for Redis with Multi-AZ for session persistence.
The correct strategy addresses all three scaling constraints. First, requesting AWS Support to pre-warm the Application Load Balancer is essential because the expected flash traffic spike (from 100100 to 450,000450,000 concurrent connections within 6060 seconds) happens too quickly for standard load balancer auto-scaling to react, which would cause HTTP 503 / connection errors. Second, configuring Aurora Auto Scaling with Aurora Replicas allows the database tier to scale read operations horizontally to match the 10:110:1 read-heavy workload. Third, Amazon ElastiCache for Redis supports Multi-AZ replication and data persistence, ensuring that user session states are preserved and highly available in the event of a cache node failure.

Adım Adım Çözüm

1
Address the immediate, massive connection surge from the flash traffic profile.
Determine that the Application Load Balancer (ALB) must be pre-warmed via an AWS Support request.
An instantaneous jump from 100100 to 450,000450,000 concurrent users in 6060 seconds exceeds the default scaling rate of ALBs, leading to HTTP 503 errors and dropped requests if not pre-warmed.
2
Design the scaling strategy for the Amazon Aurora database reads.
Configure Aurora Auto Scaling to dynamically provision Aurora Replicas based on CPU or connection metrics.
The database workload is read-heavy (10:110:1 read-to-write ratio). Horizontal scaling with Aurora Replicas offloads read traffic from the writer node. RDS Multi-AZ standby nodes cannot serve read traffic.
3
Select the appropriate caching technology to handle transient user session states and filters.
Select Amazon ElastiCache for Redis with Multi-AZ and replication enabled.
ElastiCache for Memcached lacks persistence and built-in Multi-AZ replication/failover features, making Redis the correct choice to meet the resilience and durability requirements.

Anahtar Kavram

Load balancer pre-warming, horizontal database read scaling with Aurora Replicas, and selecting caching engines based on replication and persistence requirements.
Tahmini Süre:2m 0s
Soru 258Soru

A maritime shipping coordinator is modernizing its vessel container tracking and dispatch service by refactoring a legacy monolithic system into a microservices-based serverless architecture. The database has been migrated to an Amazon RDS for PostgreSQL DB instance in a private subnet. The serverless backend consists of AWS Lambda functions running in the same VPC to access the database, fronted by an Amazon API Gateway HTTP API. The system must scale up to handle sudden peaks of 12,00012,000 concurrent requests during port unloading operations, without exhausting database connections or affecting other services in the same AWS account. Security requirements dictate that all database credentials must be rotated automatically every 3030 days and encrypted using a Customer Managed Key (CMK) in AWS KMS.

Which TWO configurations should the solutions architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon RDS Proxy in the VPC to manage database connection pooling, and configure the Lambda functions with a defined reserved concurrency limit.; Configure AWS Secrets Manager to store database credentials using a Customer Managed Key (CMK) in AWS KMS, and configure a custom rotation Lambda function to rotate the secret every 3030 days.

Cevap

Deploy an Amazon RDS Proxy in the VPC to manage database connection pooling, configure the Lambda functions with a defined reserved concurrency limit, and configure AWS Secrets Manager to store database credentials using a Customer Managed Key (CMK) in AWS KMS with a custom rotation Lambda function to rotate the secret every 3030 days.
Deploying an Amazon RDS Proxy solves the database connection exhaustion issue by pooling and sharing connections. Configuring reserved concurrency limits the maximum concurrency of the container tracking Lambda functions, thereby protecting the rest of the account's unreserved pool from exhaustion. Using AWS Secrets Manager with a Customer Managed Key (CMK) allows the policy modifications required to grant necessary permissions for rotating the credentials.

Adım Adım Çözüm

1
Assess database connection limits and Lambda scaling behavior.
Identified that Lambda's rapid horizontal scaling up to 12,00012,000 concurrent requests will exhaust the PostgreSQL connection limits.
Connection pooling is required to manage connections efficiently under peak serverless loads.
2
Address concurrency isolation across the AWS account.
Identified that unthrottled functions can consume the entire regional concurrency pool.
Configuring reserved concurrency protects the unreserved concurrency pool and prevents other workloads in the account from being starved.
3
Design credential management and key delegation.
Stored credentials in AWS Secrets Manager using a Customer Managed Key (CMK).
A Customer Managed Key is required to modify key policies to support cross-account access or security boundaries during automatic rotation.

Anahtar Kavram

Modernizing monolithic database-backed APIs to a serverless architecture requires managing database connection pooling (using Amazon RDS Proxy), controlling compute concurrency to prevent account-level resource starvation, and configuring secure credential rotation using AWS Secrets Manager with Customer Managed Keys.
Tahmini Süre:3m 0s
Soru 259Soru

A retail banking platform is launching a feature that gives customers real-time access to their investment portfolios. The platform expects an instantaneous spike of over 200,000200,000 concurrent users daily at exactly 09:00 UTC09:00\text{ UTC} when the market opens. The application is hosted on Amazon EC2 instances within an Auto Scaling group behind an Application Load Balancer (ALB). The portfolio query engine reads data from an Amazon Aurora PostgreSQL database cluster. Which strategy should a Solutions Architect implement to handle this flash traffic without dropping customer requests or degrading query response times?

Cevabı ve açıklamayı göster

Cevap: Configure scheduled scaling for the EC2 Auto Scaling group to scale out before 09:00 UTC09:00\text{ UTC}. Request AWS Support to pre-warm the Application Load Balancer to the expected traffic volume, and configure Amazon Aurora Auto Scaling to scale Aurora Replicas to handle the spike in read queries.

Cevap

Configure scheduled scaling for the EC2 Auto Scaling group to scale out before 09:00 UTC09:00\text{ UTC}. Request AWS Support to pre-warm the Application Load Balancer to the expected traffic volume, and configure Amazon Aurora Auto Scaling to scale Aurora Replicas to handle the spike in read queries.
The correct strategy combines scheduled scaling for the EC2 Auto Scaling group, requesting ALB pre-warming from AWS Support, and using Amazon Aurora Auto Scaling. Scheduled scaling ensures that the EC2 instances are fully provisioned and booted before the predictable spike at 09:00 UTC09:00\text{ UTC}. Requesting AWS Support to pre-warm the ALB ensures the load balancer is provisioned with enough capacity to prevent dropped connections during the instantaneous spike. Configuring Aurora Auto Scaling allows the database to dynamically add Aurora Replicas to handle the surge in read queries.

Adım Adım Çözüm

1
Identify the scaling properties of the front-end load balancer under instant spike conditions.
Standard ALB scaling is reactive and cannot keep up with an instantaneous spike of 200,000200,000 concurrent users, which requires pre-warming by AWS Support.
Pre-warming ensures the ALB is pre-provisioned with adequate capacity to handle the sudden burst without dropping connections.
2
Address compute capacity scaling for predictable daily spikes.
Target tracking or step scaling policies are reactive and would lag, so scheduled scaling must be used to launch EC2 instances before 09:00 UTC09:00\text{ UTC}.
Scheduled scaling guarantees compute capacity is fully booted and ready when the traffic surge arrives.
3
Determine the appropriate database read scaling mechanism.
Aurora Replicas with Auto Scaling are configured to scale horizontally to handle query volume, while the Multi-AZ standby is not queryable.
Amazon Aurora Replicas handle read queries and support auto-scaling, whereas passive standby nodes are strictly for high availability and failover.

Anahtar Kavram

Handling instantaneous flash traffic spikes by combining load balancer pre-warming, scheduled compute scaling, and horizontal read scaling of database replicas.
Soru 260Soru

A telematics company is building a connected vehicle platform on AWS to ingest telemetry from a fleet of 1.5 million1.5\text{ million} vehicles. Each vehicle transmits GPS and engine diagnostics every 10 seconds10\text{ seconds} via HTTPS, producing a steady ingestion rate of 150,000150,000 requests per second. The platform must perform real-time geofencing checks (which require querying spatial boundaries) with a sub-50 ms50\text{ ms} latency target, and persist all incoming telemetry for historical reporting. During peak rush hours, traffic can double within a 22-minute window. Which of the following architectures is the most performant, scalable, and operationally efficient?

Cevabı ve açıklamayı göster

Cevap: Deploy a Network Load Balancer (NLB) to ingest the traffic, routing to an Amazon ECS cluster on AWS Fargate. ECS tasks write telemetry data to Amazon Kinesis Data Streams. Configure AWS Lambda functions to consume the stream, perform geofencing checks by querying spatial boundaries cached in Amazon ElastiCache for Redis, and write results to Amazon DynamoDB. Use Amazon Kinesis Data Firehose to archive raw telemetry to Amazon S3.

Cevap

Deploy a Network Load Balancer (NLB) to ingest the traffic, routing to an Amazon ECS cluster on AWS Fargate. ECS tasks write telemetry data to Amazon Kinesis Data Streams. Configure AWS Lambda functions to consume the stream, perform geofencing checks by querying spatial boundaries cached in Amazon ElastiCache for Redis, and write results to Amazon DynamoDB. Use Amazon Kinesis Data Firehose to archive raw telemetry to Amazon S3.
The correct answer combines a Network Load Balancer (NLB) to handle sudden spikes in traffic, Kinesis Data Streams for high-throughput ingestion buffering, ElastiCache for Redis to store geofence coordinates and execute geospatial lookups with sub-millisecond latency, and Kinesis Data Firehose to aggregate and write raw historical data to Amazon S3.

Adım Adım Çözüm

1
Analyze the load balancing tier requirements for flash traffic scaling.
Identify that the system must handle a sudden traffic spike from 150,000150,000 to 300,000300,000 requests per second within 2 minutes2\text{ minutes}. An Application Load Balancer cannot scale this quickly without pre-warming, whereas a Network Load Balancer handles sudden spikes of millions of requests per second out-of-the-box.
Choosing the correct load balancing service is critical to prevent connection drops at the ingestion layer.
2
Evaluate the database read and cache layer for low-latency geofencing queries.
Determine that querying spatial boundaries from a relational database or an RDS standby instance is either slow or impossible (since RDS standby DB instances do not support reads). Amazon ElastiCache for Redis provides geospatial query capabilities with sub-millisecond response times.
Meeting the sub-50ms latency target requires an in-memory database with geospatial index support.
3
Determine the streaming and archival path for high-throughput persistence.
Use Amazon Kinesis Data Streams to buffer the telemetry data from ECS, allowing decoupled downstream consumption. Use Kinesis Data Firehose to batch records and archive them to Amazon S3 efficiently.
Direct writes to Amazon S3 or individual API calls per message introduce extreme latency and scaling bottlenecks.

Anahtar Kavram

Decoupled architecture for high-throughput, low-latency streaming and rapid traffic spikes
ÖncekiSayfa 13 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin