All practice questions

1964 questions

Question 81Question

A company is designing a new transactional invoicing application (OLTP workload) that requires high-performance write operations and must dynamically scale read traffic to handle seasonal audits. The architecture requires a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 5 minutes. Additionally, database backups must be securely shared with and copied to a separate, centralized security AWS account. Which database and storage strategy meets these requirements?

Show answer & explanation

Answer: Deploy Amazon Aurora PostgreSQL with Aurora Auto Scaling enabled to adjust the number of Aurora Replicas based on CPU utilization. Encrypt the database using a Customer Managed Key (CMK) in AWS Key Management Service (AWS KMS). Share the KMS key and the Aurora database cluster snapshot with the security AWS account, allowing the security account to copy the encrypted snapshot using its own KMS key.

Answer

The strategy using Amazon Aurora PostgreSQL with Aurora Auto Scaling and a Customer Managed Key (CMK) for cross-account snapshot sharing.
Deploying Amazon Aurora PostgreSQL with Aurora Replicas and Auto Scaling satisfies the dynamic read-scaling requirement and ensures an RTO of under 5 minutes through automatic failover (typically completed in under 30 seconds). Since the database is encrypted with a Customer Managed Key (CMK), the key policy can be modified to grant the external security account permissions to decrypt and copy the shared snapshots, satisfying the security and RPO/RTO constraints.

Step-by-Step Solution

1
Analyze the high availability and read-scaling requirements.
The RPO under 1 minute and RTO under 5 minutes require a database engine with rapid failover and minimal replication lag. Aurora PostgreSQL meets this with sub-30-second failovers. To scale read traffic dynamically, Aurora Replicas with Auto Scaling can scale horizontal capacity in response to dynamic workloads.
This determines the optimal database deployment mode and engine choice.
2
Evaluate the encryption and cross-account backup requirements.
To copy encrypted database snapshots to another AWS account, a Customer Managed Key (CMK) must be used. Default AWS-managed KMS keys (such as aws/rds) cannot be shared across accounts as their key policies cannot be modified.
This addresses the security and compliance requirements for centralized auditing storage.

Key Concept

Cross-account snapshot sharing with Customer Managed Keys and dynamic read-scaling with Amazon Aurora
Estimated Time:2m 0s
Question 82Question

A retail company is modernizing its catalog query service by refactoring the legacy application to use Amazon API Gateway and AWS Lambda. The application queries an Amazon RDS MySQL database. During promotional events, traffic is expected to spike from 100100 requests per second (RPS) to over 5,0005,000 RPS within a few seconds. The Solutions Architect must ensure that database connections are not exhausted and that the traffic burst does not exhaust the AWS account's regional concurrent execution limit, which would throttle other critical services. The API must also only be accessible by the company's internal web application running in a separate VPC.

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

Select all that apply

Show answer & explanation

Answer: Configure Amazon RDS Proxy for the database, configure the Lambda function to connect through the RDS Proxy endpoint, and configure a reserved concurrency limit on the Lambda function.; Deploy an Amazon API Gateway private API, create an interface VPC endpoint (AWS PrivateLink) for API Gateway in the application VPC, and configure a resource policy on the private API that allows access only from the VPC endpoint.

Answer

Configure Amazon RDS Proxy, apply a reserved concurrency limit to the Lambda function, deploy a private API in Amazon API Gateway accessed via an interface VPC endpoint, and restrict access using a resource policy.
The correct options are the ones implementing Amazon RDS Proxy and Lambda reserved concurrency, along with an Amazon API Gateway private API with an interface VPC endpoint. RDS Proxy resolves database connection limits by pooling and sharing connections, while a reserved concurrency limit on the Lambda function prevents it from consuming the entire account's concurrency pool and throttling other functions. A private API Gateway endpoint combined with an interface VPC endpoint and an API resource policy keeps all client traffic inside the private AWS network.

Step-by-Step Solution

1
Address database connection pooling and scale constraints.
Configure Amazon RDS Proxy between the Lambda function and the RDS MySQL database.
RDS Proxy pools and shares database connections, preventing the thousands of concurrent Lambda executions during flash sales from exhausting the MySQL database connection limits.
2
Protect the AWS account's regional concurrent execution limit.
Set a reserved concurrency limit on the Lambda function.
A reserved concurrency limit guarantees that the function has a maximum limit it cannot exceed, preventing it from consuming the entire regional concurrency pool and throttling other services.
3
Secure the API access path to be internal-only.
Deploy a private API Gateway endpoint and access it through an interface VPC endpoint (AWS PrivateLink) inside the application VPC, with an API resource policy restricting access to this endpoint.
This keeps all traffic within the AWS private network, satisfying the requirement to prevent traversal of the public internet.

Key Concept

Scaling serverless workloads securely and reliably with Amazon API Gateway and AWS Lambda while protecting downstream resources like Amazon RDS.
Question 83Question

A global healthcare provider is designing a patient medical records portal. The portal application runs on Amazon ECS tasks inside an Application Account (Account 444444444444). The ECS tasks must upload scanned medical records directly to a centralized Amazon S3 bucket located in a dedicated Compliance Account (Account 888888888888). The solutions architect must design a security and compliance control structure that meets the following requirements:
1. All objects uploaded to the S3 bucket must be encrypted at rest.
2. The ECS tasks must be able to write records to the S3 bucket, but must not be able to read or delete any existing objects.
3. The Compliance Account must automatically own all uploaded records to prevent cross-account access delegation complexities.
4. Security auditors in the Compliance Account must be able to read and decrypt the records.

Which combination of configuration steps will meet these requirements in the most secure manner?

Show answer & explanation

Answer: In the Compliance Account, configure the S3 bucket's Object Ownership setting to Bucket Owner Enforced. Create a customer managed KMS key in the Compliance Account, and configure its key policy to allow the ECS task role in the Application Account permissions to perform kms:GenerateDataKey and kms:Decrypt, and allow auditors in the Compliance Account to perform kms:Decrypt. In the Compliance Account, update the S3 bucket policy to allow the ECS task role in the Application Account to perform s3:PutObject. In the Application Account, grant the ECS task role IAM permissions to perform s3:PutObject on the S3 bucket and kms:GenerateDataKey and kms:Decrypt on the KMS key.

Answer

Configure the S3 bucket's Object Ownership setting to Bucket Owner Enforced, create a customer managed KMS key in the Compliance Account with key policies allowing cross-account access, update the bucket policy to permit writing from the ECS task role, and configure the ECS task role with matching S3 and KMS permissions.
The correct solution uses S3 Object Ownership set to Bucket Owner Enforced to disable ACLs and transfer object ownership directly to the Compliance Account. It implements a customer managed KMS key because AWS-managed keys cannot be shared across accounts. It configures permissions on both the destination resources (S3 bucket policy and KMS key policy) and the source identity (ECS task role) to allow the write operation, which is the required configuration for cross-account IAM access.

Step-by-Step Solution

1
Configure S3 Object Ownership in the Compliance Account.
S3 Object Ownership is set to Bucket Owner Enforced.
This automatically disables S3 ACLs and ensures that the Compliance Account owns all objects written to the bucket by external accounts.
2
Create and configure a Customer Managed Key (CMK) in the Compliance Account.
A CMK is created with a key policy allowing the ECS task role in the Application Account to perform kms:GenerateDataKey and kms:Decrypt, and auditors in the Compliance Account to perform kms:Decrypt.
AWS-managed keys (aws/s3) cannot be shared across accounts. A customer managed key allows custom policies to delegate cross-account access. The ECS task role needs kms:Decrypt to support multi-part uploads with KMS encryption.
3
Configure the S3 bucket policy in the Compliance Account.
The bucket policy allows the ECS task role ARN to perform s3:PutObject.
Cross-account access to S3 requires the bucket policy in the destination account to explicitly trust the external principal.
4
Attach a local IAM policy to the ECS task role in the Application Account.
The ECS task role is granted permission to perform s3:PutObject on the S3 bucket and kms:GenerateDataKey and kms:Decrypt on the CMK.
For cross-account access, permissions must be granted in both the destination resource policy (S3 bucket policy and KMS key policy) and the source identity policy (ECS task role IAM policy).

Key Concept

Cross-account access to S3 buckets encrypted with AWS KMS customer managed keys, using Bucket Owner Enforced to simplify object ownership.
Question 84Question

An online multiplayer gaming platform is launching a weekly synchronized global tournament. Every Sunday at 18:00 UTC, the platform experiences an instant traffic spike, growing from a baseline of 2,0002,000 active connections to over 90,00090,000 active players initiating matchmaking requests within 6060 seconds. The backend architecture consists of an Application Load Balancer (ALB), an Amazon ECS cluster running on AWS Fargate, and an Amazon DynamoDB table that stores player session states. During initial testing of the tournament start, players experienced high latency, and a significant number of matchmaking requests resulted in HTTP 503503 Service Unavailable errors. Monitoring indicates that the ECS tasks scale out, but the bottlenecks occur at the entry point and during database write operations due to the sudden nature of the surge. Which two actions should a solutions architect take to optimize the performance and scalability of the platform for the tournament? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Submit a support ticket to AWS to pre-warm the Application Load Balancer to the expected throughput of 90,00090,000 concurrent player requests.; Configure scheduled scaling actions for the DynamoDB table to scale up the provisioned write capacity units (WCUs) before the tournament begins, and scale them down afterward.

Answer

The solutions architect should submit a support ticket to AWS to pre-warm the Application Load Balancer, and configure scheduled scaling actions for the DynamoDB table to scale up the provisioned write capacity units before the tournament begins.
The correct approach involves pre-warming the Application Load Balancer to handle the sudden, massive spike of 90,00090,000 concurrent matchmaking requests, and using scheduled scaling on the DynamoDB table to proactively provision sufficient write capacity before the tournament begins. This combination ensures that neither the traffic entry point nor the persistent storage layer becomes a bottleneck during the instant surge.

Step-by-Step Solution

1
Analyze the traffic profile and entry-point constraints.
The platform experiences an instantaneous surge from 2,0002,000 to 90,00090,000 active players within 6060 seconds, which exceeds the rate at which an Application Load Balancer can automatically scale without dropping connections.
Requesting AWS to pre-warm the ALB to the anticipated load guarantees that the load balancer has sufficient capacity provisioned immediately at the start of the tournament.
2
Analyze the database scaling constraints.
DynamoDB's standard auto-scaling mechanism relies on target tracking policies, which require a few minutes of sustained traffic before triggering scale-up events, resulting in write throttling during the first few minutes of the tournament.
Proactively scheduling scaling actions to provision sufficient capacity before the tournament begins ensures that the database is fully ready to handle the immediate burst in write requests.
3
Evaluate and eliminate incorrect architectures.
Using RDS Multi-AZ standbys for read/write scaling is incorrect because standbys do not serve traffic. Using Memcached for replication and persistence is incorrect because Memcached is a simple key-value store without support for replication or persistence features.
This step validates that the chosen options are performant, architecturally sound, and aligned with AWS best practices.

Key Concept

Handling instantaneous flash traffic spikes requires proactive pre-warming of load balancers and scheduled scaling of database capacity to prevent scaling delays and throttling.
Question 85Question

Apex Cargo Systems is designing a new cloud architecture. An application hosted on Amazon ECS tasks in the Operations account (Account 111122223333111122223333) must write transactional log files to an Amazon S3 bucket located in the Compliance Archive account (Account 444455556666444455556666). The logs must be encrypted at rest using an AWS KMS key managed by the Compliance team. The solution must ensure that files written to the bucket are encrypted and that the Operations account has the minimum necessary privileges to perform these writes.

Which combination of configuration steps will satisfy these security and compliance design requirements?

Show answer & explanation

Answer: Create a Customer Managed Key (CMK) in the Compliance Archive account. Configure the CMK key policy to allow the Operations account's ECS task role to perform `kms:GenerateDataKey` and `kms:Decrypt` actions. In the Compliance Archive account, configure the S3 bucket policy to allow `s3:PutObject` from the Operations account's ECS task role. In the Operations account, configure the ECS task role's IAM policy to allow `s3:PutObject` on the destination S3 bucket and `kms:GenerateDataKey` on the CMK.

Answer

Create a Customer Managed Key (CMK) in the Compliance Archive account, authorizing the Operations account's ECS task role in its key policy. Configure the destination S3 bucket policy to allow writes from the same ECS task role, and configure the ECS task role's local IAM policy to allow writes to the destination bucket and key generation on the CMK.
The correct option correctly uses a Customer Managed Key (CMK), since AWS-managed KMS keys cannot be shared across accounts. It also establishes permissions on both sides of the trust boundary: the destination resource policies (S3 bucket policy and KMS key policy) permit access from the source identity, and the source identity's IAM policy allows it to perform the actions on those target resources.

Step-by-Step Solution

1
Select a Customer Managed Key (CMK) over an AWS-managed KMS key for encryption.
Allows customizing the key policy to support cross-account usage, which is impossible with AWS-managed keys like `aws/s3`.
AWS-managed keys cannot be shared across accounts as their key policies cannot be modified.
2
Configure the CMK key policy to grant usage permissions to the Operations account's ECS task role.
Enables the external ECS task role to perform `kms:GenerateDataKey` and `kms:Decrypt` required for S3 upload encryption.
AWS KMS requires explicit cross-account permissions in the key policy for external principals to use the key.
3
Configure the S3 bucket policy in the Compliance Archive account.
Grants the Operations account's ECS task role permission to upload objects via `s3:PutObject`.
Cross-account S3 access requires the destination resource policy to explicitly allow the source identity.
4
Configure the source IAM policy on the ECS task role in the Operations account.
Gives the ECS task role local permission to access the remote bucket and KMS key.
For cross-account access, permissions must be enabled on both the target resource policy and the source IAM identity policy.

Key Concept

Cross-account resource sharing utilizing KMS Customer Managed Keys, S3 Bucket Policies, and IAM Identity Policies.
Question 86Question

A company is designing a new transactional retail application on AWS. The application requires a highly available relational database (OLTP workload) that can automatically scale to handle sudden bursts of read traffic. In addition, the application must write daily transaction logs to an Amazon S3 bucket. These logs must be shared with a centralized compliance account. The compliance account needs to read the logs using cross-account IAM roles, and the logs must be encrypted at rest. Which two options should the solutions architect select to meet these database and storage requirements? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon Aurora PostgreSQL DB cluster with a Multi-AZ configuration and enable Aurora Auto Scaling for the Aurora Replicas to handle the read traffic bursts.; Store the logs in an Amazon S3 bucket, configure the bucket policy to grant read access to the compliance account's IAM role, and encrypt the bucket using a Customer Managed KMS key with a key policy that permits cross-account access.

Answer

Deploying an Amazon Aurora PostgreSQL DB cluster with Aurora Auto Scaling for replicas, and configuring the Amazon S3 bucket with a custom bucket policy and a Customer Managed KMS key that allows cross-account access.
To handle sudden bursts of read traffic on a highly available relational database, Amazon Aurora PostgreSQL is suitable because it supports Multi-AZ deployment and horizontal read scaling via Aurora Replicas, which can auto-scale dynamically. For cross-account access to encrypted S3 resources, a Customer Managed KMS key must be used because AWS managed KMS keys (such as aws/s3) cannot be shared across accounts. Additionally, both the S3 bucket policy in the source account and the IAM policy in the compliance account must explicitly permit the access.

Step-by-Step Solution

1
Evaluate the database tier requirements for high availability and read scaling.
Determine that Amazon Aurora with Auto Scaling replicas is appropriate because Amazon RDS standby instances in a Multi-AZ deployment are passive and cannot serve read traffic.
This design satisfies the high availability and database read capacity scaling requirements.
2
Evaluate the storage encryption requirements for cross-account access.
Identify that AWS managed keys (aws/s3) cannot be shared across accounts, requiring a Customer Managed KMS key.
Cross-account access to KMS-encrypted resources requires key policies that can be customized, which is only supported by Customer Managed Keys.
3
Evaluate the S3 cross-account access control requirements.
Determine that both the IAM policy in the compliance account and the S3 bucket policy in the application account must grant permissions.
Cross-account access to S3 resources is only allowed if both the bucket owner and the IAM identity owner permit it.

Key Concept

Database read scaling and secure cross-account storage encryption strategy
Question 87Question

A mobile gaming company is launching a multiplayer game with a weekly competitive event. The event ends every Sunday at 20:00 UTC, at which point the leaderboard is frozen, rewards are calculated, and players immediately log in to claim their rewards and view the final rankings. The peak traffic is projected to jump instantly from a baseline of 2,0002,000 requests per second (RPS) to 350,000350,000 RPS within 30 seconds30\text{ seconds}. The leaderboard and session state must be persistent, highly available across multiple Availability Zones, and support sub-millisecond read/write latency. The backend consists of a microservices architecture hosted on Amazon Elastic Container Service (Amazon ECS) on AWS Fargate, fronted by an Application Load Balancer (ALB). The primary database is an Amazon Aurora MySQL cluster. Which design should a solutions architect recommend to handle this sudden surge in load while maintaining optimal performance?

Show answer & explanation

Answer: Request AWS Support to pre-warm the Application Load Balancer (ALB) to handle the expected 350,000350,000 RPS. Configure Amazon ECS Auto Scaling using scheduled scaling policies to scale out Fargate tasks ahead of the event. Use Amazon ElastiCache for Redis to cache session and leaderboard state with replication across Availability Zones, and configure Aurora Auto Scaling to add Aurora Replicas to the cluster based on CPU utilization.

Answer

Request AWS Support to pre-warm the Application Load Balancer (ALB), scale out Fargate tasks using scheduled scaling, utilize Amazon ElastiCache for Redis to handle session and leaderboard state with Multi-AZ replication, and use Aurora Auto Scaling with Aurora Replicas to scale read capacity.
The correct design addresses the scalability limits at every layer of the architecture. Pre-warming the ALB ensures the network routing layer is ready for the massive initial wave of traffic. Scheduled scaling for ECS Fargate ensures the application containers are bootstrapped and running before the rush begins. Using ElastiCache for Redis provides the required sub-millisecond latencies for session and leaderboard state while ensuring high availability through Multi-AZ replication. Finally, using Aurora Auto Scaling ensures database read capacity scales horizontally with replica instances.

Step-by-Step Solution

1
Address the immediate network ingress spike by requesting ALB pre-warming from AWS Support.
The ALB is configured with sufficient capacity beforehand to prevent connection drops when the traffic spikes to 350,000350,000 RPS.
Default ALB scaling processes can take several minutes to respond to sudden traffic increases, which is too slow for a 3030-second flash event.
2
Configure scheduled scaling for the ECS Fargate tasks to execute shortly before 20:00 UTC.
Compute instances are provisioned and warm, ready to immediately process the incoming player traffic.
Target tracking scaling is reactive and cannot spin up containers fast enough to prevent CPU exhaustion during the initial seconds of the spike.
3
Deploy Amazon ElastiCache for Redis to cache leaderboards and session state.
Sub-millisecond latency is achieved, and session data is preserved across Availability Zones via replication.
Unlike Memcached, Redis supports replication and data persistence, satisfying the high availability and state preservation requirements.
4
Configure Aurora Auto Scaling to dynamically provision read replicas.
The database read load is offloaded to horizontal replicas, maintaining primary database performance.
Aurora Replicas are required to scale read traffic. Multi-AZ standby instances cannot serve traffic and only function as failover targets.

Key Concept

Handling rapid, scheduled flash traffic spikes requires proactive provisioning (pre-warming, scheduled scaling) at the load balancing and compute tiers, combined with horizontal read replica scaling and high-availability caching using Redis.
Estimated Time:3m 0s
Question 88Question

A media streaming platform is designing a cross-region archive storage system for high-resolution video assets. The files contain proprietary digital media assets and must be stored in Amazon S3 buckets in two AWS Regions: uswest2us-west-2 (primary) and euwest1eu-west-1 (disaster recovery). The system architecture requires that files uploaded to uswest2us-west-2 are replicated to euwest1eu-west-1 using S3 Cross-Region Replication (CRR). The security policy requires:

- The media assets must be encrypted at rest using customer-managed KMS keys.
- In the event of a regional failover, applications in euwest1eu-west-1 must be able to decrypt the replicated data directly without performing any re-encryption or key management operations.
- The encryption keys must support automatic annual rotation.

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

Select all that apply

Show answer & explanation

Answer: Create a customer-managed multi-Region primary KMS key in the uswest2us-west-2 Region, and enable automatic key rotation on it.; Create a multi-Region replica key in the euwest1eu-west-1 Region using the ARN of the primary key in the uswest2us-west-2 Region.

Answer

The correct combination of actions is to create a customer-managed multi-Region primary KMS key in the primary region (uswest2us-west-2) with automatic rotation enabled, and create a corresponding multi-Region replica key in the disaster recovery region (euwest1eu-west-1) using the primary key's Amazon Resource Name (ARN).
The correct approach involves using AWS KMS multi-Region keys. By creating a customer-managed primary multi-Region key in the source region and enabling automatic key rotation, AWS manages the rotation of key material. Creating a replica key in the destination region using the primary key's ARN ensures both keys share the same key ID and key material. When S3 replicates the encrypted objects, the application in the destination region can decrypt them directly using the local replica key without needing to re-encrypt the data or make cross-region KMS API calls.

Step-by-Step Solution

1
Deploy the primary key in the source Region.
A customer-managed KMS key is created as a multi-Region primary key in uswest2us-west-2.
This establishes the master key that controls the key material and rotation configuration.
2
Configure rotation on the primary key.
Automatic annual key rotation is enabled on the primary key in uswest2us-west-2.
Enabling rotation on the primary key automatically rotates the key material and propagates the new material to all linked replica keys.
3
Create the replica key in the destination Region.
A replica KMS key is created in euwest1eu-west-1 referencing the primary key's ARN.
This guarantees that the destination key has the exact same key ID and key material as the primary key, enabling seamless decryption of replicated objects.

Key Concept

AWS KMS Multi-Region Keys
Question 89Question

An enterprise is designing a secure federated identity access strategy for its multi-account environment managed by AWS Organizations. The identity team is integrating an on-premises SAML 2.0 compliant Identity Provider (IdP) with target IAM roles in various member accounts. To meet regulatory compliance, the solutions architect must enforce the following security controls:
1. Federated users accessing roles in production accounts must have successfully completed a multi-factor authentication (MFA) challenge at the IdP.
2. No local IAM users or IAM access keys may be created or utilized within any member accounts in the organization.

Which combination of actions must the solutions architect take to implement these compliance controls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure the trust policy of the IAM roles in the production accounts to trust the SAML provider principal with the sts:AssumeRoleWithSAML action, and add a condition that evaluates the SAML:AuthnContextClassRef attribute to ensure it matches the multi-factor authentication context class from the Identity Provider.; Create a Service Control Policy (SCP) that denies the iam:CreateUser and iam:CreateAccessKey actions, and attach this SCP to the root of the AWS Organization.

Answer

The solutions architect must configure the trust policies of the target IAM roles to allow sts:AssumeRoleWithSAML and check the SAML:AuthnContextClassRef attribute for the MFA context. Additionally, the architect must create and attach an SCP at the root of the organization that denies the creation of IAM users and access keys.
The correct options state that the trust policy must use the sts:AssumeRoleWithSAML action and evaluate the SAML:AuthnContextClassRef attribute to enforce MFA, and that a Service Control Policy (SCP) denying iam:CreateUser and iam:CreateAccessKey must be attached to the root of the organization. Because SAML federated users authenticate via an external IdP rather than AWS directly, the native aws:MultiFactorAuthPresent condition key is not populated, requiring the use of the SAML assertion attribute instead. Additionally, SCPs are the standard mechanism to enforce global restrictions such as blocking IAM user and key creation in member accounts.

Step-by-Step Solution

1
Configure SAML federation trust relationship.
Create trust policies for the production IAM roles trusting the SAML provider principal with the sts:AssumeRoleWithSAML action.
This establishes the identity federation channel with the on-premises IdP.
2
Enforce MFA for federated sessions.
Evaluate the SAML:AuthnContextClassRef attribute in the IAM trust policy condition block.
Since the aws:MultiFactorAuthPresent condition key is only valid for AWS-managed MFA, SAML assertions must be verified using the AuthnContextClassRef attribute.
3
Implement governance guardrails against local IAM accounts.
Apply an SCP that denies the iam:CreateUser and iam:CreateAccessKey actions to the organization root.
SCPs act as maximum permission boundaries, ensuring that member accounts cannot create local IAM resources.

Key Concept

Enforcing security compliance controls through IAM federated role trust policies and organizational Service Control Policies (SCPs).
Estimated Time:3m 0s
Question 90Question

A financial services company runs a reporting application on AWS. The application uses an Amazon Aurora MySQL database cluster with one primary writer instance. The application workload is highly read-intensive, with a predictable 10×10\times increase in read queries during the final three days of each month. The write query volume remains low and constant. The solution must dynamically scale the read capacity to maintain query latencies under 100 ms100\text{ ms} while minimizing costs during periods of low activity.

Which database scaling strategy should a solutions architect recommend?

Show answer & explanation

Answer: Configure Amazon Aurora Auto Scaling to dynamically scale Aurora Replicas based on CPU utilization, and direct the application's read traffic to the Aurora reader endpoint.

Answer

Configure Amazon Aurora Auto Scaling to dynamically scale Aurora Replicas based on CPU utilization, and direct the application's read traffic to the Aurora reader endpoint.
The correct strategy leverages Amazon Aurora Auto Scaling to dynamically provision Aurora Replicas as read load increases. Aurora Replicas share the same storage volume as the primary instance, meaning scaling operations are fast and do not duplicate storage. Directing read traffic to the reader endpoint automatically load balances queries across all active replica instances.

Step-by-Step Solution

1
Analyze the scaling demands of the reporting application database tier.
Identified a recurring, predictable 10×10\times increase in read queries at the end of the month, with low and constant write traffic.
This establishes that only the read tier needs dynamic horizontal scaling, while the write tier remains stable.
2
Select the appropriate scaling mechanism for read capacity in Amazon Aurora.
Aurora Replicas are chosen because they share the underlying cluster volume, have minimal replication lag, and can be scaled horizontally up to 1515 replicas using Aurora Auto Scaling.
Aurora Auto Scaling dynamically adjusts the replica count based on CPU utilization or connection count metrics, maintaining performance during spikes and lowering costs when idle.
3
Determine the routing mechanism for database read queries.
The application's read queries are directed to the Aurora reader endpoint.
The reader endpoint automatically load balances connections across all active Aurora Replicas in the cluster.

Key Concept

Horizontal Read Scaling with Amazon Aurora Replicas and Auto Scaling
Estimated Time:2m 0s
Question 91Question

A solutions architect is designing the database strategy for a new high-frequency transactional banking portal (OLTP workload). The portal requires sub-10 millisecond read and write latencies, dynamic read scaling to handle unpredictable traffic spikes, and a Recovery Time Objective (RTO) of less than 30 seconds. In compliance with corporate security guidelines, the database must be encrypted at rest using a key managed in a separate centralized security AWS account. Which database and storage strategy meets these requirements?

Show answer & explanation

Answer: Deploy an Amazon Aurora PostgreSQL cluster with Multi-AZ deployment. Create an Aurora Replica and configure Aurora Auto Scaling to dynamically adjust the number of replicas based on CPU utilization. Encrypt the cluster using an AWS KMS Customer Managed Key located in the centralized security account, with cross-account access granted via the KMS key policy.

Answer

Deploy an Amazon Aurora PostgreSQL cluster with Multi-AZ deployment, configure Aurora Replicas with Aurora Auto Scaling for read capacity, and encrypt the cluster using a Customer Managed Key from the centralized security account via cross-account key policy permissions.
The correct strategy uses Amazon Aurora PostgreSQL with Multi-AZ and Aurora Replicas combined with Aurora Auto Scaling. This guarantees automatic failover within 30 seconds and allows read capacity to scale dynamically based on CPU metrics. To meet the security guidelines, a Customer Managed Key (CMK) is created in the security account and configured with a cross-account key policy, allowing the database service to perform cryptographic operations across accounts.

Step-by-Step Solution

1
Determine the database engine and read scaling mechanism.
Amazon Aurora PostgreSQL with Aurora Replicas and Auto Scaling is chosen to handle OLTP reads with sub-10ms latency and dynamic scaling.
Standard Amazon RDS Multi-AZ standbys cannot serve read queries, making Aurora Auto Scaling with Aurora Replicas necessary to meet dynamic read requirements.
2
Verify high availability and disaster recovery constraints.
Aurora PostgreSQL Multi-AZ deployment supports automatic failover in less than 30 seconds.
Manual promotion of cross-region replicas or secondary sites cannot reliably meet the strict RTO of less than 30 seconds.
3
Select the correct encryption key configuration for cross-account access.
Create a Customer Managed Key (CMK) in the centralized security account and configure the key policy to allow cross-account access from the database account.
AWS-managed keys (such as aws/rds) cannot be modified or shared across accounts, meaning a Customer Managed Key is required.

Key Concept

Selecting the optimal database and encryption architecture to satisfy high availability, read-scaling, and cross-account security requirements.
Question 92Question

A digital publishing company is launching a breaking news notification system. When a major global news event is broadcast, the system will send push notifications that will immediately drive a surge of over 80,00080,000 concurrent readers to a web portal within three minutes. The portal runs on Amazon EC2 instances within an Auto Scaling group behind an Application Load Balancer (ALB). The database backend is an Amazon Aurora PostgreSQL cluster with one primary writer and one replica. The portal's traffic is highly read-intensive, requiring dynamic read scaling of the database. Which actions should a Solutions Architect recommend to ensure the application scales effectively without dropping incoming traffic? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Request AWS Support to pre-warm the Application Load Balancer to the anticipated traffic volume before the launch of the breaking news system.; Configure Aurora Auto Scaling to dynamically add Aurora Replicas to the DB cluster based on average reader CPU utilization.

Answer

Request AWS Support to pre-warm the Application Load Balancer, and configure Aurora Auto Scaling to dynamically add Aurora Replicas based on reader CPU utilization.
Pre-warming the Application Load Balancer ensures that the load balancer is provisioned with sufficient capacity to absorb the massive, immediate traffic spike without dropping connections. Simultaneously, configuring Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas scales out the read backend to handle the surge in query volume effectively.

Step-by-Step Solution

1
Analyze the load behavior on the entry point (the Application Load Balancer) during an instantaneous surge.
Determine that the traffic spike from near-zero to 80,00080,000 concurrent readers occurs within three minutes, which exceeds the normal gradual scaling rate of an Application Load Balancer.
This shows that pre-warming is required to avoid dropped requests.
2
Evaluate options for database scaling to handle the high volume of read queries.
Determine that Amazon Aurora Replicas are the appropriate target for read traffic and can be scaled dynamically using Aurora Auto Scaling.
This addresses database read throughput constraints.
3
Eliminate sub-optimal or invalid options.
Discard options proposing RDS Multi-AZ standbys for read traffic, trusting the ALB to scale instantly without pre-warming, or using Memcached for multi-AZ replication.
This narrows the selection down to the two optimal and valid actions.

Key Concept

Handling sudden flash traffic on Application Load Balancers through pre-warming, and scaling read capacity dynamically using Aurora Replicas and Aurora Auto Scaling.
Question 93Question

A global advertising technology company is designing a real-time bidding and analytics platform. The platform must process over 22 million bid requests per second with sub-10 millisecond latency. The bidding system is stateless and deployed on Amazon ECS on AWS Fargate. Behind the bidding service, a read-heavy database stores user profiles (10 TB10\text{ TB}) and a write-heavy ingestion pipeline receives transaction logs. During scheduled high-profile sporting events, incoming request traffic spikes instantly from a baseline of 100,000100,000 requests per second to 2,000,0002,000,000 requests per second in less than one minute. Which two of the following architectural strategies should the solutions architect implement to optimize performance and scalability for these spikes? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy a Network Load Balancer (NLB) at the ingress tier to handle the instantaneous traffic surge without pre-warming, and configure Amazon ECS scheduled scaling to scale out the bidding tasks before the events begin.; Use Amazon Aurora PostgreSQL for the user profiles database, deploy Aurora Replicas to scale read capacity horizontally, and configure Application Auto Scaling to dynamically adjust the replica count based on CPU utilization.

Answer

Deploying a Network Load Balancer (NLB) at the ingress tier combined with scheduled ECS scaling, and using Amazon Aurora PostgreSQL with auto-scaling Aurora Replicas.
The correct strategy combines Network Load Balancers (NLBs) with Amazon ECS scheduled scaling to handle the immediate ingress and compute load, and uses Amazon Aurora Replicas to scale database reads. NLBs handle rapid, massive traffic surges natively without requiring pre-warming. Scheduled scaling ensures that the ECS tasks are scaled out in advance of the known event start time. For the database tier, Amazon Aurora Replicas scale read operations horizontally and support Application Auto Scaling to adjust capacity based on CPU utilization.

Step-by-Step Solution

1
Analyze the ingestion tier requirements under sudden flash traffic.
Identify that the ingress tier must scale from 100,000100,000 to 2,000,0002,000,000 requests per second in less than a minute. Standard ALBs require manual pre-warming for such instant spikes, whereas NLBs can handle sudden millions of requests natively.
Ensures the ingress layer does not drop connections or experience high latency during the initial moments of the spike.
2
Evaluate compute scaling mechanisms for rapid spikes.
Determine that target tracking and step scaling policies are reactive and take minutes to spin up tasks, which is too slow for sub-minute spikes. Scheduled scaling is required to scale out Fargate tasks proactively.
Ensures that compute capacity matches the incoming traffic volume before the load hits the system.
3
Evaluate database read scaling strategy.
Determine that the database must scale horizontally for reads. Since RDS Multi-AZ standby instances cannot serve reads, Amazon Aurora Replicas with Application Auto Scaling should be used to dynamically scale read operations.
Provides elastic read capacity to handle lookup traffic without overloading the database writer node.

Key Concept

Handling instantaneous, extreme load spikes requires proactive compute scaling, load balancers capable of handling rapid traffic shifts without pre-warming, and horizontal read scaling on the database tier.
Estimated Time:2m 30s
Question 94Question

A property management platform is modernizing its tenant building access logging system. The legacy application receives high-volume access event telemetry from IoT-enabled doors at peak hours, which causes database connection exhaustion on the backend Amazon RDS for PostgreSQL database. The database is located in a private VPC subnet. The platform requires the API endpoint to be accessible only from the corporate network over a private network connection. Which TWO actions should a solutions architect take to implement a serverless solution that meets these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure a private REST API in Amazon API Gateway, deploy an Interface VPC Endpoint for API Gateway, and attach an API Gateway resource policy that allows access from the Interface VPC Endpoint.; Configure Amazon RDS Proxy for the RDS for PostgreSQL database, and update the AWS Lambda functions to connect using the RDS Proxy endpoint.

Answer

Configure a private REST API in Amazon API Gateway with an Interface VPC Endpoint and a resource policy, and deploy Amazon RDS Proxy to manage database connection pooling for the AWS Lambda functions.
The correct options involve configuring a private REST API in Amazon API Gateway with an Interface VPC Endpoint and resource policy, and using Amazon RDS Proxy. A private REST API restricts access to the VPC, and the resource policy secures the endpoint against unauthorized network access. Amazon RDS Proxy pools database connections, preventing the bursty Lambda functions from exhausting PostgreSQL connection limits.

Step-by-Step Solution

1
Analyze the database connection scaling issue.
Identify that AWS Lambda functions scale horizontally and open a new connection per concurrent execution, which easily exhausts PostgreSQL connection limits.
Understanding the connection pooling behavior of Lambda is necessary to select the right database proxying solution.
2
Evaluate solutions for database connection limits.
Select Amazon RDS Proxy, which sits between Lambda and the database to pool and reuse connections.
RDS Proxy resolves connection limit issues for PostgreSQL under high concurrency.
3
Analyze private access requirements for API Gateway.
Select a private REST API in Amazon API Gateway integrated with an Interface VPC Endpoint and a resource policy.
A private API Gateway ensures the endpoint is not exposed to the public internet and restricts access to requests coming from the VPC or corporate network over Direct Connect.

Key Concept

Serverless modernization of legacy relational database workloads using API Gateway private endpoints and RDS Proxy connection pooling.
Question 95Question

A media company is migrating its legacy content metadata ingestion system to a serverless architecture on AWS. The system must process high-volume, bursty traffic from external publishing partners, decrypt incoming metadata payloads that are encrypted in an Amazon S3 bucket, and write updates to an Amazon Aurora PostgreSQL database. The design must be highly available, run within a private subnet, connect to the database securely without exhausting connections, and prevent traffic surges from throttling other critical Lambda functions in the AWS account. The external partners run their applications in a separate AWS account and need permission to access the encrypted S3 bucket. Which architecture meets these requirements?

Show answer & explanation

Answer: Configure Amazon API Gateway with a regional endpoint that triggers an AWS Lambda function. Configure the Lambda function in the VPC across multiple Availability Zones with an Amazon RDS Proxy to handle database connections. Set reserved concurrency on the Lambda function. Encrypt the S3 bucket using an AWS KMS Customer Managed Key (CMK) and grant cross-account access in the key policy. Configure NAT Gateways in multiple Availability Zones for outbound connectivity.

Answer

Configure Amazon API Gateway with a regional endpoint, run the AWS Lambda function in the VPC across multiple Availability Zones using Amazon RDS Proxy, set a reserved concurrency limit on the Lambda function, encrypt the S3 bucket using an AWS KMS Customer Managed Key (CMK) with cross-account access granted, and deploy NAT Gateways in multiple Availability Zones.
The correct answer provides a highly available, secure, and isolated solution. Running AWS Lambda within a multi-AZ VPC subnet and utilizing Amazon RDS Proxy ensures secure database communication while preventing connection limits from being exceeded during traffic bursts. Configuring reserved concurrency isolates the ingestion workload's concurrency usage, protecting other applications in the region from being throttled. A Customer Managed Key (CMK) is required because AWS-managed keys (such as aws/s3) cannot be shared across accounts. Lastly, deploying NAT Gateways in multiple Availability Zones eliminates single points of failure for outbound routing.

Step-by-Step Solution

1
Select the appropriate compute, database connection, and endpoint configurations.
Amazon API Gateway routes requests to Lambda, which uses RDS Proxy to queue and manage connection pooling to the Aurora PostgreSQL database, preventing connection exhaustion.
This guarantees that bursty traffic does not overwhelm the database with excessive concurrent connections.
2
Isolate compute resources from other applications in the account.
Configure reserved concurrency on the ingestion Lambda function.
Reserved concurrency limits the maximum number of concurrent executions for this specific function, protecting the account's regional concurrency pool from depletion and saving capacity for other critical applications.
3
Address the cross-account encryption requirements.
Encrypt the S3 bucket with a Customer Managed Key (CMK) in AWS KMS and add cross-account permissions in the key policy.
AWS-managed KMS keys (like aws/s3) cannot have their policies modified, so a Customer Managed Key is required to allow external AWS accounts to decrypt files.
4
Design the network architecture for high availability.
Deploy the Lambda function in private subnets across multiple Availability Zones and deploy multiple NAT Gateways.
A single NAT Gateway creates a single point of failure, violating high availability principles.

Key Concept

Serverless application architecture requiring connection pooling (RDS Proxy), resource isolation (Reserved Concurrency), cross-account encryption access (KMS CMK), and network fault tolerance (multi-AZ NAT Gateways).
Question 96Question

A biotechnology firm, BioGenetics Labs, is building a genomic analysis pipeline. The raw sequencing data is ingested into an Amazon S3 bucket in the Ingestion account (111122223333111122223333). The data must be replicated automatically to an S3 bucket in a dedicated Compliance and Archival account (555566667777555566667777) within the same AWS Organization. The compliance requirements specify that all objects must be encrypted at rest in both source and destination buckets using AWS KMS, the Ingestion account must not retain permission to read or delete the replicated objects once they are in the Compliance account, and access to decrypt the replicated data in the Compliance account must be restricted strictly to users within the Compliance account. Which of the following designs meets these security and compliance requirements?

Show answer & explanation

Answer: Configure Amazon S3 cross-account replication with the replica ownership override option enabled. In the Compliance account, configure the destination bucket to encrypt objects using a Customer Managed Key (CMK). Modify the key policy of this CMK to grant the Ingestion replication IAM role permissions for the kms:GenerateDataKey and kms:Encrypt actions. In the Ingestion account, grant the replication IAM role permissions to decrypt with the source KMS key and to encrypt and generate data keys with the destination CMK.

Answer

Configure Amazon S3 cross-account replication with the replica ownership override option enabled. In the Compliance account, configure the destination bucket to encrypt objects using a Customer Managed Key (CMK). Modify the key policy of this CMK to grant the Ingestion replication IAM role permissions for the kms:GenerateDataKey and kms:Encrypt actions. In the Ingestion account, grant the replication IAM role permissions to decrypt with the source KMS key and to encrypt and generate data keys with the destination CMK.
The correct design uses a Customer Managed Key (CMK) in the Compliance account because its key policy can be modified to trust the replication IAM role from the Ingestion account. By enabling replica ownership override, the ownership of the replicated objects transfers to the Compliance account, which allows the Compliance account's bucket and key policies to dictate access. Since the destination CMK's key policy does not grant decrypt permissions to the Ingestion account, users in the Ingestion account will be unable to read the data once it has been replicated, satisfying all compliance constraints.

Step-by-Step Solution

1
Select the correct key type for cross-account S3 replication encryption.
Identify that a Customer Managed Key (CMK) must be used in the destination Compliance account instead of the AWS-managed aws/s3 key.
AWS-managed keys do not allow policy modifications and cannot grant access to external accounts or roles, whereas CMKs can be configured to trust the replication role from the Ingestion account.
2
Ensure object ownership is transferred to the destination account.
Enable the replica ownership override option (Access Control Translation) in the replication configuration.
By default, replicated objects are owned by the source account. Overriding ownership transfers it to the destination Compliance account, allowing the destination account to enforce its own security boundary.
3
Configure the KMS key policies and IAM permissions for encryption/decryption boundaries.
Grant kms:GenerateDataKey and kms:Encrypt on the destination CMK to the replication role. Do not grant kms:Decrypt to the replication role or the Ingestion account on the destination CMK.
This allows the replication role to write encrypted objects to the destination bucket but prevents the Ingestion account from reading (decrypting) the objects once replicated, meeting the compliance requirements.

Key Concept

Cross-account AWS KMS access delegation and S3 replica ownership management for security boundary enforcement.
Question 97Question

A company is designing a new real-time mobile gaming leaderboard and user profile service (NoSQL and key-value caching workload) that must support users across North America and Europe. The key performance indicators include single-digit millisecond latency for both write and read operations globally. The session store and query cache must support data persistence, multi-Availability Zone replication, and sub-key eviction. Additionally, the database tier must support an active-active multi-region deployment to meet a Recovery Time Objective (RTO) of near-zero. Which of the following database and storage configurations should the solutions architect select to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon DynamoDB table with global tables enabled in the required regions to achieve active-active replication and single-digit millisecond latency.; Deploy an Amazon ElastiCache for Redis cluster with Multi-AZ and auto-failover enabled to cache frequent queries and provide session storage with data persistence.

Answer

Deploying an Amazon DynamoDB table with global tables enabled satisfies the active-active multi-region and low-latency database requirements. Deploying an Amazon ElastiCache for Redis cluster with Multi-AZ satisfies the caching and session store requirements including data persistence and sub-key eviction.
Deploying Amazon DynamoDB with global tables enabled provides active-active multi-region replication and single-digit millisecond latency. Deploying Amazon ElastiCache for Redis provides a persistent, replicated cache with sub-key eviction, meeting all key performance indicators.

Step-by-Step Solution

1
Determine the database requirements for active-active global replication.
Amazon DynamoDB with global tables is selected.
DynamoDB Global Tables provide the required active-active multi-region replication and single-digit millisecond read/write latency globally.
2
Determine the caching and session store requirements.
Amazon ElastiCache for Redis is selected.
Redis supports multi-AZ replication, auto-failover, data persistence, and sub-key eviction, unlike Memcached.
3
Eliminate sub-optimal or invalid options.
Options proposing RDS standby reads, Memcached, and pilot light DR are eliminated.
RDS standby instances cannot serve read traffic, Memcached lacks persistence and replication, and pilot light cannot meet a near-zero RTO requirement.

Key Concept

Selecting appropriate database and caching engines to meet multi-region active-active, performance, durability, and availability SLA requirements.
Question 98Question

A financial services company is designing a new compliance reporting pipeline. A data ingestion application running on Amazon EC2 instances in a Production account (Account ID 111111111111111111111111) must write monthly transaction reports directly to an Amazon S3 bucket located in a dedicated Security and Auditing account (Account ID 222222222222222222222222). All objects written to the destination S3 bucket must be encrypted at rest using Server-Side Encryption with AWS KMS (SSE-KMS) to meet PCI-DSS requirements. Which combination of S3 and KMS configuration will successfully allow the application to write encrypted reports to the bucket?

Show answer & explanation

Answer: Configure the destination S3 bucket to use a customer managed KMS key in the Security and Auditing account. Modify the key policy of this customer managed KMS key to grant the Production application's IAM role permission to perform the kms:GenerateDataKey and kms:Decrypt actions. Configure the destination S3 bucket policy to allow the Production application's IAM role to perform the s3:PutObject action. Attach an IAM policy to the Production application's IAM role that grants permissions to write to the S3 bucket and use the customer managed KMS key.

Answer

Configure the destination S3 bucket to use a customer managed KMS key in the Security and Auditing account. Modify the key policy of this customer managed KMS key to grant the Production application's IAM role permission to perform the kms:GenerateDataKey and kms:Decrypt actions. Configure the destination S3 bucket policy to allow the Production application's IAM role to perform the s3:PutObject action. Attach an IAM policy to the Production application's IAM role that grants permissions to write to the S3 bucket and use the customer managed KMS key.
The correct configuration uses a customer managed KMS key, updates its key policy to allow the Production role to generate a data key, updates the destination S3 bucket policy to allow the Production role to write objects, and configures the caller's local IAM policy. This satisfies all cross-account permission checks on AWS.

Step-by-Step Solution

1
Determine the KMS key type requirement for cross-account encryption.
Identify that AWS managed keys cannot be shared cross-account, meaning a customer managed KMS key must be created in the destination account (Security and Auditing account).
AWS managed KMS keys have read-only key policies that cannot be modified to delegate access to external account identities.
2
Configure the key policy for the customer managed KMS key.
Add a policy statement to the key in the Security and Auditing account that allows the Production IAM role principal to call kms:GenerateDataKey and kms:Decrypt.
When uploading objects to S3 with SSE-KMS, the caller needs to generate a data key to encrypt the payload.
3
Configure the S3 bucket policy in the Security and Auditing account.
Add a policy statement to the destination S3 bucket allowing s3:PutObject for the Production IAM role principal.
Cross-account resource access requires the destination resource's resource-based policy to explicitly trust and authorize the external identity.
4
Configure the IAM policy in the Production account.
Attach an IAM policy to the Production application's role allowing s3:PutObject on the destination S3 bucket and kms:GenerateDataKey/kms:Decrypt on the customer managed KMS key.
Cross-account access requires permissions to be granted in both the caller's IAM policy and the destination's resource-based policies.

Key Concept

Cross-account access with KMS encryption requires explicit authorization in the KMS key policy, destination S3 bucket policy, and source IAM identity policy, and is only supported with Customer Managed Keys.
Estimated Time:1m 30s
Question 99Question

A smart utility company is modernizing its on-premises customer smart meter management system by migrating to a serverless architecture on AWS. The solution will use Amazon API Gateway and AWS Lambda to process bursty configuration updates sent to millions of meters during scheduled maintenance windows. The Lambda functions must securely query and update an Amazon Aurora PostgreSQL database located in a private subnet. The functions also require highly available outbound internet access to retrieve security token updates from a third-party API. Any update to the Lambda functions must support automated rollback if latency increases.

Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure Amazon RDS Proxy between the Lambda functions and the Aurora PostgreSQL database, and configure AWS Lambda reserved concurrency for the configuration-update function.; Deploy the Lambda functions in private subnets across multiple Availability Zones, configure route tables to use a NAT Gateway in each Availability Zone, and use AWS CodeDeploy to execute a canary deployment with CloudWatch alarm monitoring.

Answer

Configure Amazon RDS Proxy with reserved concurrency for the Lambda function, and deploy the functions across multiple Availability Zones with dedicated NAT Gateways and AWS CodeDeploy canary deployments.
The correct architecture uses Amazon RDS Proxy to pool and reuse database connections, preventing connection exhaustion. It also reserves concurrency for the high-volume Lambda function to isolate its execution capacity and protect other workloads. Outbound traffic is kept highly available by utilizing a NAT Gateway per Availability Zone, and deployment risk is mitigated through CodeDeploy canary releases integrated with CloudWatch alarms.

Step-by-Step Solution

1
Address database connection exhaustion and scaling isolation.
Implement Amazon RDS Proxy to pool connections to the Aurora PostgreSQL database, and set reserved concurrency on the bursty Lambda function.
RDS Proxy prevents database crash from connection spikes, and reserved concurrency prevents the function from exhausting the regional limit.
2
Design highly available outbound network access.
Deploy the Lambda functions in private subnets across multiple Availability Zones and route traffic through a NAT Gateway in each AZ.
This avoids a single point of failure in case one Availability Zone experiences an outage.
3
Implement safe deployment and automated rollbacks.
Use AWS CodeDeploy with a canary deployment strategy combined with CloudWatch alarm tracking.
This automatically rolls back the update if key performance metrics like latency degrade during the deployment.

Key Concept

Designing highly available, scalable, and safe serverless architectures integrating Lambda, API Gateway, RDS Proxy, and NAT Gateways.
Estimated Time:2m 0s
Question 100Question

A company is designing a high-performance web application to support a highly anticipated, time-sensitive product release. The release event will start precisely at 15:00 UTC and is expected to attract an immediate wave of over 300,000300,000 concurrent users submitting search queries and orders. The proposed architecture consists of a stateless web tier running on Amazon EC2 instances behind an Application Load Balancer (ALB), and a database tier utilizing an Amazon Aurora MySQL database cluster. Which TWO actions should the solutions architect implement to ensure the application scales effectively and maintains sub-second latencies during the start of the event? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Submit a support case to AWS to pre-warm the Application Load Balancer (ALB) with the expected traffic profile prior to the event.; Configure an Auto Scaling group scheduled scaling policy to pre-provision the required number of EC2 instances for the web tier before 15:00 UTC.

Answer

Submit a support case to AWS to pre-warm the Application Load Balancer (ALB) prior to the event, and configure a scheduled scaling policy on the EC2 Auto Scaling group to pre-provision compute instances before 15:00 UTC.
The correct options recommend submitting an ALB pre-warming support ticket to ensure the load balancer is sized for the immediate burst, and using scheduled scaling for the EC2 Auto Scaling group to pre-provision instances before the spike occurs. This proactive strategy ensures both the entry point and the compute layer are ready to accept the sudden volume of traffic.

Step-by-Step Solution

1
Analyze the load characteristics of the event
Determine that the traffic spike is instantaneous (starting precisely at 15:00 UTC) and massive (300,000300,000 concurrent users).
Understanding the instantaneous nature of the load indicates that dynamic scaling policies (which respond reactively) will be too slow.
2
Address load balancer scalability constraints
Formulate a request for ALB pre-warming from AWS Support to handle the immediate burst in request rates.
This prevents the ALB from dropping connection requests during the initial minutes of the event while trying to scale out reactively.
3
Address compute tier scalability constraints
Create scheduled scaling actions to spin up the required web tier instances prior to the event's start time.
Pre-provisioning instances avoids latency spikes caused by instance startup and bootstrapping time.

Key Concept

Optimizing architectures for predictable flash events requires proactive resource provisioning (scheduled scaling) and pre-warming of infrastructure layers (such as load balancers) rather than relying solely on reactive scaling mechanisms.
PreviousPage 5 / 99Next
All practice questions — AWS Certified Solutions Architect - Professional | Examkin