Tüm alıştırma soruları

1462 soru

Tüm türler1,462 Çoktan seçmeli739 Çoklu seçim723

A global e-learning company serves dynamic content to users worldwide. The application backend is deployed behind Application Load Balancers (ALBs) in both the eu-central-1 and ap-southeast-1 regions. The company wants to route users to the region that provides the lowest network latency. If one of the regions experiences an outage, Route 53 must automatically stop routing traffic to that region's ALB. The application uses the apex domain learn.example.com. Which configuration should the solutions architect implement to meet these requirements?

Create Latency Alias records for the apex domain pointing to the ALBs in each region, and set the 'Evaluate Target Health' parameter to 'No' to maximize DNS caching efficiency.

Create Latency Alias records for the apex domain. Configure the primary record to point to the eu-central-1 ALB, and configure the secondary record to point directly to the DNS endpoint of the Amazon RDS read replica in ap-southeast-1.

Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

Create Failover records for the apex domain, pointing the primary record to the eu-central-1 ALB. Point the secondary record to a stopped EC2 instance in ap-southeast-1 that serves as a standby database, expecting Route 53 to automatically start the instance and route traffic during a failover.

Cevabı ve açıklamayı göster

Cevap: Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

Cevap

Create Latency Alias records for the apex domain pointing to the respective ALBs in each region, and set the 'Evaluate Target Health' parameter to 'Yes' on both records.

The correct configuration utilizes Latency-based routing with Alias records pointing to the ALBs in each region. Because the zone apex domain (learn.example.com) is used, CNAME records are not permitted, necessitating Alias records. Setting 'Evaluate Target Health' to 'Yes' allows Route 53 to determine the health of the ALBs based on the underlying target group health checks, enabling automatic failover and routing redirection during a regional outage.

Adım Adım Çözüm

Determine the routing policy and record type required for the zone apex domain.

An Alias record must be used because DNS standards do not allow CNAME records at the zone apex (learn.example.com). To satisfy the requirement of routing to the lowest latency region, Latency-based routing must be used.

Alias records allow mapping the zone apex to AWS resources like ALBs, and Latency routing satisfies the performance requirement.

Configure health checks and automatic failover mechanism.

Enable the 'Evaluate Target Health' setting (set to Yes) on the Route 53 Latency Alias records pointing to the ALBs.

This allows Route 53 to inherit the health of the ALB (based on its target group health checks) to stop routing traffic to an unhealthy region automatically without needing a separate Route 53 health check.

Anahtar Kavram

Route 53 Latency Routing with Alias records and Target Health Evaluation

Soru 142Soru →

A company needs to implement a security monitoring strategy for its AWS environment. The strategy must include auditing all API activities for unauthorized actions and automatically detecting when security groups are modified to allow unrestricted public access (0.0.0.0/0). Which of the following actions should the solutions architect take to meet these requirements? (Select TWO.)

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

Enable AWS CloudTrail to record and audit all API activity across the AWS account.

Create an AWS Config rule to automatically monitor and detect when security groups are modified to allow unrestricted public traffic.

Deploy AWS Shield Standard to inspect application-layer traffic and automatically block SQL injection exploits on the web application.

Configure stateful Network Access Control Lists (NACLs) to log, monitor, and restore the configuration history of individual security groups.

Store administrative credentials as plaintext String parameters in Systems Manager Parameter Store to automate threat remediation scripts.

Cevabı ve açıklamayı göster

Cevap: Enable AWS CloudTrail to record and audit all API activity across the AWS account.; Create an AWS Config rule to automatically monitor and detect when security groups are modified to allow unrestricted public traffic.

Cevap

Enable AWS CloudTrail to record all API activity, and create an AWS Config rule to monitor security group modifications.

AWS CloudTrail logs and monitors all API activity across the AWS account, providing auditing capability for unauthorized modifications. AWS Config continuously records configuration changes of AWS resources, such as security groups, and evaluates them against compliance rules (e.g., detecting if a security group allows unrestricted 0.0.0.0/0 ingress traffic). Together, these services fulfill the requirements of monitoring API changes and detecting insecure resource configurations.

Adım Adım Çözüm

Identify the requirement for tracking and auditing API actions.

AWS CloudTrail is selected to log all API calls across the AWS account.

CloudTrail provides a complete history of API activity, enabling security auditing and monitoring.

Identify the requirement for monitoring and alerting on resource configuration compliance.

AWS Config is chosen to detect security group compliance violations.

AWS Config continuously monitors resource configurations and evaluates them against rules (e.g., checking for unrestricted port access).

Anahtar Kavram

AWS CloudTrail is used for auditing and monitoring API activity, while AWS Config is used to monitor, audit, and evaluate the configurations of AWS resources.

Tahmini Süre:1m 0s

Soru 143Soru →

A medical research institute distributes large, static genomic data files that are updated weekly, and provides a search API for genomic metadata. The genomic files are stored in an Amazon S3 bucket, and the search API is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). During new publication releases, the institute experiences sudden spikes in global traffic. The institute needs a resilient architecture that minimizes load on both S3 and the ALB, reduces latency for researchers worldwide, and protects the search API from SQL injection attacks. Which architecture meets these requirements with the lowest latency and highest resiliency?

Configure Amazon Route 53 with latency-based routing policies to distribute traffic directly to the S3 bucket for static files and to the ALB for API requests. Associate an AWS WAF web ACL with the ALB to mitigate SQL injection attacks.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure cache behaviors to cache static files and forward API requests. Enable AWS Shield Advanced on the CloudFront distribution to detect and block SQL injection attacks on the API.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure two cache behaviors: one for static file paths with caching enabled, and one for API paths that forwards requests to the ALB. Associate an AWS WAF web ACL with the CloudFront distribution.

Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure a cache behavior for the static files with Minimum TTL, Default TTL, and Maximum TTL set to 0 to ensure the weekly files are never stale. Associate an AWS WAF web ACL with the CloudFront distribution.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon CloudFront distribution with the S3 bucket and ALB configured as origins. Configure two cache behaviors: one for static file paths with caching enabled, and one for API paths that forwards requests to the ALB. Associate an AWS WAF web ACL with the CloudFront distribution.

Cevap

The correct solution uses Amazon CloudFront to cache static files from S3 at edge locations, significantly reducing global latency and origin S3 read load during traffic spikes. Dynamic API requests are routed through a separate CloudFront cache behavior to the ALB without caching. By attaching an AWS WAF web ACL to CloudFront, the API is protected against SQL injection attacks at the edge, before the traffic reaches the backend servers.

Adım Adım Çözüm

Analyze the static and dynamic requirements.

The static genomic data files stored in S3 can be cached at the edge, while the dynamic search API requests behind the ALB should be forwarded to the origin without caching.

Separating static and dynamic traffic allows for optimized caching rules and reduces load on the origin S3 bucket and ALB.

Configure Amazon CloudFront origins and cache behaviors.

Create a CloudFront distribution with the S3 bucket and ALB as origins. Create a behavior for `/static/*` that caches content, and a behavior for `/api/*` that forwards requests to the ALB origin with caching disabled.

CloudFront edge locations serve cached static content directly to users, minimizing latency and origin load, while acting as a reverse proxy for the API traffic.

Address the security requirement for the search API.

Associate an AWS WAF web ACL with the CloudFront distribution to inspect incoming requests for SQL injection signatures.

AWS WAF provides Layer 7 protection at the edge, blocking malicious requests before they reach the ALB or S3 origins.

Anahtar Kavram

Using Amazon CloudFront cache behaviors to segregate and optimize static caching and dynamic forwarding, combined with AWS WAF for Layer 7 edge security.

Tahmini Süre:2m 0s

Soru 144Soru →

A company operates a global shipment tracking API at api.shipments.example.com. The application is deployed in the eu-central-1 and ap-southeast-1 Regions behind an Application Load Balancer (ALB) in each Region. The company wants an active-active setup that routes users to the Region with the lowest network latency. If an ALB in one Region fails, Route 53 must automatically stop routing traffic to that Region. Which configuration meets these requirements with the lowest administrative complexity and cost?

Create Route 53 Latency CNAME records for api.shipments.example.com pointing to the ALB DNS names, and set Evaluate Target Health to Yes.

Create Route 53 Failover Alias records pointing to the ALBs, configuring eu-central-1 as primary and ap-southeast-1 as a pilot light secondary that only provisions compute resources after a failover event is detected.

Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

Create Route 53 Latency Alias records pointing to the ALBs, and configure the DNS failover to route traffic directly to the Amazon RDS Read Replica in the secondary Region when the primary database becomes unhealthy.

Cevabı ve açıklamayı göster

Cevap: Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

Cevap

Create Route 53 Latency Alias records for api.shipments.example.com pointing to the Application Load Balancer (ALB) in each Region, and set Evaluate Target Health to Yes.

The correct configuration uses Route 53 Latency Alias records pointing to the Application Load Balancers with Evaluate Target Health set to Yes. This fulfills the active-active requirement by routing users to the Region with the lowest latency, and it automatically stops routing traffic to a Region if its ALB becomes unhealthy, using the inherited ALB health checks without any extra cost or administrative overhead.

Adım Adım Çözüm

Analyze the active-active and latency requirements.

Determine that Latency routing must be used to send clients to the closest Region to minimize latency, rather than Failover routing which is active-passive.

The requirement specifies routing users to the Region with the lowest network latency under normal operating conditions.

Determine the health checking and failover mechanism.

Identify that 'Evaluate Target Health' must be set to Yes to let Route 53 monitor the ALBs automatically.

Enabling Evaluate Target Health allows Route 53 to check the health of the ALB targets and stop routing traffic if they fail, without needing custom HTTP health checks.

Evaluate record types (Alias vs CNAME) for the load balancers.

Select Alias records because Route 53 'Evaluate Target Health' is only supported on Alias records, and Alias records do not incur DNS query charges.

CNAME records do not support the 'Evaluate Target Health' feature directly, requiring additional configurations and costs.

Anahtar Kavram

Route 53 Latency Alias routing with Evaluate Target Health enables cost-effective, low-latency, active-active regional failover.

Soru 145Soru →

A financial services company is deploying a distributed financial risk modeling application on Amazon EC2 instances. The application nodes must communicate with each other using low-latency, high-throughput network connections with sub-millisecond latencies. A Network Load Balancer (NLB) distributes external simulation traffic to these nodes on TCP port 8443. The architecture must ensure optimal compute performance and accurate health reporting.

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

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

Deploy the EC2 instances in a cluster placement group within a single Availability Zone.

Configure the target group health check for the Network Load Balancer to use TCP port 8443.

Deploy the EC2 instances in a spread placement group across multiple Availability Zones.

Configure the target group health check to query the default HTTP port 80 to minimize processing overhead on the instances.

Deploy the EC2 instances in a partition placement group to isolate failure domains.

Cevabı ve açıklamayı göster

Cevap: Deploy the EC2 instances in a cluster placement group within a single Availability Zone.; Configure the target group health check for the Network Load Balancer to use TCP port 8443.

Cevap

Deploy the EC2 instances in a cluster placement group within a single Availability Zone, and configure the target group health check for the Network Load Balancer to use TCP port 8443.

The correct architecture uses a cluster placement group to enable low-latency, high-throughput node-to-node communication, and aligns the target group health check port with the application's actual port (8443) to prevent false health check failures.

Adım Adım Çözüm

Identify the networking performance requirements for the cluster nodes.

Tightly coupled nodes requiring sub-millisecond latencies point to a cluster placement group within a single Availability Zone.

Cluster placement groups logically group instances within a single Availability Zone to enable low-latency, high-throughput networking between nodes.

Identify the load balancer health check requirements.

The target group must be configured with a health check port matching the application service port (8443).

Mismatched health check ports (such as using default port 80 when the application runs on port 8443) will cause health checks to fail, marking healthy nodes as unhealthy.

Anahtar Kavram

High-Performance Compute Placement and Load Balancer Health Monitoring

Tahmini Süre:2m 0s

Soru 146Soru →

A blockchain development company is deploying a private distributed ledger validator network on Amazon EC2 instances. The validator nodes require sub-millisecond network latency to achieve consensus on block transactions. The validator API is exposed on port 3000, while a separate management agent runs on port 9000 to handle internal status reporting and health endpoint checks. An Application Load Balancer (ALB) is configured to route client RPC traffic to the validators. Which combination of configuration settings satisfies the latency requirements and ensures that validator nodes are correctly identified as healthy by the load balancer?

Deploy the EC2 instances in a Cluster placement group. Configure the ALB target group to perform health checks on port 9000 and route client traffic to port 3000.

Deploy the EC2 instances in a Spread placement group. Configure the ALB target group to perform health checks on port 9000 and route client traffic to port 3000.

Deploy the EC2 instances in a Cluster placement group. Configure the ALB target group to perform health checks on the traffic port and route client traffic to port 3000.

Deploy the EC2 instances in a Partition placement group. Configure the ALB target group to perform health checks on the traffic port and route client traffic to port 3000.

Cevabı ve açıklamayı göster

Cevap: Deploy the EC2 instances in a Cluster placement group. Configure the ALB target group to perform health checks on port 9000 and route client traffic to port 3000.

Cevap

Deploy the EC2 instances in a Cluster placement group, configure the Application Load Balancer target group to perform health checks on port 9000, and route client traffic to port 3000.

To achieve sub-millisecond network latency, instances must be launched in a Cluster placement group, which places them close together within a single Availability Zone. Additionally, because the status reporting and health monitoring daemon is hosted on port 9000 while the client API runs on port 3000, the target group health checks must be explicitly configured to point to port 9000. This ensures that the load balancer correctly validates target status while routing client traffic to the correct application port.

Adım Adım Çözüm

Identify network latency requirements for validator nodes.

A Cluster placement group is required to achieve sub-millisecond node-to-node communication within a single Availability Zone.

Cluster placement groups pack instances close together on the underlying hardware to minimize network latency.

Determine the correct port configuration for application traffic and health checks.

The Application Load Balancer must route client traffic to port 3000 and execute health checks on port 9000.

The validator API listens on port 3000, but the health monitoring daemon listens on port 9000, meaning traffic-port health checks will fail.

Anahtar Kavram

Deploying instances in a Cluster placement group for high-performance low-latency workloads, and configuring target groups with custom health check ports when health daemons run on a non-traffic port.

Soru 147Soru →

A retail company hosts a promotional web application on AWS. The static product catalog images are stored in an Amazon S3 bucket, and an Amazon CloudFront distribution is deployed to serve these images to global users. During a marketing campaign, the company observes a massive spike in S3 data transfer and API request costs, and users experience increased latency. A review of the CloudFront configuration reveals that the cache behavior for the images has the Minimum TTL, Maximum TTL, and Default TTL all set to 0 seconds. Which action should the solutions architect recommend to resolve this issue and optimize performance?

Configure the CloudFront cache behavior with positive TTL values, such as a Default TTL of 86400 seconds, to allow the CDN to cache the images at edge locations.

Keep the CloudFront TTL settings at 0 seconds to ensure immediate updates, and deploy an Amazon ElastiCache cluster to cache the static image files.

Transition the product images in the Amazon S3 bucket to the S3 Standard-Infrequent Access (S3 Standard-IA) storage class to optimize request costs.

Associate an AWS WAF web ACL with the CloudFront distribution and configure a rate-limiting rule to block excess requests to the catalog images.

Cevabı ve açıklamayı göster

Cevap: Configure the CloudFront cache behavior with positive TTL values, such as a Default TTL of 86400 seconds, to allow the CDN to cache the images at edge locations.

Cevap

Configure the CloudFront cache behavior with positive TTL values, such as a Default TTL of 86400 seconds, to allow the CDN to cache the images at edge locations.

Configuring positive TTL values (such as a Default TTL of 86400 seconds) enables CloudFront to cache the static product catalog images at edge locations. Subsequent requests from users will be served directly from the nearest Edge cache rather than going to the S3 origin bucket. This reduces both S3 API call charges and data transfer costs, while significantly lowering latency for global end-users.

Adım Adım Çözüm

Identify the root cause of the high latency and origin request spike.

The CloudFront distribution is configured with Minimum, Maximum, and Default TTLs of 0 seconds, meaning no caching is happening at edge locations.

When TTL is 0, CloudFront must forward every incoming request back to the S3 origin, negating the benefits of the CDN.

Select the appropriate remedy to enable caching for static assets.

Modify the CloudFront cache behavior to use positive TTL values (e.g., Default TTL of 86400 seconds).

This allows CloudFront to store the images at Edge locations, satisfying subsequent requests locally and offloading the S3 origin.

Anahtar Kavram

CloudFront Caching Behaviors and Time-To-Live (TTL) Configuration

Soru 148Soru →

An enterprise application hosted on Amazon ECS Fargate needs to access two types of configuration data: database credentials for a production Amazon RDS for PostgreSQL instance, and public API endpoints for external microservices. The database credentials must be encrypted at rest, rotated every 30 days, and accessed securely. The public API endpoints are non-sensitive, do not change frequently, and must be retrieved with the lowest possible cost.

Which combination of actions should a solutions architect recommend to manage these configurations? (Select TWO.)

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

Store the database credentials in AWS Secrets Manager and enable automatic secret rotation with a schedule of 30 days.

Store the public API endpoints as Standard String parameters in AWS Systems Manager Parameter Store.

Store the database credentials as Standard String parameters in AWS Systems Manager Parameter Store to minimize storage costs.

Store the database credentials in AWS Systems Manager Parameter Store as SecureString parameters, and rely on AWS KMS automatic key rotation of the Customer Managed Key to automatically update the database password every 30 days.

Store both the database credentials and the public API endpoints as String parameters in AWS Systems Manager Parameter Store, relying on IAM policies to restrict decryption permissions.

Cevabı ve açıklamayı göster

Cevap: Store the database credentials in AWS Secrets Manager and enable automatic secret rotation with a schedule of 30 days.; Store the public API endpoints as Standard String parameters in AWS Systems Manager Parameter Store.

Cevap

Store the database credentials in AWS Secrets Manager with automatic rotation, and store the public API endpoints as Standard String parameters in AWS Systems Manager Parameter Store.

To securely manage sensitive and non-sensitive configuration data at the lowest cost, a solutions architect should use AWS Secrets Manager for database credentials and Systems Manager Parameter Store for public API endpoints. Secrets Manager encrypts data at rest and natively supports automatic 30-day rotation for Amazon RDS. For the non-sensitive API endpoints, Systems Manager Parameter Store's Standard String parameters are free of charge, making them the most cost-effective choice.

Adım Adım Çözüm

Evaluate the security and rotation requirements of the database credentials.

Database credentials are sensitive secrets that require encryption at rest and automatic rotation every 30 days. AWS Secrets Manager is the optimal service because it provides built-in integration with RDS and automatic secret rotation via Lambda.

Systems Manager Parameter Store does not support out-of-the-box automatic database credential rotation, whereas Secrets Manager does.

Evaluate the storage and cost requirements of the non-sensitive public API endpoints.

The public API endpoints are non-sensitive and need to be stored at the lowest possible cost. Standard parameters (String type) in AWS Systems Manager Parameter Store do not incur additional costs.

Using AWS Secrets Manager for non-sensitive settings would incur unnecessary storage costs ($0.40 per secret per month).

Anahtar Kavram

Selecting the appropriate AWS service for configuration management based on data sensitivity, rotation requirements, and cost-effectiveness.

Tahmini Süre:1m 30s

Soru 149Soru →

A logistics company operates a central distribution dashboard that consists of a fleet of Amazon ECS tasks running on AWS Fargate to handle constant, predictable API requests throughout the day. The backend stores shipment records in an Amazon RDS for PostgreSQL database instance that also runs continuously. The company wants to minimize compute costs for these resources without modifying the application code or architecture. Which combination of purchasing strategies should a solutions architect recommend to meet these requirements? (Select TWO.)

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

Purchase a Compute Savings Plan to cover the AWS Fargate tasks

Purchase Amazon RDS Reserved Instances for the PostgreSQL database

Purchase a Compute Savings Plan to cover the Amazon RDS database instance usage

Migrate the database to Amazon DynamoDB using Provisioned Capacity Mode to manage unpredictable query traffic

Migrate the API processing components to AWS Lambda to handle the constant, 24/7 requests

Cevabı ve açıklamayı göster

Cevap: Purchase a Compute Savings Plan to cover the AWS Fargate tasks; Purchase Amazon RDS Reserved Instances for the PostgreSQL database

Cevap

Purchase a Compute Savings Plan to cover the AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the PostgreSQL database.

Purchasing a Compute Savings Plan provides significant savings for AWS Fargate compute usage, which fits the predictable API traffic profile. Purchasing Amazon RDS Reserved Instances provides a discounted hourly rate for the database instance, which runs continuously 24/7. Together, these strategies minimize compute costs for both components without requiring application modifications.

Adım Adım Çözüm

Evaluate the compute options for the containerized API workload.

The AWS Fargate tasks run continuously with predictable resource needs. A Compute Savings Plan is selected as it directly covers Fargate usage and offers a significant discount.

Compute Savings Plans are flexible and apply automatically to Fargate, ECS, Lambda, and EC2 compute usage.

Evaluate the compute options for the database workload.

The PostgreSQL database runs continuously on Amazon RDS. Amazon RDS Reserved Instances are selected to reduce the hourly database instance cost.

Compute Savings Plans do not apply to Amazon RDS. RDS Reserved Instances must be purchased separately for RDS databases.

Compare against constraints and alternative purchasing models.

Alternative options such as migrating to AWS Lambda or DynamoDB are rejected because they either increase costs for 24/7 workloads or require major architectural modifications.

The scenario requires minimizing costs without modifying the application code or architecture.

Anahtar Kavram

Matching appropriate AWS purchasing models (Compute Savings Plans, RDS Reserved Instances) to specific compute and database workloads to maximize cost savings.

Soru 150Soru →

A financial services company runs a mission-critical web application on AWS. The application uses Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) and an Amazon Aurora MySQL database. The company requires a cross-region disaster recovery (DR) solution with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 2 minutes. The architecture must minimize ongoing idle compute costs. Which solution best meets these requirements?

Configure Amazon Aurora Global Database with the primary database cluster in the active Region and a secondary cluster in the recovery Region. Set up an Auto Scaling group in the recovery Region with the desired capacity set to zero, maintaining pre-configured launch templates and target groups. Create a cross-Region Amazon S3 replication pipeline for application state. Use Amazon Route 53 Application Recovery Controller (ARC) routing control to fail over by promoting the secondary Aurora cluster and scaling the Auto Scaling group to the required capacity.

Set up Amazon Aurora cross-Region Read Replicas from the active Region to the recovery Region. Configure an Application Load Balancer in the recovery Region pointing to EC2 instances in a scaled-down Warm Standby state. Rely on Amazon Route 53 Latency routing with health checks to automatically promote the cross-Region Read Replica to primary and route traffic to the recovery Region if the active Region becomes unhealthy.

Establish a Pilot Light disaster recovery environment in the recovery Region. Schedule Aurora database snapshots every 15 minutes and replicate them to the recovery Region. Deploy an Auto Scaling group scaled to zero in the recovery Region. During a failover event, restore the database from the latest replicated snapshot, scale up the EC2 instances, and update Route 53 failover records.

Configure a Backup and Restore strategy by exporting Aurora database backups every 2 minutes to Amazon S3, and use S3 cross-region replication to copy these files to the recovery Region where they are transitioned to Amazon S3 Glacier Flexible Retrieval. Set up an Auto Scaling group in the recovery Region. During failover, use Standard Retrieval to restore the database in the recovery Region.

Cevabı ve açıklamayı göster

Cevap: Configure Amazon Aurora Global Database with the primary database cluster in the active Region and a secondary cluster in the recovery Region. Set up an Auto Scaling group in the recovery Region with the desired capacity set to zero, maintaining pre-configured launch templates and target groups. Create a cross-Region Amazon S3 replication pipeline for application state. Use Amazon Route 53 Application Recovery Controller (ARC) routing control to fail over by promoting the secondary Aurora cluster and scaling the Auto Scaling group to the required capacity.

Cevap

The configuration using Amazon Aurora Global Database satisfies the 2-minute RPO due to its typical sub-second replication latency. Keeping the recovery Region's EC2 Auto Scaling group capacity at zero minimizes compute costs when idle, conforming to the Pilot Light architecture pattern. Since launch templates and target groups are pre-configured, the EC2 instances can scale up quickly, and promoting the Aurora secondary cluster takes less than a minute, allowing the entire recovery workflow to complete well within the 15-minute RTO. Route 53 ARC routing controls provide the mechanism to safely orchestrate this cross-region traffic shift.

Adım Adım Çözüm

Evaluate the RPO requirement of 2 minutes.

Identify that backup-and-restore or database snapshot strategies with intervals greater than 2 minutes are insufficient. Aurora Global Database replication is asynchronous and typically completes in under a second, meeting the RPO.

Choosing the correct replication technology is necessary to ensure data loss is kept within the RPO window.

Evaluate the RTO requirement of 15 minutes and the cost constraint.

Determine that compute resources in the recovery Region should be kept shut down or scaled to zero when idle (Pilot Light) to minimize cost, but must be launchable within minutes to meet the RTO.

Maintaining fully running EC2 instances (Warm Standby or Active-Active) would violate the cost optimization goal, while recreating infrastructure from scratch would violate the RTO.

Analyze database promotion and routing mechanism during failover.

Identify that promoting an Aurora Global Database secondary cluster is a fast, coordinated action (typically under a minute). Route 53 Application Recovery Controller (ARC) provides the necessary health checks and routing controls to coordinate the shift of application traffic safely.

Automated cross-region database promotion does not happen natively via Route 53 DNS policies; it requires orchestration or manual trigger, which Route 53 ARC routing controls support.

Anahtar Kavram

Selecting the appropriate disaster recovery strategy (Pilot Light vs Warm Standby vs Backup & Restore) and technology stack (Aurora Global Database, Route 53 ARC) to meet strict RTO/RPO requirements while optimizing costs.

Tahmini Süre:3m 0s

Soru 151Soru →

A financial services company hosts a report generation API on Amazon EC2 instances. The instances are managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The report generation requests are computationally intensive and can take up to $180$ seconds to complete. To allow fast instance replacement during application deployments, a developer set the ALB target group's deregistration delay to $30$ seconds. However, during scale-in events, users report receiving HTTP 502 (Bad Gateway) errors for reports that were in progress.

Which modification should a solutions architect recommend to resolve these errors?

Add a rule to the private subnet's Network ACL to allow inbound traffic on ephemeral ports (

1024

65535

) from the ALB, and reduce the ASG cooldown period to

30

seconds.

Increase the deregistration delay of the ALB target group to at least

180

seconds.

Configure the ALB target group health check to use a dedicated management port instead of the traffic port, and reduce the health check interval.

Implement an Amazon Route 53 latency-based routing policy to redirect active user sessions to a secondary region during scale-in events.

Cevabı ve açıklamayı göster

Cevap: Increase the deregistration delay of the ALB target group to at least $180$ seconds.

Cevap

Increase the deregistration delay of the ALB target group to at least

180

seconds.

Increasing the deregistration delay (also known as connection draining) of the target group to match or exceed the maximum request processing time (

180

seconds) ensures that the Application Load Balancer allows in-flight requests to complete before the Auto Scaling group terminates the instance.

Adım Adım Çözüm

Analyze the cause of the HTTP 502 errors during scale-in events.

The errors occur because the target group's deregistration delay of

30

seconds is shorter than the maximum request completion time of

180

seconds, leading to premature connection termination.

Understanding the connection lifecycle is key to resolving premature terminations.

Determine the necessary configuration adjustment for the load balancer.

The deregistration delay must be increased to a value equal to or greater than

180

seconds.

This configuration tells the load balancer to wait for active requests to finish before the instances are fully terminated.

Verify if other configuration elements like Network ACLs, health checks, or DNS routing can resolve this.

None of the other options address connection draining; they either misapply network access controls, load balancer health checks, or DNS routing policies.

Deregistration delay is the specific ELB feature designed to manage connection lifecycle during scaling.

Anahtar Kavram

Deregistration delay (connection draining) ensures that a load balancer stops routing new requests to targets that are deregistering, but allows existing in-flight connections to complete before the target is fully terminated.

Soru 152Soru →

A retail corporation recently migrated its inventory management system to AWS. The security team must implement a solution to continuously monitor for configuration compliance drifts, such as unencrypted Amazon Elastic Block Store (Amazon EBS) volumes or public Amazon S3 buckets, and receive immediate alerts when unauthorized IAM policy changes occur. Which combination of AWS services should the solutions architect recommend to meet these monitoring and alerting requirements? (Select TWO.)

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

Enable AWS Config to continuously monitor and record resource configuration changes, evaluating compliance against AWS managed rules.

Configure Amazon EventBridge to detect IAM configuration API events logged in AWS CloudTrail and trigger Amazon Simple Notification Service (Amazon SNS) notifications.

Deploy AWS Shield Advanced to continuously scan and block unauthorized IAM policy updates before they are committed.

Configure a stateless Network ACL rule at the subnet level to intercept, log, and prevent unauthorized IAM API calls.

Use AWS WAF to inspect internal IAM API requests and automatically block any unauthorized configuration changes.

Cevabı ve açıklamayı göster

Cevap: Enable AWS Config to continuously monitor and record resource configuration changes, evaluating compliance against AWS managed rules.; Configure Amazon EventBridge to detect IAM configuration API events logged in AWS CloudTrail and trigger Amazon Simple Notification Service (Amazon SNS) notifications.

Cevap

The correct solution involves enabling AWS Config to monitor and evaluate resource configuration compliance drifts, and configuring Amazon EventBridge to detect IAM configuration API events in AWS CloudTrail to trigger notifications via Amazon Simple Notification Service (Amazon SNS).

AWS Config is the native service designed to track and record AWS resource configurations, evaluating them against rules such as verifying that S3 buckets are private and EBS volumes are encrypted. To alert on security alterations like IAM changes in real time, AWS CloudTrail audits the API logs, and Amazon EventBridge can be configured with a rule matching those API activities to trigger an Amazon SNS topic for instant alert notifications.

Adım Adım Çözüm

Identify the tool suitable for continuous resource configuration compliance monitoring.

AWS Config is identified as the service that records configurations and evaluates them against custom or managed rules.

AWS Config maintains a configuration history and evaluates resource compliance status (such as identifying public S3 buckets or unencrypted EBS volumes).

Determine the service integration necessary to capture IAM API activity and generate real-time alerts.

AWS CloudTrail logs the IAM API actions, Amazon EventBridge matches the specific pattern of those events, and Amazon SNS sends notifications.

This integration enables near real-time event-driven alerting for critical security configuration changes like IAM mutations.

Anahtar Kavram

Continuous security configuration auditing and near real-time compliance monitoring on AWS.

Tahmini Süre:2m 0s

Soru 153Soru →

An online multiplayer gaming platform hosts real-time match sessions on a fleet of Amazon EC2 instances. The game server software runs on custom TCP port 8200, and a Network Load Balancer (NLB) distributes player connections across the fleet. To maintain game state consistency, the instances require the highest possible throughput and lowest packet latency for their inter-node synchronization. During testing, the game instances are marked as unhealthy by the NLB, preventing player traffic from reaching the active sessions. Which configuration strategy resolves the health check failure while ensuring optimal node-to-node network performance?

Utilize a spread placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the custom port 8200.

Utilize a cluster placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the default port.

Utilize a partition placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the default port.

Utilize a cluster placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the custom port 8200.

Cevabı ve açıklamayı göster

Cevap: Utilize a cluster placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the custom port 8200.

Cevap

Utilize a cluster placement group for the EC2 instances, and configure the Network Load Balancer's target group health check to use the custom port 8200.

The correct strategy is to utilize a cluster placement group for the EC2 instances and configure the Network Load Balancer's target group health check to use the custom port 8200. A cluster placement group groups instances closely inside a single Availability Zone to enable low-latency, 10 Gbps or higher node-to-node throughput. Additionally, because the game server process is bound to the custom port 8200, the target group's health checks must be explicitly pointed to port 8200 so the load balancer can verify application health rather than failing on a default port.

Adım Adım Çözüm

Select the correct EC2 placement strategy for high-performance, low-latency inter-node communication.

Identify that a cluster placement group is the required strategy because it places instances physically close together within a single Availability Zone, enabling low-latency, high-throughput network performance.

Other placement groups like spread or partition are designed for fault tolerance and high availability across different hardware racks, which introduces network latency.

Identify the cause of the load balancer marking instances as unhealthy.

Determine that the Network Load Balancer is performing health checks on a default port, whereas the game server application is listening on custom TCP port 8200.

When the load balancer queries a port where no service is listening, the connection fails, causing the targets to be marked as unhealthy.

Reconfigure the target group health check settings.

Set the health check port in the target group configuration to custom port 8200.

This alignment allows the Network Load Balancer to establish successful TCP handshakes with the actual game server process, resolving the false unhealthy status.

Anahtar Kavram

Selecting the optimal placement group for latency-sensitive workloads and aligning load balancer health checks with custom application ports.

Tahmini Süre:1m 30s

Soru 154Soru →

A petroleum exploration firm is deploying a distributed reservoir simulation application on Amazon EC2. The application relies on Message Passing Interface (MPI) for tightly coupled, high-throughput node-to-node communication. To handle input parameter submissions, the EC2 instances are registered to a Target Group behind an Application Load Balancer (ALB). The simulation workload runs on port 9095, while a lightweight administrative dashboard on the instances listens on port 8088 to process health checks. Currently, the ALB is marking all registered EC2 instances as unhealthy. Which combination of actions will resolve the health check failures and optimize compute performance for the simulation workload?

Launch the EC2 instances in a cluster placement group. Set the Target Group health check port to 8088.

Launch the EC2 instances in a spread placement group. Set the Target Group health check port to 8088.

Launch the EC2 instances in a cluster placement group. Leave the Target Group health check port configured to traffic-port.

Launch the EC2 instances in a partition placement group. Leave the Target Group health check port configured to traffic-port.

Cevabı ve açıklamayı göster

Cevap: Launch the EC2 instances in a cluster placement group. Set the Target Group health check port to 8088.

Cevap

Launch the EC2 instances in a cluster placement group. Set the Target Group health check port to 8088.

The correct option correctly suggests launching the EC2 instances in a cluster placement group to achieve the low-latency network performance required by MPI-based simulation workloads, and changing the health check port to 8088 to match the port of the administrative dashboard that handles health checks.

Adım Adım Çözüm

Analyze the network latency and throughput requirements of the MPI application.

Identify that a cluster placement group is necessary to locate the EC2 instances close together on the same underlying hardware to achieve low-latency, high-throughput communication.

MPI applications require tightly coupled node-to-node communication that only cluster placement groups can deliver on AWS.

Identify the cause of the load balancer marking the instances as unhealthy.

Determine that the health check requests are being sent to the default traffic-port (port 9095), where the simulation runs instead of the administrative dashboard (port 8088).

The load balancer health checks must be explicitly configured to target the port where the health check service is active.

Configure the target group settings.

Change the health check port configuration from 'traffic-port' to port 8088.

This redirects health check traffic to the administrative dashboard, allowing the ALB to receive successful health check responses and mark the instances as healthy.

Anahtar Kavram

Selecting appropriate EC2 placement groups for high-performance compute workloads and configuring custom health check ports on target groups.

Tahmini Süre:2m 0s

Soru 155Soru →

A company runs a financial ledger application that processes transaction records in batches. The transaction batches are uploaded at unpredictable intervals throughout the day. To prevent account balance discrepancies, all transactions within a batch must be processed in the exact order they were received. Each processing job takes between 20 to 30 minutes to complete. The company wants to minimize costs by ensuring that compute resources are only active and incurring charges when transactions are actually being processed. Which architecture meets these requirements in the most cost-effective manner?

Publish transactions to an Amazon SQS FIFO queue. Configure an Amazon ECS service running on AWS Fargate with target tracking scaling based on queue depth to run the processing containers, scaling the service down to zero tasks when the queue is empty.

Publish transactions to a standard Amazon SQS queue. Configure an Amazon ECS service running on AWS Fargate with target tracking scaling based on queue depth to run the processing containers, scaling the service down to zero tasks when the queue is empty.

Publish transactions to an Amazon SQS FIFO queue. Configure an AWS Lambda function triggered by the queue to process the transaction batches, taking advantage of Lambda's pay-per-invocation pricing.

Publish transactions to an Amazon SQS FIFO queue. Configure an Amazon ECS service running on AWS Fargate to process the messages, scaling down to zero when empty. Store transaction metadata in an Amazon DynamoDB table configured with provisioned capacity mode.

Cevabı ve açıklamayı göster

Cevap: Publish transactions to an Amazon SQS FIFO queue. Configure an Amazon ECS service running on AWS Fargate with target tracking scaling based on queue depth to run the processing containers, scaling the service down to zero tasks when the queue is empty.

Cevap

The correct answer combines Amazon SQS FIFO queues to guarantee strict order processing with Amazon ECS on AWS Fargate. Fargate is appropriate because it has no 15-minute timeout restriction like AWS Lambda, allowing the 20 to 30-minute jobs to complete successfully. Furthermore, by configuring target tracking scaling based on queue depth, the ECS service can scale the number of tasks down to zero when the queue is empty, eliminating idle compute costs.

Adım Adım Çözüm

Analyze the execution runtime requirement for the processing job.

Since each processing batch takes 20 to 30 minutes, it exceeds the 15-minute maximum timeout of AWS Lambda. A containerized solution using Amazon ECS on AWS Fargate is selected instead.

To ensure that compute resources can execute continuously for more than 15 minutes without timing out.

Analyze the data sequencing and ordering constraints.

To guarantee strict first-in, first-out ordering of transaction processing and prevent balance discrepancies, Amazon SQS FIFO queues are chosen over standard SQS queues.

Standard SQS queues do not guarantee strict message ordering.

Evaluate the scaling and pricing optimization strategies.

An ECS service running on Fargate is configured to scale dynamically based on the queue depth of the SQS FIFO queue, scaling down to zero tasks when no messages are present.

Scaling to zero tasks ensures that the company pays nothing for compute when there is no workload active.

Anahtar Kavram

Combining SQS FIFO queues for strict ordering with Amazon ECS on AWS Fargate auto-scaled to zero for cost-effective long-running batch execution.

Tahmini Süre:1m 30s

Soru 156Soru →

A manufacturing company is deploying a smart assembly line where automated robotic arms perform high-precision tasks. Each arm reports telemetry status messages (such as 'calibrating', 'started', and 'completed') that must be processed in the exact order they are generated for each individual arm to maintain a digital twin representation in a database. If messages are processed out of order, the digital twin state becomes corrupt. During peak production hours, the volume of telemetry messages spikes significantly. The downstream backend consists of a fleet of worker processes running in an Auto Scaling group. Which combination of steps should a solutions architect recommend to decouple the ingestion tier from the backend workers while ensuring strict ordering per assembly arm and preventing message loss? (Select TWO.)

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

Create an Amazon SQS FIFO queue and publish the telemetry events to it, using the assembly arm ID as the Message Group ID.

Configure the Auto Scaling group workers to poll the Amazon SQS FIFO queue and delete messages after they are successfully processed.

Create a standard Amazon SQS queue and publish the telemetry events using the assembly arm ID as the Message Group ID.

Create an Amazon SQS FIFO queue and publish the telemetry events using the assembly arm ID as the Message Deduplication ID.

Configure the Auto Scaling group workers to retrieve messages from a standard Amazon SQS queue, utilizing a client-side sorting library to order messages chronologically.

Cevabı ve açıklamayı göster

Cevap: Create an Amazon SQS FIFO queue and publish the telemetry events to it, using the assembly arm ID as the Message Group ID.; Configure the Auto Scaling group workers to poll the Amazon SQS FIFO queue and delete messages after they are successfully processed.

Cevap

To satisfy the requirements, the solutions architect should create an Amazon SQS FIFO queue, publishing telemetry events with the assembly arm ID as the Message Group ID, and configure the Auto Scaling group workers to poll the SQS FIFO queue and delete messages upon successful processing.

To decouple the ingestion tier from backend workers while maintaining message order per assembly arm, a solutions architect should use an Amazon SQS FIFO queue. By using the unique assembly arm ID as the Message Group ID, SQS FIFO ensures that all messages for that specific arm are processed sequentially in the order they were received. The workers in the Auto Scaling group should poll the queue, process the messages, and delete them upon completion. When a worker is processing a message from a specific Message Group, SQS FIFO blocks other workers from receiving messages from the same group, preventing out-of-order execution.

Adım Adım Çözüm

Select a message queuing service that guarantees ordering and grouping.

Amazon SQS FIFO queue is chosen because standard queues do not guarantee FIFO ordering or support message grouping.

Maintaining digital twin states requires strict sequential processing per assembly arm.

Configure message routing parameters to segment messages by source.

Use the assembly arm ID as the Message Group ID.

This guarantees that all messages for a specific arm are processed in order, while allowing messages from different arms to be processed concurrently across multiple backend workers.

Configure the consumer worker processing logic.

Workers poll the FIFO queue and delete the message after successful processing.

Deleting the message releases the next message in the same Message Group for processing, preventing concurrency conflicts and ensuring reliable processing.

Anahtar Kavram

Amazon SQS FIFO queues use Message Group IDs to group messages that must be processed in order. SQS FIFO guarantees first-in, first-out delivery within each message group while allowing parallel processing across different groups.

Soru 157Soru →

An online ticketing platform experiences extreme spikes in database writes during ticket release events for major concerts, which occur once or twice a month. For the rest of the month, database traffic is negligible. The platform uses a key-value data structure to temporarily store seat reservation sessions for up to $15\text{ minutes}$ . During a ticket release, write throughput spikes to $6,000\text{ write operations per second}$ , while the off-peak average is less than $10\text{ writes per second}$ . The database must automatically handle these traffic spikes and tolerate Availability Zone failures. Which database configuration is the most cost-effective for this workload?

Configure an Amazon DynamoDB table using Provisioned capacity mode with the write capacity permanently set to

6,000

Write Capacity Units (WCUs).

Configure an Amazon DynamoDB table using On-Demand capacity mode.

Configure an Amazon DynamoDB table using Provisioned capacity mode, and purchase a Compute Savings Plan to lower the hourly cost of the provisioned capacity.

Deploy an Amazon RDS for PostgreSQL DB instance with a Read Replica in a separate Availability Zone, and configure the application to failover automatically to the replica.

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon DynamoDB table using On-Demand capacity mode.

Cevap

Configure an Amazon DynamoDB table using On-Demand capacity mode.

The correct option is to configure an Amazon DynamoDB table using On-Demand capacity mode. This mode is designed for workloads with unpredictable or highly spiky traffic, as it scales instantly to accommodate requests up to the table's partition limits. Since charges are based strictly on the actual read and write request units consumed, it eliminates the cost of provisioning idle resources during off-peak times, making it the most cost-effective choice for this pattern.

Adım Adım Çözüm

Analyze the workload characteristics and requirements.

The workload uses a key-value data structure, requires high write throughput up to

6,000\text{ writes per second}

during rare spikes, averages less than

10\text{ writes per second}

off-peak, and needs high availability across Availability Zones.

Understanding the access patterns and scaling needs is the first step in cost-optimized capacity planning.

Select the appropriate database engine and scaling mode.

Amazon DynamoDB is a managed NoSQL database that offers native key-value storage and Multi-AZ availability. On-Demand capacity mode scales instantly to handle spikes and charges only for actual read/write requests, making it cost-optimal for highly spiky, low-average workloads.

Comparing pricing models of on-demand versus provisioned capacity helps determine the lowest-cost configuration.

Evaluate and eliminate less cost-efficient or invalid alternatives.

Provisioned capacity causes expensive idle resource waste. Compute Savings Plans cannot be applied to DynamoDB. Amazon RDS with a Read Replica does not support automatic failover and is less cost-effective for simple key-value session storage.

Ensuring the selected solution is valid and offers the lowest operational and resource cost.

Anahtar Kavram

Selecting the most cost-effective database capacity mode (On-Demand vs. Provisioned) based on workload predictability and spikiness.

Soru 158Soru →

A sports media website uses an Amazon DynamoDB table to store live commentary updates for popular matches. During major tournaments, write volume spikes to $15,000$ writes per second. The application requires sub-millisecond read latency for the most active match commentary threads. Currently, the database partition key is a combination of the tournament name and a sequential timestamp (TournamentName_Timestamp). During peak events, the application experiences write throttling and elevated latency. Which configuration should a solutions architect implement to resolve the performance bottlenecks and meet the latency requirements?

Redesign the partition key using a high-cardinality attribute like a hashed combination of MatchID and CommentaryID, and deploy Amazon DynamoDB Accelerator (DAX) to serve reads.

Keep the existing TournamentName_Timestamp partition key to maintain chronological ordering, and deploy DynamoDB Accelerator (DAX) to handle the write cache.

Migrate the database layer to Amazon RDS for PostgreSQL, utilizing a single primary instance with multiple Read Replicas configured as the primary failover targets to achieve high performance and immediate disaster recovery.

Maintain the current DynamoDB table structure but configure the table with Provisioned Capacity Mode using static read and write capacity settings set to the historical average to prevent throttling.

Cevabı ve açıklamayı göster

Cevap: Redesign the partition key using a high-cardinality attribute like a hashed combination of MatchID and CommentaryID, and deploy Amazon DynamoDB Accelerator (DAX) to serve reads.

Cevap

Redesign the partition key using a high-cardinality attribute like a hashed combination of MatchID and CommentaryID, and deploy Amazon DynamoDB Accelerator (DAX) to serve reads.

Redesigning the partition key to a high-cardinality key like a hashed combination of MatchID and CommentaryID ensures that writes are distributed evenly across DynamoDB's physical partitions, preventing write throttling. Deploying DynamoDB Accelerator (DAX) fulfills the sub-millisecond read latency requirement by providing an in-memory cache.

Adım Adım Çözüm

Analyze the workload requirements and current bottlenecks.

The application requires high write throughput (

15,000

writes/sec) and sub-millisecond read latency. The current key (TournamentName_Timestamp) causes partition throttling due to sequential writes hitting the same partition.

Identifying the root cause of the performance bottleneck is necessary to choose the correct architectural fix.

Address the write bottleneck by redesigning the primary key structure.

By using a high-cardinality partition key (hashed combination of MatchID and CommentaryID), writes are distributed evenly across multiple physical DynamoDB partitions.

Distributing the partition key values prevents hot partitions and allows DynamoDB to scale throughput horizontally.

Address the read latency requirement.

Deploying Amazon DynamoDB Accelerator (DAX) caches reads, reducing response times from single-digit milliseconds to microseconds.

DAX is a fully managed, highly available, in-memory cache for DynamoDB that delivers microsecond response times.

Anahtar Kavram

Avoiding hot partitions in DynamoDB by using high-cardinality partition keys, and using DAX for microsecond read latency.

Soru 159Soru →

A company is deploying a latency-sensitive gRPC microservice on a fleet of Amazon EC2 instances managed by an Auto Scaling group (ASG). The gRPC service communicates over TCP port 50051. A Network Load Balancer (NLB) distributes client traffic to these instances. The solutions architect needs to ensure that the NLB only routes traffic to healthy instances and that the ASG automatically replaces any instances where the microservice application has crashed. Which two configurations should the solutions architect implement to meet these requirements? (Select TWO.)

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

Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks.

Configure the target group health check to use TCP protocol on port 50051.

Configure the target group health check to use HTTP protocol on port 80 to minimize CPU usage on the EC2 instances.

Configure a subnet Network ACL rule allowing inbound TCP traffic on port 50051, relying on stateful security groups to permit the return outbound health check response traffic.

Configure Amazon Route 53 with a Latency routing policy pointing to the NLB to automatically route client traffic away from individual unhealthy instances.

Cevabı ve açıklamayı göster

Cevap: Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks.; Configure the target group health check to use TCP protocol on port 50051.

Cevap

Configure the Auto Scaling group to use ELB health checks instead of the default EC2 health checks, and configure the target group health check to use TCP protocol on port 50051.

Configuring the load balancer target group to monitor port 50051 via TCP ensures that the NLB only forwards traffic to instances where the gRPC service is active. Furthermore, changing the Auto Scaling group health check source to ELB ensures that when an instance fails the target group health checks, the ASG will automatically terminate and replace the failed instance, ensuring continuous application availability.

Adım Adım Çözüm

Analyze the health check requirements for the gRPC application.

Identify that health checks must target the active application port (50051) using TCP protocol because the application runs on port 50051 and does not listen on port 80.

This ensures the load balancer accurately identifies whether the service itself is running.

Determine the mechanism to automatically replace failed instances.

Enable ELB health checks on the Auto Scaling group.

By default, the ASG only uses EC2 status checks. Enabling ELB health checks ensures the ASG replaces instances that fail target group health checks.

Anahtar Kavram

Auto Scaling Group and Elastic Load Balancing health check synchronization for custom service ports

Soru 160Soru →

A retail company is launching a new promotions portal that experiences sudden bursts of traffic. The database tier must support two distinct workloads: a transactional relational workload to process orders, and a highly concurrent, low-latency search workload for the active promotions catalog. The solutions architect needs to design a high-performing database architecture that can scale dynamically to handle these demands.

Which combination of database configurations should the solutions architect choose? (Select two.)

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

Amazon Aurora MySQL database cluster with Aurora Auto Scaling for read replicas to handle transactional order processing

Amazon ElastiCache for Redis cluster to cache promotional catalog queries

Amazon DynamoDB table with a partition key of monotonically increasing transaction timestamps to store order details

Amazon RDS for MySQL instance using a read replica in a separate Availability Zone as the primary automatic failover mechanism for transaction writes

Amazon DynamoDB table configured in Provisioned Capacity Mode with fixed capacity units to handle the highly unpredictable spiky transactional traffic

Cevabı ve açıklamayı göster

Cevap: Amazon Aurora MySQL database cluster with Aurora Auto Scaling for read replicas to handle transactional order processing; Amazon ElastiCache for Redis cluster to cache promotional catalog queries

Cevap

The correct configurations are using an Amazon Aurora MySQL database cluster with Aurora Auto Scaling for read replicas to handle transactional order processing, and deploying an Amazon ElastiCache for Redis cluster to cache promotional catalog queries.

The relational order processing requires a high-performance transactional database, which is served by Amazon Aurora MySQL. Aurora supports Auto Scaling read replicas to handle variable read capacity during traffic spikes. The search catalog requires highly concurrent, low-latency retrieval, which is served by Amazon ElastiCache for Redis, shielding the database from high read volume.

Adım Adım Çözüm

Analyze the workload requirements for the relational transaction processing system.

The system requires a database that supports transactional integrity (ACID compliance) and is capable of scaling read capacity dynamically during sudden bursts of traffic.

Amazon Aurora MySQL matches these requirements by offering a high-performance relational database with support for Auto Scaling read replicas.

Analyze the workload requirements for the promotions catalog searches.

Catalog searches require sub-millisecond, highly concurrent read capabilities to handle traffic spikes without placing excessive load on the main relational database.

Amazon ElastiCache for Redis provides a high-performing in-memory caching layer that handles concurrent read traffic with microsecond latencies.

Anahtar Kavram

High-performing database architectures leverage specialized services for different read/write patterns, such as using Aurora MySQL for relational transactional operations and Amazon ElastiCache to cache high-frequency, low-latency read requests.

Tahmini Süre:2m 0s

ÖncekiSayfa 8 / 74Sonraki

Tüm alıştırma soruları

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Cevap

Adım Adım Çözüm

Anahtar Kavram