Tüm alıştırma soruları

1964 soru

Soru 1221Soru

An enterprise operates a citizen portal application using a multi-tier microservices architecture in the us-east-1 Region. The web tier consists of Amazon ECS tasks running on AWS Fargate behind an Application Load Balancer (ALB). The application logic runs on AWS Lambda behind Amazon API Gateway. The data tier utilizes Amazon DynamoDB. The entire environment is provisioned using AWS CloudFormation. To enhance the disaster recovery (DR) posture, the enterprise wants to establish a warm standby architecture in the us-west-2 Region with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. Which combination of actions should the Solutions Architect take to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Convert the Amazon DynamoDB tables into DynamoDB global tables to enable continuous replication between the primary and secondary regions.; Pre-deploy the web and application infrastructure in the secondary region with the ECS service scaled to minimum capacity, and configure Amazon Route 53 active-passive failover routing linked to health checks.

Cevap

Convert the DynamoDB tables to DynamoDB global tables for replication, and pre-deploy the application tier in the secondary region at minimum capacity while configuring Route 53 active-passive failover with health checks.
To meet the RPO of 5 minutes, DynamoDB global tables are required as they provide sub-second replication latency across AWS regions. To meet the RTO of 15 minutes, a warm standby strategy must have the infrastructure pre-deployed and running at minimal scale in the secondary region, combined with automated Route 53 active-passive failover routing. The failover routing must be linked to health checks to enable automated diversion of traffic to the standby region in the event of an outage.

Adım Adım Çözüm

1
Address the Recovery Point Objective (RPO) constraint of 5 minutes by choosing an appropriate replication mechanism for the database layer.
Identify that DynamoDB global tables replicate data across regions with sub-second replication latency, satisfying the 5-minute RPO.
Standard backup and restore methods or manual synchronization cannot guarantee data freshness under 5 minutes during a disaster.
2
Address the Recovery Time Objective (RTO) constraint of 15 minutes by choosing a deployment pattern and routing mechanism.
Select a warm standby pattern where critical infrastructure is already running at minimal scale in the secondary region, and configure automated DNS failover using Route 53 active-passive failover routing policies associated with application health checks.
Cold standby or manual failover steps cannot consistently recover containerized services and update DNS records within 15 minutes.
3
Evaluate and eliminate options that violate the reliability design principles or the specified RTO/RPO thresholds.
Eliminate the options proposing daily backups (violates RPO/RTO), manual Route 53 failover without health checks (violates RTO), and a single NAT Gateway configuration (violates multi-AZ redundancy principles).
Each of these distractors introduces architectural defects or fails the service level agreements required by the business.

Anahtar Kavram

Designing multi-region disaster recovery architectures with tight RPO and RTO constraints requires automated database replication (such as DynamoDB global tables) and pre-deployed compute tiers with automated DNS routing failover (such as Route 53 health-checked active-passive failover) while maintaining high availability best practices.
Soru 1222Soru

An enterprise is designing a new multi-VPC architecture in the `us-west-2` Region. The architecture contains:
- `vpc-logistics-core` (10.120.0.0/1610.120.0.0/16) hosting critical backend applications across two Availability Zones.
- `vpc-egress-shared` (192.168.0.0/22192.168.0.0/22) serving as a centralized egress VPC with NAT Gateways.
- A centralized Route 53 Private Hosted Zone (PHZ) `logistics.aws.internal` hosted in a separate shared services account.

All spoke VPCs connect to `vpc-egress-shared` using an AWS Transit Gateway (`tgw-global-transit`). The solution must provide highly available outbound internet connectivity, prevent any direct network communication between spoke VPCs, and enable private DNS resolution of names within `logistics.aws.internal` for all instances in the spoke VPCs.

Which TWO configurations must a Solutions Architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Associate the Route 53 Private Hosted Zone `logistics.aws.internal` with each consumer VPC by creating VPC association authorizations in the shared services account and then associating the zone with the VPCs in their respective accounts.; Configure a Transit Gateway route table associated with the spoke VPC attachments that has a static route for 0.0.0.0/00.0.0.0/0 pointing to the egress VPC attachment, and do not propagate spoke VPC routes into this route table.

Cevap

To satisfy the requirements, the Solutions Architect must associate the Route 53 Private Hosted Zone with each consumer VPC using VPC association authorizations, and configure a separate Transit Gateway route table for the spokes that directs default traffic to the egress VPC without propagating spoke routes.
Associating the private hosted zone directly with each VPC allows local DNS resolution to function natively without routing queries across Transit Gateway. Using separate Transit Gateway route tables for spokes that contain only a default route to the egress VPC (and disabling propagation of spoke routes) ensures spoke-to-spoke traffic cannot be routed, while outbound traffic is successfully directed to the egress VPC.

Adım Adım Çözüm

1
Enable cross-account DNS resolution by creating association authorizations for the Private Hosted Zone `logistics.aws.internal` with each consumer VPC using the Route 53 API in the owner account.
Authorized consumer VPCs in other accounts can now associate with the hosted zone.
This allows the instances in the spoke VPCs to resolve private domain names natively and securely.
2
Associate the authorized consumer VPCs with the hosted zone from their respective AWS accounts.
DNS queries for the domain are resolved locally in each VPC.
This satisfies the DNS resolution requirement without requiring complex hybrid resolver endpoints.
3
Create separate Transit Gateway route tables for the spoke VPCs and the egress VPC. Associate the spoke VPC attachments with the spoke Transit Gateway route table.
Traffic originating from spokes is evaluated against the spoke Transit Gateway route table.
Separating route tables is required to implement custom route propagation rules.
4
Add a static default route (0.0.0.0/00.0.0.0/0) in the spoke Transit Gateway route table pointing to the egress VPC attachment, and do not propagate spoke routes into this table.
Spokes can route outbound traffic to the egress VPC, but cannot route traffic to other spokes because they lack routes to those spokes.
This prevents transitive spoke-to-spoke communication while allowing centralized internet egress.

Anahtar Kavram

Centralized multi-account networking design with secure egress routing and private DNS resolution.
Tahmini Süre:3m 0s
Soru 1223Soru

An enterprise is planning to migrate a two-tier customer portal application to AWS. The web tier consists of an ASP.NET Core application running on Windows Server IIS that requires no modifications and must be migrated within a two-week window. The database tier runs on an on-premises Microsoft SQL Server database. To eliminate licensing costs and reduce administrative overhead, the enterprise wants to migrate the database to Amazon Aurora PostgreSQL. This migration will require database schema conversion and modifications to the application's data access layer. Which TWO migration strategies should the solutions architect select for this migration? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Rehost the web tier by migrating the IIS virtual machines to Amazon EC2 without modification.; Refactor the database tier by using the AWS Schema Conversion Tool (AWS SCT) and modifying the application code to use Amazon Aurora PostgreSQL.

Cevap

The solutions architect should select Rehost for the web tier by migrating the IIS virtual machines to Amazon EC2 without modification, and Refactor for the database tier by using the AWS Schema Conversion Tool (AWS SCT) and modifying the application code to use Amazon Aurora PostgreSQL.
For the web tier, a Rehost strategy (migrating to Amazon EC2) is correct because it satisfies the constraint of no code changes and the strict two-week migration window. For the database tier, a Refactor strategy is correct because migrating from Microsoft SQL Server to Amazon Aurora PostgreSQL requires database schema conversion and code modifications to the application's data access layer.

Adım Adım Çözüm

1
Analyze the migration requirements and constraints for the web tier.
The web tier requires no code modifications and has a tight timeline of two weeks, pointing to a Rehost (lift-and-shift) migration strategy.
Rehosting allows quick migration of virtual machines to Amazon EC2 with minimal configuration changes, fitting the two-week timeline.
2
Analyze the migration requirements and constraints for the database tier.
The database tier requires changing from SQL Server to Aurora PostgreSQL to eliminate licensing, requiring schema conversion and code modifications.
A change in database engine coupled with schema conversion and application code adjustments is classified as a Refactor (Re-architect) strategy.
3
Map the identified strategies to the correct options.
Rehosting the web tier on Amazon EC2 and refactoring the database tier to Amazon Aurora PostgreSQL are the correct migration strategies.
These strategies align with the enterprise's technical constraints, timeline, and goals.

Anahtar Kavram

Selecting the correct migration strategy from the 7 Rs (Rehost, Replatform, Refactor, Repurchase, Retire, Retain, Relocate) based on technical, operational, and business constraints.
Soru 1224Soru

A digital document management and e-signature platform uses an Amazon RDS for PostgreSQL DB instance to track active user signing sessions, signer verification states, and document metadata. During peak business hours at the end of the fiscal quarter, the database CPU utilization exceeds 92%92\% due to a surge in read-heavy queries verifying session tokens and user permissions. The application requires session data to be highly available, replicate across multiple Availability Zones to prevent data loss during failovers, and maintain sub-millisecond retrieval times. The solutions architect must optimize the database layer to resolve the performance bottleneck while meeting these availability and persistence requirements.

Which of the following database and caching strategies should the solutions architect implement?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon ElastiCache for Redis cluster with replication enabled across multiple Availability Zones. Configure the application to store session tokens and verification states in the Redis cluster utilizing a cache-aside pattern, and query the RDS PostgreSQL database only on cache misses.

Cevap

Deploying an Amazon ElastiCache for Redis cluster with replication enabled across multiple Availability Zones, and configuring the application to store session tokens and states in the cluster utilizing a cache-aside pattern.
The correct strategy implements ElastiCache for Redis with replication enabled across multiple Availability Zones. This meets the requirement of high availability and prevents data loss in the event of an Availability Zone outage. Storing session tokens and user permissions using a cache-aside pattern offloads the high CPU read-heavy queries from the RDS PostgreSQL database, maintaining sub-millisecond latencies for active sessions.

Adım Adım Çözüm

1
Identify the performance bottleneck and database workload characteristics.
The bottleneck is caused by read-heavy queries verifying session tokens and user permissions on RDS PostgreSQL.
This establishes that a caching mechanism is required to offload the high volume of reads from the primary relational database.
2
Evaluate the requirements for the session cache layer.
The cache layer requires sub-millisecond retrieval times, high availability, replication across multiple Availability Zones to prevent data loss, and data persistence/durability support.
This rules out caching engines or configurations that do not support multi-AZ replication or data persistence.
3
Compare caching engines (Redis vs Memcached).
Memcached is a simple key-value store that lacks data persistence, replication, and multi-AZ automatic failover. Redis supports replication, multi-AZ auto-failover, and persistence.
This rules out the option using ElastiCache for Memcached.
4
Compare database read offloading architectures.
An RDS Multi-AZ standby replica is passive and cannot accept read queries. Caching is more optimal than deploying read replicas for sub-millisecond latencies.
This rules out the option proposing routing reads to the standby replica.
5
Select the strategy that combines a Multi-AZ ElastiCache for Redis cluster with a cache-aside pattern.
The database read load is successfully reduced, and session retrieval times are reduced to sub-milliseconds, while maintaining data persistence and high availability.
This architecture meets all technical and business requirements.

Anahtar Kavram

Distinguishing between Amazon ElastiCache for Redis and ElastiCache for Memcached features, and understanding RDS Multi-AZ replication capabilities.
Tahmini Süre:2m 0s
Soru 1225Soru

A company wants to migrate its on-premises self-hosted PostgreSQL database to Amazon RDS for PostgreSQL to eliminate the administrative overhead of patching and backups. The migration must be completed with no changes to the application code or the database engine. Which migration strategy under the 7 Rs framework represents this path?

Cevabı ve açıklamayı göster

Cevap: Replatform

Cevap

Replatform
The correct strategy is Replatforming because the database is being moved to a managed service (Amazon RDS) to optimize operations (backups and patching) without changing the application's code or switching database engines.

Adım Adım Çözüm

1
Analyze the migration goal and requirements.
The target is to move an on-premises self-hosted PostgreSQL database to a managed database service (Amazon RDS) to reduce administrative tasks like patching and backups.
This establishes the target platform type as a managed service rather than an Infrastructure as a Service (IaaS) virtual machine.
2
Evaluate the required changes to the database and application code.
No changes to the application code or the database engine are required.
Keeping the database engine the same eliminates the need for schema conversion or code rewrites, ruling out Refactoring.
3
Map the migration characteristics to the 7 Rs framework.
Migrating to a managed platform (RDS) without changing the database engine or application code is classified as Replatforming.
Replatforming optimizes the database operations by offloading administrative tasks to AWS while keeping the core application logic unchanged.

Anahtar Kavram

Replatforming involves modifying ('tinkering' with) the infrastructure environment to adopt managed cloud services without altering the core application architecture.
Soru 1226Soru

A logistics company is planning to migrate its fleet management system to AWS. The system consists of the following components:

1. A web application running on Red Hat Enterprise Linux (RHEL) virtual machines. The migration must be completed quickly with zero modification to the application code.
2. A commercial Oracle database containing transactional data. The company wants to migrate this workload to Amazon Aurora PostgreSQL to eliminate license costs and take advantage of serverless scaling, which will require schema conversion and rewriting stored procedures.
3. A legacy dispatch scheduling console running on an unsupported custom UNIX operating system. The console is tied to proprietary local serial-port hardware and cannot be virtualized or moved to the cloud.

Which combination of migration strategies from the 7 Rs framework should the company select for these components?

Cevabı ve açıklamayı göster

Cevap: Web application: Rehost; Database: Refactor (Rearchitect); Console: Retain

Cevap

Web application: Rehost; Database: Refactor (Rearchitect); Console: Retain
The correct strategy combines Rehosting the web application to meet the fast timeline with zero code changes, Refactoring (Rearchitecting) the Oracle database to Aurora PostgreSQL because of the heterogeneous database engine change and necessary code updates, and Retaining the legacy console on-premises since it is still active but cannot be migrated due to hardware dependencies.

Adım Adım Çözüm

1
Analyze the migration requirements for the web application tier.
The web application must be moved quickly with zero modification to the application code.
This constraint points directly to a lift-and-shift (Rehost) strategy using a tool like AWS Application Migration Service (MGN).
2
Evaluate the database migration strategy and requirements.
The Oracle database is being migrated to Amazon Aurora PostgreSQL, which requires schema conversion and rewriting stored procedures.
A database engine change combined with significant schema and code modifications represents a heterogeneous database migration, which falls under the Refactor (Rearchitect) strategy.
3
Determine the migration strategy for the legacy dispatch scheduling console.
The console runs on an unsupported UNIX OS and is tied to proprietary physical serial-port hardware that cannot be virtualized or migrated to the cloud.
Since the console is still needed for operations but cannot be moved to AWS, it must be kept running on-premises, which represents the Retain strategy.

Anahtar Kavram

Selecting the correct migration strategy from the 7 Rs framework based on application constraints, dependencies, and modernization goals.
Soru 1227Soru

A company is designing the network architecture for a new AWS deployment in the `us-west-2` Region. The deployment consists of three VPCs: `vpc-app-prod`, `vpc-app-test`, and `vpc-shared-services`. An on-premises data center is connected to AWS via an AWS Direct Connect connection. The networking requirements are:
1. Enable routing between the on-premises data center and all three VPCs.
2. Enable direct routing between `vpc-app-prod` and `vpc-shared-services`.
3. Provide redundant outbound internet connectivity for resources in private subnets across multiple Availability Zones in `vpc-app-prod` and `vpc-app-test`.
4. Allow both the on-premises servers and resources in all three VPCs to resolve DNS hostnames within a Route 53 Private Hosted Zone (PHZ) named `cloud.internal`.

Which of the following designs meets these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway (TGW) and attach all three VPCs. Associate an AWS Direct Connect Gateway (DXGW) with the TGW to enable on-premises connectivity. In `vpc-shared-services`, deploy a NAT Gateway in each public subnet across multiple Availability Zones, and configure route tables in the spoke VPCs to direct internet traffic through the TGW. Create a Route 53 Resolver Inbound Endpoint in `vpc-shared-services` across multiple Availability Zones, associate the Private Hosted Zone `cloud.internal` with all three VPCs, and configure the on-premises DNS servers to forward queries for `cloud.internal` to the inbound endpoint.

Cevap

Deploy an AWS Transit Gateway connected to a Direct Connect Gateway, use multiple NAT Gateways across Availability Zones in the shared services VPC, and associate the Private Hosted Zone with all three VPCs while using a multi-AZ Route 53 Resolver Inbound Endpoint.
The correct design uses an AWS Transit Gateway (TGW) to route traffic transitively between the on-premises network (via a Direct Connect Gateway) and all three VPCs, while also allowing direct communication between the application and shared services VPCs. To ensure high availability and redundancy for outbound egress, it deploys a NAT Gateway in each Availability Zone within the shared services VPC. Finally, it ensures complete internal name resolution by creating a multi-AZ Route 53 Resolver Inbound Endpoint and associating the Private Hosted Zone with all three VPCs.

Adım Adım Çözüm

1
Determine the routing mechanism that supports transitive routing between the VPCs and the on-premises network, as well as inter-VPC traffic.
An AWS Transit Gateway (TGW) associated with an AWS Direct Connect Gateway (DXGW) is identified as the solution because it supports transitive routing, whereas DXGW with VGWs does not allow inter-VPC traffic.
To satisfy the requirement of direct routing between `vpc-app-prod` and `vpc-shared-services` alongside on-premises connectivity.
2
Evaluate the configuration of the NAT Gateways for outbound internet connectivity.
Deploying a NAT Gateway in each Availability Zone (AZ) in `vpc-shared-services` ensures there is no single point of failure.
The requirement specifies redundant outbound internet connectivity across multiple AZs.
3
Configure private DNS resolution for both on-premises servers and the three AWS VPCs.
Associate the Route 53 Private Hosted Zone (PHZ) `cloud.internal` with all three VPCs and configure Route 53 Resolver Inbound Endpoints in `vpc-shared-services` across multiple AZs.
Failing to associate the PHZ with the spoke VPCs will prevent resources in those VPCs from resolving the hostnames, even if they can route to the inbound endpoint.

Anahtar Kavram

AWS Transit Gateway transitive routing, centralized NAT Gateway redundancy, and cross-account Route 53 Private Hosted Zone association.
Tahmini Süre:2m 0s
Soru 1228Soru

An enterprise web application is hosted on Amazon EC2 instances in private subnets across three Availability Zones (AZAAZ-A, AZBAZ-B, and AZCAZ-C). The instances are managed by an Auto Scaling Group (ASG) behind an Application Load Balancer (ALB). The instances execute a complex bootstrap script that downloads dependencies from external repositories, taking approximately 88 minutes to become fully operational. Outbound internet traffic is routed through a single NAT Gateway located in AZAAZ-A.

The company is preparing for a scheduled marketing campaign that will generate a massive, instantaneous 10×10\times surge in traffic. Historically, during similar events, the ALB dropped initial requests, and the ASG launched far more instances than needed, leading to unnecessary costs.

Which TWO actions should the Solutions Architect implement to improve the system's fault tolerance and optimize its scaling behavior for the campaign?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an active NAT Gateway in each of the three Availability Zones and update the private subnet route tables to direct outbound traffic (0.0.0.0/00.0.0.0/0) to the local NAT Gateway within the same zone.; Submit a request to AWS Support to pre-warm the Application Load Balancer to the expected peak traffic, and configure the Auto Scaling group's target tracking policy instance warmup to 540540 seconds.

Cevap

Deploying a NAT Gateway in each Availability Zone for fault tolerance, requesting AWS Support to pre-warm the Application Load Balancer to handle the instant traffic surge, and setting the Auto Scaling group instance warmup to 540 seconds to prevent over-provisioning.
Deploying a dedicated NAT Gateway in each Availability Zone ensures that a failure in one zone does not disrupt internet connectivity and bootstrapping in the remaining zones, eliminating a single point of failure. Pre-warming the Application Load Balancer ensures it is provisioned with sufficient capacity to absorb the instantaneous traffic spike without dropping initial requests. Setting the Auto Scaling group's instance warmup to 540 seconds (which is longer than the 8-minute bootstrapping time) prevents the scaling policy from launching additional instances prematurely while the initial scaling batch is still bootstrapping, avoiding over-provisioning and high costs.

Adım Adım Çözüm

1
Review the current outbound traffic path for EC2 instances in private subnets.
The single NAT Gateway in one zone is a single point of failure.
If the Availability Zone hosting the single NAT Gateway fails, instances in other zones cannot download dependencies and fail to bootstrap.
2
Determine how the Application Load Balancer handles a sudden 10×10\times traffic spike.
The load balancer needs to be pre-warmed by AWS Support.
Standard automatic scaling of the load balancer is gradual; an instantaneous surge will result in dropped requests (HTTP 503) before the load balancer can scale out.
3
Compare the instance bootstrapping time (88 minutes) with the Auto Scaling scaling metrics evaluation cycle and warmup settings.
Set the instance warmup to 540540 seconds (99 minutes).
Setting the warmup period to be longer than the 88-minute bootstrapping duration ensures that the scaling policy does not launch additional instances while the current ones are still initializing, avoiding over-provisioning.

Anahtar Kavram

Auto Scaling configuration, Application Load Balancer pre-warming, and redundant NAT Gateway design for high availability and fault tolerance.
Soru 1229Soru

A logistics company is designing a real-time supply chain tracking platform. The platform must ingest high-volume IoT telemetry data from millions of active sensors (write-intensive NoSQL workload, up to 100,000100,000 writes per second) and store historical device logs for regulatory audits (cold object storage, up to 50 TB50\text{ TB} monthly). The tracking data must be queryable by device ID with sub-1010 millisecond latency for the latest 3030 days. Historical logs must be retained for 77 years, encrypted with a key controlled by the security team in a centralized security account, and must be cost-optimized with a retrieval time of under 55 hours for audits. The disaster recovery requirements dictate an RTO of under 1515 minutes and an RPO of under 11 minute for the real-time tracking data. Which of the following database and storage strategies meets these requirements with the lowest cost and complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon DynamoDB global tables with replication between two AWS Regions to handle the sensor writes and queries, configuring Time to Live (TTL) to delete records after 30 days. Enable DynamoDB Streams to trigger an AWS Lambda function in the logistics account that writes the telemetry logs to an Amazon S3 bucket located in the centralized security account. Configure the S3 bucket policy in the security account to grant write permissions to the logistics account's Lambda execution role. Encrypt the S3 bucket using Server-Side Encryption with AWS KMS (SSE-KMS) using a customer managed key (CMK) in the security account, ensuring the KMS key policy explicitly permits the logistics account's Lambda role to perform kms:GenerateDataKey and kms:Decrypt. Transition the objects to S3 Glacier Flexible Retrieval after 30 days and delete them after 7 years.

Cevap

Deploy Amazon DynamoDB global tables with replication between two AWS Regions, use DynamoDB Streams with a Lambda function to write logs to an S3 bucket in the centralized security account with cross-account CMK and bucket policy permissions, and transition the S3 objects to S3 Glacier Flexible Retrieval.
The correct answer leverages Amazon DynamoDB global tables for the high-volume writes and low-latency queries, satisfying the RTO/RPO objectives through cross-region active-active replication. Transitioning historical logs to S3 Glacier Flexible Retrieval minimizes cost and satisfies the 5-hour retrieval SLA. Using a Customer Managed Key (CMK) in the centralized security account and explicitly modifying both the KMS key policy and S3 bucket policy enables secure, cross-account log delivery.

Adım Adım Çözüm

1
Select the correct database platform for high-throughput NoSQL telemetry ingestion and low-latency queries.
Amazon DynamoDB is chosen because it natively scales to support 100,000100,000 writes per second and provides sub-1010 millisecond single-digit millisecond latency queries by primary key.
Relational options like RDS PostgreSQL cannot handle this scale without complex sharding, and DynamoDB's schema-less model fits unstructured sensor payloads.
2
Determine the disaster recovery configuration to meet RTO and RPO requirements.
DynamoDB Global Tables are selected to replicate data between two AWS Regions.
Global Tables replicate asynchronously with latency under 11 second, satisfying the RPO under 11 minute and supporting instant failover for an RTO under 1515 minutes.
3
Design the archiving pipeline for historical logs to meet the retrieval time and cost requirements.
Enable DynamoDB TTL to clean up records after 3030 days. Configure DynamoDB Streams to trigger an AWS Lambda function that writes logs to S3, and use an S3 Lifecycle policy to transition them to S3 Glacier Flexible Retrieval.
Glacier Flexible Retrieval provides standard retrieval times of 3 to 53\text{ to }5 hours, satisfying the audit SLA while keeping long-term storage costs extremely low.
4
Establish secure cross-account encryption and access control.
Configure a Customer Managed Key (CMK) in the centralized security account. Grant the logistics Lambda role permission in the KMS key policy, and update the destination S3 bucket policy to allow the Lambda role to write logs.
AWS-managed KMS keys (such as `aws/s3`) do not support policy modification and cannot be shared across accounts. Cross-account S3 access requires explicit authorization in the resource-based bucket policy.

Anahtar Kavram

Selecting and configuring AWS database and storage engines for scale, cross-account security, cost optimization, and strict RTO/RPO requirements.
Tahmini Süre:3m 0s
Soru 1230Soru

A company hosts a high-traffic gaming platform on AWS. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The session data and player profiles are stored in an Amazon RDS for PostgreSQL database. During scheduled weekend tournament events, the platform experiences an instantaneous 10x spike in traffic. During these events, users encounter high latency and connection timeouts. Monitoring reveals that the ALB is dropping connections with HTTP 502 errors due to the sudden surge, and the RDS database experiences high read latency under the heavy query load. Which combination of actions should a solutions architect take to optimize the compute and storage performance of the architecture for these events?

Cevabı ve açıklamayı göster

Cevap: Contact AWS Support to pre-warm the Application Load Balancer before the scheduled tournaments, and migrate the database to Amazon Aurora PostgreSQL with Aurora Replicas configured to scale horizontally to handle the read query spikes.

Cevap

Contact AWS Support to pre-warm the Application Load Balancer before the scheduled tournaments, and migrate the database to Amazon Aurora PostgreSQL with Aurora Replicas configured to scale horizontally to handle the read query spikes.
The correct option addresses both the load balancer scaling limitation and the database read bottleneck. An instantaneous 10x traffic spike cannot be absorbed in time by normal ALB auto-scaling, requiring pre-warming by AWS Support. Amazon Aurora PostgreSQL read replicas can scale horizontally to handle the surge in read queries, whereas standard RDS Multi-AZ standby instances are passive and cannot serve read traffic.

Adım Adım Çözüm

1
Address the immediate frontend capacity bottleneck during sudden traffic spikes.
By pre-warming the Application Load Balancer (ALB) through AWS Support, the load balancer is pre-provisioned with the necessary capacity to handle the instantaneous 10x traffic surge without dropping connections.
Standard ELB auto-scaling is reactive and cannot scale rapidly enough to handle instantaneous surges, leading to HTTP 502 errors.
2
Optimize the database storage and compute layer for read-heavy query surges.
Migrate the database to Amazon Aurora PostgreSQL and create Aurora Replicas to serve read traffic.
Amazon Aurora Replicas share the same underlying storage volume as the primary instance, minimizing replication lag, and allow horizontal scaling of read capacity.

Anahtar Kavram

Handling instantaneous load spikes on ALBs and scaling database read workloads using Aurora Replicas.
Soru 1231Soru

An automotive company operates an IoT connected vehicle platform that transmits real-time telemetry data, location records, and vehicle diagnostic logs from vehicles to an Amazon S3 bucket in a Production AWS account. Due to new industry compliance mandates, the company must enhance data protection and auditability for this platform.

The solutions architect must implement a security solution that satisfies the following requirements:
- All telemetry data written to the S3 bucket must be encrypted at rest using an AWS KMS key that is rotated annually.
- Key management must be strictly segregated: the security team in a separate Central Security AWS account must control the KMS key and its policy, while the application in the Production account must only be granted permission to encrypt and decrypt the telemetry files.
- Access to the telemetry files must be audited. Any unauthorized access attempts must trigger an immediate notification.
- The telemetry data must remain completely immutable and protected against deletion or modification by any user, including the root user, for a retention period of 7 years.

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

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

Cevabı ve açıklamayı göster

Cevap: Create a Customer Managed Key (CMK) in the Central Security account with key rotation enabled. Update the CMK key policy in the Central Security account to grant kms:GenerateDataKey and kms:Decrypt permissions to the application's IAM role in the Production account. In the Production account, configure the application's IAM role with a policy allowing these same KMS actions on the Central Security account's CMK ARN, and configure the S3 bucket to use this key for default encryption.; Enable versioning on the S3 bucket and configure S3 Object Lock in compliance mode with a retention duration of 7 years. Configure AWS CloudTrail to log data events for the S3 bucket, and create an Amazon EventBridge rule that filters for S3 API call errors containing AccessDenied, triggering an Amazon SNS topic to notify the security team.

Cevap

Create a Customer Managed Key (CMK) in the Central Security account with key rotation enabled, updating the key policy to delegate access to the Production application's IAM role, and configure the Production IAM role with matching permissions. Additionally, enable S3 versioning and S3 Object Lock in compliance mode with a 7-year retention period, and configure CloudTrail data events with EventBridge rules to alert on AccessDenied errors.
To establish cross-account encryption while maintaining segregation of duties, a Customer Managed Key (CMK) must be created in the Central Security account. The key policy must delegate access to the Production account's application IAM role, and the application's IAM role must also have matching permissions. This satisfies the KMS cross-account access requirement. To enforce absolute immutability where no user (including root) can modify or delete data, versioning must be enabled alongside S3 Object Lock in compliance mode with a 7-year retention period. Monitoring unauthorized access is achieved by logging S3 data events in CloudTrail and using EventBridge rules to match 'AccessDenied' errors to trigger SNS notifications.

Adım Adım Çözüm

1
Set up the KMS key configuration for cross-account access.
Create a Customer Managed Key (CMK) in the Central Security account, enable annual rotation, and configure the key policy to grant the Production application IAM role kms:GenerateDataKey and kms:Decrypt permissions.
AWS managed keys cannot be modified or shared cross-account; a CMK is required to delegate cross-account access.
2
Configure the client-side IAM policy in the Production account.
Attach an IAM policy to the application's IAM role in the Production account allowing kms:GenerateDataKey and kms:Decrypt on the CMK ARN in the Central Security account.
Cross-account access to KMS requires both the key policy and the local IAM identity policy to permit the action.
3
Configure data immutability using S3 Object Lock.
Enable S3 versioning on the Production telemetry bucket and configure S3 Object Lock in compliance mode for 7 years.
Compliance mode guarantees that no user, including the root account, can shorten the retention period or delete objects during the 7-year window.
4
Set up auditing and access alerting.
Enable CloudTrail logging for S3 data events on the telemetry bucket, and create an EventBridge rule matching AccessDenied errors that targets an SNS topic.
CloudTrail data events capture object-level operations, and EventBridge provides real-time alerting based on specific API failure modes.

Anahtar Kavram

Cross-Account KMS Key Delegation and Immutability Controls
Soru 1232Soru

An enterprise is designing a new multi-account architecture in the `ap-northeast-1` region. The architecture contains:

* An application VPC (`vpc-tokyo-app`, CIDR 10.200.0.0/1610.200.0.0/16) spanning two Availability Zones (`ap-northeast-1a` and `ap-northeast-1c`).
* A shared services VPC (`vpc-tokyo-shared`, CIDR 10.210.0.0/1610.210.0.0/16) spanning `ap-northeast-1a` and `ap-northeast-1c`, which hosts a centralized Route 53 Private Hosted Zone (PHZ) named `corp.internal`.
* An on-premises datacenter connected via a 10 Gbps10\text{ Gbps} AWS Direct Connect (DX) connection terminating at a Direct Connect Gateway (DXGW).

The requirements are:
1. All spoke VPCs must route outbound internet traffic through centralized NAT Gateways in `vpc-tokyo-shared`.
2. The network architecture must be highly resilient against Availability Zone failures.
3. Resources in both `vpc-tokyo-app` and the on-premises datacenter must be able to resolve DNS queries for `corp.internal`.
4. Route propagation must be automated to minimize administrative routing overhead.

Which of the following designs best meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway (TGW) and attach `vpc-tokyo-app` and `vpc-tokyo-shared`. In `vpc-tokyo-shared`, deploy a NAT Gateway in each Availability Zone. In the spoke TGW route table, point 0.0.0.0/00.0.0.0/0 to the `vpc-tokyo-shared` attachment. In `vpc-tokyo-shared`, configure subnet route tables to direct outbound traffic to the local NAT Gateway in that Availability Zone. Associate the `corp.internal` PHZ with both `vpc-tokyo-app` and `vpc-tokyo-shared`. Deploy a Route 53 Resolver Inbound Endpoint in `vpc-tokyo-shared` across both Availability Zones and forward on-premises DNS queries for `corp.internal` to these endpoints. Connect the DXGW to the TGW using a Transit Virtual Interface.

Cevap

The correct design implements AWS Transit Gateway to orchestrate connectivity, deploys redundant NAT Gateways in each Availability Zone of the shared services VPC, associates the Private Hosted Zone with both the application and shared services VPCs, and configures a Route 53 Resolver Inbound Endpoint in the shared services VPC to allow resolution from the on-premises datacenter.
The correct design utilizes AWS Transit Gateway to route traffic transitively between the application VPC, the shared services VPC, and the on-premises datacenter via a Transit Virtual Interface. It maintains high availability by deploying a NAT Gateway in each Availability Zone in the shared services VPC. It ensures complete DNS resolution by associating the Private Hosted Zone with both VPCs and deploying a Route 53 Resolver Inbound Endpoint across multiple Availability Zones to handle queries from the on-premises datacenter.

Adım Adım Çözüm

1
Configure hybrid and multi-VPC transit routing using AWS Transit Gateway.
Create an AWS Transit Gateway, attach both VPCs, and connect the Direct Connect Gateway to the Transit Gateway using a Transit Virtual Interface.
This establishes a scalable transit routing architecture that handles traffic between the VPCs and the on-premises datacenter without relying on unsupported transitive routing patterns.
2
Implement redundant outbound internet routing.
Deploy a NAT Gateway in each public subnet across the two Availability Zones in the shared services VPC, and route spoke internet-bound traffic through the Transit Gateway pointing to these gateways.
This architecture ensures outbound internet traffic remains highly available and resilient to an Availability Zone failure.
3
Set up private DNS resolution for hybrid environments.
Associate the Route 53 Private Hosted Zone with both VPCs, and deploy a Route 53 Resolver Inbound Endpoint across two Availability Zones in the shared services VPC.
Associating the Private Hosted Zone with both VPCs allows local DNS resolution for resources within the cloud, while the Inbound Endpoint allows the on-premises DNS servers to forward queries for the internal domain.

Anahtar Kavram

Centralized egress and hybrid DNS resolution in a multi-VPC environment using AWS Transit Gateway and Route 53 Resolver Endpoints.
Tahmini Süre:3m 0s
Soru 1233Soru

An enterprise is setting up a new production workload in a newly created VPC named `vpc-billing-prod` within the `eu-central-1` region. The application runs across private subnets in three Availability Zones. The application must interact with:

1. An on-premises database via an existing AWS Site-to-Site VPN connection.
2. Amazon S3 to store large transaction logs.
3. A shared DNS domain (`internal.corp`) hosted on a Route 53 Private Hosted Zone (PHZ) in a separate AWS account managed by the network team.
4. The public internet to retrieve software updates.

To meet business requirements, the architecture must be highly available, avoid single points of failure, and minimize data transfer and operational costs.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy a NAT Gateway in a public subnet in each of the three Availability Zones, and update the private subnet route tables to direct outbound internet traffic (0.0.0.0/00.0.0.0/0) to the NAT Gateway in the same Availability Zone.; Create Gateway VPC endpoints for Amazon S3, and associate them with the route tables of all private subnets containing the billing application.

Cevap

To meet the requirements, the Solutions Architect should deploy a NAT Gateway in each of the three Availability Zones to ensure highly available outbound internet access, and create Gateway VPC endpoints for Amazon S3 associated with the private subnet route tables to minimize costs and optimize routing.
Deploying a NAT Gateway in each Availability Zone ensures that an outage in one zone does not impact the outbound internet connectivity of the other zones. Implementing Gateway VPC endpoints for Amazon S3 allows private subnets to route traffic directly to S3 at no additional cost, meeting the cost optimization and high availability constraints.

Adım Adım Çözüm

1
Ensure high availability for outbound internet traffic by provisioning a NAT Gateway in a public subnet within each of the three Availability Zones, rather than relying on a single NAT Gateway.
This eliminates the single point of failure for internet egress across the entire VPC.
Outages in a single Availability Zone will not impact the other zones' ability to reach the public internet.
2
Configure Gateway VPC endpoints for Amazon S3 and update the route tables of the private subnets.
S3 traffic is routed directly to the service over the AWS network without traversing NAT Gateways or the internet.
Gateway VPC endpoints do not incur hourly or data processing charges, satisfying the cost-minimization constraint.
3
Verify and associate Route 53 Private Hosted Zones for multi-account DNS resolution.
The Private Hosted Zone in the shared services account must be associated with the new VPC.
Simply using IAM roles or cross-account access does not enable local DNS resolution of private hosted zone records in another VPC.

Anahtar Kavram

Designing resilient, cost-effective VPC connectivity, NAT Gateway redundancy, and S3 Gateway VPC endpoints.
Soru 1234Soru

A global SaaS platform hosts its consumer-facing application on Amazon EC2 instances in private subnets across two AWS Regions: us-east-1 and eu-west-1. The application uses Application Load Balancers (ALBs) to distribute traffic. Users in Asia and South America are experiencing high latency and connection timeouts during peak utilization hours. Additionally, the internal microservices in both regions need to resolve each other's DNS queries securely and with minimal latency. An upcoming marketing event is expected to increase traffic by 10 times the current peak within a few minutes. Which two actions should the solutions architect recommend to optimize network performance and reduce latency? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy AWS Global Accelerator to route user traffic over the AWS global network, onboarding traffic at the closest Edge Location to minimize latency and TCP connection establishment time.; Request AWS Support to pre-warm the ALBs in both regions prior to the marketing event to handle the sudden traffic surge without dropping packets or causing queuing latency.

Cevap

Deploy AWS Global Accelerator to route user traffic over the AWS global network backbone, and request AWS Support to pre-warm the ALBs in both regions prior to the high-volume marketing event.
Deploying AWS Global Accelerator ensures that global user traffic is routed over the high-speed, congestion-free AWS global network backbone from the nearest Edge Location, minimizing latency and packet loss. Additionally, requesting ALB pre-warming from AWS Support before a scheduled traffic surge ensures that the load balancers have sufficient capacity to handle the peak traffic immediately without causing latency spikes or dropped connections due to scaling delays.

Adım Adım Çözüm

1
Analyze the user entry point and global latency issues.
Identify that users in distant regions (Asia and South America) experience high latency due to public internet routing jitter and TCP handshake overhead.
Onboarding traffic closer to the user using Anycast IPs with AWS Global Accelerator minimizes the path over the public internet.
2
Address the upcoming 10x traffic spike constraint.
Recognize that standard ALB scaling is gradual and cannot handle a sudden 10-fold traffic surge instantly, which would lead to connection failures and high queuing latency.
Requesting ALB pre-warming configures the load balancers to handle the peak capacity from the start of the event.
3
Evaluate internal DNS and egress configurations.
Confirm that Private Hosted Zones must be associated with all target VPCs to avoid DNS resolution failure, and that NAT Gateways should be deployed per Availability Zone to prevent cross-AZ latency.
Eliminating cross-AZ hops and public routing paths optimizes internal network latency and throughput.

Anahtar Kavram

Optimizing global ingress paths with AWS Global Accelerator and pre-empting load balancer scaling limitations during massive traffic surges.
Soru 1235Soru

A company has an existing application that stores sensitive customer documents in an Amazon S3 bucket within a production AWS account. The S3 bucket is currently encrypted using the AWS-managed KMS key (aws/s3). To meet new regulatory compliance requirements, a security audit determines that:

- The encryption key must be rotated automatically on an annual basis, and the security team must have the ability to explicitly edit its key policy.
- A compliance audit team operating from a separate, dedicated audit AWS account must be able to read the encrypted documents directly from the S3 bucket.

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

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

Cevabı ve açıklamayı göster

Cevap: Create a Customer Managed Key (CMK) in the production account, enable automatic key rotation, and configure the key policy to allow the audit account's IAM role to perform the kms:Decrypt action.; Modify the S3 bucket policy in the production account to allow the audit account's IAM role to perform the s3:GetObject action, and configure the audit account's IAM role policy to allow s3:GetObject and kms:Decrypt actions on the production S3 and KMS key resources.

Cevap

To meet the compliance and encryption requirements, the company must create a Customer Managed Key (CMK) in the production account, enable automatic key rotation, and configure the key policy to permit the audit account's IAM role to decrypt. Additionally, the production account's S3 bucket policy must grant read access to the audit account's IAM role, and the audit role itself must have IAM permissions to read from the S3 bucket and decrypt using the production account's KMS CMK.
The correct options work together to establish cross-account trust and decryption permissions. The option stating to create a Customer Managed Key (CMK) and enable key rotation correctly addresses the limitation of AWS-managed keys (aws/s3), which cannot be modified to support cross-account access. The option stating to modify the S3 bucket policy and update the audit account's IAM role policy properly establishes the mutual trust relationship required for cross-account S3 operations.

Adım Adım Çözüm

1
Address the KMS key limitation.
Create a Customer Managed Key (CMK) instead of using the default AWS-managed key (aws/s3) because AWS-managed keys do not permit cross-account policy delegation.
AWS-managed key policies cannot be modified to grant decrypt permissions to another account.
2
Configure the KMS key policy and key rotation.
Enable automatic annual key rotation on the CMK and add a statement in the CMK key policy in the production account allowing the audit account's IAM role to perform kms:Decrypt.
Allows the external audit principal to use the production key to decrypt the objects.
3
Configure S3 bucket-level cross-account trust.
Modify the S3 bucket policy in the production account to grant the audit account's IAM role the s3:GetObject permission.
Establish cross-account trust on the resource side for S3 bucket access.
4
Configure client-side permissions.
Add IAM policies to the audit account's IAM role allowing it to perform s3:GetObject on the production S3 bucket and kms:Decrypt on the production KMS CMK.
Provides the audit principal with explicit authorization to execute read and decrypt operations on the target resources.

Anahtar Kavram

Cross-account access to S3 buckets encrypted with KMS requires Customer Managed Keys (CMKs) rather than AWS-managed keys. Access must be explicitly granted on the KMS key policy, the S3 bucket policy, and the caller's IAM policy.
Tahmini Süre:2m 0s
Soru 1236Soru

An enterprise is planning to migrate its on-premises inventory management system to AWS. The system consists of three distinct components:

1. A Java-based web application running on Apache Tomcat. The development team wants to avoid modifying the application code but wishes to eliminate operating system maintenance by hosting it on AWS Fargate.
2. A backend Oracle Database Enterprise Edition 19c that requires high licensing fees. The enterprise wants to eliminate these license costs by migrating to Amazon Aurora PostgreSQL.
3. A legacy reporting system running on a Solaris UNIX server that utilizes a physical hardware key (USB dongle) for license validation. The vendor software does not support x86-64 virtualization, and the software contract is active for another three years.

Which of the following migration strategies represent the correct alignment under the AWS 7 Rs framework for these components? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Replatform the web application by containerizing it to run on AWS Fargate without modifying the application code.; Refactor the database tier by converting the Oracle schema and migrating the database to Amazon Aurora PostgreSQL.

Cevap

Replatform the web application by containerizing it to run on AWS Fargate without modifying the application code, and Refactor the database tier by converting the Oracle schema and migrating the database to Amazon Aurora PostgreSQL.
Containerizing the web application without code changes to run on AWS Fargate represents a Replatform strategy because it changes the hosting platform to optimize operations while preserving the application logic. Transitioning from Oracle to Aurora PostgreSQL represents a Refactor strategy because it involves an engine change that requires schema translation, code rewrite, and data migration.

Adım Adım Çözüm

1
Evaluate the migration strategy for the Tomcat web application.
Identify it as Replatforming.
The platform is changing from VMs to AWS Fargate to reduce OS management overhead, but the application code is not being rewritten.
2
Evaluate the migration strategy for the database tier.
Identify it as Refactoring (Rearchitecting).
Migrating from Oracle to Aurora PostgreSQL involves converting the database engine, requiring schema migration and SQL rewrites, which changes the application architecture.
3
Evaluate the migration strategy for the legacy reporting system.
Identify it as Retaining.
Hardware dependencies (USB dongles) and SPARC architecture compatibility issues mean it cannot be migrated to AWS and must remain on-premises.

Anahtar Kavram

Selecting migration strategies (7 Rs) based on technical, runtime, and licensing constraints.
Soru 1237Soru

A logistics company has an existing application that stores customer delivery signatures and shipping manifests in an Amazon S3 bucket. The bucket is currently configured with Server-Side Encryption with Amazon S3 managed keys (SSE-S3). Due to new regulatory compliance mandates, the company must enhance its data protection posture by meeting the following requirements:
- All data must be encrypted using a key that supports automatic annual rotation.
- Detailed audit logs of all encryption and decryption operations must be centralized in a dedicated security monitoring AWS account.
- The system must minimize the volume of KMS API requests to avoid throttling errors during peak hours when a high volume of documents are uploaded.
- Any attempt to upload objects using incorrect encryption configurations or without encryption must be blocked.

Which combination of actions should the Solutions Architect implement to meet these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Create a customer managed key (CMK) in AWS KMS within the application account, enable automatic key rotation, and configure the S3 bucket's default encryption to use this KMS key. Enable S3 Bucket Keys on the S3 bucket. Configure AWS CloudTrail to log S3 data events and KMS key management events, delivering them to a centralized S3 bucket in the security account. Add a bucket policy to the S3 bucket that denies s3:PutObject requests if the x-amz-server-side-encryption header is present and not set to aws:kms.

Cevap

Create a customer managed key in AWS KMS with automatic rotation enabled, configure default S3 bucket encryption with this key, enable S3 Bucket Keys to minimize KMS request volume, centralize CloudTrail logs in the security account, and use an S3 bucket policy to deny uploads that do not specify SSE-KMS.
The correct solution uses a customer managed KMS key to support automatic annual rotation and allow custom policy delegation. Enabling S3 Bucket Keys caches bucket-level keys to significantly reduce KMS API requests and avoid throttling. S3 data events and KMS management events are logged via CloudTrail to a centralized bucket in the security account. The S3 bucket policy ensures that clients cannot override the default encryption with unencrypted requests or SSE-S3 headers.

Adım Adım Çözüm

1
Create a customer managed KMS key in the application account and enable automatic key rotation.
Establishes a cryptographically secure key under customer control that automatically rotates yearly, meeting compliance requirements.
AWS-managed keys do not support custom rotation configurations or key policy changes for cross-account access.
2
Enable S3 Bucket Keys and configure the S3 bucket's default encryption to use the newly created customer managed KMS key.
Ensures all newly written objects are encrypted using the customer managed KMS key and drastically reduces the volume of KMS API requests.
S3 Bucket Keys cache bucket-level keys, reducing KMS request traffic by up to 99% and preventing API throttling during high-volume uploads.
3
Configure AWS CloudTrail in the application account to deliver data and management logs to a centralized, secured S3 bucket in the security monitoring account.
Creates a secure, immutable audit trail of all bucket access and KMS operations in a separate administrative domain.
Separating audit trails to a dedicated security account prevents tamper risk and complies with strict auditing frameworks.
4
Apply a bucket policy to the S3 bucket denying s3:PutObject requests that contain encryption headers other than aws:kms.
Enforces encryption standards at the bucket level, preventing clients from uploading unencrypted data or using weaker SSE-S3 encryption.
Default encryption handles requests without headers, but a explicit deny policy prevents clients from explicitly overriding default settings with non-compliant encryption methods.

Anahtar Kavram

Combining S3 Bucket Keys, Customer Managed KMS Keys, S3 Bucket Policies, and Centralized CloudTrail logging to satisfy strict data protection, audit, and performance scalability requirements.
Tahmini Süre:2m 30s
Soru 1238Soru

A medical technology company operates a critical patient telemetry application running on Amazon EC2 instances in an Auto Scaling group across multiple AWS member accounts. The application writes log data to `/var/log/telemetry/active.log`. Due to high write volume, these log files are rotated and renamed hourly to `/var/log/telemetry/active.log.YYYY-MM-DD-HH` using a local utility. The company needs to centralize these application logs into a single Amazon S3 bucket located in a dedicated monitoring account for long-term retention and security analysis. The solution must ensure that logs are continuously delivered even immediately after rotation, must support encryption at rest in the destination bucket using a customer-managed key, and must scale efficiently with minimum administrative overhead. Which solutions architecture meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Install the unified Amazon CloudWatch agent on the EC2 instances. In the agent configuration, specify the log file path using the wildcard pattern `/var/log/telemetry/active.log*` to match the rotated files. Configure the agent to stream the logs to a local Amazon CloudWatch log group. Set up a CloudWatch subscription filter in each member account to stream the logs to an Amazon Kinesis Data Firehose delivery stream in the monitoring account, which writes the logs to the central S3 bucket using a Customer Managed KMS key for SSE-KMS encryption.

Cevap

Install the unified Amazon CloudWatch agent on the EC2 instances using a wildcard pattern for the log file path, stream the logs to local CloudWatch log groups, and use subscription filters to forward the logs to a central Kinesis Data Firehose delivery stream in the monitoring account that writes to the S3 bucket with Customer Managed KMS encryption.
The correct architecture uses the unified CloudWatch agent configured with a wildcard pattern to ensure log rotation does not interrupt log ingestion. Streaming to local CloudWatch log groups and forwarding via subscription filters to a central Kinesis Data Firehose delivery stream in the monitoring account provides a secure, highly scalable, and low-latency pipeline. Using a Customer Managed Key for SSE-KMS ensures that cross-account access can be configured via key policies.

Adım Adım Çözüm

1
Configure the CloudWatch agent log path with a wildcard pattern.
The agent continuously tracks and streams the active log file as well as any rotated log files with timestamp suffixes, preventing log delivery gaps.
Rotated logs will be renamed, and a static path would cause the agent to stop reading the rotated logs once the file handles change.
2
Use CloudWatch subscription filters to forward logs to Kinesis Data Firehose.
Local CloudWatch log streams are automatically aggregated and sent across accounts to Kinesis Data Firehose in the monitoring account.
This avoids direct cross-account S3 write complications from EC2 and provides a scalable, managed delivery pipeline.
3
Configure Kinesis Data Firehose to write to S3 with SSE-KMS using a Customer Managed Key.
Logs are encrypted at rest in the central S3 bucket using a key whose policy permits the cross-account Firehose and security roles.
AWS-managed KMS keys do not support policy modification and cannot be shared cross-account, necessitating a Customer Managed Key.

Anahtar Kavram

Continuous operational monitoring and secure cross-account log centralization using CloudWatch agents, subscription filters, and managed keys.
Soru 1239Soru

A luxury watch retailer hosts its online storefront on AWS, using an Amazon Aurora MySQL database cluster with one writer and two reader instances to manage product cataloging and real-time inventory reservations. During high-traffic product releases, customers experience transaction failures, and the database writer node experiences 100% CPU utilization, leading to database connection timeouts and application-level thread exhaustion. An analysis shows that the bottleneck is caused by high-concurrency database connections and frequent read-modify-write operations on the inventory table. The retailer requires a solution that guarantees sub-millisecond read latency for inventory status, maintains transactional persistence for reservations, and scales automatically to handle connection spikes while maintaining high availability. Which two of the following architectural changes should the Solutions Architect implement to resolve the performance bottlenecks?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon ElastiCache for Redis replication group with Multi-AZ and automatic failover enabled to cache inventory status and manage reservation states.; Deploy Amazon RDS Proxy between the application layer and the Amazon Aurora MySQL cluster to pool and reuse database connections, minimizing connection overhead on the database writer.

Cevap

Deploying an Amazon ElastiCache for Redis replication group with Multi-AZ and automatic failover enabled, and deploying Amazon RDS Proxy between the application layer and the Amazon Aurora MySQL cluster.
The correct solution involves deploying Amazon ElastiCache for Redis to achieve sub-millisecond latencies, with Multi-AZ and automatic failover enabled to meet the persistence and high availability requirements. Simultaneously, deploying Amazon RDS Proxy pools and reuses database connections, resolving connection bottlenecks and preventing thread pool exhaustion on the primary writer.

Adım Adım Çözüm

1
Analyze the bottleneck on the database writer due to connection spikes and connection timeouts.
Identify that connection overhead is causing thread pool exhaustion, which can be mitigated by introducing Amazon RDS Proxy to pool and reuse connections.
RDS Proxy sits between the application and database to prevent excessive connection creation and reuse existing pools.
2
Identify the cache requirements for inventory reservations: sub-millisecond latency, persistence, and replication/high availability.
Choose Amazon ElastiCache for Redis over Memcached because Redis supports persistence, replication, and Multi-AZ failover.
Memcached is transient, lacks built-in replication/failover, and cannot guarantee data persistence for active reservations.
3
Evaluate replica scaling options for handling the write-modify-read reservation load.
Determine that read replicas (Aurora Replicas or RDS Standby instances) cannot process write operations or offload the primary writer's reservation updates.
Writes must execute on the primary writer, making replica scaling ineffective for write-heavy hotspots.

Anahtar Kavram

To handle write-modify-write bottlenecks and connection spikes in a database cluster, introduce a connection proxy (like Amazon RDS Proxy) and offload low-latency states to a persistent, highly available cache (like Amazon ElastiCache for Redis).
Tahmini Süre:3m 0s
Soru 1240Soru

A solutions architect is migrating an on-premises physical server to AWS using AWS Application Migration Service (MGN). The replication traffic is configured to travel over a Site-to-Site VPN connection directly into the staging area subnet of the target VPC. The AWS Replication Agent has been successfully installed on the source server, but the replication status shows as disconnected, and data transfer cannot begin. Which of the following configuration changes will resolve the replication connectivity issue?

Cevabı ve açıklamayı göster

Cevap: Configure the on-premises firewall and the replication staging area security groups to allow traffic over TCP port 1500 between the source server and the replication servers.

Cevap

Configure the on-premises firewall and the replication staging area security groups to allow traffic over TCP port 1500 between the source server and the replication servers.
The correct action is to open TCP port 1500. During the migration process, the AWS Replication Agent on the source server communicates with the replication servers in the staging area over TCP port 1500 to perform data replication. Opening this port in both the on-premises firewall (outbound) and the staging area security groups (inbound) allows the replication stream to flow.

Adım Adım Çözüm

1
Identify the port requirements for AWS Application Migration Service data replication.
TCP port 1500 is identified as the required port for data replication between the agent and the replication servers.
The AWS Replication Agent sends compressed and encrypted data blocks to the replication servers over TCP port 1500.
2
Inspect the network path security configurations.
Verify that both the source network's firewall and the staging subnet's security group allow TCP port 1500.
Any blockage on TCP port 1500 along the VPN path will prevent the replication data from being received, causing the agent to report a disconnected status.

Anahtar Kavram

AWS MGN Data Replication Port Requirements
ÖncekiSayfa 62 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin