Tüm alıştırma soruları

1964 soru

Soru 321Soru

A company is designing a new integration between two workloads deployed in separate AWS accounts. An application running on Amazon EC2 instances in Account A (111111111111) needs to retrieve and process encrypted messages from an Amazon Simple Queue Service (Amazon SQS) queue located in Account B (222222222222). The security requirements state that the SQS queue must be encrypted at rest, and access must follow the principle of least privilege. The application's IAM role in Account A has already been configured with the necessary SQS and KMS permissions.

Which two configuration steps must be performed in Account B to allow the cross-account application to successfully receive and decrypt messages from the queue? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable server-side encryption on the SQS queue using a Customer Managed Key (CMK), and configure the CMK's key policy to allow the application's IAM role in Account A to perform the kms:Decrypt action.; Configure the SQS queue policy to allow the application's IAM role in Account A to perform the sqs:ReceiveMessage and sqs:DeleteMessage actions.

Cevap

To configure secure cross-account access to the encrypted SQS queue, you must use a Customer Managed Key (CMK) and grant kms:Decrypt permissions to the application role in the key policy. You must also configure the SQS queue policy to grant sqs:ReceiveMessage and sqs:DeleteMessage permissions to the application role.
To allow cross-account access to an encrypted SQS queue, both the SQS queue policy and the KMS key policy in Account B must be updated to grant permissions to the IAM role in Account A. Additionally, because AWS-managed keys (like aws/sqs) cannot have their policies modified and cannot be shared across accounts, a Customer Managed Key must be used for SQS encryption. Therefore, the solutions architect must configure SQS with a Customer Managed Key and update its key policy to allow decryption, and also update the SQS queue policy to grant receive and delete permissions to the external IAM role.

Adım Adım Çözüm

1
Ensure the SQS queue is encrypted with a Customer Managed Key (CMK) rather than an AWS-managed key.
Allows key policy modifications needed for cross-account sharing.
AWS-managed KMS keys do not support policy modifications and cannot be used across accounts.
2
Modify the key policy of the Customer Managed Key (CMK) in Account B.
Grants the application's IAM role in Account A kms:Decrypt permissions.
The calling application must be able to decrypt the payload encrypted by the key.
3
Modify the SQS queue policy in Account B.
Grants the application's IAM role in Account A sqs:ReceiveMessage and sqs:DeleteMessage permissions.
Resource-based SQS queue policies must authorize the cross-account principal to access the queue.

Anahtar Kavram

Cross-account access to AWS KMS-encrypted Amazon SQS queues requires updating both SQS resource policies and Customer Managed Key (CMK) policies, as AWS-managed keys cannot be shared across accounts.
Soru 322Soru

An enterprise is designing a hybrid network connectivity solution to connect its 25 spoke VPCs in a single AWS Region with its on-premises corporate network. The design requires a highly available, transit hub architecture where spoke VPCs can communicate with each other and with the on-premises network. The primary hybrid connection must use an AWS Direct Connect (DX) connection, and a Site-to-Site VPN connection must serve as a backup path. The system must automatically fail over to the backup VPN path if the DX connection becomes unavailable, without adding unnecessary routing tables or manual intervention.

Which TWO actions should the solutions architect take to implement this architecture?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway, attach all spoke VPCs to it, and associate the Transit Gateway with a Direct Connect Gateway using a transit virtual interface (transit VIF) on the DX connection.; Propagate the on-premises network routes into the Transit Gateway route table from both the Direct Connect Gateway and the Site-to-Site VPN attachments, allowing the Transit Gateway to prefer the Direct Connect path.

Cevap

The solutions architect should deploy an AWS Transit Gateway, attach all spoke VPCs to it, and associate the Transit Gateway with a Direct Connect Gateway using a transit virtual interface. Additionally, they should propagate the on-premises network routes into the Transit Gateway route table from both the Direct Connect Gateway and the Site-to-Site VPN attachments, relying on the Transit Gateway's default route selection logic to prefer the Direct Connect path.
Deploying a Transit Gateway and associating it with a Direct Connect Gateway using a transit VIF establishes a scalable, centralized hub for the spoke VPCs. When the same on-premises prefixes are propagated via BGP from both the Direct Connect Gateway and Site-to-Site VPN attachments, Transit Gateway automatically prefers the Direct Connect Gateway path due to its default route evaluation order (Direct Connect Gateway prefix is preferred over VPN prefix for matching paths). This achieves automatic failover to the VPN if the Direct Connect link fails.

Adım Adım Çözüm

1
Select a centralized transit hub architecture.
Identify AWS Transit Gateway as the standard hub-and-spoke solution to interconnect multiple VPCs and connect them to on-premises networks.
Transit Gateway simplifies configuration by consolidating connections and route tables compared to individual Virtual Private Gateways.
2
Establish the primary path via AWS Direct Connect.
Associate the Transit Gateway with a Direct Connect Gateway using a transit virtual interface (transit VIF).
A transit VIF is required to carry traffic between a Direct Connect Gateway and a Transit Gateway.
3
Establish the backup path and configure routing.
Attach a Site-to-Site VPN to the Transit Gateway and configure BGP propagation for both attachments.
By propagating the same routes via both paths, Transit Gateway uses its default evaluation logic to prioritize Direct Connect over VPN, enabling automated failover.

Anahtar Kavram

AWS Transit Gateway routing evaluation order and hybrid connectivity failover design.
Soru 323Soru

A regional public transit authority is launching a mobile ticketing application to support commuters during a city-wide cultural festival. The authority expects an immediate traffic burst where active user sessions will surge from 500500 to over 80,00080,000 within a 55-minute window. The backend application runs on Amazon EC2 instances inside an Auto Scaling group behind an Application Load Balancer (ALB), with transactional data stored in a Multi-AZ Amazon RDS for PostgreSQL database. High-frequency queries retrieve transit schedule data which changes daily. Which architecture optimization strategy should a Solutions Architect recommend to handle this sudden traffic spike while maintaining low-latency read operations?

Cevabı ve açıklamayı göster

Cevap: Configure Amazon ElastiCache for Redis to cache the daily transit schedule data, and submit a support ticket to AWS to pre-warm the Application Load Balancer before the festival begins.

Cevap

Configure Amazon ElastiCache for Redis to cache the daily transit schedule data, and submit a support ticket to AWS to pre-warm the Application Load Balancer before the festival begins.
The correct answer combines pre-warming the Application Load Balancer to prepare for the massive, rapid surge in connections, and caching the static transit schedules in ElastiCache for Redis. This strategy ensures the load balancer has sufficient capacity from the start and offloads read queries from the primary transactional database, maintaining low-latency response times.

Adım Adım Çözüm

1
Analyze the scaling characteristics of the entry point (Application Load Balancer) during an extreme, sudden surge of traffic.
Identify that the ALB needs to scale from a baseline supporting 500 sessions to 80,000 sessions within 5 minutes. Since the default scaling rate of ALBs cannot accommodate this extreme rate of increase, a pre-warming request must be submitted to AWS Support.
This prevents HTTP 503 errors and connection timeouts at the load balancer layer during the initial minutes of the festival spike.
2
Evaluate options for offloading read-heavy, daily changing transit schedule queries from the transactional database.
Determine that caching the schedules using Amazon ElastiCache for Redis is the most performant and low-latency mechanism to handle the high-frequency queries.
This offloads read traffic from the RDS database, protecting the primary database instance's CPU and memory resources for write-heavy ticketing transactions.
3
Verify database replication and high availability constraints for read traffic.
Confirm that RDS PostgreSQL Multi-AZ standby instances cannot be read from directly, and rule out any options attempting to route queries to the standby.
Only Read Replicas (not the Multi-AZ standby instance) support read traffic in RDS PostgreSQL.

Anahtar Kavram

Caching static read data with ElastiCache for Redis and pre-warming Application Load Balancers for immediate, extreme traffic spikes.
Tahmini Süre:1m 30s
Soru 324Soru

An application hosted on Amazon EC2 instances uses General Purpose SSD (gp2) EBS volumes. During a daily batch reporting process, write operations experience significant latency. CloudWatch metrics indicate that the volumes are consistently hitting their baseline IOPS limit and exhausting their burst balance. Which of the following is the most cost-effective action to resolve the storage performance bottleneck with the least administrative effort?

Cevabı ve açıklamayı göster

Cevap: Modify the EBS volumes from gp2 to gp3 and provision the required IOPS and throughput independently of the volume size.

Cevap

Modify the EBS volumes from gp2 to gp3 and provision the required IOPS and throughput independently of the volume size.
Transitioning EBS volumes from gp2 to gp3 is the most cost-effective and low-effort way to solve this bottleneck. In gp2, baseline IOPS are tied to the volume size (3 IOPS per GB3 \text{ IOPS per GB} up to a maximum of 16,000 IOPS16,000 \text{ IOPS}), whereas gp3 volumes offer a constant baseline of 3,000 IOPS3,000 \text{ IOPS} and 125 MB/s125 \text{ MB/s} throughput for free and allow scaling performance parameters independently without increasing the underlying storage volume size.

Adım Adım Çözüm

1
Analyze the metrics and identify the storage bottleneck.
The application's gp2 volumes are hitting their baseline IOPS limit and depleting their burst credit pool.
gp2 volume performance scales linearly with capacity (3 IOPS per GB3 \text{ IOPS per GB}), meaning small volumes have low baseline IOPS and rely on burst credits.
2
Evaluate the storage optimization alternatives.
gp3 volumes allow upgrading baseline IOPS and throughput without increasing the volume size, unlike gp2 which requires increasing volume size to get higher baseline IOPS.
This provides a highly cost-effective and low-effort way to tune performance directly on the volume.

Anahtar Kavram

EBS storage performance optimization by transitioning from gp2 to gp3 to provision performance parameters independently of size.
Soru 325Soru

A financial services company hosts a high-frequency transactional application in the us-east-1 region. The application components are distributed across two VPCs: a transaction processing VPC and a ledger database VPC. The VPCs are currently interconnected using an AWS Transit Gateway. During high-volume trading hours, the network latency between the transaction processing application and the ledger database increases, leading to transaction timeouts. The database replication requires maximum throughput and the lowest possible latency. Which network architecture modification will optimize the network performance and reduce latency for this inter-VPC traffic?

Cevabı ve açıklamayı göster

Cevap: Establish a VPC Peering connection directly between the transaction processing VPC and the ledger database VPC, and update the route tables to route database traffic via the peering connection.

Cevap

Establish a direct VPC Peering connection between the two VPCs and route the database traffic through it.
VPC Peering establishes a direct relationship between two VPCs. Because it does not pass through an intermediate gateway or router instance (like AWS Transit Gateway), it offers lower latency and has no aggregate bandwidth limits, making it the most performant choice for high-throughput database replication.

Adım Adım Çözüm

1
Analyze the current connectivity model and performance bottlenecks.
The current model uses AWS Transit Gateway, which introduces an extra network hop (adding latency) and has bandwidth limits of 50 Gbps per Availability Zone attachment.
Understanding the limits of the current architecture explains why latency increases during peak traffic hours.
2
Compare alternative VPC-to-VPC connectivity options.
VPC Peering provides a direct connection path with no bandwidth limits and lower latency since it does not pass through an intermediate gateway device.
Direct VPC Peering is the optimal solution for low-latency, high-throughput requirements between two specific VPCs.
3
Update route tables to redirect the database traffic.
Traffic between the transaction processing VPC and the ledger database VPC is routed directly over the peering connection instead of going through the Transit Gateway.
Updating route tables ensures that only the relevant traffic is optimized while leaving other traffic on the Transit Gateway if desired.

Anahtar Kavram

VPC Peering provides lower latency and higher bandwidth compared to Transit Gateway because it routes traffic directly on the AWS network fabric without gateway processing overhead.
Soru 326Soru

An organization is running a legacy application on Amazon EC2 instances. The CloudWatch agent is configured to collect application logs from a static path of /var/log/app/app.log. The application rotates its logs hourly by renaming the active log file to /var/log/app/app.log.YYYY-MM-DD-HH and creating a new empty /var/log/app/app.log file. The operations team notices that the CloudWatch agent ceases log ingestion after the first log rotation occurs. Which configuration change will resolve this issue and ensure continuous log ingestion?

Cevabı ve açıklamayı göster

Cevap: Modify the CloudWatch agent configuration file to use a wildcard pattern (e.g., /var/log/app/app.log*) in the file_path setting to monitor both the active and rotated files.

Cevap

Modify the CloudWatch agent configuration file to use a wildcard pattern (e.g., /var/log/app/app.log*) in the file_path setting to monitor both the active and rotated files.
The correct answer is to modify the CloudWatch agent configuration to use a wildcard pattern. This allows the agent to monitor the directory for both the active and rotated files, ensuring that new files are detected and ingested without interruption.

Adım Adım Çözüm

1
Analyze the log rotation behavior of the application.
The application rotates logs by renaming the active file to a timestamped format and creating a new active log file.
This shows that the agent needs to track file creation and matches across name changes.
2
Evaluate the CloudWatch agent configuration settings.
A static path like /var/log/app/app.log stops collecting data once the file is rotated because the agent cannot track the renamed file or identify the new file.
Correcting the path to a wildcard pattern enables the agent to dynamically match and ingest rotated log files.

Anahtar Kavram

Configuring the Unified CloudWatch Agent log paths using wildcard patterns to support log rotation and avoid data loss.
Soru 327Soru

An enterprise is designing a deployment pipeline for a new microservice backend consisting of Amazon API Gateway and AWS Lambda. The deployment pipeline must release updates to the Lambda function according to the following requirements:

- The new version must receive exactly 10%10\% of the incoming API traffic immediately upon deployment.
- The remaining 90%90\% of the traffic must be routed to the new version after a 1010-minute stabilization period.
- If the new version experiences elevated error rates or response latencies during this 1010-minute window, the traffic must automatically and immediately revert to the previous stable version.

Which two actions should the solutions architect combine to design this deployment strategy? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure AWS CodeDeploy to use the CodeDeployDefault.LambdaCanary10Percent10Minutes deployment configuration.; Create Amazon CloudWatch alarms to monitor Lambda errors and API Gateway 5xx5xx errors, and configure the CodeDeploy deployment group to roll back the deployment when any alarm is triggered.

Cevap

Configure AWS CodeDeploy to use the canary deployment configuration along with Amazon CloudWatch alarms to monitor and automatically roll back the deployment.
To satisfy the deployment requirements with minimal operational overhead, the solutions architect should use AWS CodeDeploy to manage traffic shifting for the Lambda function. The Canary 10 percent 10 minutes configuration routes 10%10\% of the traffic to the new version immediately and shifts the remaining 90%90\% after a 1010-minute testing window. By configuring CloudWatch alarms for Lambda errors and API Gateway 5xx5xx errors and attaching them to the CodeDeploy deployment group, the deployment will automatically roll back if any issues are detected.

Adım Adım Çözüm

1
Select the appropriate traffic shifting pattern.
Identify that the Canary 10 percent 10 minutes pattern shifts 10%10\% of traffic immediately and the remaining 90%90\% after 1010 minutes.
This matches the requirement to test a small subset (10%10\%) for a fixed duration (1010 minutes) before promoting the version fully.
2
Establish the rollback mechanism.
Create CloudWatch alarms for Lambda errors and API Gateway 5xx5xx errors, and attach them to the CodeDeploy deployment group.
This enables native automated rollback in case performance issues occur during the 1010-minute window.

Anahtar Kavram

AWS CodeDeploy Canary Traffic Shifting with Automated Rollbacks
Soru 328Soru

A company is designing a new web application in a single VPC across two Availability Zones: us-east-1a and us-east-1b. The application consists of web servers in public subnets and database servers in private subnets. The database servers must download software patches from the internet, and the design must remain resilient to a single Availability Zone outage. Which configuration meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy one NAT Gateway in the public subnet of us-east-1a and another NAT Gateway in the public subnet of us-east-1b. Configure the route table of the private subnet in each Availability Zone to route outbound internet traffic through the local NAT Gateway in that same zone.

Cevap

Deploy one NAT Gateway in the public subnet of us-east-1a and another NAT Gateway in the public subnet of us-east-1b, configuring each private subnet to use its local NAT Gateway.
The correct answer is to deploy a NAT Gateway in the public subnet of each Availability Zone (us-east-1a and us-east-1b) and configure the local private subnets to point their outbound route (0.0.0.0/00.0.0.0/0) to the local NAT Gateway. Since NAT Gateways are redundant within a single Availability Zone but do not span multiple zones, having one in each zone ensures that an outage in one zone does not affect outbound connectivity for the other zone.

Adım Adım Çözüm

1
Analyze the requirements for outbound internet connectivity and high availability across multiple Availability Zones.
Identified that database servers in private subnets must reach the internet, and the solution must tolerate a single Availability Zone outage.
This establishes the need for redundant NAT Gateways to avoid a single point of failure.
2
Evaluate the NAT Gateway placement strategy for multi-AZ resiliency.
A NAT Gateway is a zonal resource; therefore, to ensure high availability, a NAT Gateway must be deployed in each Availability Zone.
If a single NAT Gateway is used and its Availability Zone fails, all other zones lose outbound internet access.
3
Configure the VPC route tables to direct outbound traffic (0.0.0.0/00.0.0.0/0) to the corresponding local NAT Gateway.
The private subnet in us-east-1a routes to the NAT Gateway in us-east-1a, and the private subnet in us-east-1b routes to the NAT Gateway in us-east-1b.
This keeps traffic within the same Availability Zone, reducing inter-AZ data transfer costs and ensuring zone independence.

Anahtar Kavram

Multi-Availability Zone NAT Gateway Redundancy
Soru 329Soru

An enterprise application runs on Amazon EC2 instances within an Auto Scaling group. The application writes logs to `/var/log/app/output.log`. Every hour, a cron job rotates the log file by renaming the active file to `/var/log/app/output.log.YYYY-MM-DD-HH` and creating a new empty `/var/log/app/output.log` file. The CloudWatch agent is configured on the instances to stream `/var/log/app/output.log` to a CloudWatch Logs group. However, after the first hourly log rotation occurs, the operations team notices that new log entries are no longer delivered to CloudWatch until the CloudWatch agent is restarted. Which configuration change in the CloudWatch agent configuration file is required to resolve this issue and ensure continuous log delivery?

Cevabı ve açıklamayı göster

Cevap: Modify the `file_path` parameter in the CloudWatch agent configuration file to use a wildcard pattern, such as `/var/log/app/output.log*`, so that the agent monitors the directory and identifies both the renamed historical files and the newly created active file.

Cevap

Modify the `file_path` parameter in the CloudWatch agent configuration file to use a wildcard pattern, such as `/var/log/app/output.log*`, so that the agent monitors the directory and identifies both the renamed historical files and the newly created active file.
The correct answer is to modify the `file_path` parameter to use a wildcard pattern. When the CloudWatch agent monitors a static file path, it maintains an open file descriptor. When log rotation renames the file, the agent continues to read from the renamed file (since the inode doesn't change) until it reaches the end of the file, but it will not automatically open the new file created with the original name. By specifying a wildcard pattern like `/var/log/app/output.log*`, the agent monitors the directory for files matching the pattern, enabling it to detect and stream from the new active file as soon as it is created.

Adım Adım Çözüm

1
Analyze the log rotation mechanism and how the CloudWatch agent tracks files.
The application renames the active `/var/log/app/output.log` file and creates a new one. Since the agent was tracking the specific file path, it retains the file descriptor for the renamed file and fails to open the new file containing the active log stream.
To understand why log delivery stops after rotation.
2
Identify the configuration parameter in the CloudWatch agent config that controls file tracking.
The `file_path` parameter specifies the path of the files to collect logs from. It supports wildcard patterns.
To determine where and how the configuration needs to be modified.
3
Formulate a wildcard pattern that covers both the active and rotated files.
Using a pattern like `/var/log/app/output.log*` ensures that when a new `/var/log/app/output.log` file is created, it matches the pattern and the agent starts tracking it automatically.
To restore continuous log streaming without agent restarts.

Anahtar Kavram

CloudWatch Agent Wildcard File Path Configuration
Soru 330Soru

An enterprise financial platform operates its core transaction processing engine in private subnets across 33 Availability Zones in the `us-east-1` Region. The workloads must satisfy three networking requirements:

1. Establish high-throughput, low-latency communication with a database cluster located in a separate VPC within the same Region.
2. Query external credit-scoring APIs via the internet with a target latency of less than 50 ms50\text{ ms} and high availability.
3. Resolve private DNS hostnames for utility resources hosted in a shared services VPC.

Currently, all private subnets route internet-bound traffic through a single NAT Gateway located in Availability Zone `us-east-1a`, a Transit Gateway is used for VPC-to-VPC routing, and the Route 53 Private Hosted Zones (PHZs) are associated only with the shared services VPC. During high-volume trading hours, users experience query timeouts, increased latency, and host resolution failures.

Which combination of actions will resolve the bottlenecks and optimize network performance?

Cevabı ve açıklamayı göster

Cevap: Associate the Route 53 PHZ of the shared services VPC with the transaction processing VPC. Deploy a NAT Gateway in each of the 33 Availability Zones, and update the private subnet route tables to direct internet traffic (0.0.0.0/00.0.0.0/0) to the local NAT Gateway in each respective Availability Zone.

Cevap

Associate the Route 53 Private Hosted Zone of the shared services VPC with the transaction processing VPC. Deploy a NAT Gateway in each of the 3 Availability Zones, and update the private subnet route tables to direct internet traffic to the local NAT Gateway in each respective Availability Zone.
Associating the Route 53 Private Hosted Zone with the transaction processing VPC allows local resources to resolve the private hostnames. Deploying a NAT Gateway in each of the three Availability Zones ensures that egress traffic to external APIs does not cross Availability Zone boundaries, which minimizes latency, eliminates cross-AZ charges, and removes a single point of failure.

Adım Adım Çözüm

1
Analyze the DNS resolution failure for private hostnames.
Identify that the Route 53 Private Hosted Zone (PHZ) is only associated with the shared services VPC.
For resources in the transaction processing VPC to resolve private hostnames in the shared services VPC, the PHZ must be explicitly associated with the transaction processing VPC.
2
Analyze the NAT Gateway architecture for egress API traffic.
Identify that a single NAT Gateway in one Availability Zone is used by resources across all 3 zones.
Routing traffic across Availability Zones to a single NAT Gateway introduces latency, cross-AZ data transfer charges, and a single point of failure. Deploying a NAT Gateway in each Availability Zone optimizes routing paths and avoids cross-AZ overhead.
3
Verify inter-VPC routing options for database traffic.
Retain Transit Gateway attachments for multi-VPC routing.
Transit Gateway supports transitive routing and high throughput within the same Region, whereas alternative options like Direct Connect Gateway do not support transitive VPC-to-VPC routing.

Anahtar Kavram

Multi-AZ NAT Gateway redundancy and Route 53 Private Hosted Zone cross-VPC association for network latency and reliability optimization
Tahmini Süre:2m 30s
Soru 331Soru

A company runs a batch processing application on a fleet of Amazon EC2 instances using gp2 Amazon EBS volumes. The application's database backend is hosted on an Amazon RDS for PostgreSQL Multi-AZ DB instance. The solutions architect needs to optimize both compute and storage performance for this existing solution while keeping administrative effort low. Which of the following recommendations should the solutions architect implement? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Migrate the storage volumes from gp2 to gp3 to gain higher performance at a lower cost and enable independent scaling of throughput and IOPS.; Use AWS Compute Optimizer to analyze historical utilization metrics and resize the EC2 instances to the recommended optimal instance types.

Cevap

Migrate the storage volumes from gp2 to gp3 to gain higher performance at a lower cost, and use AWS Compute Optimizer to analyze utilization metrics and resize the EC2 instances.
Migrating storage volumes from gp2 to gp3 provides immediate performance and cost benefits by allowing independent scaling of IOPS and throughput. Utilizing AWS Compute Optimizer helps automatically identify size adjustments needed for EC2 instances based on actual usage telemetry.

Adım Adım Çözüm

1
Analyze storage performance options for EBS volumes.
GP3 volumes are identified as offering higher performance and lower cost than GP2, allowing independent configuration of IOPS and throughput.
Upgrading to gp3 directly optimizes storage performance and cost.
2
Evaluate compute optimization tools.
AWS Compute Optimizer is selected to analyze historical metrics and suggest optimal EC2 instance types.
This automates the sizing optimization process for compute instances.

Anahtar Kavram

Continuous performance optimization of EC2 instances and EBS volumes using managed tools and modern resource types.
Tahmini Süre:2m 0s
Soru 332Soru

An enterprise wants to centralize API activity logs across all AWS accounts in their AWS Organization. A solutions architect configures an organization trail in the management account to deliver logs to a centralized Amazon S3 bucket located in a dedicated security account. The S3 bucket uses Amazon S3 managed keys (SSE-S3) for encryption. Although the organization trail is successfully created, the operations team reports that no log files are being delivered to the S3 bucket. Which of the following is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The S3 bucket policy in the security account does not grant write permissions to the CloudTrail service principal for the organization path structure.

Cevap

The S3 bucket policy in the security account does not grant write permissions to the CloudTrail service principal for the organization path structure.
AWS CloudTrail delivers logs to S3 using its service principal (cloudtrail.amazonaws.com). When centralizing logs from an organization trail into a bucket located in another account, the destination S3 bucket policy must explicitly permit the CloudTrail service principal to perform the s3:PutObject action on the path corresponding to the AWS Organization's logs (typically prefixed with AWSLogs/o-organizationid/). Without this permission, CloudTrail will be blocked from writing to the bucket.

Adım Adım Çözüm

1
Identify the service delivering logs and the destination bucket's location.
AWS CloudTrail is configured in the management account, and the destination S3 bucket is in a separate security account.
Since the bucket is in a different account, cross-account permissions must be explicitly granted.
2
Determine how CloudTrail delivers logs to Amazon S3.
CloudTrail uses its service principal (cloudtrail.amazonaws.com) to write logs directly to the S3 bucket.
Log delivery relies on the bucket policy allowing the CloudTrail service principal rather than individual IAM users or roles.
3
Verify if the bucket policy is properly configured for the organization trail structure.
The bucket policy must grant s3:PutObject permissions to cloudtrail.amazonaws.com for the prefix matching the organization's ID.
Without this resource-based policy permission, CloudTrail cannot write logs to the S3 bucket in the security account, resulting in delivery failure.

Anahtar Kavram

Cross-account log centralization with AWS CloudTrail and S3 bucket policies
Soru 333Soru

A geophysics research firm runs a seismic data processing pipeline on AWS. The pipeline consists of a fleet of Amazon EC2 instances in an Auto Scaling group (ASG) that ingest sensor telemetry logs, perform complex spatial transformations, write intermediate results to local scratch spaces, and update metadata in an Amazon RDS PostgreSQL DB instance. The processed datasets are ultimately uploaded to Amazon S3 for long-term research.

During daily calculation cycles, the solutions architect observes the following performance issues:
- The EC2 instances encounter severe disk write latency while writing intermediate sensor logs to local storage. The instances use Amazon EBS gp2 volumes, which frequently exhaust their I/O burst credits.
- The RDS PostgreSQL DB instance experiences high CPU utilization and query timeouts due to a sudden influx of read-heavy telemetry lookup queries.
- The final archive process to S3 fails with HTTP 503503 (Slow Down) errors when uploading thousands of small datasets concurrently to a single path: `s3://seismic-data-archive/raw-outputs/`.

Which two actions should the solutions architect take to resolve these performance bottlenecks? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Upgrade the EC2 instance root and scratch volumes to gp3, configure them with sufficient provisioned IOPS and throughput, and modify the application to upload archives to S3 using key paths prepended with a hash of the sensor identifier.; Add RDS PostgreSQL Read Replicas to offload the read-heavy telemetry lookup queries from the primary database instance, and update the application's lookup queries to connect to the replica endpoints.

Cevap

The correct actions are to upgrade the EC2 scratch volumes to gp3 with provisioned performance while prepending a partition hash to S3 archive paths, and to add RDS PostgreSQL Read Replicas to offload read-heavy lookup queries from the primary database.
Optimizing local storage write performance is achieved by migrating from gp2 to gp3 volumes, which allows provisioning specific IOPS and throughput values independently of capacity to eliminate I/O queuing. S3 write performance is optimized by prepending a hash to the S3 bucket paths. This distributes concurrent writes across multiple S3 partitions, bypassing the limit of 3,5003,500 write requests per second per prefix. Database read performance is scaled by adding RDS PostgreSQL Read Replicas and routing read-heavy queries to the replica endpoints, reducing CPU contention on the primary writer.

Adım Adım Çözüm

1
Analyze local disk write latency on the EC2 nodes.
The EBS gp2 volumes are identified as exhausting their I/O burst credit bucket during calculation cycles.
EBS gp2 volumes scale performance based on size. Under high write loads, small or medium gp2 volumes deplete their burst credits, dropping performance to a low baseline and causing latency.
2
Optimize the local disk write performance and S3 upload throughput.
EBS volumes are upgraded to gp3 with customized IOPS and throughput. S3 upload key paths are modified to prepend a partition hash.
gp3 volumes allow provisioning performance parameters independently of size, guaranteeing consistent throughput. Introducing a hash prefix in S3 partitions writes across multiple prefixes, bypassing the 3,5003,500 write requests per second limit per prefix and resolving the HTTP 503503 errors.
3
Analyze RDS PostgreSQL DB high CPU utilization and query timeouts.
High CPU utilization is traced to read-heavy telemetry lookup queries hitting the primary writer database instance.
Mixing high-volume read traffic with transactional updates on the primary database instance exhausts CPU resources, leading to query delays and execution timeouts.
4
Deploy RDS PostgreSQL Read Replicas.
Read Replicas are created and the application configures read queries to use the replica endpoints.
Read Replicas asynchronously replicate data and remain active for read-only queries, freeing up the primary writer instance for transactional metadata updates.

Anahtar Kavram

Identifying storage performance limits (EBS gp2 vs gp3 and S3 prefix request limits) and scaling compute database queries horizontally via Read Replicas.
Tahmini Süre:3m 0s
Soru 334Soru

A multinational retail corporation is designing a secure vendor inventory ingestion platform. Vendors must upload inventory catalogs from their respective AWS accounts directly to an Amazon S3 bucket located in the retailer's central Ingestion account. The retailer's security policy mandates that all data must be encrypted at rest using AWS KMS. The solutions architect initially configures default S3 bucket encryption using the AWS-managed S3 key (aws/s3). However, vendor IAM roles receive 'Access Denied' errors when attempting to upload objects, despite having explicit s3:PutObject permissions in their IAM policies and the S3 bucket policy. Which configuration change will resolve this issue while maintaining compliance with the security policy?

Cevabı ve açıklamayı göster

Cevap: Replace the default S3 bucket encryption with a Customer Managed Key (CMK) created in the Ingestion account. Configure the CMK's key policy to allow the vendor's IAM roles to perform the kms:GenerateDataKey and kms:Encrypt actions, and add corresponding permissions to the vendor roles' local IAM policies.

Cevap

Replace the default S3 bucket encryption with a Customer Managed Key (CMK) created in the Ingestion account, configure the CMK's key policy to allow the vendor's IAM roles to perform the kms:GenerateDataKey and kms:Encrypt actions, and add corresponding permissions to the vendor roles' local IAM policies.
The correct solution is to use a Customer Managed Key (CMK) because AWS-managed keys (such as aws/s3) cannot be shared across accounts. Their key policies are managed by AWS, cannot be modified, and do not permit cross-account usage. By replacing the default encryption with a CMK in the target account, the retailer can modify its key policy to explicitly trust the vendor's IAM roles. The vendor's IAM roles must also be granted permission to perform kms:GenerateDataKey and kms:Encrypt in their local IAM policies to allow the cross-account KMS operations.

Adım Adım Çözüm

1
Identify the root cause of the cross-account upload failure.
The S3 bucket is configured with default encryption using the AWS-managed KMS key (aws/s3). AWS-managed keys cannot be shared across accounts because their key policies cannot be modified.
Understanding why the initial setup fails is necessary to rule out suggestions that attempt to reuse the AWS-managed key.
2
Select the correct KMS key type for cross-account S3 bucket uploads.
A Customer Managed Key (CMK) must be created in the destination (retailer's) account.
Only Customer Managed Keys support custom key policies that can be configured to grant access to external accounts or roles.
3
Configure permissions on the resource side.
Modify the CMK's key policy to allow the vendor's IAM roles the permissions to call kms:GenerateDataKey and kms:Encrypt.
For cross-account access, the resource policy (key policy) must explicitly authorize the external principal.
4
Configure permissions on the identity side.
Ensure the vendor's IAM policies grant the roles permissions to call kms:GenerateDataKey and kms:Encrypt on the CMK's ARN.
Cross-account authorization requires permission checks to pass on both the resource policy and the caller's identity policy.

Anahtar Kavram

Cross-account KMS key sharing and policy requirements for default S3 bucket encryption.
Soru 335Soru

An energy grid management company runs a telemetry ingestion application on a fleet of Amazon EC2 instances. The application writes log files to `/var/log/grid/telemetry.log`. A cron job rotates these logs hourly, renaming the active file to `telemetry.log.YYYY-MM-DD-HH` and creating a new empty `telemetry.log` file. The operations team configured the unified CloudWatch agent to monitor the active `/var/log/grid/telemetry.log` file, but they notice that log entries written immediately before and during the rotation process are frequently missed in Amazon CloudWatch Logs. Which configuration change will resolve this issue while maintaining operational excellence?

Cevabı ve açıklamayı göster

Cevap: Modify the CloudWatch agent configuration file by changing the `file_path` parameter to `/var/log/grid/telemetry.log*` to ensure the agent monitors both the active and rotated log files.

Cevap

Modify the CloudWatch agent configuration file by changing the file_path parameter to /var/log/grid/telemetry.log* to ensure the agent monitors both the active and rotated log files.
The correct option addresses the log rotation issue by using a wildcard character (`*`) in the `file_path` configuration. When the file is rotated and renamed to `telemetry.log.YYYY-MM-DD-HH`, the CloudWatch agent continues to read from the renamed file until it reaches the end of the file, while also starting to monitor the newly created `telemetry.log` file.

Adım Adım Çözüm

1
Analyze how the CloudWatch agent tracks log files.
The agent tailing a static path like `/var/log/grid/telemetry.log` will lose track of log events if the file is renamed during rotation while active writing continues or buffer flush is incomplete.
Understanding the interaction between the CloudWatch agent and file system rotation is critical to diagnosing log loss.
2
Select the correct pattern matching configuration.
Using a wildcard pattern such as `/var/log/grid/telemetry.log*` allows the agent to monitor both the active and rotated files concurrently, letting it process any remaining lines in the rotated file.
Wildcards allow the agent to track multiple files matching the pattern, ensuring continuity across rotation boundaries.

Anahtar Kavram

Configuring CloudWatch Agent for Log Rotation using Wildcards
Tahmini Süre:2m 0s
Soru 336Soru

A company runs a web application with a MySQL database hosted on Amazon RDS. The database is experiencing performance degradation due to a high volume of read and write requests for user session states. A solutions architect must improve database efficiency by moving the session state data to a dedicated caching layer. The caching solution must support multi-AZ replication to ensure session data is not lost if a primary cache node fails. Which caching and database optimization strategy should the solutions architect implement?

Cevabı ve açıklamayı göster

Cevap: Migrate the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled.

Cevap

Migrate the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled.
Migrating the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled is the correct approach. Unlike Memcached, ElastiCache for Redis supports replication, Multi-AZ replication groups, and automatic failover, ensuring that session data remains available if a primary node fails.

Adım Adım Çözüm

1
Analyze the application requirements for caching session states.
The requirement demands a caching layer that offloads session data from RDS MySQL and supports multi-AZ replication for high availability.
Identifying the caching requirements helps filter out incompatible services.
2
Evaluate the caching capabilities of ElastiCache for Memcached and ElastiCache for Redis.
Memcached is a simple, multi-threaded cache but lacks replication and Multi-AZ capabilities. Redis supports replication, Multi-AZ automatic failover, and data persistence.
This determines which caching engine meets the high availability requirement.
3
Select the correct ElastiCache engine and configuration.
Choose ElastiCache for Redis with Multi-AZ replication enabled.
Redis satisfies both the low-latency caching and the high-availability replication requirements.

Anahtar Kavram

Selecting the appropriate caching engine (Redis vs. Memcached) based on replication and persistence requirements.
Tahmini Süre:1m 0s
Soru 337Soru

An enterprise is setting up a multi-account environment on AWS. A central Shared Services account contains a Route 53 Private Hosted Zone (PHZ) named `internal.infra` that hosts DNS records for shared infrastructure resources. Two new application VPCs, `vpc-app-dev` and `vpc-app-prod`, are deployed in separate AWS member accounts. The workloads in these application VPCs must resolve domain names within `internal.infra` with minimal latency and without exposing the traffic to the public internet. Which of the following approaches satisfies these requirements with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Authorize the association of the `internal.infra` Private Hosted Zone with `vpc-app-dev` and `vpc-app-prod` from the Shared Services account, and then associate the VPCs with the hosted zone from the respective member accounts.

Cevap

Authorize the association of the Private Hosted Zone with the member VPCs from the Shared Services account, and then associate the VPCs with the hosted zone from the member accounts.
The correct approach is to authorize the cross-account association from the Shared Services account and then perform the association from the member accounts. This allows resources in the application VPCs to resolve domain names in the Private Hosted Zone directly and natively using their local Route 53 Resolver (the VPC CIDR plus two address). This design provides the lowest latency, avoids additional network infrastructure costs, and eliminates single points of failure.

Adım Adım Çözüm

1
Create an association authorization from the owner account.
Grants permission for the target VPCs in the consumer accounts to link to the Private Hosted Zone.
Route 53 requires explicit authorization from the hosted zone's owning account before a VPC in a different AWS account can be associated with it.
2
Associate the VPCs from the consumer accounts.
The target VPCs are linked to the Private Hosted Zone, enabling local DNS resolution of its records.
Once authorized, the VPC owner must accept or execute the association to enable the Route 53 Resolver in that VPC to answer queries for the zone.

Anahtar Kavram

Cross-Account Route 53 Private Hosted Zone Association
Soru 338Soru

An enterprise SaaS company hosts a high-throughput reporting application. The application's web tier runs on Amazon EC2 instances in an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The database tier consists of an Amazon RDS for PostgreSQL DB instance in a Multi-AZ deployment on a db.m6g.4xlargedb.m6g.4xlarge instance with a 2 TB2\text{ TB} Provisioned IOPS SSD (gp3gp3) storage volume configured at 12,000 IOPS12,000\text{ IOPS} and 500 MB/s500\text{ MB/s} throughput. During monthly billing cycles, tenants execute resource-intensive reporting queries, causing primary DB instance CPU utilization to reach 98%98\% and causing write transactions to fail due to lock contention and connection timeouts. The reporting queries require data that is no more than 5 seconds5\text{ seconds} out of date. Additionally, during the first hour of the billing cycle, the application experiences a massive, instantaneous surge in traffic that results in HTTP 503 Service Unavailable errors for initial users. Which combination of actions should a Solutions Architect recommend to optimize performance and resolve these issues?

Cevabı ve açıklamayı göster

Cevap: Create an Amazon RDS read replica and configure the reporting application to direct read-only queries to the read replica endpoint. Submit a request to AWS Support to pre-warm the Application Load Balancer (ALB) prior to the start of the monthly billing cycle.

Cevap

Create an Amazon RDS read replica and configure the reporting application to direct read-only queries to the read replica endpoint. Submit a request to AWS Support to pre-warm the Application Load Balancer (ALB) prior to the start of the monthly billing cycle.
Directing read-only queries to an Amazon RDS read replica offloads compute-heavy workloads from the primary DB instance, resolving the primary CPU exhaustion and preventing write transaction timeouts. The replica lag for RDS PostgreSQL is typically under 1 second1\text{ second}, which satisfies the consistency constraint of data being no more than 5 seconds5\text{ seconds} out of date. Furthermore, pre-warming the Application Load Balancer (ALB) ensures that the load balancer is pre-scaled to handle the instantaneous surge of traffic at the beginning of the billing cycle, preventing initial HTTP 503 errors.

Adım Adım Çözüm

1
Identify the primary database bottleneck and consistency requirements.
The primary RDS DB instance's CPU utilization spikes to 98%98\% due to read-heavy reporting queries, but the reports can tolerate data up to 5 seconds5\text{ seconds} out of date.
Since the write queries are failing due to resource exhaustion on the primary, read queries must be offloaded to a secondary compute resource that supports asynchronous replication with lag under 5 seconds5\text{ seconds}.
2
Select the correct RDS read scaling mechanism.
Deploy an Amazon RDS read replica. Verify that it typically operates with sub-second replication lag.
Amazon RDS Multi-AZ standby instances are passive and cannot accept read queries. Horizontal scaling of reads must be achieved using read replicas, not standby instances.
3
Address the web tier load balancing drop in initial requests.
Identify that the surge is instantaneous (flash traffic) and request ALB pre-warming from AWS Support.
Dynamic auto-scaling policies react to sustained traffic increases and are too slow to scale the ALB immediately, leading to dropped requests at the very start of the traffic spike. Pre-warming prepares the ALB capacity in advance.

Anahtar Kavram

Offloading read traffic to RDS Read Replicas for database compute optimization, and pre-warming Application Load Balancers for instantaneous traffic spikes.
Soru 339Soru

A retail company hosts a customer loyalty application that stores transaction records in an Amazon S3 bucket. To comply with new data protection regulations, the company must encrypt all objects in the bucket using a key that supports automatic annual rotation. Additionally, the company must securely share these encrypted transaction records with a third-party auditing firm's external AWS account. Which two configuration steps should a solutions architect perform to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the Amazon S3 bucket to use server-side encryption with an AWS KMS customer managed key (SSE-KMS).; Enable automatic key rotation for the customer managed KMS key, and update its key policy to grant decrypt permissions to the third-party auditing firm's AWS account.

Cevap

Configure the Amazon S3 bucket to use server-side encryption with an AWS KMS customer managed key (SSE-KMS), and enable automatic key rotation for the customer managed KMS key while updating its key policy to grant decrypt permissions to the third-party auditing firm's AWS account.
To satisfy both the key rotation and external sharing requirements, the solutions architect must use an AWS KMS customer managed key for SSE-KMS. Customer managed keys permit the modification of key policies to delegate decrypt permissions to external AWS accounts, and support automatic annual rotation. Enabling key rotation and defining the decryption policy for the auditing firm's AWS account ensures secure, compliant data protection.

Adım Adım Çözüm

1
Identify the encryption key type that allows cross-account key sharing.
Determine that an AWS KMS customer managed key is required because AWS managed keys (aws/s3) do not allow policy modification to grant cross-account permissions.
Compliance and sharing requirements necessitate key policy customization.
2
Configure the encryption and key rotation behavior.
Enable SSE-KMS on the Amazon S3 bucket with the customer managed key, and turn on the automatic key rotation property in the KMS key configuration.
This automates the annual rotation requirement without manual intervention.
3
Update the KMS key policy to permit external account access.
Add a statement in the KMS key policy that grants the third-party auditing firm's AWS account principal permission to execute the kms:Decrypt action.
An IAM policy or S3 bucket policy alone cannot grant cross-account access to KMS keys without the KMS key policy explicitly delegating it.

Anahtar Kavram

AWS KMS Customer Managed Keys are required for cross-account S3 bucket access because AWS managed keys do not support policy modification.
Tahmini Süre:1m 30s
Soru 340Soru

A company runs production workloads across two AWS accounts that belong to an organization in AWS Organizations. Account A runs microservices hosted on AWS Fargate. Account B runs legacy processing applications on Amazon EC2 instances. The company wants to reduce compute costs by committing to a 1-year Savings Plan. The solution must provide maximum savings coverage across both workloads, maintain high availability, and require minimal administrative effort. Which of the following actions should a Solutions Architect recommend to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Purchase a Compute Savings Plan in the organization's management account.; Ensure that Savings Plan discount sharing is enabled in the Consolidated Billing settings for the organization.

Cevap

To optimize costs while maintaining flexibility and high availability, purchase a Compute Savings Plan in the organization's management account and verify that Savings Plan discount sharing is enabled in the Consolidated Billing configurations.
Purchasing a Compute Savings Plan in the management account provides maximum flexibility as it covers both Amazon EC2 and AWS Fargate usage. Ensuring that discount sharing is enabled in Consolidated Billing allows these savings to apply automatically to workloads in both member accounts without any manual allocation or administration.

Adım Adım Çözüm

1
Determine the resource types in scope for cost optimization.
The architecture uses both Amazon EC2 instances and AWS Fargate tasks across multiple accounts.
Understanding the compute mix dictates which Savings Plan type will provide coverage.
2
Select the correct Savings Plan type.
Choose a Compute Savings Plan since it applies to both EC2 and AWS Fargate, unlike EC2 Instance Savings Plans which only apply to EC2.
Maximizing discount coverage requires a plan that spans across heterogeneous compute types.
3
Configure organization-wide sharing.
Enable Savings Plan discount sharing in the Consolidated Billing settings of the management account.
This allows the benefits of the Savings Plan purchased in the management account to flow automatically to the workloads in Account A and Account B.

Anahtar Kavram

Compute Savings Plans are the most flexible Savings Plan type as they automatically apply to EC2 and Fargate across any AWS Organization account when discount sharing is enabled.
ÖncekiSayfa 17 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin