All practice questions

1964 questions

Question 1781Question

A financial technology company is designing a new cloud-native wealth management application. The architecture must span two AWS Regions (Primary and Secondary) to support disaster recovery. The workload consists of:

1. An OLTP database containing transaction records. The database must sustain rapid, unpredictable spikes in read traffic, maintain read replication lag under 20 milliseconds, and support a disaster recovery plan with a Recovery Point Objective (RPO) of 1 second and Recovery Time Objective (RTO) of 1 minute.
2. A centralized audit vault containing monthly PDF statement exports. These statement files must be stored in Amazon S3, encrypted at rest, and made securely accessible to a compliance audit application running in a separate AWS account within the same AWS Organization.

Which combination of database and encryption configurations should a solutions architect select to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an Amazon Aurora Global Database with the primary cluster in the primary Region and a secondary cluster in the secondary Region, and configure Aurora Auto Scaling for the Aurora Replicas to handle read spikes.; Encrypt the S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and update the KMS key policy to grant the external audit account's IAM role permissions to decrypt the data.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in the primary Region and a secondary cluster in the secondary Region, configure Aurora Auto Scaling for the Aurora Replicas to handle read spikes, encrypt the S3 bucket using a Customer Managed Key (CMK) in AWS KMS, and update the KMS key policy to grant the external audit account's IAM role permissions to decrypt the data.
The correct combination requires Amazon Aurora Global Database for the transaction database to meet the 1-second RPO (via asynchronous physical replication) and 1-minute RTO (via fast promotion of the secondary cluster), with Aurora Auto Scaling to handle read spikes without exceeding the 20-millisecond replica lag constraint. For the cross-account S3 bucket access, a Customer Managed Key (CMK) in AWS KMS is required because its key policy can be updated to delegate access to the compliance audit account's role.

Step-by-Step Solution

1
Analyze the database requirements for RTO, RPO, and read scaling.
Identify that Amazon Aurora Global Database matches the RPO of 1 second (asynchronous physical replication lag is typically < 1 second) and RTO of 1 minute (secondary promotion takes less than a minute). Aurora Replicas share the same storage volume as the primary instance, keeping replication lag under 10 ms, and can scale dynamically using Aurora Auto Scaling.
This establishes the necessary database engine and multi-region replication architecture.
2
Analyze the S3 encryption and cross-account access requirements.
Determine that cross-account access to encrypted S3 objects requires a Customer Managed Key (CMK) because the default AWS-managed key (aws/s3) cannot have its key policy modified to delegate access to an external account.
This establishes the security and encryption architecture for the PDF statement exports.
3
Evaluate and eliminate incorrect database configurations.
Reject directing reads to the RDS Multi-AZ standby because it is passive and cannot serve read traffic. Reject daily snapshot replication because it fails the 1-second RPO and 1-minute RTO constraints.
This filters out sub-optimal or non-functional database setups.
4
Evaluate and eliminate incorrect encryption configurations.
Reject the option utilizing the default AWS-managed KMS key (aws/s3) for cross-account access because AWS-managed keys cannot be shared cross-account.
This filters out the invalid KMS design.

Key Concept

Selecting and configuring AWS database and storage services to meet strict RTO/RPO targets, read scalability, and secure cross-account encryption access.
Question 1782Question

An enterprise is implementing federated access to its production database AWS account. The database administrators must authenticate via an external SAML 2.0-compliant Identity Provider (IdP) and assume a specific administrative role (db-admin-role) in the database account. A Solutions Architect has created an IAM SAML identity provider in the target database account. However, when database administrators attempt to log in through the IdP portal, the authentication fails with a 'Not authorized to perform sts:AssumeRoleWithSAML' error. Which configuration change in the database AWS account will resolve this authentication failure?

Show answer & explanation

Answer: Update the trust policy of the database account's IAM role to specify the SAML identity provider as the Principal and allow the sts:AssumeRoleWithSAML action.

Answer

Update the trust policy of the database account's IAM role to specify the SAML identity provider as the Principal and allow the sts:AssumeRoleWithSAML action.
To authenticate external users via SAML 2.0, the target IAM role must have a trust policy that explicitly designates the IAM SAML provider as a federated principal and allows the sts:AssumeRoleWithSAML action. This allows the AWS Security Token Service (STS) to validate the SAML assertion and issue temporary credentials.

Step-by-Step Solution

1
Analyze the error message 'Not authorized to perform sts:AssumeRoleWithSAML'.
Identify that the federation flow requires the target IAM role to trust the SAML Identity Provider (IdP) for the specific sts:AssumeRoleWithSAML action.
SAML federation does not use the standard sts:AssumeRole action, but rather a dedicated API call designed for federating external users.
2
Review the trust policy of the target IAM role in the database account.
Ensure the Principal block references the ARN of the IAM SAML identity provider created in that account, and the Action is set to sts:AssumeRoleWithSAML.
The trust policy is the gatekeeper that allows external SAML assertions to exchange for temporary AWS security credentials.
3
Verify that Service Control Policies (SCPs) and KMS keys are not used to establish authentication trust.
Confirm that permission configuration lies within the IAM role trust policy and cannot be bypassed or configured via SCPs or AWS-managed KMS keys.
SCPs act as boundaries, not permission grantors, and AWS-managed KMS keys cannot have their policies altered.

Key Concept

SAML 2.0 federation trust relationships in AWS IAM
Estimated Time:1m 30s
Question 1783Question

A regional media broadcasting corporation is planning to migrate its on-premises broadcasting and media asset management (MAM) system to AWS. The environment consists of 120 VMware vSphere VMs hosting web servers, transcoding engines, and database systems. Strict corporate security policies prohibit the installation of any software agents on the database virtual machines. Additionally, there are 15 physical bare-metal media servers running an unsupported legacy Unix-like operating system. The on-premises network restricts direct outbound internet access, but a centralized proxy server is available for outbound HTTPS traffic. The corporation wants to perform a discovery phase to determine dependencies, estimate AWS sizing, and track the migration progress in AWS Migration Hub using both AWS and integrated third-party migration tools.

Which two actions should the Solutions Architect recommend to perform the discovery and track the migration progress in AWS Migration Hub? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy the AWS Agentless Collector in the VMware environment, configure it to route outbound traffic through the centralized HTTPS proxy server to perform discovery for the virtualized workloads, and manually import the metadata for the physical legacy servers using the AWS Application Discovery Service CSV template.; Register the third-party migration tools with AWS Migration Hub to automatically track the migration progress of the virtualized workloads, and use the AWS Migration Hub API or CLI to publish migration status updates for the manually migrated physical legacy servers.

Answer

Deploy the AWS Agentless Collector in the VMware environment to perform discovery for the virtualized workloads while routing traffic through the proxy, import the bare-metal servers' metadata using a CSV template, integrate third-party tools with AWS Migration Hub, and use the Migration Hub API/CLI for manual tracking.
The correct answer recommends using the AWS Agentless Collector to discover virtualized workloads, which is agentless and meets the constraint of not placing agents on the database VMs. It also supports configuration of proxy settings for outbound communications. For the physical bare-metal legacy systems running an unsupported OS, manual metadata import using the CSV template is the appropriate discovery strategy. Tracking is achieved by integrating third-party tools directly with AWS Migration Hub for automatically tracked workloads, and using the Migration Hub API/CLI for manual migrations.

Step-by-Step Solution

1
Determine the appropriate discovery mechanism based on server types, operating systems, and agent constraints.
Since database VMs cannot have agents and physical bare-metal servers run an unsupported OS, agent-based discovery is ruled out. Deploying the AWS Agentless Collector as a virtual appliance in VMware solves the VM discovery, and importing configuration details via a CSV template solves the legacy bare-metal server discovery.
This respects security policies prohibiting database VM agents and handles unsupported OS environments that cannot run the discovery agent.
2
Configure proxy settings for the discovery tools.
Configure the Agentless Collector to communicate with the AWS endpoint using the centralized proxy server over port 443.
The on-premises network restricts direct outbound internet access, necessitating proxy configuration.
3
Align tracking and migration tools in AWS Migration Hub.
Enable third-party migration tool integration with Migration Hub to track the VM migrations automatically, and use the Migration Hub API/CLI to manually publish status updates for the legacy bare-metal migrations.
This allows centralizing migration tracking in one dashboard across multiple migration tools and manual processes.

Key Concept

AWS Migration Discovery and Hub Integration
Question 1784Question

A global logistics provider has a multi-account AWS environment consisting of 2020 spoke VPCs spread across 22 AWS Regions: `us-east-1` and `us-west-2`. The provider must establish a highly available, transitive network topology that connects all VPCs to each other and to an on-premises datacenter over a new AWS Direct Connect connection. The architecture must minimize administrative overhead and scale easily as new VPCs are added. Which of the following actions should the solutions architect take to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy an AWS Transit Gateway in each Region, attach the local spoke VPCs to their respective Transit Gateway, and configure a Transit Gateway peering connection between the two Transit Gateways.; Create a Direct Connect gateway, associate it with the Transit Gateways in both Regions using transit virtual interfaces (transit VIFs) on the Direct Connect connections, and configure BGP to advertise VPC CIDR blocks to the on-premises datacenter.

Answer

To meet the requirements, the solutions architect should deploy an AWS Transit Gateway in each Region, attach the local spoke VPCs to their respective Transit Gateway, and configure a Transit Gateway peering connection between them. Additionally, the architect should create a Direct Connect gateway, associate it with the Transit Gateways in both Regions using transit virtual interfaces (transit VIFs) on the Direct Connect connections, and configure BGP to advertise the VPC CIDR blocks.
The correct solution involves deploying an AWS Transit Gateway in each Region to act as a regional hub for the local spoke VPCs and peering them to allow inter-region transitive routing. To connect to the on-premises datacenter, a Direct Connect gateway is associated with the Transit Gateways using transit virtual interfaces (transit VIFs), which allows BGP to advertise routes and enables hybrid connectivity.

Step-by-Step Solution

1
Design the regional hub-and-spoke VPC connectivity using AWS Transit Gateway.
An AWS Transit Gateway is created in `us-east-1` and `us-west-2`. Local VPCs in each Region are attached to their respective regional Transit Gateway, enabling centralized routing and simplified administration.
Transit Gateway simplifies VPC connectivity at scale and removes the management complexity of a full-mesh VPC peering configuration.
2
Enable inter-region VPC-to-VPC routing.
A Transit Gateway peering connection is established between the `us-east-1` Transit Gateway and the `us-west-2` Transit Gateway, with static routes configured to direct cross-region traffic.
Peering the Transit Gateways enables transitive routing across Regions for the spoke VPCs.
3
Design the hybrid connectivity to the on-premises datacenter.
A Direct Connect gateway is created and associated with the Transit Gateways in both Regions using transit VIFs on the AWS Direct Connect connections.
Transit VIFs are required to connect AWS Direct Connect to an AWS Transit Gateway, and the Direct Connect gateway allows multiple Transit Gateways to share the same hybrid connection.

Key Concept

AWS Transit Gateway simplifies multi-VPC and multi-account routing, while Transit Gateway Peering and Direct Connect Gateway with transit VIFs enable highly available, scalable inter-region and hybrid connectivity.
Question 1785Question

A healthcare provider manages 110110 AWS accounts under a single organization in AWS Organizations. The lead security architect is designing a centralized auditing solution to track resource configuration changes. AWS Config must be enabled in all member accounts, with configuration history and snapshots consolidated into a central Amazon S3 bucket in a dedicated Security account. The solution must meet the following requirements:
- All configuration logs must be encrypted at rest using a customer managed key (KMS CMK) controlled by the security team.
- The central S3 bucket must enforce a write-once-read-many (WORM) policy to prevent log deletion or modification, even by administrative users in the Security account.
- Individual member accounts must be prevented from disabling the AWS Config recording or altering the delivery channel configuration.

Which combination of actions will meet these requirements?

Show answer & explanation

Answer: In the Security account, create the S3 bucket with S3 Object Lock enabled in Compliance mode. Configure a bucket policy that grants the s3:PutObject and s3:GetBucketAcl permissions to the AWS Config service principal (config.amazonaws.com) and restricts access using the aws:PrincipalOrgID condition. In the Security account, create a KMS customer managed key (CMK) and configure its key policy to allow kms:GenerateDataKey* and kms:Decrypt for the AWS Config service principal (config.amazonaws.com) with the aws:PrincipalOrgID condition. Set the bucket default encryption to use this KMS CMK. In the management account, attach a Service Control Policy (SCP) to the organization root that denies config:StopConfigurationRecorder, config:DeleteDeliveryChannel, and config:PutDeliveryChannel actions.

Answer

In the Security account, create the S3 bucket with S3 Object Lock enabled in Compliance mode. Configure a bucket policy that grants the s3:PutObject and s3:GetBucketAcl permissions to the AWS Config service principal (config.amazonaws.com) and restricts access using the aws:PrincipalOrgID condition. In the Security account, create a KMS customer managed key (CMK) and configure its key policy to allow kms:GenerateDataKey* and kms:Decrypt for the AWS Config service principal (config.amazonaws.com) with the aws:PrincipalOrgID condition. Set the bucket default encryption to use this KMS CMK. In the management account, attach a Service Control Policy (SCP) to the organization root that denies config:StopConfigurationRecorder, config:DeleteDeliveryChannel, and config:PutDeliveryChannel actions.
The correct solution uses S3 Object Lock in Compliance mode to meet the WORM requirement, preventing even administrative users in the Security account from altering or deleting logs. S3 bucket policies and Customer Managed Key (CMK) policies in the Security account must explicitly grant access to the AWS Config service principal (config.amazonaws.com) using the aws:PrincipalOrgID condition to restrict access to the organization. Additionally, both s3:PutObject and s3:GetBucketAcl are required for AWS Config delivery, and the SCP effectively prevents member accounts from disabling the configuration recorder.

Step-by-Step Solution

1
Enable S3 Object Lock in Compliance mode on the target bucket in the Security account.
Enforces WORM retention, preventing administrative or root users from deleting or modifying objects in the bucket during the compliance window.
Meets the regulatory security requirement to prevent data tampering of centralized auditing logs.
2
Configure the S3 bucket policy to allow config.amazonaws.com to perform s3:PutObject and s3:GetBucketAcl, restricted by the aws:PrincipalOrgID condition.
Allows AWS Config delivery channels from all member accounts under the organization to verify bucket ownership and write log files.
AWS Config requires both permissions to successfully establish a delivery channel and write configuration records cross-account.
3
Create a Customer Managed Key (CMK) in the Security account, authorize config.amazonaws.com in the key policy, and enable S3 default encryption using this key.
Enables AWS Config service principals in the member accounts to use kms:GenerateDataKey* and kms:Decrypt to write encrypted configuration snapshots to S3.
AWS-managed keys (aws/s3) cannot be shared cross-account, so a Customer Managed Key is required for cross-account KMS encryption.
4
Attach a Service Control Policy (SCP) to the Organization Root that denies config:StopConfigurationRecorder, config:DeleteDeliveryChannel, and config:PutDeliveryChannel.
Prevents administrators in member accounts from turning off auditing or redirecting logs to an alternate destination.
Enforces operational compliance globally across the organization.

Key Concept

Centralized configuration auditing with AWS Config requires cross-account S3 bucket policies with GetBucketAcl and PutObject permissions, KMS customer managed keys with service principal delegation, S3 Object Lock for WORM compliance, and Service Control Policies to enforce governance.
Estimated Time:3m 0s
Question 1786Question

Aether Grid Solutions is modernizing its on-premises grid simulation engine by migrating the workload to Amazon ECS. The application consists of several high-performance containerized microservices that must bind directly to the host's network interface to bypass Docker network virtualization layers, minimize latency, and handle UDP broadcast traffic. The architecture must be highly available and deployed across multiple Availability Zones. To download external simulation datasets, the containers require outbound internet connectivity. The network security team mandates that this outbound path must not have any single points of failure. The infrastructure team wants to minimize the operational overhead associated with operating system patching and server provisioning where possible.

Which architectural design should the solutions architect recommend to satisfy these requirements?

Show answer & explanation

Answer: Deploy the tasks using the Amazon ECS EC2 launch type with the host network mode, configure an Auto Scaling group using the Amazon ECS-optimized AMI, and provision a NAT Gateway in each Availability Zone.

Answer

Deploy the tasks using the Amazon ECS EC2 launch type with the host network mode, configure an Auto Scaling group using the Amazon ECS-optimized AMI, and provision a NAT Gateway in each Availability Zone.
Deploying the containers on the Amazon ECS EC2 launch type using the host network mode allows the tasks to bind directly to the host's network interfaces, meeting the low-latency and UDP broadcast requirements. To minimize operational overhead, using an Auto Scaling group with the Amazon ECS-optimized AMI automates container instance management. Redundant NAT Gateways deployed across each Availability Zone ensure outbound connectivity is highly available without a single point of failure.

Step-by-Step Solution

1
Analyze the container networking requirements (direct host network interface binding and UDP broadcast support).
Identify that the host network mode is required, which is supported on Amazon ECS EC2 launch type but not on AWS Fargate.
AWS Fargate only supports the awsvpc network mode, which does not allow tasks to bind directly to the host network interface or support raw host-level networking behaviors like UDP broadcast.
2
Evaluate the high availability and outbound network connectivity requirements.
Determine that outbound internet access must be routed through redundant NAT Gateways in each Availability Zone.
A single NAT Gateway creates a single point of failure, violating the requirement for high availability and zero single points of failure in the outbound path.
3
Review the host management strategy to minimize operational overhead.
Implement an Auto Scaling group using the Amazon ECS-optimized AMI.
Using AWS-managed, container-optimized AMIs with Auto Scaling reduces the burden of manual OS patching and server provisioning.

Key Concept

Selecting the correct Amazon ECS launch type and network mode based on low-latency network performance and host-level binding constraints, combined with redundant network egress routing.
Estimated Time:2m 0s
Question 1787Question

A financial services firm, ApexLedger, is modernizing its transaction reconciliation application by migrating from on-premises virtual machines to AWS. The application consists of several containerized microservices that must run on a container orchestration platform. The backend reconciliation tasks require high CPU and memory resources that scale dynamically, and compliance mandates that each task must run in its own dedicated, isolated virtualization boundary with no sharing of the underlying host OS or resources with other tasks. The microservices must also communicate securely using internal DNS names across a multi-account network containing a Shared Services VPC and a Production VPC connected via AWS Transit Gateway. Finally, the application must decrypt sensitive transaction logs using a KMS key managed in a centralized Security account.

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

Select all that apply

Show answer & explanation

Answer: Configure the Amazon ECS task definitions to use the AWS Fargate launch type with the awsvpc network mode, register the services with AWS Cloud Map, and associate the resulting Route 53 Private Hosted Zone with both the Shared Services and Production VPCs.; In the centralized Security account, create a KMS Customer Managed Key (CMK) and update its key policy to grant the Amazon ECS task role in the Production account permissions to use the key for decryption.

Answer

The correct actions are configuring the task definitions to use AWS Fargate with the awsvpc network mode, registering with AWS Cloud Map, associating the Route 53 Private Hosted Zone with both VPCs, and creating a KMS Customer Managed Key in the Security account with a key policy allowing the Production ECS task role cross-account access.
AWS Fargate provides hypervisor-level VM isolation for each ECS task, meeting compliance rules against host-level resource sharing. Fargate mandates the awsvpc network mode. The Private Hosted Zone created by Cloud Map in the Shared Services account must be explicitly associated with the Production VPC to allow DNS resolution. Finally, cross-account access to KMS requires a Customer Managed Key (CMK) since AWS-managed key policies cannot be modified, and permissions must be granted to the task role (which the application uses) rather than the task execution role (used by the ECS agent).

Step-by-Step Solution

1
Select the container launch type and networking mode based on compliance boundary constraints.
Choose AWS Fargate with the awsvpc network mode.
AWS Fargate runs tasks in dedicated kernel-isolated VM boundaries, fulfilling the requirement of zero host resource sharing. Fargate only supports the awsvpc network mode.
2
Establish cross-account, multi-VPC name resolution for internal service communication.
Configure AWS Cloud Map and associate the resulting Route 53 Private Hosted Zone with the Production VPC.
Private Hosted Zones must be explicitly associated with each VPC that needs to resolve the namespace, regardless of the Transit Gateway connectivity between those VPCs.
3
Implement secure cross-account decryption of sensitive data.
Create a Customer Managed Key (CMK) in the Security account and grant permissions to the ECS task role.
AWS-managed keys do not support policy modifications for cross-account access. The ECS task role represents the application container runtime identity, which performs the decryption.

Key Concept

Amazon ECS task networking, Fargate isolation, Route 53 Private Hosted Zone multi-VPC association, and cross-account AWS KMS key policies.
Estimated Time:3m 0s
Question 1788Question

A smart-grid utility provider is modernizing its legacy telemetry collection backend by migrating to a serverless architecture on AWS. The system must process highly bursty, intermittent telemetry payloads from millions of smart meters via an API and write the processed records to an Amazon Aurora PostgreSQL database in a private subnet. The design must satisfy the following requirements:

1. Outbound internet traffic to third-party validation endpoints must be highly available and resilient to single Availability Zone failures.
2. The database must be protected from connection exhaustion during sudden traffic spikes.
3. Other critical microservices running in the same AWS account must be shielded from resource starvation caused by telemetry spikes.
4. Telemetry data must be encrypted with custom security policies and audit controls using AWS KMS.
5. Deployments of the backend code must shift traffic gradually to the new version over 1010 minutes and automatically roll back if errors occur.

Which of the following architectures meets these requirements while adhering to AWS best practices?

Show answer & explanation

Answer: Configure Amazon API Gateway with a regional endpoint integration to AWS Lambda. Deploy the Lambda functions in a private VPC spanning multiple Availability Zones, using Amazon RDS Proxy to manage database connection pooling. Deploy a NAT Gateway in each Availability Zone's public subnet to provide redundant outbound routes. Apply reserved concurrency to the ingestion Lambda function. Encrypt the data using an AWS KMS Customer Managed Key. Utilize AWS CodeDeploy with a canary deployment configuration, monitored by Amazon CloudWatch alarms, to shift traffic to new Lambda versions.

Answer

The architecture that configures API Gateway with a regional Lambda integration, uses Amazon RDS Proxy, deploys redundant NAT Gateways across multiple Availability Zones, applies reserved concurrency to the ingestion function, encrypts data with an AWS KMS Customer Managed Key, and utilizes AWS CodeDeploy canary shifting with CloudWatch alarms.
The correct architecture leverages a multi-AZ VPC layout with redundant NAT Gateways to ensure that outbound third-party validation traffic is not disrupted by a single AZ outage. Utilizing Amazon RDS Proxy protects the Aurora PostgreSQL database by pooling database connections during telemetry traffic bursts. To prevent telemetry spikes from exhausting the AWS account's execution concurrency and throttling other microservices, the ingestion function is configured with reserved concurrency, which sets a hard limit on its maximum concurrent executions. Security compliance is met by encrypting data using an AWS KMS Customer Managed Key, which allows for custom key policies and audit controls, unlike the default AWS-managed key. Finally, using AWS CodeDeploy with a canary configuration and CloudWatch alarms satisfies the requirement for a gradual, monitored deployment with automated rollbacks.

Step-by-Step Solution

1
Analyze VPC networking and redundancy requirements for outbound validation traffic.
Identify that to prevent a single point of failure across Availability Zones, a NAT Gateway must be deployed in each AZ's public subnet, rather than relying on a single NAT Gateway.
Ensures high availability and resilience for outbound traffic if a single zone experiences an outage.
2
Evaluate database connection scaling and performance under high-burst traffic.
Determine that an Amazon RDS Proxy is required between AWS Lambda and the Aurora PostgreSQL database to manage connection pooling.
Prevents the database from running out of connections during rapid, concurrent Lambda scaling events.
3
Address resource contention and concurrency management for serverless functions in the same AWS account.
Identify that reserved concurrency must be configured on the telemetry ingestion Lambda function to cap its maximum execution count and guarantee concurrency is available for other services.
Provisioned concurrency alone does not restrict a function from scaling beyond its provisioned capacity and consuming the regional pool, potentially throttling other services.
4
Assess encryption and key management compliance requirements.
Select an AWS KMS Customer Managed Key (CMK) instead of the default AWS-managed KMS key.
Customer Managed Keys allow modification of key policies, which is necessary to define custom access controls and audit capabilities.
5
Formulate the deployment and rollback strategy.
Use AWS CodeDeploy with a canary deployment configuration (e.g., shifting traffic over 1010 minutes) and CloudWatch alarms for automated rollback.
Minimizes deployment risk by gradually shifting alias traffic and rolling back automatically upon alarm breaches.

Key Concept

Serverless Modernization with API Gateway and Lambda Concurrency/Network Controls
Question 1789Question

An enterprise is migrating its legacy on-premises ERP application consisting of 15 virtual machines to AWS using AWS Application Migration Service (MGN). The hybrid connectivity between the on-premises data center and AWS is established via a 1 Gbps AWS Direct Connect connection that terminates at an AWS Transit Gateway in a centralized Network Services VPC. The Transit Gateway distributes traffic to a dedicated Staging VPC where the MGN replication servers are provisioned. After installing the AWS Replication Agent on the on-premises source servers, the migration team observes that the data replication status remains stuck at 'Initiating' and the agent log files show connection timeouts when attempting to reach the replication servers. Which of the following actions should a Solutions Architect take to resolve this issue and allow data replication to proceed?

Show answer & explanation

Answer: Configure the on-premises firewall to permit outbound traffic on TCP port 1500 to the staging area subnet CIDR block, and verify that the security group associated with the replication servers in the Staging VPC allows inbound traffic on TCP port 1500 from the on-premises IP address range.

Answer

Configure the on-premises firewall to permit outbound traffic on TCP port 1500 to the staging area subnet CIDR block, and verify that the security group associated with the replication servers in the Staging VPC allows inbound traffic on TCP port 1500 from the on-premises IP address range.
The correct answer is to configure the on-premises firewall and the Staging VPC security group to allow traffic on TCP port 1500. AWS MGN requires TCP port 1500 for replication data transmission from the Replication Agent on the source servers to the replication servers in the staging area. Opening this port resolves the connection timeout.

Step-by-Step Solution

1
Identify the network port required for data replication in AWS Application Migration Service (MGN).
AWS MGN requires TCP port 1500 to be open from the source servers to the replication servers in the staging area.
Although control plane communication uses HTTPS over port 443, the actual replication stream flows over TCP port 1500.
2
Analyze the network path and security controls between the on-premises environment and the Staging VPC.
The connection times out, indicating a firewall or security group block on the data replication port (TCP 1500) rather than a routing or DNS resolution failure.
A timeout indicates packets are being dropped by a security mechanism (firewall or security group) along the network path.
3
Verify and apply the correct security configurations.
Allowing outbound traffic on TCP port 1500 from on-premises and inbound traffic on the replication servers' security group establishes the replication channel.
This establishes private, secure data replication over the Direct Connect and Transit Gateway network path.

Key Concept

Data replication in AWS MGN requires TCP port 1500 to be open from the source servers to the replication servers in the staging area.
Estimated Time:2m 0s
Question 1790Question

A multinational retail pharmaceutical company manages 120 member accounts under AWS Organizations. The security team requires all VPC Flow Logs from all member accounts to be collected and consolidated into a single central Amazon S3 bucket in a dedicated Security account. For data security compliance, all log data must be encrypted at rest using a customer managed KMS key (CMK). Which configuration should a solutions architect recommend to meet these requirements with the least administrative overhead?

Show answer & explanation

Answer: Configure the Amazon S3 bucket in the Security account. Create a Customer Managed KMS key in the Security account with a key policy that allows the delivery.logs.amazonaws.com service principal to perform kms:GenerateDataKey* actions. Update the S3 bucket policy to allow the delivery.logs.amazonaws.com service principal to write objects. Configure VPC Flow Logs in each member account to publish to the central S3 bucket.

Answer

Configure the Amazon S3 bucket and a Customer Managed KMS key in the Security account, update the key policy to allow the delivery.logs.amazonaws.com service principal to perform kms:GenerateDataKey* actions, update the S3 bucket policy to allow the service principal to write objects, and configure the member VPC Flow Logs to target the central bucket.
The correct answer provides the only valid method for publishing VPC Flow Logs cross-account to an S3 bucket encrypted with a KMS key. It uses a Customer Managed Key whose policy can be modified to grant the log delivery service principal (delivery.logs.amazonaws.com) permissions to generate data keys. Simultaneously, the S3 bucket policy is configured to allow the same service principal to write objects to the bucket.

Step-by-Step Solution

1
Configure the centralized Amazon S3 bucket and Customer Managed KMS key in the Security account.
Unified destination and key resources are created in the dedicated security account.
This establishes central control over logging resources and provides a key that can be configured with cross-account access.
2
Update the KMS key policy to permit the log delivery service principal to perform key generation actions.
The delivery.logs.amazonaws.com principal is granted kms:GenerateDataKey* permissions on the Customer Managed key.
The log delivery service requires permission to generate data keys to encrypt files before depositing them into the cross-account bucket.
3
Add a statement to the S3 bucket policy allowing the log delivery service principal to put objects.
The delivery.logs.amazonaws.com principal is granted s3:PutObject permissions on the centralized bucket.
Cross-account log delivery relies on the S3 bucket policy to authorize the write operations from the log delivery service.
4
Configure the VPC Flow Logs in all member accounts to publish to the S3 bucket in the Security account.
Log collection is initiated, and flow logs are successfully delivered and encrypted in the central bucket.
This links the source network traffic in the member accounts to the central audit repository.

Key Concept

Cross-account VPC Flow Logs delivery to an encrypted S3 bucket requires granting permissions to the Log Delivery service principal (delivery.logs.amazonaws.com) using both the S3 bucket policy and a Customer Managed KMS key policy.
Question 1791Question

Sidero Logistics is modernizing its on-premises containerized warehouse management application by migrating the workload to AWS. Due to strict data residency regulations and a latency requirement of less than 5 ms5\text{ ms} to local automated sorting systems, the application's processing containers and database must run on AWS Outposts deployed in the local warehouse. The company demands high availability with a Recovery Time Objective (RTO) of less than 1 minute for local component failures. Crucially, the solution must remain fully operational—including the ability to schedule, scale, and restart containers locally—even during a temporary WAN outage that disconnects the AWS Outpost from the parent AWS Region. Which architecture should a solutions architect design to meet these requirements with the least operational complexity?

Show answer & explanation

Answer: Deploy an Amazon EKS local cluster directly on the AWS Outpost, hosting both the Kubernetes control plane and the worker nodes on the Outpost hardware. Configure the cluster to use local EBS volumes on Outposts for persistent storage.

Answer

Deploy an Amazon EKS local cluster directly on the AWS Outpost, hosting both the Kubernetes control plane and the worker nodes on the Outpost hardware. Configure the cluster to use local EBS volumes on Outposts for persistent storage.
Deploying an Amazon EKS local cluster directly on the AWS Outpost ensures that both the Kubernetes control plane and worker nodes run locally on the physical hardware. This configuration allows the cluster to remain fully functional, including scheduling new pods, scaling, and recovering from local node failures, even when connectivity to the parent AWS Region is lost. Using local EBS volumes satisfies the local data residency and low-latency storage requirements.

Step-by-Step Solution

1
Evaluate the survivability requirement under WAN disconnection.
Identify that if the control plane remains in the parent AWS Region, container scheduling, scaling, and auto-healing will fail during a WAN outage.
The regional control plane must communicate with worker nodes to perform scheduling and lifecycle operations.
2
Determine the supportability of serverless container runtimes on Outposts.
Rule out options recommending AWS Fargate on AWS Outposts.
AWS Fargate is not supported on AWS Outposts; physical instances or local nodes must be managed directly.
3
Verify local storage and DNS resolution requirements.
Select Amazon EKS local clusters which deploy the control plane locally on the Outpost, and ensure local data storage and resolution components are configured to survive WAN outages.
EKS local clusters run the Kubernetes API server, controller manager, scheduler, and etcd locally on the Outpost hardware, guaranteeing complete local operationality.

Key Concept

Amazon EKS local clusters on AWS Outposts allow running the Kubernetes control plane locally, ensuring that the cluster remains operational and capable of scheduling, scaling, and evicting pods even when disconnected from the parent AWS Region.
Question 1792Question

An enterprise needs to migrate 1.2 PB1.2\text{ PB} of unstructured data from an on-premises NFSv4 file system to an Amazon FSx for NetApp ONTAP file system. The target file system is located in the company's production AWS account (Account B), while all migration operations must be initiated and managed from a dedicated migration account (Account A). The migration must be completed within a strict window of 30 days30\text{ days}. The enterprise has a dedicated 300 Mbps300\text{ Mbps} AWS Direct Connect connection available for the migration. All migrated data must be encrypted at rest using a Customer Managed Key (CMK) to satisfy security requirements.

Which of the following actions should the Solutions Architect take to complete this migration within the required timeline? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Order multiple AWS Snowball Edge Storage Optimized devices in the migration account (Account A). Copy the NFSv4 data to the devices on-premises, and ship them to AWS to import the data into an Amazon S3 staging bucket in Account A encrypted with a Customer Managed Key (CMK).; Create an AWS DataSync task in the destination account (Account B) with the source pointing to the Amazon S3 staging bucket in Account A and the destination pointing to the Amazon FSx for NetApp ONTAP file system. Configure the staging S3 bucket policy and the Customer Managed Key (CMK) policy in Account A to grant read permissions to the DataSync execution role in Account B.

Answer

Order multiple AWS Snowball Edge Storage Optimized devices in the migration account (Account A) to import data into an S3 staging bucket encrypted with a Customer Managed Key (CMK), and create an AWS DataSync task in the destination account (Account B) to copy the data from the S3 bucket to the FSx for NetApp ONTAP file system, configuring the S3 bucket and CMK policies to allow cross-account access.
The correct architecture requires using AWS Snowball Edge Storage Optimized devices to physically ship the 1.2 PB1.2\text{ PB} of data to AWS, importing it into a staging S3 bucket in Account A. Because the destination FSx file system is in Account B, a cross-account AWS DataSync task must be created in Account B. To enable this, the staging S3 bucket must be encrypted using a Customer Managed Key (CMK) in Account A, and the key policy must grant read/decrypt permissions to the DataSync execution role in Account B.

Step-by-Step Solution

1
Calculate the transfer time over the network link to determine the viability of online migration.
Transferring 1.2 PB1.2\text{ PB} over 300 Mbps300\text{ Mbps} requires at least 370 days370\text{ days}, indicating that an offline migration with AWS Snowball Edge is required to meet the 3030-day window.
To evaluate the feasibility of online versus offline data transfer paths.
2
Identify the encryption requirements for cross-account data consumption.
The AWS Snowball Edge jobs must use a Customer Managed Key (CMK) rather than an AWS-managed key, as only CMK key policies can be modified to allow cross-account access.
To ensure that Account B's resources can access and decrypt Account A's staging S3 bucket objects.
3
Select the correct cross-account data movement method from the staging bucket to the final destination.
An AWS DataSync task is created in Account B with cross-account access configured on the staging S3 bucket in Account A, writing directly to the Amazon FSx for NetApp ONTAP file system.
To safely and efficiently copy data from Amazon S3 to FSx for NetApp ONTAP across accounts.

Key Concept

Selecting online vs. offline migration paths under strict network bandwidth constraints, and configuring secure cross-account data ingestion using KMS Customer Managed Keys and AWS DataSync.
Question 1793Question

An enterprise is migrating a 280 TB280\text{ TB} dataset from an on-premises NFS file system to an Amazon S3 bucket located in the company's Production AWS account. The entire migration must be completed within 3 weeks. The company has a 1 Gbps1\text{ Gbps} AWS Direct Connect connection, but only 200 Mbps200\text{ Mbps} of this bandwidth can be dedicated to the migration project. The solution must support automatic daily replication of incremental changes until the final cutover, preserve file metadata, and ensure that the data is encrypted at rest using a key that can be shared with a separate Analytics AWS account. Which strategy will meet these requirements within the specified timeframe?

Show answer & explanation

Answer: Order multiple AWS Snowball Edge Storage Optimized devices. Configure the import job to point to the target S3 bucket, specifying a Customer Managed KMS key (CMK) configured with a key policy that allows cross-account access. Copy the bulk data to the devices and ship them back to AWS. Once the data is imported, deploy an AWS DataSync agent on-premises to copy daily incremental changes from the NFS share to the target S3 bucket over the dedicated Direct Connect bandwidth using the same CMK.

Answer

The correct strategy is to order multiple AWS Snowball Edge Storage Optimized devices for the initial bulk data import using a Customer Managed KMS key (CMK) that allows cross-account access, and then use an on-premises AWS DataSync agent to replicate incremental changes over the Direct Connect link using the same CMK.
The correct strategy uses AWS Snowball Edge devices for the bulk import because transferring 280 TB280\text{ TB} over a dedicated 200 Mbps200\text{ Mbps} link would take approximately 130 days, which fails the 3-week timeline constraint. AWS DataSync is then configured to sync daily incremental changes over the Direct Connect link. Since the target bucket is in a different account and the data must be shared with an Analytics account, a Customer Managed KMS key (CMK) is required because AWS-managed keys (`aws/s3`) cannot be configured with custom policies for cross-account sharing.

Step-by-Step Solution

1
Calculate the transfer time over the network link to determine if offline transfer is required.
At 200 Mbps200\text{ Mbps}, the maximum theoretical throughput is 25 MB/s25\text{ MB/s} (2.16 TB/day2.16\text{ TB/day}). Transferring 280 TB280\text{ TB} requires 280/2.16129.6 days280 / 2.16 \approx 129.6\text{ days}, which exceeds the 21-day (3-week) limit. An offline transfer using AWS Snowball Edge is mandatory.
To verify if the available network bandwidth is sufficient for direct migration of the bulk data.
2
Evaluate the encryption and cross-account sharing requirements for the target S3 bucket.
The default AWS-managed S3 KMS key (`aws/s3`) cannot be shared across accounts. A Customer Managed Key (CMK) must be created in the Production account, and its key policy must grant permissions to the Snowball service, the on-premises DataSync agent, and the Analytics account roles.
To satisfy security compliance and cross-account access requirements.
3
Define the architecture for capturing updates after the bulk transfer.
Once the bulk data is imported into S3 via Snowball Edge, configure an AWS DataSync agent on-premises to sync incremental updates over the 200 Mbps200\text{ Mbps} network allocation. Daily incrementals will fit easily within the network bandwidth.
To achieve metadata preservation and low-overhead incremental updates until the cutover.

Key Concept

Selecting the optimal hybrid migration path using Snowball Edge for bulk transfer and DataSync for incremental network synchronization, while using Customer Managed Keys (CMKs) to satisfy cross-account key sharing policies.
Question 1794Question

A media streaming platform is designing a new video-on-demand application. The application requires a database and storage strategy for two distinct workloads:

1. User session state: A NoSQL workload requiring sub-1010 millisecond latency for both reads and writes, scaling up to 150,000150,000 writes per second during peak hours.
2. Catalog metadata: A highly relational OLTP workload that experiences unpredictable spikes in read traffic. The solution must support horizontal read scaling with minimal replica lag, support cross-account key management and rotation policies for at-rest encryption, and replicate data to a secondary AWS Region to achieve a disaster recovery Recovery Time Objective (RTO) of 55 minutes and a Recovery Point Objective (RPO) of 11 minute.

Which database and storage architecture should the solutions architect recommend to satisfy these requirements?

Show answer & explanation

Answer: Store user session states in Amazon DynamoDB. Store catalog metadata in an Amazon Aurora PostgreSQL Global Database encrypted with a Customer Managed Key (CMK). Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on demand, and utilize the global database for cross-region replication.

Answer

Store user session states in Amazon DynamoDB. Store catalog metadata in an Amazon Aurora PostgreSQL Global Database encrypted with a Customer Managed Key (CMK). Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on demand, and utilize the global database for cross-region replication.
The correct architecture leverages Amazon DynamoDB to handle the high-throughput, low-latency session store, as it scales horizontally to handle 150,000150,000 writes per second. For the catalog metadata, Amazon Aurora PostgreSQL Global Database provides multi-region replication with replication lag typically under 11 second, satisfying the 11-minute RPO and 55-minute RTO. Aurora Auto Scaling dynamically manages Aurora Replicas to handle read spikes. Using a Customer Managed Key (CMK) allows for cross-account KMS key policies and rotation management, which is required for security compliance.

Step-by-Step Solution

1
Identify the storage requirements for the NoSQL user session state.
Determine that Amazon DynamoDB is the appropriate service to support sub-1010 millisecond latency at 150,000150,000 writes per second.
DynamoDB is fully managed, scales horizontally to virtually unlimited write throughput, and consistently delivers single-digit millisecond latency.
2
Determine the scaling and high availability requirements for the catalog metadata workload.
Identify that Amazon Aurora PostgreSQL Global Database supports horizontal scaling with Aurora Replicas and cross-region replication.
Aurora Replicas support auto-scaling to handle read spikes with sub-millisecond replication lag, and Aurora Global Database achieves cross-region disaster recovery with near-zero RPO and RTO under 55 minutes.
3
Evaluate the encryption and key management compliance requirements.
Identify that a KMS Customer Managed Key (CMK) is required instead of an AWS-managed key.
AWS-managed keys (e.g., `aws/rds`) cannot have their key policies modified and cannot be shared across accounts, whereas CMKs support custom cross-account permissions and management.

Key Concept

Selecting and configuring optimal AWS database and encryption services to meet strict performance, scaling, cross-account security, and multi-region disaster recovery requirements.
Question 1795Question

A company is designing a new multi-tenant online booking platform that requires a highly available database to handle a read-heavy OLTP workload. The database must automatically fail over to a standby instance in another Availability Zone during an outage to minimize downtime. Additionally, the platform must handle heavy read traffic for reporting dashboards with minimal latency without impacting the performance of the write operations. Which database configuration best meets these requirements?

Show answer & explanation

Answer: Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration, and create one or more RDS Read Replicas in different Availability Zones. Route write operations to the primary endpoint and read-heavy reporting queries to the Read Replica endpoints.

Answer

Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration for high availability and automatic failover, and deploy one or more RDS Read Replicas to serve the read-heavy reporting queries.
Deploying Amazon RDS for PostgreSQL in a Multi-AZ configuration ensures high availability and automatic failover by maintaining a synchronous standby instance in a different Availability Zone. Creating RDS Read Replicas allows read-heavy queries to be offloaded to read-only endpoints, improving overall performance and keeping the primary instance dedicated to write operations.

Step-by-Step Solution

1
Analyze high availability and failover requirements.
Amazon RDS Multi-AZ deployment is selected to provide synchronous replication to a standby instance and automatic failover capabilities.
The system must minimize downtime and automatically fail over to another Availability Zone in the event of an outage.
2
Analyze the read scalability and latency requirements.
RDS Read Replicas are chosen to scale read capacity horizontally across Availability Zones.
Routing read traffic to Read Replicas offloads the primary database instance, maintaining write performance and reducing read latency.
3
Evaluate the architectural constraints of standby instances and KMS key sharing.
Rule out options that attempt to query the passive standby instance directly or use AWS-managed keys for cross-account resource sharing.
RDS standby instances in Multi-AZ are passive and inaccessible, and AWS-managed KMS keys do not support key policy modifications for cross-account access.

Key Concept

RDS Multi-AZ vs Read Replicas and cross-account access limitations
Question 1796Question

An enterprise is establishing a multi-account structure in AWS Organizations. The Security team must enforce two governance requirements across all accounts in a newly created Organizational Unit (OU) named Workloads:

1. Prevent local administrators in member accounts from deleting or modifying a cross-account IAM role named SecurityAuditRole.
2. Allow applications in member accounts to encrypt data in their local Amazon S3 buckets using a centralized, customer-managed AWS KMS key hosted in a dedicated Security account. The key must only be usable for S3 encryption services.

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

Select all that apply

Show answer & explanation

Answer: Attach a Service Control Policy (SCP) to the Workloads OU that denies the iam:DeleteRole, iam:PutRolePolicy, and iam:DeleteRolePolicy actions when the resource is the SecurityAuditRole.; In the Security account, create a KMS customer managed key and configure its key policy to grant the kms:GenerateDataKey and kms:Decrypt permissions to the member account root principals, using a condition that restricts the kms:ViaService to s3.amazonaws.com.

Answer

Attach a Service Control Policy (SCP) to the Workloads OU that denies modifying the SecurityAuditRole, and create a KMS customer managed key in the Security account with a key policy granting access to member accounts restricted via the kms:ViaService condition for S3.
Protecting a critical cross-account role is best achieved using a Service Control Policy (SCP) targeting the specific role name/ARN. For S3 cross-account encryption, a KMS customer managed key must be used since AWS-managed keys do not support policy modification or cross-account access. The key policy must allow the member accounts' principals to use the key, scoped down with a condition matching the S3 service principal.

Step-by-Step Solution

1
Address the role protection requirement by applying an SCP at the OU level.
Local administrative accounts in the member accounts are blocked from deleting or updating the SecurityAuditRole.
SCPs apply to all users and roles in member accounts, including the root user, making them the correct tool to enforce restriction guardrails.
2
Address the cross-account S3 encryption requirement by using a KMS customer managed key.
A key is created that allows configuration of a custom key policy for cross-account access.
AWS-managed keys cannot be shared across accounts, so a customer managed key is required.
3
Restrict the cross-account KMS key usage to S3 operations.
The key policy delegates access to member accounts under the condition that the service calling it is s3.amazonaws.com.
The kms:ViaService condition enforces that the key can only be used when requests originate from the specified AWS service (S3).

Key Concept

Centralized resource access control and policy guardrails using SCPs and KMS key policies in a multi-account AWS Organization.
Estimated Time:1m 30s
Question 1797Question

A large logistics company is migrating its on-premises VMware vSphere workloads to VMware Cloud (VMC) on AWS. The migration scope includes 1010 transactional database virtual machines (VMs) totaling 4 TB4\text{ TB} of storage and 5050 application VMs totaling 12 TB12\text{ TB} of storage. The database VMs have a maximum allowable downtime of 11 minute during migration cutover, while the application VMs can tolerate a reboot of up to 1515 minutes. The enterprise has an existing 2 Gbps2\text{ Gbps} AWS Direct Connect connection (with 1 Gbps1\text{ Gbps} available capacity) linked to a multi-account AWS environment. The workloads must retain their original on-premises IP addresses to prevent application reconfiguration. In addition, the migrated VMs must resolve private DNS records hosted in a Route 53 Private Hosted Zone (PHZ) in the Shared Services VPC. Which combination of VMware HCX migration types and DNS configurations will satisfy these requirements?

Show answer & explanation

Answer: Deploy VMware HCX and configure an HCX L2 Network Extension. Migrate the database VMs using HCX Replication-Assisted vMotion (RAV) and the application VMs using HCX Bulk Migration. Configure the SDDC DNS service to forward DNS requests to a Route 53 Inbound Resolver endpoint in the Shared Services VPC.

Answer

Deploy VMware HCX and configure an HCX L2 Network Extension. Migrate the database VMs using HCX Replication-Assisted vMotion (RAV) and the application VMs using HCX Bulk Migration. Configure the SDDC DNS service to forward DNS requests to a Route 53 Inbound Resolver endpoint in the Shared Services VPC.
The correct configuration utilizes VMware HCX Replication-Assisted vMotion (RAV) for the database VMs to achieve live migration with sub-minute downtime, and HCX Bulk Migration for the application VMs to migrate them in parallel while scheduling their switchover (reboot). To preserve IP addresses, an HCX L2 Network Extension must be configured. Since Route 53 Private Hosted Zones cannot be directly associated with the VMC SDDC network, DNS resolution for internal domains must be handled by configuring the VMC SDDC DNS forwarder to point to Route 53 Inbound Resolver endpoints in the associated Shared Services VPC, which is reachable over the Transit Connect attachment through the Transit Gateway.

Step-by-Step Solution

1
Evaluate the downtime and IP preservation requirements to select the correct migration methods.
The database VMs require less than 1 minute of downtime, meaning a live migration is necessary. HCX Replication-Assisted vMotion (RAV) fulfills this by using replication and a final live vMotion switchover. The application VMs can tolerate a reboot (up to 15 minutes), making HCX Bulk Migration appropriate. An HCX L2 Network Extension is required to preserve on-premises IP addresses.
This guarantees that the databases remain online during data transfer and switch over with minimal downtime, while application VMs are migrated in bulk without IP changes.
2
Design DNS resolution for the migrated workloads to access private DNS zones.
Create a Route 53 Inbound Resolver endpoint in the Shared Services VPC. Configure the VMC SDDC DNS forwarder to point to this Inbound Resolver endpoint.
Since Route 53 Private Hosted Zones cannot be directly associated with the VMC SDDC network, VMC workloads must use DNS forwarding to query Route 53 over the Transit Connect attachment.

Key Concept

Selecting appropriate VMware HCX migration types (RAV vs. Bulk) to satisfy strict RTO/RPO limits and configuring DNS forwarding via Route 53 Inbound Resolvers for VMC on AWS workloads.
Question 1798Question

A SaaS company operates a document generation platform on AWS. The application tier runs on Amazon EC2 instances within an Auto Scaling group (ASG) behind an Application Load Balancer (ALB) across three Availability Zones. The instances are launched from a standard Amazon Linux AMI and execute a user data bootstrap script to download 4 GB of template libraries and compile application dependencies. This process takes 8 minutes before the instances can pass ALB health checks. During scheduled marketing events, a rapid spike in requests causes the ASG's target tracking policy (set to 70% average CPU utilization) to launch new instances. However, because these instances take 8 minutes to bootstrap, the ASG repeatedly launches additional instances before the first batch becomes healthy, leading to severe over-provisioning. Additionally, a recent NAT Gateway outage in Availability Zone A prevented instances in Availability Zones B and C from retrieving remote template libraries during bootstrapping. Which solution should a Solutions Architect implement to resolve the scaling instability and ensure high availability for outbound traffic?

Show answer & explanation

Answer: Create a custom AMI with the template libraries and dependencies pre-installed, update the Auto Scaling group to use this AMI, and configure a target tracking scaling policy with an instance warmup of 120 seconds. Deploy a NAT Gateway in each Availability Zone and configure the route table of each private subnet to route outbound traffic through its local NAT Gateway.

Answer

Create a custom AMI with the template libraries and dependencies pre-installed, update the Auto Scaling group to use this AMI, and configure a target tracking scaling policy with an instance warmup of 120 seconds. Deploy a NAT Gateway in each Availability Zone and configure the route table of each private subnet to route outbound traffic through its local NAT Gateway.
Pre-baking the dependencies and libraries into a custom AMI drastically reduces the bootstrapping time to under a minute. Combined with setting an appropriate instance warmup period, this prevents the Auto Scaling group from repeatedly launching unnecessary instances before the first batch can help handle the workload. Additionally, deploying a NAT Gateway in each Availability Zone ensures there is no single point of failure for outbound traffic and maintains high availability across all zones.

Step-by-Step Solution

1
Identify the root cause of the Auto Scaling group over-provisioning.
The 8-minute bootstrapping process causes a lag in instances becoming healthy, leading target tracking to assume more capacity is needed.
To prevent this, the boot time must be reduced, and the scaling policy must be given sufficient warmup time.
2
Determine the best approach to reduce the initialization time.
Create a custom AMI with pre-installed template libraries and dependencies, reducing launch-to-ready time from 8 minutes to under 1 minute.
This minimizes the time instances spend in the bootstrapping phase and allows them to handle traffic almost immediately.
3
Eliminate the single point of failure for outbound traffic.
Deploy a NAT Gateway in each Availability Zone and update corresponding private subnet route tables to route outbound traffic locally.
This ensures that a failure of a NAT Gateway in one Availability Zone does not impact outbound traffic or bootstrapping in other zones.

Key Concept

Scaling policy tuning and multi-AZ fault tolerance for outbound network paths.
Estimated Time:2m 30s
Question 1799Question

A logistics company is planning to migrate its on-premises infrastructure to AWS. The environment consists of 150 VMware virtual machines and 20 legacy physical servers running custom Linux distributions that cannot be virtualized. The physical servers require detailed CPU and memory utilization data at the process level to optimize AWS target sizing. However, the corporate security policy strictly forbids installing any third-party agents or making OS-level modifications on the VMware VMs. Both environments have outbound internet connectivity blocked, but they can access a VPC via an existing AWS Direct Connect connection. The migration team wants to track all migration phases, including discovery and server replication progress, from a single centralized dashboard. Which discovery and tracking strategy should the solutions architect recommend to meet these requirements?

Show answer & explanation

Answer: Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server, and install the AWS Application Discovery Agent on the physical servers. Configure both discovery mechanisms to communicate with the AWS Application Discovery Service using VPC endpoints. Track the discovery and migration replication status using AWS Migration Hub.

Answer

Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server, and install the AWS Application Discovery Agent on the physical servers. Configure both discovery mechanisms to communicate with the AWS Application Discovery Service using VPC endpoints. Track the discovery and migration replication status using AWS Migration Hub.
The correct strategy involves deploying the Agentless Collector on VMware vCenter to respect the constraint against OS-level agent installation on virtual machines, and installing the Application Discovery Agent on the physical servers to capture process-level utilization metrics. Using VPC endpoints accommodates the outbound internet block by routing data over Direct Connect, and AWS Migration Hub provides the unified tracking dashboard.

Step-by-Step Solution

1
Determine the discovery mechanism for VMware virtual machines.
Since the security policy restricts OS-level changes on VMware VMs, the AWS Application Discovery Agentless Collector should be deployed as an OVA appliance in vCenter.
The Agentless Collector does not require any agent installation on individual virtual machines and retrieves VM configuration and performance history through the vCenter APIs.
2
Determine the discovery mechanism for the physical legacy servers.
Install the AWS Application Discovery Agent on the physical servers.
Process-level CPU and memory utilization analysis requires the Application Discovery Agent, as the Agentless Collector is only compatible with VMware vCenter and cannot fetch process-level details from physical bare-metal hardware.
3
Resolve the network connectivity constraints.
Configure both the Agentless Collector and the Discovery Agents to communicate with AWS Application Discovery Service via VPC endpoints (AWS PrivateLink).
Outbound internet access is blocked on-premises, but Direct Connect is available. Using VPC endpoints enables traffic to route privately into the AWS environment without accessing the public internet.
4
Select the unified migration tracking tool.
Use AWS Migration Hub to aggregate and track the discovery and migration replication status.
AWS Migration Hub provides a single dashboard to track the progress of discovery, grouping servers into applications, and monitoring replication from various AWS and partner migration services.

Key Concept

AWS Application Discovery Service supports both agent-based and agentless discovery models. Agent-based discovery provides detailed process-level information but requires OS installation, whereas agentless discovery collects configuration and performance metrics at the VM level via VMware vCenter. AWS Migration Hub acts as a centralized console for tracking the status of discovery and migration tools.
Estimated Time:2m 0s
Question 1800Question

A solutions architect is designing the deployment strategy for a critical transaction processing microservice running on Amazon ECS with the AWS Fargate launch type behind an Application Load Balancer (ALB). The business requires a deployment strategy that minimizes the blast radius of new releases by routing exactly 10%10\% of client traffic to the new version initially. The remaining 90%90\% of traffic must be routed to the new version after a 10-minute observation period, provided no errors are detected. If the microservice experiences an elevated 5XX error rate during the transition, the system must execute an automated rollback to the previous version within 2 minutes. Which deployment strategy and configuration should the solutions architect select to satisfy these requirements?

Show answer & explanation

Answer: Configure an AWS CodeDeploy blue/green deployment for the Amazon ECS service using the CodeDeployDefault.ECSCanary10Percent10Minutes deployment configuration, and associate CloudWatch alarms on the ALB target group's 5XX error rate directly with the CodeDeploy deployment group.

Answer

Configure an AWS CodeDeploy blue/green deployment for the Amazon ECS service using the CodeDeployDefault.ECSCanary10Percent10Minutes deployment configuration, and associate CloudWatch alarms on the ALB target group's 5XX error rate directly with the CodeDeploy deployment group.
The correct answer is to use AWS CodeDeploy with a blue/green deployment type and select the ECSCanary10Percent10Minutes configuration. This configuration shifts 10%10\% of the traffic to the new task set, waits for 10 minutes, and then shifts the remaining 90%90\% if no alarms are triggered. Linking CloudWatch alarms on the 5XX error rate directly to the CodeDeploy deployment group ensures that CodeDeploy automatically and immediately rolls back traffic to the previous version if the alarm is breached, easily meeting the 2-minute rollback requirement.

Step-by-Step Solution

1
Analyze the traffic shifting requirements.
The requirement is to shift 10%10\% of traffic initially, wait for 10 minutes, and then shift the remaining 90%90\%. This matches a Canary deployment pattern, specifically CodeDeploy's Canary10Percent10Minutes configuration.
Linear configurations shift traffic incrementally over multiple intervals, whereas canary configurations shift a specific portion once and then shift the rest after a soak period.
2
Evaluate the rollback mechanism against the 2-minute constraint.
Native AWS CodeDeploy blue/green deployments support linking CloudWatch alarms to the deployment group. When an alarm is triggered, CodeDeploy immediately stops the deployment and routes all traffic back to the original task set.
This native integration operates within seconds of the alarm state change, meeting the 2-minute automated rollback requirement. Using Route 53 DNS failover or custom Lambda code introduces propagation delays and complexity.

Key Concept

AWS CodeDeploy blue/green deployments with canary configurations and native CloudWatch alarm integrations allow for precise traffic shifting and near-instant automated rollbacks.
PreviousPage 90 / 99Next
All practice questions — AWS Certified Solutions Architect - Professional | Examkin