Tüm alıştırma soruları

1964 soru

Soru 601Soru

A solutions architect is designing a centralized logging architecture for a company's AWS Organization. The company wants to enable an organization-wide AWS CloudTrail trail in the management account and deliver all log files to a centralized Amazon S3 bucket located in a dedicated Security account. The security team requires all log files to be encrypted at rest using a Customer Managed Key (CMK) in AWS KMS. Which of the following configurations are required to implement this architecture? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the S3 bucket policy in the Security account to allow s3:PutObject and s3:GetBucketAcl actions for the cloudtrail.amazonaws.com service principal, with a condition checking that the aws:PrincipalOrgID matches the company's organization ID.; Create a customer managed KMS key in the Security account, and configure its key policy to grant the cloudtrail.amazonaws.com service principal permissions to perform kms:GenerateDataKey* and kms:DescribeKey actions.

Cevap

Configure the S3 bucket policy in the Security account to allow CloudTrail to write objects, restricted by the organization ID, and create a customer managed KMS key in the Security account with a key policy allowing CloudTrail to generate data keys and describe the key.
The correct solution involves configuring the S3 bucket policy in the destination Security account to allow access to the CloudTrail service principal (cloudtrail.amazonaws.com), restricted by the organization ID (aws:PrincipalOrgID) to ensure only logs from the company's organization are accepted. Furthermore, since AWS managed keys cannot be configured with custom policies to grant cross-account permissions, a customer managed KMS key must be created, and its key policy must allow the CloudTrail service principal to perform generate data key and describe key actions.

Adım Adım Çözüm

1
Configure S3 bucket permissions in the Security account.
The S3 bucket policy is updated to allow the cloudtrail.amazonaws.com service principal to call s3:PutObject and s3:GetBucketAcl, restricted to the organization ID via the aws:PrincipalOrgID condition key.
This allows CloudTrail to write logs from any member account in the organization directly to the centralized bucket in the Security account while preventing unauthorized external write attempts.
2
Configure KMS key permissions in the Security account.
A customer managed KMS key is created and configured with a key policy that allows the cloudtrail.amazonaws.com service principal to use kms:GenerateDataKey* and kms:DescribeKey.
CloudTrail requires these permissions to generate data keys for encrypting log files on a per-account basis before delivering them. A customer managed key is required because AWS managed keys do not support policy modification for cross-account access.

Anahtar Kavram

Cross-account centralized logging using AWS CloudTrail requires configuring both resource-based permissions (S3 bucket policy) and encryption keys (KMS key policy) to trust the CloudTrail service principal, restricting access appropriately via organization-scoped condition keys.
Tahmini Süre:2m 0s
Soru 602Soru

A global container logistics company is migrating its operations to AWS, establishing a multi-account structure managed under AWS Organizations. The network topology uses a Hub-and-Spoke model where a central Network VPC is connected to multiple spoke VPCs and to the company’s on-premises data centers via AWS Transit Gateway (TGW) and AWS Direct Connect. The on-premises DNS servers manage the `onprem.cargo.internal` domain. The spoke accounts host private hosted zones (PHZs) for their respective services, such as `booking.aws.cargo.internal` and `tracking.aws.cargo.internal`.

The solution must meet the following requirements:
- On-premises clients must be able to resolve records within the `aws.cargo.internal` domain.
- Instances in all spoke VPCs must resolve records within the `onprem.cargo.internal` domain.
- Spoke VPCs must be able to resolve records in each other’s PHZs.

Which TWO steps should a solutions architect take to implement this DNS architecture? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy Route 53 Resolver inbound endpoints in the Network VPC, and configure the on-premises DNS servers to forward queries for the `aws.cargo.internal` domain and its subdomains to the inbound endpoint IP addresses.; For each spoke private hosted zone (PHZ), authorize VPC associations to the Network VPC and other spoke VPCs from the respective spoke accounts using the AWS CLI or SDK, and then associate the PHZs from the target VPC accounts.

Cevap

Deploying Route 53 Resolver inbound endpoints in the Network VPC for on-premises forwarding, and authorizing/associating the cross-account Private Hosted Zones with the respective VPCs using the Route 53 API.
Deploying Route 53 Resolver inbound endpoints in the Network VPC allows the on-premises DNS servers to forward queries for AWS private domains to AWS. For cross-account private hosted zone resolution, the spoke accounts must first authorize the associations for their hosted zones to other VPCs, and the associations must then be completed. This enables all spoke VPCs to resolve each other's private DNS records.

Adım Adım Çözüm

1
Deploy Route 53 Resolver inbound endpoints in the Network VPC.
On-premises clients can forward DNS queries for the `aws.cargo.internal` domain to the inbound endpoint IP addresses.
This enables inbound hybrid DNS resolution from the on-premises environment.
2
Authorize cross-account VPC associations for the spoke Private Hosted Zones.
The spoke accounts authorize the Network VPC and other spoke VPCs to associate with the hosted zones.
This is a prerequisite step in Route 53 when the private hosted zones and target VPCs reside in different AWS accounts.
3
Associate the spoke Private Hosted Zones with the authorized target VPCs.
Instances in any associated VPC can resolve the records of the associated private hosted zones.
This enables inter-VPC private DNS resolution without traversing external endpoints.

Anahtar Kavram

Route 53 Resolver endpoints and cross-account Private Hosted Zone association.
Soru 603Soru

A multinational retail conglomerate manages its AWS environment using AWS Organizations. The organization contains a Security account under a CoreServices Organizational Unit (OU), and fifty member accounts under a Production OU. To satisfy strict industry regulatory standards, the corporate security team mandates that all new Amazon Elastic Block Store (EBS) volumes created within the Production OU must be encrypted using a specific customer managed key (CMK). The security team wants to manage the key centrally within the Security account to control key rotation and audit access logs from a single location. The solution must prevent member account users from creating unencrypted volumes or using their local AWS-managed keys, while allowing production workloads to auto-scale and launch instances without manual intervention from the security team. Which of the following strategies should a solutions architect implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Customer Managed Key (CMK) in the Security account. Configure the key policy of this CMK to allow the member accounts to perform 'kms:DescribeKey', 'kms:Decrypt', and 'kms:CreateGrant' actions. Attach a Service Control Policy (SCP) to the Production OU that denies 'ec2:RunInstances' and 'ec2:CreateVolume' if the volume is not encrypted, or if the encryption key used does not match the CMK in the Security account. Configure local IAM policies in the member accounts to permit workloads to use the central CMK.

Cevap

Create a Customer Managed Key (CMK) in the Security account, configure its key policy to allow member accounts to perform key actions including 'kms:CreateGrant', and use an SCP to deny EBS volume creation that is not encrypted with this key, while configuring local IAM policies to allow workload access.
The correct strategy requires creating a Customer Managed Key (CMK) in the central Security account, modifying its key policy to grant usage permissions to the member accounts (specifically including 'kms:CreateGrant' to allow EBS to manage encryption keys on behalf of users), enforcing encryption using an SCP on the Production OU, and configuring local IAM policies to allow workloads access. This satisfies all security and operational requirements.

Adım Adım Çözüm

1
Create a Customer Managed Key (CMK) in the central Security account instead of using AWS-managed keys.
A CMK is created, which supports cross-account policy delegation.
AWS-managed keys cannot be shared across accounts.
2
Configure the CMK key policy to allow member accounts to perform 'kms:DescribeKey', 'kms:Decrypt', and 'kms:CreateGrant'.
Member account IAM principals can use the key, and AWS services can create grants on their behalf.
EBS and EC2 auto-scaling require these permissions to manage volume encryption.
3
Attach an SCP to the Production OU to deny 'ec2:RunInstances' and 'ec2:CreateVolume' unless the volume is encrypted with the specific CMK.
Unencrypted EBS volumes or volumes encrypted with other keys are prevented from being created in member accounts.
Ensures governance compliance across all member accounts in the OU.

Anahtar Kavram

Cross-account KMS key sharing and Service Control Policy guardrails
Soru 604Soru

A company is launching a flash sale campaign where web traffic is expected to instantly spike from 100 requests per second to 150,000 requests per second. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). Which configuration should a Solutions Architect recommend to ensure the load balancer handles this sudden traffic surge without dropping initial requests?

Cevabı ve açıklamayı göster

Cevap: Contact AWS Support to pre-warm the Application Load Balancer with the expected traffic metrics, and configure the EC2 Auto Scaling group to scale out proactively before the campaign starts.

Cevap

Contact AWS Support to pre-warm the Application Load Balancer with the expected traffic metrics, and configure the EC2 Auto Scaling group to scale out proactively before the campaign starts.
Pre-warming the Application Load Balancer (ALB) is the standard AWS best practice when preparing for a predictable, massive, and instantaneous traffic surge. Because standard ALB scaling takes time, pre-warming ensures that sufficient resources are provisioned beforehand. Additionally, proactively scaling out the EC2 instances before the event begins ensures the application tier has the compute capacity ready to process the requests.

Adım Adım Çözüm

1
Analyze the scale and rate of the traffic increase.
Traffic goes from 100 to 150,000 requests per second instantly, indicating an extreme flash traffic spike.
This rate of change exceeds standard automatic scaling speeds for both Application Load Balancers and EC2 instances.
2
Select the correct ELB scaling strategy.
Pre-warming the ALB ensures AWS provisions the necessary capacity in advance.
Default ALB auto-scaling is gradual and cannot keep pace with instant spikes of this magnitude.
3
Verify database and caching choices to eliminate incorrect architectures.
Avoid routing reads to RDS Multi-AZ standby instances or using Memcached for multi-AZ replication.
These choices represent fundamental architectural misconceptions regarding AWS service capabilities.

Anahtar Kavram

ELB pre-warming and proactive capacity planning for flash traffic events
Tahmini Süre:1m 0s
Soru 605Soru

An organization is designing a disaster recovery (DR) architecture for a non-critical internal HR portal. The application currently runs on Amazon EC2 instances behind an Application Load Balancer, with data stored in an Amazon RDS for MySQL database. The business requires a Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 4 hours. The architecture must minimize ongoing running costs in the secondary DR region. Which TWO options should the Solutions Architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Create daily snapshots of the Amazon RDS for MySQL database and copy them to the secondary AWS Region.; Create an Amazon Machine Image (AMI) of the EC2 instances, copy the AMI to the secondary AWS Region, and use AWS CloudFormation to deploy the compute infrastructure only when a disaster is declared.

Cevap

To meet the requirements, the Solutions Architect should copy daily database snapshots to the secondary region and use AWS CloudFormation with copied AMIs to deploy the compute resources only when a disaster occurs.
For an RTO of 4 hours and RPO of 24 hours, a Backup and Restore DR strategy is the most cost-effective solution. Copying daily database snapshots to the secondary region meets the 24-hour RPO, and using AWS CloudFormation along with copied AMIs to launch compute resources on-demand during a failover ensures the 4-hour RTO is met while keeping standby costs minimal.

Adım Adım Çözüm

1
Analyze RTO and RPO requirements.
The target RTO is 4 hours and RPO is 24 hours, which allows for a Backup and Restore strategy. Active-Active or warm standby strategies are not necessary and would violate the low-cost constraint.
Determining the correct disaster recovery pattern prevents over-provisioning and minimizes cost.
2
Determine the database DR mechanism.
Daily snapshots meet the 24-hour RPO. Copying these snapshots to the secondary region ensures data is available for restoration within the 4-hour RTO.
Database snapshots stored in a different region provide a secure and low-cost backup solution.
3
Determine the compute DR mechanism.
Create AMIs in the primary region, copy them to the secondary region, and use CloudFormation templates to provision the load balancer and instances only when needed.
This avoids paying for idle compute capacity in the secondary region, aligning with the cost-optimization constraint.

Anahtar Kavram

Disaster Recovery strategies (Backup & Restore) vs cost and RTO/RPO objectives
Soru 606Soru

An enterprise is establishing a multi-account governance framework using AWS Organizations. To comply with regulatory requirements, the solutions architect must enforce a Service Control Policy (SCP) that restricts resource provisioning to a subset of approved AWS Regions without disrupting essential global services or production workloads. Arrange the following steps in the correct order to design, test, and implement this governance control.

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

Cevabı ve açıklamayı göster

Cevap

The correct order begins with identifying global services to exempt, followed by creating the Service Control Policy (SCP) in the management account, attaching it to a sandbox OU, validating the policy's behavior with test resources, and finally attaching the SCP to the production OUs.
The correct order follows standard safe deployment practices and AWS best practices for managing SCPs. You must first identify which global services to exempt to prevent locking administrative actions. Next, you author the SCP with the appropriate conditions. To ensure safety, you must test the policy inside a sandbox/test OU first, validate the expected behavior (allowing permitted regions and blocking unpermitted ones), and only then promote the policy to production OUs.

Adım Adım Çözüm

1
Identify global services that require exemption from region restrictions.
A list of global AWS services such as IAM, Billing, and Route 53.
Excluding global services is critical because they operate out of global endpoints and would otherwise fail if restricted to specific regions.
2
Create the SCP in the management account.
An SCP containing the region restriction logic and the global service exemptions.
Designing the policy rules is necessary before any testing or deployment can take place.
3
Attach the SCP to a Sandbox or Test OU.
The policy rules are active only for accounts inside the test OU.
Applying guardrails to sandbox environments first prevents accidental disruption of production workloads during the validation phase.
4
Verify and validate policy constraints by launching resources in approved and unapproved regions within the test accounts.
Confirmation that workloads operate correctly in approved regions and are successfully denied in unapproved regions.
Testing validates that the policy conditions are working as intended and do not have unintended side effects.
5
Apply the validated SCP to the Production OUs.
The compliance control is enforced across all production workloads.
Once validated in sandbox, the control can be safely promoted to production OUs to satisfy governance requirements.

Anahtar Kavram

Enforcing multi-account regional governance using Service Control Policies (SCPs) requires identifying global service exemptions and applying policy changes sequentially through sandbox environments to prevent operational disruption.
Soru 607Soru

A solutions architect is designing a multi-account environment using AWS Organizations and AWS Control Tower for a large enterprise. The architecture must enforce custom guardrails, structure accounts into business-specific Organizational Units (OUs), and automatically deploy custom local network resources (such as VPCs and security groups) during account onboarding. The solutions architect decided to use AWS Control Tower Lifecycle Events linked to an Amazon EventBridge rule that triggers an AWS Lambda function for post-enrollment customization.

Arrange the steps in the correct chronological order to establish this governed environment and ensure all target accounts are automatically customized upon enrollment.

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

Cevabı ve açıklamayı göster

Cevap

To establish this environment and ensure all accounts are automated upon enrollment, the solutions architect must first launch the landing zone, create the custom OUs, apply guardrails, configure the EventBridge rules for lifecycle events, and finally enroll the member accounts via Account Factory.
The correct sequence starts with launching the landing zone and creating the custom OUs. Guardrails must be applied next to ensure immediate compliance. Crucially, the EventBridge rule for Lifecycle Events must be created before enrolling accounts to ensure that the orchestration workflow is active when the accounts are provisioned, allowing for automatic deployment of VPCs and security groups. Enrolling accounts is the final step that triggers this sequence.

Adım Adım Çözüm

1
Initialize AWS Organizations and launch the AWS Control Tower landing zone from the management account.
Deploys core AWS Control Tower architecture including Security and Sandbox OUs, and Log Archive and Audit accounts.
This establishes the foundation required for any multi-account governance setup.
2
Create custom OUs in AWS Control Tower.
Creates workload-specific OUs in the organizational directory.
OUs must exist to act as containers for member accounts and policy attachments.
3
Apply guardrails (SCPs and Config rules) to the custom OUs.
Enforces guardrail compliance policies on the selected OUs.
Enforces governance guardrails before accounts are placed in the OUs, avoiding any temporary compliance gaps.
4
Create the Amazon EventBridge rule that detects AWS Control Tower Lifecycle Events and targets AWS Lambda.
Prepares the event listener for the CreateManagedAccount event.
Ensures that the event-driven customization workflow is active before the accounts are created; otherwise, the creation events will not trigger the Lambda function.
5
Enroll member accounts using AWS Control Tower Account Factory into the target OUs.
Accounts are created, placed in OUs under the applied guardrails, and trigger the EventBridge rule to complete local setup.
This initiates the creation sequence, relying on pre-existing guardrails and event rules to secure and customize the accounts automatically.

Anahtar Kavram

AWS Control Tower Lifecycle Events and multi-account governance setup flow
Soru 608Soru

A company is configuring passwordless deployment pipelines from an external, OpenID Connect (OIDC)-compliant CI/CD platform to deploy application stacks across multiple member accounts in AWS Organizations. Each pipeline must be able to assume a deployment role in its respective target member account. Which of the following configurations are required to establish the trust relationship and enable this federated access? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure an IAM OIDC identity provider in each target member account, specifying the external CI/CD provider's issuer URL and the configured audience (client ID).; In each target member account, create an IAM role with a trust policy that allows the sts:AssumeRoleWithWebIdentity action and includes conditions restricting access based on OIDC claim parameters.

Cevap

To establish federated OIDC access, you must configure an IAM OIDC identity provider in each member account with the provider's URL and client ID, and then create an IAM role in each member account with a trust policy that allows the sts:AssumeRoleWithWebIdentity action and validates specific OIDC claims.
Establishing web identity federation with an OIDC provider requires registering the provider in IAM using its issuer URL and audience (client ID). To assume the roles, the trust policy must explicitly allow the 'sts:AssumeRoleWithWebIdentity' action, which allows the external client to exchange its OIDC token for temporary AWS credentials. Restricting access using conditions (like audience or subject) ensures that only the specified external pipelines can assume the role.

Adım Adım Çözüm

1
Register the OIDC Identity Provider in IAM
AWS IAM trusts the token signing keys from the external OIDC provider.
This establishes a cryptographic trust chain between AWS and the external Identity Provider.
2
Create the IAM role with the correct trust action and conditions
An IAM role is created that can only be assumed by external clients presenting valid tokens from the trusted provider.
Web identity federation requires sts:AssumeRoleWithWebIdentity, and validating conditions like aud and sub ensures that only authorized pipelines can assume the role.

Anahtar Kavram

OIDC Federation and Role Trust Policies
Soru 609Soru

An enterprise manages a multi-account AWS environment using AWS Organizations. The organization has set up AWS IAM Identity Center in a delegated administrator security account, integrated with Okta as the external identity provider (IdP) via SAML 2.0 and SCIM. The security team is implementing Attribute-Based Access Control (ABAC) to restrict access to sensitive Amazon S3 buckets located in a Shared Services account. Corporate users must only access buckets where the bucket's CostCenter tag matches their corporate cost center, which is stored in Okta as the costCenter profile attribute.

During testing, two issues are observed:
1. Users federated through AWS IAM Identity Center are denied access to the S3 buckets in the Shared Services account, despite having the correct costCenter value in Okta and matching tags on the S3 buckets.
2. A legacy third-party auditing tool that bypasses IAM Identity Center and federates directly via a custom IAM SAML identity provider in each member account fails to assume its target role, returning an 'Access Denied' error when attempting to pass the cost center as a session tag.

Which of the following actions must the Solutions Architect take to resolve these issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable 'Attributes for access control' in AWS IAM Identity Center and map the SCIM attribute costCenter to the key CostCenter. Ensure the IAM policy attached to the permission sets in the member accounts explicitly grants permissions to the S3 buckets in the Shared Services account, rather than relying on Service Control Policies (SCPs) to grant the permissions.; In the member accounts, update the trust policy of the IAM role used by the auditing tool to include the sts:TagSession action in addition to sts:AssumeRoleWithSAML. Configure the Okta SAML assertion to include the cost center attribute under the https://aws.amazon.com/SAML/Attributes/PrincipalTag:CostCenter attribute namespace.

Cevap

Enable 'Attributes for access control' in AWS IAM Identity Center, mapping Okta's costCenter to the key CostCenter, and ensure that local permission sets explicitly grant S3 access. In addition, update the auditing tool's IAM role trust policy in the member accounts to permit sts:TagSession alongside sts:AssumeRoleWithSAML, and format the SAML assertion with the PrincipalTag namespace.
To successfully implement ABAC across accounts with AWS IAM Identity Center, the 'Attributes for access control' feature must be enabled to map Okta's SCIM attribute to the AWS tag key. In addition, since Service Control Policies (SCPs) do not grant permissions, the permission sets must explicitly allow the S3 actions. For direct SAML federation, the role's trust policy must include the sts:TagSession action to authorize the IdP to send session tags, and the SAML assertion must format the attributes with the proper PrincipalTag namespace.

Adım Adım Çözüm

1
Enable session tags in AWS IAM Identity Center.
Configured the 'Attributes for access control' feature and mapped the SCIM-synchronized costCenter attribute to the CostCenter tag key.
This allows IAM Identity Center to pass user attributes as session tags (aws:PrincipalTag/CostCenter) during federation.
2
Verify local permissions for the S3 bucket.
Added explicit S3 permissions (s3:GetObject, s3:PutObject) in the IAM Identity Center permission sets for the member accounts.
SCPs act as filters and do not grant permissions. Local IAM policies must grant the actual S3 access.
3
Configure SAML trust policy for session tagging.
Updated the custom IAM role trust policy in the member accounts to include the sts:TagSession action.
Without sts:TagSession in the trust policy, attempts to pass session tags during direct SAML federation will return an Access Denied error.
4
Configure SAML assertion attributes in Okta.
Configured Okta to send the cost center attribute under the 'https://aws.amazon.com/SAML/Attributes/PrincipalTag:CostCenter' namespace.
This matches the required namespace format for AWS to map SAML attributes directly into principal session tags.

Anahtar Kavram

Multi-Account Identity Federation and Session Tags
Soru 610Soru

A company is configuring single sign-on access for its database administrators to manage resources in a dedicated database member account under AWS Organizations. The database administrators authenticate using a third-party SAML 2.0 Identity Provider (IdP). A Solutions Architect needs to set up the trust relationship in the database member account to allow these users to assume an IAM role named 'DB-Admin-Role'. Which two actions must the Solutions Architect take to configure this federated trust?

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

Cevabı ve açıklamayı göster

Cevap: Create an IAM SAML identity provider in the database member account by uploading the XML metadata document from the third-party IdP.; Configure the trust policy of the target IAM role to define the Principal as the ARN of the IAM SAML provider and set the Action to sts:AssumeRoleWithSAML.

Cevap

Create an IAM SAML identity provider in the database member account using the XML metadata from the IdP, and configure the target IAM role's trust policy to define the SAML provider's ARN as the Principal with the action set to `sts:AssumeRoleWithSAML`.
To establish SAML federation within a member account, a Solutions Architect must first configure a local IAM SAML provider using the IdP metadata. Then, the trust policy of the destination IAM role must be updated to trust this provider's ARN and authorize the `sts:AssumeRoleWithSAML` action.

Adım Adım Çözüm

1
Create the SAML identity provider in the member account.
An IAM SAML provider resource with a unique ARN is generated in the database member account.
This establishes the cryptographic trust between AWS and the external SAML IdP within the scope of that specific account.
2
Update the trust policy of the target role DB-Admin-Role.
The role's trust policy lists the SAML provider ARN as the Principal and permits sts:AssumeRoleWithSAML.
This allows users authenticated by the SAML IdP to assume the role and obtain temporary security credentials.

Anahtar Kavram

SAML 2.0 Federation Trust Configuration in Multi-Account Environments
Soru 611Soru

A multinational retail company manages its multi-account environment on AWS using AWS Organizations. The central infrastructure is hosted in a Shared Services account, while application workloads run in multiple Spoke accounts. The company recently acquired a regional retail chain that operates an on-premises data center with a local Active Directory domain (corp.acquired.internal). A Transit Gateway connects the central Shared Services VPC, the Spoke VPCs, and the on-premises network via a Direct Connect connection.

The solutions architect must implement a hybrid DNS resolution strategy with the following requirements:
1. Instances in the Spoke VPCs must be able to resolve resources in the corp.acquired.internal domain.
2. On-premises servers must be able to resolve resources in a Route 53 Private Hosted Zone (PHZ) named prod.enterprise.aws, which is hosted in the Shared Services account.

Which TWO configuration steps must the solutions architect perform to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the Shared Services account, create a Route 53 Resolver outbound endpoint in the Shared Services VPC. Create an outbound Resolver forwarding rule for corp.acquired.internal that targets the on-premises DNS servers, share this rule with the organization using AWS Resource Access Manager (RAM), and associate the rule with the Spoke VPCs.; Authorize the cross-account association of the prod.enterprise.aws Private Hosted Zone with the Spoke VPCs using the Route 53 API in the Shared Services account, and then associate the Spoke VPCs with the Private Hosted Zone in each respective Spoke account.

Cevap

The correct architecture requires: (1) Creating an outbound Route 53 Resolver endpoint in the Shared Services VPC, creating a forwarding rule for the acquired domain targeting the on-premises DNS servers, sharing the rule with the organization via AWS RAM, and associating it with the Spoke VPCs. (2) Authorizing the association of the central Private Hosted Zone with the Spoke VPCs using the Route 53 API in the Shared Services account, and then associating the Spoke VPCs with the Private Hosted Zone from each Spoke account.
To satisfy both requirements, the solution must establish cross-account DNS resolution and hybrid resolution. The option to create a Route 53 Resolver outbound endpoint in the Shared Services VPC, define a forwarding rule for the on-premises domain, share it via AWS RAM, and associate it with the Spoke VPCs addresses the first requirement. The option to authorize the cross-account association of the Private Hosted Zone with the Spoke VPCs using the Route 53 API, followed by associating the Spoke VPCs in the Spoke accounts, addresses the second requirement by allowing the Spoke VPCs to query the central Private Hosted Zone.

Adım Adım Çözüm

1
Configure Outbound DNS Resolution for Spoke VPCs
Created a Route 53 Resolver outbound endpoint in the Shared Services VPC, created a forwarding rule for corp.acquired.internal pointing to the on-premises DNS servers, and shared the rule with the Spoke accounts via AWS Resource Access Manager (RAM).
This allows all Spoke VPCs associated with the shared rule to forward DNS queries for the acquired on-premises domain over the Transit Gateway/Direct Connect connection to the on-premises Active Directory DNS servers.
2
Authorize and Establish Cross-Account Private Hosted Zone Association
Authorized the cross-account association of the prod.enterprise.aws Private Hosted Zone (PHZ) with the Spoke VPCs from the Shared Services account, and then associated each Spoke VPC with the PHZ in the Spoke accounts.
This enables instances within the Spoke VPCs to resolve records in the prod.enterprise.aws hosted zone which resides in the Shared Services account.

Anahtar Kavram

Cross-account Private Hosted Zone association and Route 53 Resolver rules shared via RAM are key to multi-account, hybrid DNS architectures.
Soru 612Soru

An enterprise has a multi-account AWS environment with 3030 spoke VPCs distributed across 22 regions: `us-east-1` (2020 VPCs) and `us-west-2` (1010 VPCs). The enterprise needs to connect these VPCs to two on-premises locations: a primary data center in New York and a backup data center in San Francisco.

The primary data center in New York has a 10 Gbps10\text{ Gbps} AWS Direct Connect connection. The backup data center in San Francisco has an internet connection capable of establishing IPsec VPN tunnels. The network architecture must ensure:
- High availability: If the primary New York Direct Connect connection or New York data center fails, hybrid traffic must automatically fail over to the San Francisco VPN connection.
- Symmetric routing: Traffic from AWS to the on-premises network must prefer the New York Direct Connect path under normal operations.
- Scalability: The solution must minimize administrative overhead and avoid configuring individual connections to every spoke VPC.

Which TWO configuration steps must be implemented to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure a Direct Connect Gateway (DXGW) and associate it with the Transit Gateways (TGWs) deployed in both `us-east-1` and `us-west-2`. Create a transit virtual interface (transit VIF) on the New York Direct Connect connection and terminate it on the DXGW.; Establish AWS Site-to-Site VPN connections from the San Francisco customer gateway to the Transit Gateways in both `us-east-1` and `us-west-2`. Configure the San Francisco customer gateway to advertise the on-premises IP ranges via BGP with multiple AS-Path prepends.

Cevap

The correct configurations are to set up a Direct Connect Gateway associated with Transit Gateways in both regions using a transit VIF for the primary path, and to establish Site-to-Site VPN connections from the backup site to the Transit Gateways while prepending AS paths to ensure the VPN is passive.
The correct solution involves deploying a Transit Gateway (TGW) in each region and associating them with a central Direct Connect Gateway (DXGW) using a transit virtual interface (transit VIF) for the primary connection from New York. For backup connectivity from San Francisco, Site-to-Site VPN connections are established to both TGWs, with BGP AS-Path prepending configured on the customer gateway. This configuration provides a scalable architecture that satisfies the active-passive routing requirements automatically via dynamic BGP routing.

Adım Adım Çözüm

1
Evaluate the scalability requirements for 3030 spoke VPCs across 22 regions.
Determine that deploying local Transit Gateways (TGWs) in `us-east-1` and `us-west-2` is the most scalable pattern, as associating individual VGWs is limited to 1010 per Direct Connect Gateway.
Direct Connect Gateway (DXGW) allows up to 66 Transit Gateway associations, which easily accommodates the two regional TGWs.
2
Configure primary connectivity from New York.
Create a transit virtual interface (transit VIF) on the New York Direct Connect connection and terminate it on the DXGW associated with both regional TGWs.
Transit VIF is required when routing traffic from Direct Connect to Transit Gateways.
3
Configure backup connectivity from San Francisco.
Establish Site-to-Site VPN connections from San Francisco to both Transit Gateways.
Terminating the VPN on the Transit Gateways provides a backup path to all spoke VPCs in both regions.
4
Configure routing preferences to establish active-passive behavior.
Configure BGP on the backup VPN customer gateway to advertise the on-premises CIDR block with AS-Path prepends.
AS-Path prepending makes the VPN route less preferred than the Direct Connect route, ensuring symmetric routing over the primary path during normal operations.

Anahtar Kavram

Designing scalable hybrid connectivity with AWS Transit Gateway, Direct Connect Gateway, and Site-to-Site VPN using BGP AS-Path prepending for active-passive routing.
Soru 613Soru

An enterprise manages its multi-account environment using AWS Organizations. The environment consists of a Management account, a central Infrastructure account, a Security account, a Log Archive account, and three developer accounts (Dev1Dev1, Dev2Dev2, and Dev3Dev3).

A solutions architect must design a resource sharing, billing, and logging strategy that meets the following requirements:
* Subnets from a VPC in the Infrastructure account must be shared with the developer accounts to allow them to deploy EC2 instances.
* VPC Flow Logs for the shared subnets must be published to an Amazon S3 bucket in the Log Archive account. These logs must be encrypted at rest using an AWS KMS Customer Managed Key (CMK) stored in the Security account.
* Compute Savings Plans purchased in the Management account must apply only to Dev1Dev1 and Dev2Dev2. The Dev3Dev3 account must be excluded from receiving these discounts to maintain standard On-Demand pricing for external client auditing.
* Developer accounts must be restricted from sharing their own resources with external accounts outside the organization using AWS Resource Access Manager (RAM).

Which combination of actions should the solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Enable resource sharing in AWS RAM for the organization. In the Infrastructure account, create a resource share for the subnets and share them with the developer accounts. Attach an SCP to the Developer OU that denies `ram:CreateResourceShare` and `ram:UpdateResourceShare` if `ram:AllowsExternalPrincipals` is set to true. In the Management account's Billing Preferences, keep discount sharing enabled, but uncheck the Dev3Dev3 account under the Savings Plans discount sharing preferences. In the Security account, create a KMS CMK and configure its key policy to grant `delivery.logs.amazonaws.com` the `kms:GenerateDataKey*` and `kms:Decrypt` permissions. In the Log Archive account, configure the S3 bucket policy to allow `delivery.logs.amazonaws.com` to perform `s3:PutObject`, and configure the bucket to use the KMS CMK in the Security account.

Cevap

The correct strategy is to share subnets within the organization using AWS Resource Access Manager (RAM), disable Savings Plans discount sharing specifically for the third developer account in the Management account's Billing Preferences, restrict external RAM sharing using a Service Control Policy (SCP) with the `ram:AllowsExternalPrincipals` condition, and encrypt cross-account VPC Flow Logs using a Customer Managed Key (CMK) with a key policy that trusts the VPC Flow Logs service principal.
The correct strategy combines AWS RAM organizational sharing, granular discount sharing preferences in the Management account, a Service Control Policy to prevent external resource sharing, and cross-account logging using a Customer Managed Key. Using the Billing Preferences in the Management account allows selective exclusion of the third developer account from the Compute Savings Plans. Creating a Customer Managed Key in the Security account and configuring its policy to allow the `delivery.logs.amazonaws.com` service principal enables secure, cross-account encryption of VPC Flow Logs.

Adım Adım Çözüm

1
Configure AWS RAM sharing within the organization.
Enable sharing within the organization in RAM settings, then share the subnets from the Infrastructure account with the developer accounts. This allows the developer accounts to access the shared subnets without manual acceptance.
This establishes secure, centralized resource sharing according to best practices.
2
Enforce sharing boundaries using a Service Control Policy (SCP).
Attach an SCP to the Developer OU that denies `ram:CreateResourceShare` and `ram:UpdateResourceShare` when the condition `ram:AllowsExternalPrincipals` is true.
This prevents developer accounts from sharing their local resources with external entities while permitting internal resource sharing.
3
Configure Savings Plans discount sharing preferences.
In the Management account's Billing Preferences, uncheck the third developer account from the discount sharing list while keeping the other developer accounts checked.
This selectively excludes the third developer account from receiving the shared Savings Plans discounts, leaving its resources to be billed at standard On-Demand rates for external client auditing.
4
Configure cross-account KMS and S3 bucket policies for encrypted VPC Flow Logs.
Create a Customer Managed Key (CMK) in the Security account. Add a policy statement allowing the VPC Flow Logs service principal (`delivery.logs.amazonaws.com`) permissions for `kms:GenerateDataKey*` and `kms:Decrypt`. In the Log Archive account, configure the S3 bucket policy to allow `delivery.logs.amazonaws.com` to write objects, and set the default bucket encryption to use the Security account's CMK.
This enables cross-account VPC Flow Logs delivery and encryption. AWS-managed keys cannot be used because their key policies cannot be customized to grant access to the service principal.

Anahtar Kavram

Centralized cost management and secure resource sharing are achieved by combining AWS Resource Access Manager (RAM), Service Control Policies (SCPs), Management account discount sharing preferences, and cross-account Customer Managed Keys (CMKs) to satisfy strict compliance and auditing boundaries.
Soru 614Soru

A financial services company is designing a disaster recovery (DR) architecture for a critical web application. The primary environment runs in the `us-east-1` Region, and the DR environment will be deployed in the `us-west-2` Region. The business requirements specify a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 2 minutes. The architecture must be highly available and resilient to single-zone failures in both regions while keeping ongoing standby costs as low as possible. Which solution meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy the application in `us-east-1` using Amazon Aurora PostgreSQL. Create an Amazon Aurora Global Database with a secondary cluster in `us-west-2` containing a single db.r6g.large reader instance. Set up Application Load Balancers in both regions. Configure Amazon Route 53 with an Active-Passive Failover routing policy and health checks pointing to the Application Load Balancer in each region. Promote the secondary cluster if the primary region fails.

Cevap

Deploy the application in the primary region using Amazon Aurora PostgreSQL, configure an Aurora Global Database with a secondary cluster containing a single reader instance in the disaster recovery region, set up Application Load Balancers in both regions, and use Route 53 Failover routing with health checks to manage the failover.
The correct solution utilizes Amazon Aurora Global Database, which replicates data asynchronously to a secondary region with latency typically under 1 second, meeting the 2-minute RPO. Promoting the secondary cluster takes only a few minutes, meeting the 15-minute RTO. Having a single replica instance in the secondary region minimizes standby costs, and using Route 53 Active-Passive Failover routing with health checks automates traffic redirection.

Adım Adım Çözüm

1
Evaluate the database replication strategy to satisfy the 2-minute RPO.
Amazon Aurora Global Database provides cross-region replication lag of less than 1 second, meeting the 2-minute RPO requirement, unlike hourly snapshots which have up to a 60-minute RPO.
Selecting the correct replication method is necessary to guarantee data recovery boundaries.
2
Select a disaster recovery pattern that satisfies the 15-minute RTO.
Aurora Global Database allows cluster promotion in under 5 minutes. Combined with Route 53 Active-Passive Failover routing, the entire recovery process takes less than 15 minutes.
An active-passive warm standby/pilot light setup ensures that resources are pre-provisioned or quickly promotable to meet recovery timelines.
3
Verify high availability and cost constraints in the secondary region.
To maintain high availability, NAT Gateways must be deployed in each Availability Zone in the DR region. Standby costs are kept low by using a single reader instance that can be scaled up during promotion.
Ensuring the secondary region contains no single points of failure while minimizing the size of standby compute satisfies both high availability and cost requirements.

Anahtar Kavram

Cross-region disaster recovery using Amazon Aurora Global Database and Route 53 Active-Passive Failover to meet strict RTO/RPO and HA requirements.
Soru 615Soru

A technology company has a multi-account structure managed via AWS Organizations. The data engineering team in the Analytics account needs to run transient Amazon EMR clusters that access a centralized Amazon Aurora PostgreSQL database cluster situated in the Shared Services account. To comply with strict security requirements, the database must not be exposed to the public internet, and cross-account network traffic must avoid the data processing charges associated with Transit Gateway or VPC peering. The finance team requires that EMR compute costs are billed directly to the Analytics account, while the database storage and instance costs are billed to the Shared Services account. Which combination of actions will meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the Shared Services account, use AWS Resource Access Manager (RAM) to share the private subnets containing the Aurora database with the Analytics account.; In the Analytics account, launch the Amazon EMR clusters directly into the shared private subnets.

Cevap

In the Shared Services account, use AWS Resource Access Manager (RAM) to share the private subnets containing the Aurora database with the Analytics account, and in the Analytics account, launch the Amazon EMR clusters directly into the shared private subnets.
By sharing private subnets from the Shared Services account using AWS Resource Access Manager (RAM), resources created in the Analytics account can reside in the same VPC as the Aurora database. This configuration permits direct private IP communication without the need for VPC peering or Transit Gateway, thereby avoiding any extra cross-account transit or data processing fees. Furthermore, AWS billing assigns the cost of resources to the account that created them, meaning the Analytics account pays for the EMR compute resources, while the Shared Services account continues to pay for the Aurora database storage and instances.

Adım Adım Çözüm

1
Share the private subnets in the Shared Services account VPC using AWS Resource Access Manager.
The Analytics account is granted permission to deploy resources into the specified subnets in the Shared Services VPC.
This sets up the network foundation to allow direct, private IP communication between the Analytics resources and the Shared Services database without transit costs.
2
Launch the EMR cluster from the Analytics account into the shared subnets.
EMR nodes run within the Shared Services VPC, allowing local routing to the database, while the EMR compute charges are billed directly to the Analytics account.
This satisfies the requirement to assign compute costs to the Analytics account and database costs to the Shared Services account.

Anahtar Kavram

VPC sharing via AWS Resource Access Manager (RAM) allows sharing subnets with other accounts in the same AWS Organization, facilitating secure, low-latency, and cost-effective communication while maintaining individual account billing for launched resources.
Soru 616Soru

A web application is deployed on AWS Elastic Beanstalk. The development team wants to update the application using a strategy that maintains full serving capacity during the deployment. Additionally, if the deployment fails, the rollback must be immediate and avoid any modification to the original running instances. Which of the following deployment policies meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Immutable; Traffic splitting

Cevap

The Immutable and Traffic splitting deployment policies meet the requirements because they both maintain full capacity and allow an immediate, clean rollback by terminating a temporary Auto Scaling group without modifying active production instances.
The correct policies are the ones that maintain full capacity and do not modify the original instances during deployment, allowing for immediate rollback. Immutable updates create a new Auto Scaling group, deploy the application, and then switch traffic. Traffic splitting also creates a new Auto Scaling group and routes a fraction of traffic to it while keeping the original group at full capacity. Both options keep the original instances untouched until the deployment is successful, allowing for a safe, instant rollback by deleting the new instances or shifting traffic back.

Adım Adım Çözüm

1
Analyze the capacity requirement during deployment
The strategy must maintain 100% capacity, ruling out All at once (0% capacity) and Rolling (reduced capacity).
To ensure no performance degradation during updates.
2
Analyze the rollback requirement
The rollback must be immediate and not touch the original instances. This rules out Rolling with additional batch, because failed deployments require another rolling update to revert, affecting the active instances.
To minimize blast radius and ensure zero-downtime recovery.
3
Identify the remaining valid policies
Immutable and Traffic splitting both create a separate, temporary Auto Scaling group, keeping the original instances safe and active, and allowing instant rollback by redirecting traffic or terminating the new group.
These match all constraints perfectly.

Anahtar Kavram

AWS Elastic Beanstalk deployment policies and their capacity and rollback characteristics.
Soru 617Soru

A multinational financial corporation is designing a secure, high-availability hybrid network topology across two AWS Regions: `us-east-1` and `us-west-2`. The organization has 60 spoke VPCs distributed across multiple AWS accounts. The primary data centers are in New York and London. The architecture must satisfy the following constraints:
1. Primary connectivity must use AWS Direct Connect (DX) via two 10 Gbps10\text{ Gbps} connections (one at a DX location near `us-east-1` and one near `us-west-2`).
2. High availability must be guaranteed via automated failover to backup Site-to-Site VPN connections over the public internet to each region. The VPN paths should only carry traffic if the local DX connection is down.
3. Spoke VPCs in both regions must be able to communicate with each other over the AWS network backbone.
4. Corporate users on-premises must be able to resolve private DNS names in an AWS Route 53 Private Hosted Zone (PHZ) hosted in a centralized Shared Services account. AWS resources must also resolve on-premises DNS records.
5. All outbound internet traffic from the spoke VPCs must be inspected by AWS Network Firewall in a centralized egress VPC in each region before routing to the internet, while avoiding single points of failure and minimizing inter-AZ data transfer costs.

Which architectural design and routing configuration meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy a Transit Gateway (TGW) in each region and establish a TGW peering connection between them. Attach the local spoke VPCs to their respective regional TGW. Create a single Direct Connect Gateway (DXGW), associate it with both TGWs, and attach a Transit VIF from each DX connection to the DXGW. Configure Site-to-Site VPN connections from on-premises to the TGW in each region. Advertise the on-premises prefix over BGP via both DX and VPN; the TGWs will automatically prefer the DXGW route over the VPN route. On the customer gateways, configure BGP local preference to prefer the DX routes over the VPN routes. Deploy a centralized egress VPC in each region with redundant NAT Gateways and Network Firewall endpoints across multiple Availability Zones, routing outbound traffic from the TGW through them. Deploy Route 53 Resolver Inbound and Outbound Endpoints in a Shared Services VPC. Share the on-premises DNS forwarding rules via AWS RAM and associate them with all VPCs, and associate the PHZ directly with all spoke VPCs.

Cevap

The correct option is the architecture that peers the regional Transit Gateways, connects them via a single Direct Connect Gateway with backup VPNs, utilizes redundant NAT Gateways across multiple Availability Zones in the egress VPCs, and configures hybrid DNS resolution using Resolver Endpoints along with direct cross-account Private Hosted Zone association.
The correct answer configures a peered Transit Gateway topology to enable spoke-to-spoke routing over the AWS backbone. It connects both regional TGWs to a single Direct Connect Gateway with backup Site-to-Site VPNs. For equal prefix advertisements, AWS Transit Gateway naturally prefers DXGW over VPN for outbound routing, while BGP local preference on-premises ensures symmetric routing. Redundant NAT Gateways across multiple Availability Zones in the egress VPCs prevent a single point of failure and avoid inter-AZ data transfer charges. Cross-account PHZ association is the most efficient and cost-effective method to share private hosted zones, while Resolver Endpoints handle bi-directional DNS resolution with on-premises.

Adım Adım Çözüm

1
Configure regional Transit Gateways and TGW Peering.
Transit Gateways in us-east-1 and us-west-2 are peered, and local spoke VPCs are attached to their respective regional TGWs.
This establishes a scalable inter-region connection allowing spoke VPCs to communicate over the AWS backbone network.
2
Set up a single Direct Connect Gateway and Site-to-Site VPNs.
A single DXGW is associated with both TGWs. Site-to-Site VPNs are created from on-premises to each regional TGW.
Associating one DXGW with both TGWs allows transit VIFs to route to both regions. VPNs attached to the TGWs serve as backup paths.
3
Configure prefix advertisements and BGP preferences.
Advertise the on-premises prefix over BGP via DX and VPN. Configure BGP local preference on customer gateways to prefer DX.
TGW naturally prefers DXGW over VPN for outbound traffic. On-premises local preference ensures inbound traffic to AWS also prefers DX, preventing asymmetric routing.
4
Deploy centralized egress VPCs with redundant NAT Gateways.
A centralized egress VPC is deployed in each region containing redundant NAT Gateways and AWS Network Firewall endpoints across multiple AZs.
Using redundant NAT Gateways in multiple AZs ensures high availability and eliminates cross-AZ data transfer charges for internet-bound traffic.
5
Configure hybrid DNS resolution and cross-account PHZ association.
Route 53 Resolver Inbound and Outbound Endpoints are deployed in the Shared Services VPC. The on-premises forwarding rules are shared via AWS RAM, and the PHZ is associated with all spoke VPCs.
Direct PHZ association avoids the cost and potential routing loop of forwarding internal queries through Resolver endpoints, while Resolver Endpoints handle hybrid DNS resolution with on-premises.

Anahtar Kavram

Hybrid and Multi-Account Network Connectivity Design
Soru 618Soru

A company has five AWS accounts, each containing a single VPC in the us-east-1 Region. The company needs to establish hybrid connectivity between all five VPCs and their on-premises data center. The solution must minimize administrative complexity and avoid managing a full mesh of connections. Which AWS networking component should the company use as a central hub to connect the VPCs and the on-premises network?

Cevabı ve açıklamayı göster

Cevap: An AWS Transit Gateway to attach to each VPC and route traffic to the on-premises network via a single VPN or Direct Connect connection

Cevap

An AWS Transit Gateway to attach to each VPC and route traffic to the on-premises network via a single VPN or Direct Connect connection
The correct answer is the option stating that an AWS Transit Gateway should be used to attach to each VPC and route traffic to the on-premises network. AWS Transit Gateway acts as a central regional router that simplifies the management of hybrid and multi-account VPC connections by avoiding the complexity of a full mesh network.

Adım Adım Çözüm

1
Analyze the requirements for connecting multiple VPCs across different accounts to an on-premises network while avoiding a full mesh configuration.
Identify that a hub-and-spoke architecture is required to centralize and simplify the network topology.
This simplifies management and routing compared to point-to-point connections.
2
Evaluate the capabilities of AWS Transit Gateway as a centralized network hub.
AWS Transit Gateway natively supports attaching multiple VPCs across different AWS accounts (via AWS RAM) and connecting them to an on-premises network via a single Direct Connect or VPN.
It acts as a regional router that simplifies transitive routing and centralizes hybrid connectivity.

Anahtar Kavram

Hub-and-spoke transit network design using AWS Transit Gateway
Soru 619Soru

A media streaming company uses AWS Organizations to manage a multi-account environment. A central Shared Services VPC in the `Network` account contains Route 53 Resolver inbound and outbound endpoints, connected to the on-premises network via AWS Transit Gateway and AWS Direct Connect. A Private Hosted Zone (PHZ) for `media.internal` is hosted in the `Production` account. A new Development VPC has been created in the `Development` account. Developers in the `Development` account require resolution of hostnames in `media.internal` from the Development VPC. Additionally, servers in the on-premises datacenter must resolve hostnames in `media.internal`.

Which of the following architectures will allow both the Development VPC and the on-premises network to resolve hostnames in `media.internal` with the lowest latency and administrative overhead?

Cevabı ve açıklamayı göster

Cevap: In the Production account, authorize the association of the `media.internal` Private Hosted Zone with both the Development VPC and the Shared Services VPC. In the Development account, associate the Development VPC with the Private Hosted Zone. In the Network account, associate the Shared Services VPC with the Private Hosted Zone. Configure the on-premises DNS servers to forward queries for `media.internal` to the inbound resolver endpoint IP addresses in the Shared Services VPC.

Cevap

In the Production account, authorize the association of the `media.internal` Private Hosted Zone with both the Development VPC and the Shared Services VPC. In the Development account, associate the Development VPC with the Private Hosted Zone. In the Network account, associate the Shared Services VPC with the Private Hosted Zone. Configure the on-premises DNS servers to forward queries for `media.internal` to the inbound resolver endpoint IP addresses in the Shared Services VPC.
The correct solution involves using Route 53 cross-account Private Hosted Zone (PHZ) association. The Production account (owner of the PHZ) must authorize the association for the Development VPC and the Shared Services VPC. The consumer accounts then complete the association. Once the PHZ is associated with the Shared Services VPC, the inbound resolver endpoint in that VPC can answer queries for `media.internal` forwarded from the on-premises DNS servers.

Adım Adım Çözüm

1
Authorize cross-account Private Hosted Zone (PHZ) association from the owner account.
VPC association authorizations are created in the Production account for the Development VPC and the Shared Services VPC.
Before a VPC in another AWS account can be associated with a PHZ, the account that owns the PHZ must explicitly authorize the association using `create-vpc-association-authorization`.
2
Associate the target VPCs with the PHZ from the consumer accounts.
The Development VPC and the Shared Services VPC are associated with the `media.internal` PHZ.
The association must be completed by running the `associate-vpc-with-private-hosted-zone` API call from the accounts hosting the respective VPCs (Development and Network accounts).
3
Configure DNS forwarding from the on-premises network.
On-premises DNS forwarders point queries for `media.internal` to the inbound resolver endpoints in the Shared Services VPC.
Since the PHZ is associated with the Shared Services VPC, the inbound resolver endpoint residing in that VPC can successfully resolve names within `media.internal` for on-premises clients.

Anahtar Kavram

Cross-account Private Hosted Zone (PHZ) association and Route 53 Resolver inbound endpoints are required to facilitate hybrid and multi-account DNS resolution without sharing zones via AWS RAM or routing traffic to link-local IP addresses.
Soru 620Soru

An organization is designing a deployment strategy for a critical, high-volume payment processing application hosted on AWS Fargate behind an Application Load Balancer (ALB). The backend database is an Amazon Aurora PostgreSQL cluster. A new release requires updating the Fargate task definition and applying a database schema modification that introduces a new column. The deployment must guarantee zero downtime, support automatic rollback within 5 minutes based on synthetic transaction errors, and ensure that if a rollback occurs, the database remains in a consistent state without losing any transaction data captured during the deployment window. Which deployment strategy meets these requirements with the least operational complexity?

Cevabı ve açıklamayı göster

Cevap: Implement a two-phase database schema change (Expand/Contract). First, deploy a database migration that adds the new column as nullable. Use AWS CodePipeline with AWS CodeDeploy to perform a blue/green deployment of the Fargate service. Configure a CodeDeploy AppSpec hook at AfterAllowTestTraffic to trigger an AWS Lambda function that runs synthetic test transactions against the green target group. If the tests fail, CodeDeploy rolls back traffic automatically. Once the deployment is successfully completed, execute a second database migration to enforce the non-null constraint on the column.

Cevap

Implement a two-phase database schema change (Expand/Contract). First, deploy a database migration that adds the new column as nullable. Use AWS CodePipeline with AWS CodeDeploy to perform a blue/green deployment of the Fargate service. Configure a CodeDeploy AppSpec hook at AfterAllowTestTraffic to trigger an AWS Lambda function that runs synthetic test transactions against the green target group. If the tests fail, CodeDeploy rolls back traffic automatically. Once the deployment is successfully completed, execute a second database migration to enforce the non-null constraint on the column.
The correct strategy implements the Expand/Contract database migration pattern combined with AWS CodeDeploy blue/green deployment. Creating the new column as nullable first keeps the schema backward-compatible with active production tasks. The AfterAllowTestTraffic hook runs validation tests on the green target group using a separate test port before any production traffic is routed. If the tests fail, CodeDeploy rolls back the application version automatically, preserving all database writes. Once the new application version is successfully serving all production traffic, a final migration applies the non-null constraint.

Adım Adım Çözüm

1
Analyze the database schema change and deployment constraints.
Identify that adding a non-null column directly violates backward compatibility, as older application tasks still serving traffic will not write to this column, causing database constraint failures.
Ensures the application can maintain zero downtime during the deployment phase.
2
Adopt the Expand/Contract database design pattern.
The new column is first created as nullable (expand phase) so both older (blue) and newer (green) tasks can write to the database. The non-null constraint is deferred until after the blue tasks are fully decommissioned (contract phase).
Allows safe rollback without dropping the database column or losing data from newly routed writes.
3
Configure the blue/green deployment pipeline using AWS CodeDeploy.
Fargate tasks are updated using a CodeDeploy blue/green deployment pattern. The AfterAllowTestTraffic hook triggers an AWS Lambda function to run synthetic transaction tests against the green environment via a test listener.
Provides a safe mechanism to validate the green application version using actual database connections before switching production traffic.
4
Validate the rollback mechanism.
If validation fails, CodeDeploy automatically redirects traffic back to the blue environment. Because the database was not modified in a breaking way, the old application tasks can immediately continue serving traffic, and database records written during the test window are preserved.
Guarantees zero data loss and fits the 5-minute rollback requirement.

Anahtar Kavram

The Expand/Contract pattern combined with CodeDeploy blue/green hooks enables zero-downtime application deployments and safe rollbacks when schema changes are required.
ÖncekiSayfa 31 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin