Tüm alıştırma soruları

1964 soru

Soru 1821Soru

A logistics company is designing its multi-account governance strategy using AWS Organizations. The Security team must ensure that no member account in the Workloads Organizational Unit (OU) can disable or modify AWS Config configurations. Simultaneously, the Development team within the Workloads OU needs the ability to deploy and delete AWS CloudFormation templates that manage EC2 and RDS resources. What is the most operationally efficient way to implement these access controls?

Cevabı ve açıklamayı göster

Cevap: Attach a Service Control Policy (SCP) to the Workloads OU that denies the config:Delete* and config:Stop* actions. In the member accounts, configure local IAM policies that allow developers to manage AWS CloudFormation, EC2, and RDS resources.

Cevap

Attach a Service Control Policy (SCP) to the Workloads OU that denies AWS Config modifications, and configure local IAM policies in the member accounts to allow developers to manage AWS CloudFormation, EC2, and RDS resources.
The correct solution uses an SCP to deny AWS Config modifications at the OU level, acting as a guardrail. Since SCPs only define the maximum permissions boundary and do not grant permissions, the default FullAWSAccess SCP is left in place, and developers are granted the required permissions using local IAM policies within their respective member accounts.

Adım Adım Çözüm

1
Identify the mechanism to enforce compliance guardrails across multiple AWS accounts.
Determine that Service Control Policies (SCPs) applied to the Workloads Organizational Unit (OU) are the correct tool to deny AWS Config changes.
SCPs allow administrators to centrally restrict services and actions for all accounts in an OU, overriding local administrator actions.
2
Determine how to grant developers permissions to deploy resources while staying within the SCP guardrails.
Create local IAM policies in the member accounts allowing access to CloudFormation, EC2, and RDS, while keeping the default FullAWSAccess SCP attached to the OU.
SCPs act as a filter rather than granting permissions. A local IAM policy is still required to explicitly allow the developer actions.

Anahtar Kavram

Service Control Policies (SCPs) establish permissions guardrails in an organization but do not grant permissions directly. Local IAM policies are required to authorize users to perform actions.
Tahmini Süre:1m 30s
Soru 1822Soru

A healthcare enterprise is planning to migrate a 680 TB680\text{ TB} dataset from an on-premises S3-compatible object storage system to an Amazon S3 bucket. The enterprise has a 100 Mbps100\text{ Mbps} internet connection and a dedicated 1 Gbps1\text{ Gbps} AWS Direct Connect connection. To minimize impact on other corporate workloads, only 150 Mbps150\text{ Mbps} of the Direct Connect bandwidth can be allocated for this migration. The migration must be completed within 30 days. The source dataset is actively modified, with approximately 2 TB2\text{ TB} of new files added weekly. Security policies require all data to be encrypted at rest in the target bucket using an AWS KMS Customer Managed Key (CMK). Which migration strategy meets these requirements within the specified timeframe and with the lowest operational overhead?

Cevabı ve açıklamayı göster

Cevap: Order multiple AWS Snowball Edge Storage Optimized devices. Copy the initial data from the on-premises storage to the devices using the S3-compatible endpoint, encrypting it with the KMS Customer Managed Key. Ship the devices to AWS. Once ingested, deploy an AWS DataSync agent on-premises, create a task from the S3-compatible source to the target S3 bucket, and execute it over the Direct Connect link to sync the remaining delta changes.

Cevap

Order multiple AWS Snowball Edge Storage Optimized devices to copy the initial data using a Customer Managed Key, ship them to AWS, and then use an AWS DataSync task to synchronize the remaining delta changes over the Direct Connect link.
The correct strategy uses multiple AWS Snowball Edge Storage Optimized devices to transport the bulk data (680 TB680\text{ TB}), which solves the network bandwidth limitation. Once the bulk data is ingested, AWS DataSync is used to replicate the remaining delta changes (2 TB2\text{ TB} per week) over the 150 Mbps150\text{ Mbps} connection. Using a Customer Managed Key meets both the encryption policy and Snowball compatibility requirements.

Adım Adım Çözüm

1
Calculate network migration viability for bulk data.
Transferring 680 TB680\text{ TB} over 150 Mbps150\text{ Mbps} requires approximately 420 days (680×1012×8/150,000,00036,266,667680 \times 10^{12} \times 8 / 150,000,000 \approx 36,266,667 seconds), which is far beyond the 30-day limit.
Determines whether an online-only migration using AWS DataSync is feasible.
2
Select the bulk transfer mechanism and configure encryption.
Order AWS Snowball Edge Storage Optimized devices and copy the 680 TB680\text{ TB} base dataset using a Customer Managed Key (CMK) for encryption.
Allows secure physical shipment of the bulk dataset within 1-2 weeks.
3
Synchronize active updates and delta changes.
Deploy an AWS DataSync agent on-premises to sync the weekly 2 TB2\text{ TB} changes to the target S3 bucket over the Direct Connect link.
Allows capturing updates made during the Snowball shipping and processing window within a few days, finishing the migration inside the 30-day target.

Anahtar Kavram

Combining offline physical migration (Snowball Edge) with online delta replication (DataSync) for large-scale datasets with limited bandwidth and strict migration windows.
Soru 1823Soru

An energy trading firm is modernizing its legacy real-time gas nomination settlement system. The API is hosted on Amazon API Gateway in Account A, which must invoke an AWS Lambda function in Account B. The Lambda function in Account B is deployed inside a VPC across three Availability Zones to securely query an Amazon Aurora PostgreSQL database in Account A via an Amazon RDS Proxy. The database credentials are stored in AWS Secrets Manager in Account A and are encrypted. The Lambda function must also make outbound HTTPS calls to an external public energy pricing index API to fetch daily indexes. To handle sudden settlement spikes, the design must protect Account B from regional concurrency exhaustion and prevent database overload. Outbound internet connectivity must not have a single point of failure. Secrets decryption must work across accounts. Code updates must shift 10%10\% of traffic to the new version, wait 1010 minutes for evaluation, and roll back automatically if errors occur. Which architecture design meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure API Gateway in Account A with cross-account permissions to invoke the Lambda function in Account B. Deploy the Lambda function in three private subnets in Account B, with each subnet's route table pointing to a dedicated NAT Gateway in a public subnet in its respective Availability Zone. Set a reserved concurrency limit on the Lambda function. Encrypt the database credentials in AWS Secrets Manager using a Customer Managed Key (CMK) in Account A, and configure its key policy to allow the Lambda execution role in Account B decrypt permissions. Deploy the function using AWS CodeDeploy with a Canary10Percent10Minutes configuration monitored by CloudWatch alarms.

Cevap

Configure API Gateway in Account A with cross-account permissions to invoke the Lambda function in Account B. Deploy the Lambda function in three private subnets in Account B, with each subnet's route table pointing to a dedicated NAT Gateway in a public subnet in its respective Availability Zone. Set a reserved concurrency limit on the Lambda function. Encrypt the database credentials in AWS Secrets Manager using a Customer Managed Key (CMK) in Account A, and configure its key policy to allow the Lambda execution role in Account B decrypt permissions. Deploy the function using AWS CodeDeploy with a Canary10Percent10Minutes configuration monitored by CloudWatch alarms.
The correct solution addresses all cross-account, security, routing, performance, and deployment requirements. It uses a Customer Managed Key (CMK) with a custom key policy in Account A, permitting the execution role in Account B to decrypt the database credentials. It ensures high availability for outbound pricing calls by configuring redundant NAT Gateways across all three Availability Zones. It also prevents regional concurrency pool exhaustion by setting a reserved concurrency limit on the Lambda function, and employs AWS CodeDeploy with a Canary10Percent10Minutes configuration along with CloudWatch alarms to execute safe, automated rollbacks.

Adım Adım Çözüm

1
Analyze cross-account decryption requirements for Secrets Manager.
Determine that a Customer Managed Key (CMK) must be used, as the default AWS-managed KMS key (aws/secretsmanager) does not allow key policy modifications to grant access to external accounts.
The Lambda execution role in Account B requires permission to decrypt the database credentials stored in Account A.
2
Evaluate subnet routing for outbound internet access across Availability Zones.
Identify that a NAT Gateway must be deployed in each Availability Zone where the Lambda function resides.
Routing all subnet traffic through a single NAT Gateway creates a single point of failure, violating the high-availability requirement for fetching pricing indexes.
3
Determine the concurrency strategy to protect the database and Lambda execution environments.
Apply a reserved concurrency limit on the Lambda function.
Without reserved concurrency, sudden traffic spikes could deplete the regional concurrency pool in Account B and overwhelm the downstream RDS database despite having an RDS Proxy.
4
Select the correct AWS CodeDeploy deployment configuration.
Choose the Canary10Percent10Minutes configuration.
This matches the operational requirement to shift 10% of traffic, evaluate for 10 minutes, and roll back via CloudWatch alarms if errors occur.

Anahtar Kavram

Designing secure, resilient, and performant serverless architectures spanning multiple AWS accounts and VPCs.
Soru 1824Soru

An enterprise is planning to migrate its on-premises VMware vSphere environment to VMware Cloud (VMC) on AWS. The migration scope includes 5050 virtual machines (VMs) running multi-tier applications, including a critical Oracle database VM that requires zero replication-induced downtime during the cutover. The on-premises data center is connected to AWS via a 10 Gbps10\text{ Gbps} AWS Direct Connect connection terminated on a Direct Connect Gateway (DXGW).

Additionally, the architecture requires:
- Transitive routing between the VMC on AWS Software-Defined Data Center (SDDC), the on-premises environment, and multiple spoke VPCs across different AWS accounts.
- Resolution of the private domain `corp.internal` hosted in a Route 53 Private Hosted Zone (PHZ) in a shared-services VPC.

Which TWO actions should the Solutions Architect take to migrate these workloads and configure the network connectivity?

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

Cevabı ve açıklamayı göster

Cevap: Use VMware HCX Replication-Assisted vMotion (RAV) to migrate the Oracle database VM and other application workloads to enable parallel replication with a zero-downtime hot switchover.; Deploy VMware Cloud (VMC) Transit Connect to connect the SDDC to an AWS Transit Gateway, and associate the Direct Connect Gateway with the Transit Connect to enable transitive routing between the SDDC, spoke VPCs, and the on-premises environment.

Cevap

To migrate the workloads with zero-downtime switchover and configure transitive routing, the Solutions Architect should use VMware HCX Replication-Assisted vMotion (RAV) for the migration, and deploy VMware Cloud Transit Connect to connect the SDDC to the AWS Transit Gateway while associating the Direct Connect Gateway with the Transit Connect.
Using VMware HCX Replication-Assisted vMotion (RAV) allows the parallel replication of multiple virtual machines while executing a live, zero-downtime switchover (vMotion) for the database and application workloads, satisfying the zero replication-induced downtime requirement. Furthermore, deploying VMware Cloud Transit Connect (VTGW) and associating the Direct Connect Gateway with it enables transitive routing between the VMware Cloud on AWS SDDC, on-premises data center, and the spoke VPCs, satisfying the hybrid connectivity and routing requirements.

Adım Adım Çözüm

1
Evaluate the downtime requirements for the migration phase.
Identify that the Oracle database requires zero replication-induced downtime, which rules out HCX Bulk Migration.
HCX Bulk Migration forces a VM reboot during switchover, whereas HCX Replication-Assisted vMotion (RAV) enables parallel bulk replication combined with a zero-downtime live vMotion switchover.
2
Determine the network routing architecture required for transitive routing.
Select VMware Cloud Transit Connect to connect the SDDC and customer spoke VPCs, and associate the Direct Connect Gateway with it.
Direct Connect Gateway alone does not support transitive VPC-to-VPC or VPC-to-VMC routing when attached directly to Virtual Private Gateways. Transit Connect (VTGW) resolves this by acting as a hub that supports transitive routing.
3
Identify and exclude invalid DNS and routing configuration options.
Eliminate options suggesting direct Private Hosted Zone association with the VMC management VPC, or direct DXGW-to-VGW transitive routing.
These violate AWS networking rules and limitations regarding cross-account resource ownership and routing transit limits.

Anahtar Kavram

VMware Cloud on AWS hybrid migration using HCX RAV and hybrid network routing with Transit Connect and Direct Connect Gateway.
Soru 1825Soru

A financial services institution is designing a hybrid and multi-account network topology. The environment comprises 30 spoke VPCs divided equally across the us-east-1 and us-west-2 Regions, managed under a single organization in AWS Organizations. The network design must connect all spoke VPCs to an on-premises data center. The primary connection must be a high-speed AWS Direct Connect connection, with a backup path using AWS Site-to-Site VPN connections. Traffic from AWS to the on-premises data center must default to the Direct Connect link and automatically fail over to the VPN connections if the Direct Connect link becomes unavailable. The design must minimize administrative routing complexity and support transitive routing between all spoke VPCs and the on-premises network. Which TWO actions should the Solutions Architect take to implement this architecture? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Create an AWS Transit Gateway in each Region, peer the two Transit Gateways, and attach the local spoke VPCs to their respective local Transit Gateway. Associate a central AWS Direct Connect Gateway with both Transit Gateways using a Transit Virtual Interface (Transit VIF) for the Direct Connect connection.; Establish AWS Site-to-Site VPN connections from the on-premises customer gateway to each Transit Gateway. Configure BGP dynamic routing on both the Direct Connect and VPN paths, and advertise the on-premises IP ranges to AWS with a shorter AS path over the Direct Connect connection than over the VPN connections.

Cevap

The correct architecture requires creating an AWS Transit Gateway in each Region, peering them, attaching spoke VPCs, and associating a central AWS Direct Connect Gateway using a Transit Virtual Interface. For high availability with automatic failover, establish AWS Site-to-Site VPN connections and use BGP dynamic routing, prepending the AS path on the VPN path to ensure the Direct Connect connection is the preferred path.
The correct solution involves deploying AWS Transit Gateway in each Region, peering them, and connecting the spoke VPCs to their local Transit Gateway to provide scalable hub-and-spoke transitive routing. An AWS Direct Connect Gateway is associated with the Transit Gateways using a Transit VIF to establish the primary high-speed connection. To configure the automatic failover, AWS Site-to-Site VPN connections are established to the Transit Gateways, and BGP dynamic routing is configured on both paths. By prepending the AS path on the VPN advertisements, AWS will prefer the Direct Connect path for outbound traffic to on-premises, failing over to the VPN only if the Direct Connect link fails.

Adım Adım Çözüm

1
Deploy AWS Transit Gateways in both Regions (us-east-1 and us-west-2) and peer them.
Establishes a hub-and-spoke transit network that allows inter-VPC and cross-region routing.
Transit Gateways provide centralized routing and scale efficiently to support 30 spoke VPCs.
2
Attach the local spoke VPCs to the Transit Gateway in their respective Regions.
Connects all 30 VPCs to the regional hubs.
Enables transitive routing between the spoke VPCs and the central transit network.
3
Associate a central Direct Connect Gateway with both Transit Gateways and create a Transit VIF.
Establishes the primary high-speed hybrid path between AWS and the on-premises datacenter.
Transit VIF is required to connect Direct Connect Gateway to Transit Gateways.
4
Establish AWS Site-to-Site VPN connections from the on-premises Customer Gateway to each Transit Gateway and configure BGP.
Creates the backup hybrid path.
Provides a secondary path over the public internet for redundancy.
5
Configure BGP routing by prepending the AS path on the VPN connection advertisements.
Ensures the Direct Connect path is preferred for outbound traffic, while the VPN path acts as a standby.
BGP path selection prefers shorter AS paths, ensuring automatic failover to VPN only when Direct Connect is down.

Anahtar Kavram

Designing highly available, scalable hybrid networks using AWS Transit Gateway, Direct Connect Gateway, and dynamic BGP routing with AS path prepending for automatic failover.
Soru 1826Soru

A logistics company, SwiftRoute, is modernizing its on-premises package tracking application by migrating it to Amazon ECS on AWS Fargate. The tasks must be deployed in private subnets, pull container images from Amazon ECR, and write tracking data to Amazon DynamoDB. The company's security policy strictly prohibits the use of NAT Gateways or Internet Gateways. Additionally, the solutions architect must minimize costs and operational overhead. Which configuration should the solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure interface VPC endpoints for Amazon ECR and Amazon ECS. Configure gateway VPC endpoints for Amazon S3 and Amazon DynamoDB, and associate them with the private subnets' route tables. Run the tasks on AWS Fargate using the awsvpc network mode.

Cevap

Configure interface VPC endpoints for Amazon ECR and Amazon ECS. Configure gateway VPC endpoints for Amazon S3 and Amazon DynamoDB, and associate them with the private subnets' route tables. Run the tasks on AWS Fargate using the awsvpc network mode.
The correct configuration uses interface VPC endpoints for ECR and ECS, and gateway VPC endpoints for S3 and DynamoDB. Fargate tasks run in the awsvpc network mode and require direct private network paths to access AWS APIs. ECR stores image layers in S3, requiring the S3 gateway endpoint. Gateway endpoints for S3 and DynamoDB are highly cost-effective and have no hourly fees, matching the low-cost requirement.

Adım Adım Çözüm

1
Identify the networking requirements for AWS Fargate tasks running in private subnets without public internet routes.
Recognize that the tasks require private network connectivity to Amazon ECR, Amazon ECS, Amazon S3, and Amazon DynamoDB.
Since NAT Gateways and Internet Gateways are prohibited, VPC endpoints must be used to keep traffic internal to the AWS network.
2
Determine the type of VPC endpoints required for each service.
Amazon ECR and Amazon ECS require interface VPC endpoints. Amazon S3 and Amazon DynamoDB support gateway VPC endpoints, which do not incur hourly charges.
Using gateway endpoints for S3 and DynamoDB is the most cost-effective and operationally simple method.
3
Verify Fargate network compatibility constraints.
Ensure that the tasks are configured with the awsvpc network mode, which is the only network mode supported by AWS Fargate.
Bridge and host network modes are unsupported on AWS Fargate and would fail during task execution.

Anahtar Kavram

AWS Fargate private networking with ECR, ECS, and DynamoDB using VPC Endpoints
Soru 1827Soru

An enterprise is designing a deployment strategy for a high-throughput financial transaction processing application that uses a proprietary TCP-based protocol. The application runs on Amazon EC2 instances within an Auto Scaling group and is exposed via a Network Load Balancer (NLB) in the `us-east-1` Region.

The company needs to implement a canary deployment strategy for new releases. The strategy must route 5%5\% of the production traffic to the new version (Green) while keeping 95%95\% on the current version (Blue). If the new version meets key performance indicators (KPIs) over a 22-hour monitoring window, all traffic must be routed to it. If any anomalies are detected, the deployment must support an instantaneous rollback to the Blue version without waiting for DNS records to expire, as client applications are known to ignore DNS Time to Live (TTL) settings and cache IP addresses indefinitely.

Which deployment strategy meets these requirements with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy the new version of the application in a separate Auto Scaling group behind a new NLB. Configure an AWS Global Accelerator accelerator with a single endpoint group in `us-east-1`. Add both the Blue NLB and the Green NLB as endpoints in the endpoint group. Set the endpoint weight for the Blue NLB to 9595 and the Green NLB to 55. After the 22-hour monitoring window, update the weights to 00 for Blue and 255255 for Green. If a rollback is needed, immediately set the Green NLB weight to 00.

Cevap

Deploy the new version in a separate Auto Scaling group behind a new NLB, and use AWS Global Accelerator to route traffic between the Blue and Green NLBs by adjusting their endpoint weights. This avoids DNS caching issues and provides instantaneous rollback capabilities.
The correct strategy uses AWS Global Accelerator to distribute traffic between the Blue and Green Network Load Balancers. Since Global Accelerator uses Anycast routing to direct traffic through static IP addresses, changes to the endpoint weights take effect within seconds. This allows the enterprise to split TCP traffic dynamically and roll back instantaneously, bypassing the client-side DNS caching issues that would plague a Route 53 weighted routing solution.

Adım Adım Çözüm

1
Analyze the application protocol and load balancer requirements.
The application uses a custom TCP-based protocol, which dictates the use of a Network Load Balancer (NLB) rather than an Application Load Balancer (ALB). ALB-only features, such as weighted target group routing, cannot be used.
Choosing the correct load balancer type is critical to ensuring compatibility with the proprietary TCP-based protocol.
2
Evaluate the DNS caching constraints and potential solutions.
Using Route 53 weighted routing is disqualified because client applications ignore DNS TTLs and cache IP addresses. A solution operating at the IP routing layer is required.
Instantaneous rollback requires that client traffic shifting does not rely on client-side DNS cache expiration.
3
Assess AWS Global Accelerator as the traffic routing mechanism.
AWS Global Accelerator provides static IP addresses and Anycast routing. By adding both NLBs as endpoints in an endpoint group and adjusting their weights, traffic can be shifted immediately at the edge without DNS propagation delays.
This meets the constraint of zero-downtime, gradual canary routing and instantaneous rollback capability for TCP workloads.

Anahtar Kavram

AWS Global Accelerator weighted endpoints for TCP canary deployments
Soru 1828Soru

A Solutions Architect needs to set up centralized security monitoring across all AWS accounts in an organization using AWS Organizations. The architect wants to delegate security administration to a dedicated Security Tooling account and implement standardized security controls across different Organizational Units (OUs) using AWS Security Hub.

Arrange the steps in the correct order to configure AWS Security Hub with delegated administration and centralized configuration management.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence starts by enabling trusted access for Security Hub in the organization management account, followed by designating the Security Tooling account as the delegated administrator. Next, Security Hub is enabled and member accounts are associated from the delegated administrator account, and finally, centralized configuration policies are applied to the targeted Organizational Units (OUs).
To successfully establish central security governance using AWS Security Hub, you must first enable trusted access from the Organizations management account. Once trusted access is enabled, you can designate a member account (the Security Tooling account) as the delegated administrator. Following delegation, all administrative tasks, including enabling member accounts and applying configuration policies to OUs, must be executed directly from the designated delegated administrator account, not the management account.

Adım Adım Çözüm

1
Enable trusted access in the management account.
Allows AWS Organizations to integrate and share organizational structure information with AWS Security Hub.
This is a prerequisite for registering a delegated administrator in AWS Organizations.
2
Designate the Security Tooling account as the delegated administrator.
Gives the Security Tooling account permissions to manage Security Hub settings and policies for the organization.
Delegation allows management of security services to be segregated from the Organizations management account, conforming to the principle of least privilege.
3
Enable Security Hub and associate member accounts from the Security Tooling account.
Registers all current member accounts under the centralized Security Hub administration scope.
The delegated administrator must bring the accounts under management before standard configurations can be pushed to them.
4
Create and apply Security Hub configuration policies.
Applies security standards and checks consistently across target OUs.
Centralized configuration management allows targeting specific OUs with customized or standard security requirements.

Anahtar Kavram

Delegated Administration in AWS Organizations
Soru 1829Soru

An enterprise is implementing a multi-account strategy using AWS Organizations. The solutions architect is configuring federated access for a remote team of data engineers who must access Amazon S3 buckets across multiple target member accounts. The authentication flow must use the company's external SAML 2.0-compliant Identity Provider (IdP). The solutions architect has created the SAML identity provider object in each target AWS account. The data engineers must authenticate via the IdP and assume a specific cross-account IAM role named DataEngineerRole in the target accounts. However, during testing, the data engineers receive an "Access Denied" error immediately after authenticating with the IdP and attempting to redirect to the AWS Management Console. Which combination of configuration adjustments must the solutions architect perform to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Update the trust policy of DataEngineerRole in each target account to allow the sts:AssumeRoleWithSAML action for the federated SAML provider principal. Ensure the SAML assertion sent by the Identity Provider includes the https://aws.amazon.com/SAML/Attributes/Role and https://aws.amazon.com/SAML/Attributes/RoleSessionName attributes.

Cevap

Update the trust policy of the target IAM role to allow the sts:AssumeRoleWithSAML action for the federated SAML provider principal, and ensure the SAML assertion contains the mandatory Role and RoleSessionName attributes.
The correct solution involves configuring the target IAM role's trust policy to use the sts:AssumeRoleWithSAML action and reference the SAML provider's ARN as the trusted federated principal. Additionally, the external IdP must pass the mandatory AWS SAML attributes (Role and RoleSessionName) in its assertion so that AWS STS can validate the signature and generate temporary credentials.

Adım Adım Çözüm

1
Examine the IAM role's trust policy inside the target accounts.
Identify that the trust policy must trust the SAML provider resource and allow the sts:AssumeRoleWithSAML action, which is required for external identity provider assertions.
Standard role assumption (sts:AssumeRole) is meant for internal AWS IAM principals, whereas external SAML IdPs require the specific STS SAML API.
2
Configure the external SAML Identity Provider's claims mapping.
Add the mandatory AWS-specific attributes: Role (mapping to the SAML provider ARN and the target IAM role ARN) and RoleSessionName (mapping to a unique user identifier).
AWS STS requires these attributes in the SAML assertion to successfully evaluate permissions and map the federated session.

Anahtar Kavram

SAML 2.0 Federation Trust Policy and Attributes
Tahmini Süre:2m 30s
Soru 1830Soru

A company operates an online multiplayer game matchmaking service. The matchmaking application runs on Amazon EC2 instances in an Auto Scaling group (ASG) behind an Application Load Balancer. The application has a complex initialization process that takes about 10 minutes to load static assets and establish connections to external databases. During sudden peaks of player logins, the ASG scales out, but the newly launched instances take 10 minutes before they can process requests. During this initialization window, the target tracking policy launches multiple redundant batches of instances, leading to excessive resource provisioning and increased costs. Which configuration change will prevent the Auto Scaling group from launching unnecessary instances during the initialization period?

Cevabı ve açıklamayı göster

Cevap: Configure the target tracking scaling policy and increase the instance warmup time to match the application's 10-minute initialization period.

Cevap

Configure the target tracking scaling policy and increase the instance warmup time to match the application's 10-minute initialization period.
Configuring the target tracking scaling policy and increasing the instance warmup time to match the 10-minute initialization period ensures that the Auto Scaling group does not launch additional instances while the current batch is still bootstrapping. During the warmup period, the instances do not contribute to the scaling metric, preventing the policy from executing redundant scale-out actions.

Adım Adım Çözüm

1
Analyze the application behavior and resource provisioning pattern during scaling events.
The application requires a 10-minute bootstrap/initialization phase before it can serve traffic, but the Auto Scaling group's target tracking policy triggers subsequent scale-outs before the initial new instances start contributing to metric reduction.
This shows that the target tracking policy is evaluating the metric without factoring in the capacity of the instances that are currently launching and bootstrapping.
2
Identify the configuration parameter that controls how long the Auto Scaling group waits before newly launched instances contribute to the scaling metric.
The instance warmup parameter (specifically the 'Estimated Instance Warmup' for target tracking scaling policies) determines this duration.
Setting the warmup time to 10 minutes ensures that instances currently in the bootstrap phase are not counted as active capacity, and the scaling policy will not initiate further scale-outs based on outdated metrics until the warmup period expires.

Anahtar Kavram

Auto Scaling Instance Warmup Configuration
Soru 1831Soru

A research organization is designing a new cloud-native genomics analysis platform. The platform handles an OLTP workload consisting of DNA sequence metadata stored in a relational database, and raw sequencing files (each averaging 150 MB150\text{ MB}) stored in Amazon S3. The relational database requires dynamic horizontal read scaling to handle sudden spikes in query volume. The disaster recovery (DR) strategy requires replicating both the database and raw sequencing files from the primary account in `us-east-1` to a secondary account in `us-west-2` with an RPO of under 5 minutes5\text{ minutes} and an RTO of under 15 minutes15\text{ minutes}. All data must be encrypted at rest using Customer Managed Keys (CMKs) in AWS Key Management Service (AWS KMS) to support cross-account sharing. Audit logs from the platform's S3 buckets in both regions must be written directly to a centralized S3 bucket in a separate Security Account. Which of the following database and storage architectures meets these requirements while satisfying the RTO, RPO, and security compliance constraints?

Cevabı ve açıklamayı göster

Cevap: Deploy Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Configure Aurora Auto Scaling for the reader replicas in the primary cluster. Encrypt the database using customer managed KMS keys in both accounts, granting cross-account key usage permissions. Set up Amazon S3 Cross-Region Replication (CRR) between the source and destination buckets using customer managed KMS keys, allowing cross-account decryption in the replication role policy. In the Security Account, apply a bucket policy to the centralized logging bucket that explicitly allows s3:PutObject permissions from the primary and disaster recovery account IAM roles.

Cevap

Deploy Amazon Aurora Global Database with reader auto scaling in the primary region, using customer managed KMS keys to encrypt the database and Amazon S3 buckets to allow cross-account sharing and replication, and configure the destination centralized S3 bucket policy to allow writes from the member account IAM roles.
The correct architecture uses Amazon Aurora Global Database to achieve low replication latency, enabling a secondary cluster in the disaster recovery region to satisfy the RTO and RPO. Read scaling in the primary region is addressed by configuring Aurora Auto Scaling on reader instances. To support cross-account replication, customer managed KMS keys are required since AWS-managed KMS keys cannot be shared across accounts. Raw sequencing files are copied via S3 Cross-Region Replication (CRR) utilizing customer managed keys for decryption/encryption delegation. Finally, cross-account log delivery to the Security Account is permitted by configuring a bucket policy that grants write permissions to the source accounts' IAM roles.

Adım Adım Çözüm

1
Evaluate read scalability and cross-region database replication requirements.
Amazon Aurora Global Database provides sub-second replication latency across regions (meeting RPO and RTO) and supports scaling readers dynamically via Aurora Auto Scaling. Amazon RDS Multi-AZ standbys cannot serve read traffic.
To satisfy horizontal read scaling in the primary region and cross-region business continuity constraints.
2
Assess the encryption and cross-account sharing capabilities of AWS KMS key types.
Customer managed KMS keys (CMKs) must be utilized. AWS-managed KMS keys (such as aws/rds and aws/s3) cannot be shared with external AWS accounts, which would block cross-account database replication and S3 Cross-Region Replication decryption.
To satisfy security compliance requiring encryption at rest while maintaining cross-account functionality.
3
Determine S3 replication scheduling to meet the required recovery point objective.
Configure S3 Cross-Region Replication (CRR) with the replication role authorized to use the customer managed keys. AWS DataSync running on a 12-hour schedule is rejected as it violates the 5-minute RPO constraint.
To ensure continuous replication of genomics raw files within the 5-minute RPO window.
4
Evaluate S3 bucket policy requirements for cross-account log shipping.
The destination bucket in the Security Account must have a bucket policy that grants s3:PutObject permissions to the specific logging IAM roles in the source accounts.
Because IAM policies alone in source accounts cannot authorize access to resources owned by another AWS account.

Anahtar Kavram

Cross-account database and object storage replication with KMS customer managed keys and centralized logging permissions.
Tahmini Süre:2m 30s
Soru 1832Soru

A multinational enterprise is integrating two AWS Organizations following an acquisition. Organization A has a hub-and-spoke network in the us-east-1 Region centered around an AWS Transit Gateway (TGW-A). TGW-A connects to the on-premises datacenter using an existing 10 Gbps AWS Direct Connect (DX) connection with a Direct Connect Gateway (DXGW) and a Transit Virtual Interface (Transit VIF).

Organization B has its own AWS Organization with an independent Transit Gateway (TGW-B) in the us-east-1 Region, connecting multiple spoke VPCs and a Shared Services VPC.

A solutions architect must design a hybrid connectivity and DNS architecture for Organization B that meets the following requirements:
- Primary hybrid path: Use the existing DX connection in Organization A.
- Backup hybrid path: Implement an AWS Site-to-Site VPN over the internet to TGW-B with automatic failover.
- Network Isolation: Spoke VPCs in Organization B must not communicate with VPCs in Organization A, but both must communicate with the on-premises datacenter.
- Centralized Egress: All internet-bound (0.0.0.0/0) traffic from Organization B's spoke VPCs must route through an Egress VPC in Organization B. The design must minimize costs while ensuring high availability across multiple Availability Zones (AZs).
- Name Resolution: Spoke VPCs in Organization B must resolve DNS queries for internal services hosted in a Route 53 Private Hosted Zone (PHZ) managed within the Shared Services VPC.

Which architecture should the solutions architect design to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Submit a cross-account association proposal from Organization B to associate TGW-B with the DXGW, and accept it in Organization A. Deploy an AWS Site-to-Site VPN from the customer gateway to TGW-B, configuring BGP routing with AS Path prepending on the VPN path to make it the backup. In the Egress VPC, deploy a NAT Gateway in each of the two active AZs, and configure private route tables to route internet traffic to their local NAT Gateway. Associate the Route 53 Private Hosted Zone in the Shared Services VPC with all spoke VPCs in Organization B.

Cevap

Submit a cross-account association proposal from Organization B to associate TGW-B with the DXGW, and accept it in Organization A. Deploy an AWS Site-to-Site VPN from the customer gateway to TGW-B, configuring BGP routing with AS Path prepending on the VPN path to make it the backup. In the Egress VPC, deploy a NAT Gateway in each of the two active AZs, and configure private route tables to route internet traffic to their local NAT Gateway. Associate the Route 53 Private Hosted Zone in the Shared Services VPC with all spoke VPCs in Organization B.
The correct solution uses a cross-account Direct Connect Gateway (DXGW) association to directly link TGW-B with the existing DXGW, which is fully supported and avoids transitive routing limitations. It configures the VPN as a backup path using BGP AS Path prepending. For egress traffic, high availability is ensured by deploying a NAT Gateway in each Availability Zone, preventing cross-AZ transfer costs and single-point-of-failure risks. DNS resolution is enabled by explicitly associating the Private Hosted Zone with all spoke VPCs in Organization B.

Adım Adım Çözüm

1
Configure hybrid connectivity using Direct Connect Gateway cross-account association.
TGW-B is associated with the DXGW, enabling direct hybrid connectivity over the existing Direct Connect link without peering TGW-A and TGW-B.
Direct Connect Gateway supports direct association with multiple Transit Gateways across different AWS accounts and organizations, avoiding the need for Transit Gateway peering, which does not support transitive routing to a Direct Connect Gateway.
2
Deploy Site-to-Site VPN and configure BGP routing.
Active/passive failover configuration where Direct Connect is preferred over the VPN backup path.
By using AS Path prepending on the VPN customer gateway configuration, the on-premises router prefers the Direct Connect path due to a shorter AS path, while ensuring automatic failover to the VPN if the Direct Connect path becomes unavailable.
3
Design Egress VPC with a NAT Gateway in each Availability Zone.
Highly available and cost-efficient egress architecture.
Deploying a NAT Gateway per AZ ensures that an outage in one AZ does not affect internet egress for other AZs, and eliminates cross-AZ data transfer charges for internet-bound traffic.
4
Associate the Route 53 Private Hosted Zone with all spoke VPCs in Organization B.
Name resolution is enabled for all spoke VPCs in Organization B.
Route 53 Private Hosted Zones require explicit VPC association to resolve DNS records. Cross-account VPC association allows spoke VPCs to resolve records hosted in the Shared Services VPC.

Anahtar Kavram

Multi-Account and Cross-Organization Hybrid Connectivity and Routing Integration
Soru 1833Soru

An enterprise is centralizing its multi-account access management using AWS IAM Identity Center. The company wants to federate identities from an external SAML 2.0 identity provider (IdP) and ensure that user accounts and group memberships are automatically synchronized from the IdP. Which of the following configuration steps must be performed to establish this integration? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure SAML 2.0 federation in AWS IAM Identity Center by exchanging metadata files between the IdP and AWS, and then enable and configure System for Cross-domain Identity Management (SCIM) in AWS IAM Identity Center and the IdP.; Create permission sets in AWS IAM Identity Center to define access levels, and assign these permission sets to the synchronized groups and users for the target AWS accounts in the AWS Organization.

Cevap

Configuring SAML 2.0 federation and SCIM in AWS IAM Identity Center, and creating permission sets to assign to synchronized groups in the target accounts.
To establish federated access and automated user/group provisioning using AWS IAM Identity Center, the solutions architect must configure SAML 2.0 federation (by exchanging metadata between AWS and the IdP) and enable SCIM. The SCIM endpoint and access token allow the IdP to push identity synchronization. Furthermore, the administrator must define permission sets in AWS IAM Identity Center and assign them to the synchronized users or groups for the specific target AWS accounts.

Adım Adım Çözüm

1
Establish federation and synchronization between the external identity provider (IdP) and AWS IAM Identity Center.
SAML 2.0 authentication is enabled, and users/groups are provisioned automatically via SCIM.
AWS IAM Identity Center requires metadata exchange for authentication and SCIM for automated user/group provisioning.
2
Create and assign permission sets in AWS IAM Identity Center.
Synchronized users and groups are granted specific access levels in target AWS accounts.
Permission sets are the mechanism by which AWS IAM Identity Center maps access rights to users in specific accounts.

Anahtar Kavram

Centralized multi-account identity federation and provisioning using AWS IAM Identity Center and SCIM.
Tahmini Süre:2m 0s
Soru 1834Soru

A financial tech company is modernizing its transaction reconciliation system by migrating the backend database to an Amazon Aurora PostgreSQL cluster. The system's application logic is refactored to run on AWS Lambda. The API must be accessible only to client microservices running in different VPCs across several AWS accounts within the same AWS Organization, and all traffic must remain private. The Aurora database has a maximum connection limit of 500, whereas the client microservices can generate transient bursts of up to 10,000 requests per second. The Lambda functions require access to sensitive database credentials encrypted with an AWS KMS key. Which architecture most securely and reliably meets these requirements while preventing database connection exhaustion and performance degradation?

Cevabı ve açıklamayı göster

Cevap: Deploy the Lambda functions in the database VPC and configure Amazon RDS Proxy to manage database connection pooling. Set reserved concurrency limits on the Lambda functions to prevent account-level throttling. Create a private REST API in Amazon API Gateway with a resource policy restricting access to the organization's accounts. In each client VPC, create an Interface VPC Endpoint for API Gateway and access the API via the endpoint's DNS names. Encrypt the database credentials using a Customer Managed Key in AWS KMS, and grant the Lambda execution role decrypt permissions on this key.

Cevap

The correct architecture deploys the Lambda functions in the database VPC, manages connections with Amazon RDS Proxy, configures reserved concurrency, secures private cross-account access via API Gateway private endpoints and resource policies, and uses a Customer Managed Key in AWS KMS.
The correct architecture uses Amazon RDS Proxy to pool database connections, ensuring the database connection limits are not exceeded under peak load. Setting reserved concurrency limits on the Lambda functions protects the regional concurrency pool from exhaustion. Private cross-account API access is securely achieved by deploying Interface VPC Endpoints in the client VPCs and applying an API Gateway resource policy that limits access to the AWS Organization's accounts. Using a Customer Managed Key in AWS KMS enables key policy modifications necessary to delegate decrypt permissions to the Lambda execution role.

Adım Adım Çözüm

1
Analyze the database scale and connection limits.
Determine that direct database connections will be exhausted during transient bursts of 10,000 requests per second. Implement Amazon RDS Proxy to queue and reuse database connections.
Prevents database connection saturation while avoiding scaling bottlenecks.
2
Protect the regional concurrency limits.
Configure reserved concurrency on the Lambda functions to limit their maximum simultaneous executions.
Prevents bursty traffic from consuming all regional execution capacity and throttling other workloads in the account.
3
Design private cross-account endpoint routing.
Create an Amazon API Gateway private API. Apply a resource policy restricting access to the AWS Organization. Provision Interface VPC Endpoints in client VPCs and resolve endpoints using endpoint DNS names.
Ensures that traffic does not transit the public internet and VPC DNS name resolution functions across account boundaries.
4
Establish secure encryption and decryption delegation.
Encrypt the credentials with a Customer Managed Key in AWS KMS. Grant the Lambda execution role decrypt permissions on the key.
AWS-managed keys (like `aws/lambda`) cannot have their policies modified to delegate access, making a Customer Managed Key necessary.

Anahtar Kavram

Modernizing legacy workloads using secure private API Gateway configurations, database connection pooling with RDS Proxy, Lambda concurrency management, and proper KMS key policy delegation.
Soru 1835Soru

A retail company is migrating its legacy point-of-sale (POS) application consisting of 6 servers from an on-premises data center to AWS. The migration is being conducted using AWS Application Migration Service (MGN) over an AWS Direct Connect connection. The Direct Connect virtual interface is connected to an AWS Transit Gateway, which is attached to the Staging Area VPC. The company's security policy requires that all traffic to AWS remain entirely private, and no public IP addresses or internet pathways can be used. After installing the AWS Replication Agent on the on-premises servers, the Solutions Architect notes that the replication status on the AWS MGN console displays as 'Stalled' and data replication has not started. Which of the following configuration steps must the Solutions Architect take to successfully establish replication? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the security group assigned to the replication servers in the Staging Area VPC to allow inbound traffic on TCP port 1500 from the on-premises subnet range.; Configure the on-premises firewall to permit outbound traffic on TCP port 1500 to the Staging Area VPC subnet range.

Cevap

Configure the security group of the staging area replication servers to allow inbound traffic on TCP port 1500 from the on-premises subnet range, and configure the on-premises firewall to permit outbound traffic on TCP port 1500 to the Staging Area VPC subnet range.
Establishing data replication with AWS Application Migration Service requires allowing TCP port 1500 outbound from the source environment and inbound to the replication servers in the staging area. This allows the block-level replication stream to proceed.

Adım Adım Çözüm

1
Analyze the network configuration requirements of AWS MGN data replication.
Identify that the AWS Replication Agent requires outbound TCP port 1500 to replicate data blocks to the replication servers.
This is the primary data path for copying local disk changes to AWS.
2
Adjust security group configurations in the AWS Staging Area VPC.
The staging area replication servers now accept inbound connections from the on-premises IP address range on TCP port 1500.
The default security group settings do not allow on-premises agents to reach the replication servers without this rule.
3
Adjust firewall configurations in the on-premises data center.
The on-premises servers can establish connections to the staging area IP address range on TCP port 1500.
Outbound firewall rules must allow this replication traffic to prevent connection blocks.

Anahtar Kavram

AWS MGN utilizes TCP port 1500 for data replication from the source servers to the replication servers in the staging area, which must be allowed through firewalls and security groups.
Soru 1836Soru

A company uses an AWS CloudFormation template to manage a stateless web application. The application runs on Amazon EC2 instances within an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The ASG has a desired capacity of 8 instances. The company needs to deploy a new version of the application by updating the launch template with a new Amazon Machine Image (AMI). The deployment must maintain the full capacity of 8 instances at all times during the update to prevent performance issues. Which configuration of the `UpdatePolicy` attribute for the Auto Scaling group in the CloudFormation template meets this requirement?

Cevabı ve açıklamayı göster

Cevap: Configure an `AutoScalingRollingUpdate` policy with `MinInstancesInService` set to 8 and `MaxBatchSize` set to 2.

Cevap

Configure an `AutoScalingRollingUpdate` policy with `MinInstancesInService` set to 8 and `MaxBatchSize` set to 2.
Configuring the `AutoScalingRollingUpdate` policy with `MinInstancesInService` set to 8 and `MaxBatchSize` set to a positive integer (such as 2) ensures that CloudFormation launches new instances first before terminating old instances. Because the minimum instances in service is equal to the desired capacity, CloudFormation must temporarily scale out the Auto Scaling group to maintain 8 healthy instances throughout the rolling update.

Adım Adım Çözüm

1
Analyze the capacity constraints during the deployment.
The application must maintain its full serving capacity of 8 instances throughout the update process.
This is necessary to prevent performance degradation under peak load.
2
Determine the correct CloudFormation update policy parameters.
Set `MinInstancesInService` to 8 and `MaxBatchSize` to a positive integer.
Setting `MinInstancesInService` to the desired capacity (8) forces CloudFormation to launch new instances before terminating old ones. The `MaxBatchSize` controls how many instances are updated in each batch.

Anahtar Kavram

Using CloudFormation AutoScalingRollingUpdate policies to manage deployment capacity and prevent downtime.
Soru 1837Soru

A software-as-a-service (SaaS) provider uses AWS Organizations to manage multiple AWS accounts. The security team wants to centralize AWS CloudTrail logs from all member accounts into a single Amazon S3 bucket located in a dedicated Security account. The security policy dictates that the logs must be encrypted at rest using an AWS Key Management Service (KMS) key. Which strategy should the solutions architect implement to configure this logging and encryption mechanism with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket in the Security account with a bucket policy allowing the CloudTrail service principal to write objects, using the aws:PrincipalOrgID condition to restrict access to the organization. Encrypt the bucket using a Customer Managed Key (CMK) in the Security account, with a key policy that grants CloudTrail permissions to generate data keys and decrypt.

Cevap

Configure the S3 bucket in the Security account with a bucket policy allowing the CloudTrail service principal to write objects, using the aws:PrincipalOrgID condition to restrict access to the organization. Encrypt the bucket using a Customer Managed Key (CMK) in the Security account, with a key policy that grants CloudTrail permissions to generate data keys and decrypt.
The correct strategy requires configuring a resource-based S3 bucket policy in the Security account that explicitly allows the CloudTrail service principal (`cloudtrail.amazonaws.com`) to write objects, restricted to the organization using the `aws:PrincipalOrgID` condition. Additionally, because AWS-managed keys (like `aws/s3`) cannot have their key policies modified for cross-account access, a Customer Managed Key (CMK) must be used. The CMK's key policy must explicitly allow the CloudTrail service principal to perform `kms:GenerateDataKey*` and `kms:Decrypt` operations.

Adım Adım Çözüm

1
Set up a centralized S3 bucket in the Security account.
An S3 bucket is created to store logs from all member accounts.
This establishes the target storage for cross-account logging.
2
Apply a bucket policy allowing the CloudTrail service principal to perform s3:PutObject, using aws:PrincipalOrgID in the condition block.
CloudTrail from any account belonging to the organization can write logs to the bucket.
This restricts access to the organization's member accounts while allowing the CloudTrail service principal to write objects.
3
Create a Customer Managed Key (CMK) in the Security account with a policy allowing CloudTrail to execute kms:GenerateDataKey* and kms:Decrypt.
CloudTrail service in member accounts is authorized to use the KMS key to encrypt log files.
AWS-managed keys (such as aws/s3) cannot be shared or modified for cross-account operations, making a Customer Managed Key necessary.

Anahtar Kavram

Cross-account centralized resource policies and KMS CMK sharing boundaries under AWS Organizations.
Tahmini Süre:2m 0s
Soru 1838Soru

A financial services corporation is implementing a centralized governance model for its AWS environment, which consists of 65 member accounts managed under AWS Organizations. The security team requires a centralized logging architecture that aggregates all AWS CloudTrail logs across all accounts and regions into a single Amazon S3 bucket. The S3 bucket will reside in a dedicated Log Archive account. The solution must ensure that all log files are encrypted at rest using a customer managed KMS key, and log integrity validation must be enabled. Additionally, member accounts must be prevented from disabling CloudTrail logging or altering the centralized trail configuration, while developers in the member accounts must retain their existing administrative permissions. Which combination of configurations will meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create an organizational trail in AWS CloudTrail from the management account, configured to send logs to the central S3 bucket in the Log Archive account. Configure the S3 bucket policy in the Log Archive account to grant s3:PutObject and s3:GetBucketAcl permissions to the cloudtrail.amazonaws.com service principal. Create a customer managed KMS key in the Log Archive account, and configure its key policy to allow the cloudtrail.amazonaws.com service principal to perform kms:GenerateDataKey* and kms:DescribeKey operations. Apply a Service Control Policy (SCP) to the member accounts' Organizational Unit (OU) that denies the cloudtrail:DeleteTrail, cloudtrail:UpdateTrail, and cloudtrail:StopLogging actions.

Cevap

Create an organizational trail in AWS CloudTrail, configure the destination S3 bucket policy to trust the CloudTrail service principal, use a customer managed KMS key with a key policy that allows the CloudTrail service principal to generate data keys, and use an SCP to deny trail modification.
The correct solution involves creating an organizational trail from the management account, which centralizes the logs in the S3 bucket. The S3 bucket policy must allow the cloudtrail.amazonaws.com service principal to write objects to the bucket. Because the logs are encrypted using a customer managed KMS key in the Log Archive account, the KMS key policy must explicitly allow the cloudtrail.amazonaws.com service principal to generate data keys and describe the key. Finally, the Service Control Policy (SCP) is applied to the member accounts to prevent disabling or modifying the trail.

Adım Adım Çözüm

1
Determine the logging strategy scope.
Create an organizational trail from the management account of the organization.
An organizational trail automatically ensures that events from all regions and member accounts are logged and consolidated.
2
Configure the S3 bucket policy.
Grant s3:PutObject and s3:GetBucketAcl permissions to the cloudtrail.amazonaws.com service principal.
CloudTrail log delivery is performed by the CloudTrail service principal, which needs cross-account access to write to the Log Archive S3 bucket.
3
Configure the encryption strategy.
Create a customer managed KMS key in the Log Archive account and modify its key policy to allow the cloudtrail.amazonaws.com service principal to execute kms:GenerateDataKey* and kms:DescribeKey.
AWS-managed KMS keys do not support policy modification and cannot be shared cross-account, so a customer managed key is required to permit cross-account encryption by CloudTrail.
4
Apply governance guardrails.
Attach an SCP to the member accounts' OU that denies destructive CloudTrail actions.
SCPs define boundary permissions for member accounts, preventing developers with admin privileges from disabling or deleting the trail while maintaining their administrative access.

Anahtar Kavram

Cross-account centralized CloudTrail logging with KMS CMK encryption and SCP guardrails
Soru 1839Soru

An enterprise uses AWS Organizations to manage multiple member accounts. A solutions architect is designing a centralized auditing solution using AWS Config. The configuration history and configuration snapshots from all member accounts must be delivered to a single Amazon S3 bucket located in a dedicated Security account. The S3 bucket must be encrypted using an AWS KMS key. The solution must ensure that member account administrators cannot disable AWS Config recorders or delivery channels. The S3 bucket policy and KMS key policy must follow the principle of least privilege. Which two actions should the solutions architect perform to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: In the Security account, configure the S3 bucket policy to allow the AWS Config service principal (config.amazonaws.com) to perform s3:PutObject and s3:GetBucketAcl actions, restricted by the AWS Organization ID using the aws:PrincipalOrgID condition. Configure the KMS customer managed key (CMK) policy to allow the AWS Config service principal to perform kms:GenerateDataKey and kms:Decrypt actions, restricted by the same organization condition.; In the organization's management account, create a Service Control Policy (SCP) that denies config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:StopConfigurationRecorder, and config:PutConfigurationRecorder actions unless the caller is a specific administrative IAM role, and attach this SCP to the organization's root or member organizational units (OUs).

Cevap

To meet the requirements, the solutions architect must configure the S3 bucket policy and KMS CMK key policy in the Security account to permit the AWS Config service principal (config.amazonaws.com) to write objects and generate data keys, while restricting access to the AWS Organization. Additionally, a Service Control Policy (SCP) should be applied to prevent administrators in member accounts from deleting or disabling the AWS Config recorders and delivery channels.
The correct solution combines a resource-based policy configuration in the centralized Security account with organizational control policies in the management account. First, AWS Config requires S3 permissions (s3:PutObject and s3:GetBucketAcl) and KMS permissions (kms:GenerateDataKey and kms:Decrypt) granted directly to its service principal (config.amazonaws.com) in the target resource policies. Restricting this access using the aws:PrincipalOrgID condition key ensures only accounts within the organization can use these resources. Second, a Service Control Policy (SCP) is the correct mechanism to enforce governance across member accounts by denying the ability to delete or stop the configuration recorder and delivery channel, overriding local administrator permissions.

Adım Adım Çözüm

1
Create a centralized S3 bucket and a KMS Customer Managed Key (CMK) in the Security account.
An encrypted S3 bucket is prepared to receive the AWS Config data.
This establishes the target location for centralized logging with compliance-grade encryption.
2
Configure the S3 bucket policy and KMS key policy to trust the AWS Config service principal (config.amazonaws.com) while applying a condition for aws:PrincipalOrgID.
AWS Config in any organization member account can securely write logs to the S3 bucket and generate data keys for encryption.
Resource policies are required for cross-account logging, and the service principal must be granted access directly because the logs are delivered by the service itself.
3
Apply an SCP in the organization's management account to deny delete and stop actions on AWS Config resources for all member accounts.
Member account administrators are blocked from disabling AWS Config compliance tracking.
SCPs provide organization-wide guardrails that override member account administrator permissions.

Anahtar Kavram

Centralized Config Logging with Cross-Account KMS CMK and SCP Guardrails
Tahmini Süre:2m 0s
Soru 1840Soru

A financial services company is designing a new multi-region payment processing system with the following database and storage requirements:

1. An OLTP database workload that requires a Recovery Point Objective (RPO) of less than 11 second and a Recovery Time Objective (RTO) of less than 11 minute across two AWS regions. The read traffic is highly dynamic and spikes unpredictably.
2. A centralized audit logging storage solution where application logs from multiple AWS accounts must be consolidated into a single S3 bucket in a dedicated security account. The logs must be encrypted at rest, and the encryption key must support cross-account access delegation.

Which two configurations should the Solutions Architect select to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure an Amazon Aurora Global Database with the primary cluster in the main region and a secondary cluster in the recovery region. Enable Aurora Replica Auto Scaling for the reader instances in both regions to scale dynamically based on CPU utilization.; Configure the central S3 bucket in the security account to use Server-Side Encryption with AWS KMS (SSE-KMS) utilizing a customer managed key. Update both the KMS key policy and the S3 bucket policy to allow cross-account write access from the application accounts.

Cevap

The correct configurations are: setting up an Amazon Aurora Global Database with Aurora Replica Auto Scaling for read scaling, and using a customer managed key with SSE-KMS for the centralized S3 bucket while updating both the KMS key policy and the S3 bucket policy.
Amazon Aurora Global Database replication lag is typically less than 11 second, satisfying the RPO target of less than 11 second, and failover can be completed within 11 minute, satisfying the RTO target. Auto Scaling reader instances dynamically handle read spikes in both the primary and secondary regions. For the central S3 logging bucket, AWS-managed keys (aws/s3) do not support cross-account access delegation because their key policies cannot be customized. Using a customer managed KMS key allows policy modification to delegate cross-account access, and updating the key policy along with the S3 bucket policy enables cross-account write access.

Adım Adım Çözüm

1
Evaluate the database tier requirements for RPO (<1< 1 s), RTO (<1< 1 m), and cross-region availability.
Identify that Amazon Aurora Global Database provides sub-second replication lag and fast region failover, meeting the RPO/RTO goals.
A replication-based global database is required because snapshot replication or active-passive setups with long recovery processes cannot meet these sub-second RPO and low RTO requirements.
2
Determine the database read scaling design.
Configure Aurora Replica Auto Scaling to handle dynamic and unpredictable read spikes.
This scales reader instances horizontally in both regions, whereas standard RDS standby replica instances remain passive and cannot scale or serve read traffic.
3
Select the correct encryption key type for the cross-account S3 logging destination.
Choose an AWS KMS customer managed key (CMK) and configure both the KMS key policy and S3 bucket policy.
Default AWS-managed keys (aws/s3) do not support policy modification and cannot be shared across accounts, meaning only customer managed keys allow cross-account delegation.

Anahtar Kavram

Designing highly available, low-latency database architectures using Amazon Aurora Global Database for multi-region replication and implementing cross-account resource encryption using S3 and AWS KMS customer managed keys.
ÖncekiSayfa 92 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin