Tüm alıştırma soruları

1964 soru

Soru 461Soru

An enterprise is planning to establish a secure multi-account structure using AWS Organizations. The solutions architect needs to set up a new organizational structure with Service Control Policies (SCPs) to restrict unauthorized services before any member accounts begin deploying workloads. Arrange the steps in the correct order to implement this multi-account governance structure safely.

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

Cevabı ve açıklamayı göster

Cevap

The correct order to safely implement multi-account governance is: first, enable AWS Organizations from the management account; second, create the Organizational Units (OUs); third, create and attach Service Control Policies (SCPs) to the OUs; and fourth, provision or move member accounts into the secured OUs.
The correct sequence begins with initializing the AWS Organization root. Following this, the OU structure must be defined. To ensure secure-by-default behavior, SCPs are created and attached to the OUs next. Only after the OUs are secured are member accounts provisioned or moved into them, guaranteeing immediate policy enforcement.

Adım Adım Çözüm

1
Enable AWS Organizations.
The organization root is established.
This is the prerequisite step to allow any organizational configuration or member account orchestration.
2
Create Organizational Units (OUs).
A structured hierarchy of OUs is created under the root.
OUs act as the logical containers that will hold both accounts and policies.
3
Create and attach Service Control Policies (SCPs) to OUs.
Governance guardrails are applied to the containers.
Applying policies to OUs before placing accounts in them ensures that accounts are protected and restricted from the very moment they are associated with the OU.
4
Provision or move accounts into OUs.
Member accounts inherit the attached SCPs immediately.
This is the final step where the target accounts are placed within the governed structure.

Anahtar Kavram

Multi-Account Governance and Secure Lifecycle Management
Soru 462Soru

A Solutions Architect is configuring federated access to the AWS Management Console for enterprise users using an on-premises SAML 2.0 compliant Identity Provider (IdP). Which of the following configuration steps are required in AWS IAM to successfully establish this trust relationship and allow users to assume their federated roles? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a SAML identity provider in AWS IAM by uploading the SAML metadata document retrieved from the on-premises Identity Provider.; Create an IAM role with a trust policy that allows the federated users to call the sts:AssumeRoleWithSAML action.

Cevap

The correct configuration steps are creating a SAML identity provider using the metadata document from the corporate Identity Provider and creating an IAM role with a trust policy that allows the sts:AssumeRoleWithSAML action.
Establishing SAML 2.0 federation requires registering the Identity Provider (IdP) as an IAM SAML provider using its metadata document and associating it with an IAM role that explicitly allows the sts:AssumeRoleWithSAML API action in its trust policy.

Adım Adım Çözüm

1
Register the external identity provider in AWS IAM.
AWS IAM creates a SAML 2.0 identity provider using the metadata document from the on-premises IdP.
This establishes a cryptographically verified trust relationship between the corporate IdP and the AWS account.
2
Configure the federated IAM role and its trust policy.
An IAM role is created with a trust policy that allows the SAML provider to assume the role using the sts:AssumeRoleWithSAML action.
When users authenticate through the IdP, the IdP sends a SAML assertion to AWS. The trust policy allows AWS to grant temporary security credentials based on that assertion.

Anahtar Kavram

SAML 2.0 Identity Federation requires registering the IdP in IAM and configuring federated roles with a trust policy that permits the sts:AssumeRoleWithSAML action.
Soru 463Soru

A company is designing a hybrid network architecture to connect ten VPCs in the us-east-1 region to an on-premises data center. To reduce administrative overhead, the company wants to avoid establishing individual VPN connections or VPC peering connections between all VPCs and the on-premises environment. Additionally, the design must support communication between the VPCs themselves.

Which two AWS networking components should the solutions architect combine to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: AWS Transit Gateway to act as a centralized hub for VPC-to-VPC and hybrid traffic; An AWS Site-to-Site VPN connection attached to the Transit Gateway to route on-premises traffic through the hub

Cevap

AWS Transit Gateway to act as a centralized hub for VPC-to-VPC and hybrid traffic, and an AWS Site-to-Site VPN connection attached to the Transit Gateway to route on-premises traffic through the hub
The correct solution combines AWS Transit Gateway and an AWS Site-to-Site VPN connection attached to the Transit Gateway. AWS Transit Gateway acts as a central cloud router that supports transitive routing, enabling the ten VPCs to communicate with one another and with the hybrid connection. Attaching the Site-to-Site VPN to the Transit Gateway allows all connected VPCs to share the same VPN connection to reach the on-premises data center, which minimizes administrative overhead compared to setting up individual VPN tunnels for each VPC.

Adım Adım Çözüm

1
Analyze the requirements for VPC-to-VPC and VPC-to-on-premises connectivity with minimal administrative overhead.
Identify that a hub-and-spoke architecture is required to avoid the complexity of a full-mesh configuration.
Establishing individual VPNs or peering connections scales poorly and increases management complexity.
2
Select the hub component that supports transitive routing.
AWS Transit Gateway is chosen as the central cloud router.
Transit Gateway allows multiple VPCs and VPNs to attach to it, enabling centralized traffic routing.
3
Establish the hybrid connectivity to the on-premises data center.
An AWS Site-to-Site VPN connection is attached to the Transit Gateway.
This allows all VPCs attached to the Transit Gateway to share the same VPN connection to access the on-premises network, minimizing overhead.

Anahtar Kavram

AWS Transit Gateway acts as a cloud router to simplify network topology by connecting multiple VPCs and hybrid networks through a single hub, eliminating the need for complex mesh configurations.
Soru 464Soru

A financial services company is implementing a centralized identity strategy for its AWS multi-account environment managed by AWS Organizations. The company uses an on-premises SAML 2.0 compliant Identity Provider (IdP) for user authentication. The security team wants to minimize administrative overhead by avoiding the creation of SAML Identity Provider resources in every member account. Instead, they want to establish trust in a single, centralized 'Identity' account, allowing authenticated corporate users to assume specific operations roles in various member accounts.

Which configuration steps must be performed to establish this identity flow while adhering to the security team's constraints? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In the centralized Identity account, create an IAM SAML provider and a transition IAM role with a trust policy that permits the sts:AssumeRoleWithSAML action for the SAML provider principal.; In each target member account, create the destination IAM roles with trust policies that permit the sts:AssumeRole action, specifying the centralized transition role's ARN as the principal.

Cevap

Establish the SAML 2.0 federation trust in the centralized Identity account using the sts:AssumeRoleWithSAML action on a transition IAM role, and then use role chaining by configuring target member account roles to trust the transition role ARN via the sts:AssumeRole action.
Establishing a centralized identity account avoids the overhead of creating SAML provider resources in every member account. Corporate users federate into a transition role in the centralized Identity account via the sts:AssumeRoleWithSAML action. From this transition role, users then chain to target roles in member accounts using the standard sts:AssumeRole action, which requires trust policies in the target accounts pointing to the transition role's ARN.

Adım Adım Çözüm

1
Configure SAML 2.0 federation in the central Identity account by creating an IAM SAML provider and an associated transition IAM role.
Corporate users can authenticate against the central IdP and assume the transition role in the centralized Identity account via the sts:AssumeRoleWithSAML action.
Establishing the SAML trust locally in a single account minimizes administration by avoiding provider creation in every member account.
2
Configure trust policies on destination roles in target member accounts to trust the centralized transition role's ARN.
The target roles allow the central transition role as a trusted principal using the sts:AssumeRole action.
This enables role chaining, allowing users who have assumed the transition role to assume the target role in the member accounts.
3
Implement the role-chaining flow in the corporate portal or CLI, where the user first authenticates to get credentials for the transition role, then calls sts:AssumeRole to access the target account.
Users gain authorized access to target member accounts without direct SAML provider configurations in those target accounts.
This completes the end-to-end authentication and authorization flow across the multi-account architecture.

Anahtar Kavram

Multi-Account Identity Federation with SAML 2.0 and Role Chaining
Tahmini Süre:3m 0s
Soru 465Soru

An enterprise is planning to migrate its workloads to AWS and has deployed 8 VPCs across two AWS accounts in the eu-west-1 region. The company requires a hybrid network design to connect these VPCs to its corporate office. The primary connection must be a 1 Gbps AWS Direct Connect connection, with a backup IPsec VPN connection over the internet. The solution must allow all VPCs to communicate with each other and with the corporate office, while minimizing configuration and routing management overhead. Which two options should the solutions architect select to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway, attach the 8 VPCs to it, and associate the Transit Gateway with a Direct Connect Gateway connected to the Direct Connect connection.; Configure an AWS Site-to-Site VPN connection terminated on the AWS Transit Gateway, configuring Border Gateway Protocol (BGP) routing with path prepending to prefer the Direct Connect path.

Cevap

Deploy an AWS Transit Gateway, attach the 8 VPCs to it, and associate the Transit Gateway with a Direct Connect Gateway connected to the Direct Connect connection; and configure an AWS Site-to-Site VPN connection terminated on the AWS Transit Gateway, configuring Border Gateway Protocol (BGP) routing with path prepending to prefer the Direct Connect path.
The correct answer combines AWS Transit Gateway to enable transitive VPC-to-VPC communication and simplifies routing configuration. Associating the Transit Gateway with a Direct Connect Gateway allows the on-premises environment to access all VPCs via a single Direct Connect connection. Attaching an AWS Site-to-Site VPN to the Transit Gateway and configuring BGP with AS path prepending ensures that the VPN acts as a standby backup connection and traffic is routed through it only if the primary Direct Connect connection fails.

Adım Adım Çözüm

1
Analyze the transitive connectivity requirement.
Determined that all 8 VPCs must communicate with each other and on-premises, which requires a hub-and-spoke model to avoid the high administrative overhead of a full mesh of VPC peering connections.
VPC peering does not scale easily, and Direct Connect Gateway alone does not support transitive routing between attached VPCs.
2
Select the core routing component.
AWS Transit Gateway is selected to act as the regional cloud router, interconnecting all 8 VPCs via Transit Gateway attachments.
Transit Gateway simplifies the architecture by reducing the network complexity to a single hub connection per VPC.
3
Integrate hybrid connectivity and configure failover.
Associate the Transit Gateway with a Direct Connect Gateway for the primary path. Attach an AWS Site-to-Site VPN to the same Transit Gateway as the backup path, configuring BGP with AS path prepending on the VPN connection.
This establishes a reliable active/passive hybrid network topology where the VPN carries traffic only if the Direct Connect link is unavailable.

Anahtar Kavram

AWS Transit Gateway facilitates transitive routing between multiple VPCs and centralizes hybrid connectivity through Direct Connect Gateways and VPNs.
Soru 466Soru

An enterprise is designing a secure multi-account AWS environment using AWS Organizations. The solutions architect needs to establish AWS Control Tower to govern the landing zone, apply baseline compliance controls, and deploy custom CloudFormation templates across all member accounts. Arrange the following steps in the correct chronological order to implement this multi-account governance solution.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence of steps to implement AWS Control Tower governance is: 1. Design and establish the Organizational Unit (OU) hierarchy in AWS Organizations, 2. Deploy AWS Control Tower in the management account to initialize the landing zone, 3. Configure elective guardrails on the target OUs, 4. Provision new member accounts or enroll existing accounts into the governed OUs using Account Factory, and 5. Deploy the Customizations for AWS Control Tower (CfCT) framework to distribute custom resources.
The correct implementation sequence starts with designing and establishing the Organizational Unit (OU) structure to define account boundaries. Next, AWS Control Tower is deployed to establish the landing zone control plane. Once the landing zone is active, guardrails must be configured on the OUs to define baseline security boundaries. After the guardrails are active, new or existing accounts are provisioned or enrolled via Account Factory to inherit the baseline guardrails. Finally, the Customizations for AWS Control Tower (CfCT) framework is deployed to apply additional localized configurations and custom AWS resources to the governed accounts.

Adım Adım Çözüm

1
Design and establish the OU hierarchy in AWS Organizations.
The target container structure for accounts is defined.
This provides the structure that AWS Control Tower and member accounts will utilize.
2
Deploy AWS Control Tower in the management account.
The landing zone is created along with core shared accounts (Log Archive and Audit).
This establishes the core control plane and governance framework.
3
Configure elective guardrails on the target OUs.
Service Control Policies (SCPs) and Config rules are activated for the OUs.
Applying guardrails early ensures subsequent accounts are immediately protected.
4
Provision or enroll accounts into the governed OUs using Account Factory.
Member accounts are added to the organization and inherit the OU guardrails.
Accounts must exist under governed OUs to receive configurations and baseline governance.
5
Deploy the Customizations for AWS Control Tower (CfCT) framework.
A pipeline is established to deploy custom resources and localized policies across accounts.
CfCT depends on the completed landing zone infrastructure and active member accounts to target resources.

Anahtar Kavram

AWS Control Tower multi-account landing zone establishment and governance workflow.
Soru 467Soru

A retail-tech enterprise has structured its multi-account environment using AWS Organizations. The network topology includes a central network account (Account A) containing a Shared Services VPC (`Shared-VPC`), which is connected to an on-premises network via AWS Transit Gateway (TGW) and AWS Direct Connect. Account B contains `Core-VPC` and hosts a Route 53 Private Hosted Zone (PHZ) named `core.aws.internal`. Account C contains `App-VPC`. The enterprise requires a hybrid DNS resolution strategy:

1. On-premises client machines must resolve resources in `core.aws.internal` via the Active Directory DNS servers (10.50.0.1010.50.0.10 and 10.50.0.1110.50.0.11).
2. EC2 instances in `Core-VPC` and `App-VPC` must resolve on-premises services in the `.corp.local` domain.

Which actions must a Solutions Architect take to implement this architecture while minimizing administrative overhead? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In Account B, submit a cross-account VPC association authorization for `core.aws.internal` to Account A's `Shared-VPC` using the AWS CLI or API. In Account A, accept the association request to allow the central Inbound Resolver endpoint to resolve the private zone for queries coming from on-premises.; In Account A, create Route 53 Resolver Outbound Endpoints in the `Shared-VPC` and configure an outbound forwarding rule for `.corp.local` pointing to the on-premises DNS servers. Share this rule with the AWS Organization using AWS Resource Access Manager (RAM), and associate the shared rule with the VPCs in Account B and Account C.

Cevap

Authorize and associate the private hosted zone `core.aws.internal` in Account B with Account A's `Shared-VPC` using the AWS CLI or API to allow the central Inbound Resolver to answer queries, and configure a central Outbound Resolver Rule in Account A for `.corp.local` shared via AWS RAM with the consumer VPCs.
The correct implementation requires authorizing a cross-account Private Hosted Zone (PHZ) association via the CLI or API to allow the central Inbound Resolver in Account A to query `core.aws.internal` owned by Account B. Simultaneously, a central Outbound Resolver Endpoint in Account A is created, and the forwarding rules for `.corp.local` are shared with all accounts via AWS Resource Access Manager (RAM), ensuring both inbound and outbound DNS query flows are resolved efficiently with minimal overhead.

Adım Adım Çözüm

1
Authorize cross-account association of the Private Hosted Zone (PHZ) `core.aws.internal` from Account B to Account A's `Shared-VPC` using the `create-vpc-association-authorization` CLI command or API call.
Account A is permitted to associate its VPC with the PHZ owned by Account B.
Route 53 does not support cross-account VPC associations through the AWS Console, requiring API/CLI-based authorization beforehand.
2
Associate the `Shared-VPC` in Account A with the `core.aws.internal` PHZ using the `associate-vpc-with-hosted-zone` command in Account A.
The central Route 53 Resolver Inbound Endpoint in Account A's `Shared-VPC` can resolve names in `core.aws.internal`.
On-premises Active Directory servers query the central Inbound Resolver, which needs local association to query the PHZ database.
3
In Account A, provision Route 53 Resolver Outbound Endpoints in `Shared-VPC` and create a forwarding rule for `.corp.local` directing traffic to the on-premises Active Directory DNS servers.
An outbound resolution path for `.corp.local` is established from Account A.
Enables forwarding of DNS requests destined for the on-premises environment.
4
Share the Outbound Resolver forwarding rule with the AWS Organization via AWS Resource Access Manager (RAM), and associate the shared rule with `Core-VPC` (Account B) and `App-VPC` (Account C).
VPCs in Account B and Account C resolve `.corp.local` queries through the central outbound endpoints.
Minimizes administrative overhead by avoiding the deployment of outbound resolver endpoints in every individual account's VPC.

Anahtar Kavram

Centralized hybrid DNS architecture using Route 53 Resolver endpoints, cross-account Private Hosted Zone association, and AWS RAM rule sharing.
Soru 468Soru

An international logistics enterprise manages its multi-account AWS environment using AWS Organizations. A central Shared Services VPC in Account A hosts shared utilities and is connected to the on-premises data center via AWS Direct Connect and an AWS Transit Gateway. A Private Hosted Zone (PHZ) for ops.infra is created in Account A. Application VPCs in Account B need to resolve resources in the ops.infra domain and also resolve hostnames in the on-premises domain corp.local. Which TWO configurations are required to meet these DNS resolution requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Authorize the association of the Private Hosted Zone ops.infra with the application VPCs in Account B by executing the create-vpc-association-authorization command in Account A, and then complete the association by executing the associate-vpc-with-hosted-zone command in Account B.; Create a Route 53 Resolver outbound endpoint in the Shared Services VPC of Account A, configure a forwarding rule for the domain corp.local pointing to the on-premises DNS servers, and share the rule with Account B using AWS Resource Access Manager (RAM). In Account B, associate the shared rule with the application VPCs.

Cevap

Authorize the cross-account association of the Private Hosted Zone from the owner account and complete it from the consumer account, while using Route 53 Resolver outbound endpoints and AWS RAM to share forwarding rules for the on-premises domain.
The correct steps require establishing cross-account Private Hosted Zone (PHZ) association and sharing Route 53 Resolver forwarding rules. To resolve the shared domain, which is a PHZ in Account A, from Account B, you must first authorize the cross-account association from Account A using the create-vpc-association-authorization API, and then accept the association in Account B using the associate-vpc-with-hosted-zone API. To resolve the on-premises domain, a central Route 53 Resolver outbound endpoint should be created in the Shared Services VPC in Account A, along with a forwarding rule pointing to the on-premises DNS servers. This forwarding rule must be shared with Account B via AWS Resource Access Manager (RAM) and associated with the application VPCs.

Adım Adım Çözüm

1
Authorize the cross-account Private Hosted Zone association.
The owner of the Private Hosted Zone (Account A) authorizes the consumer VPCs (Account B) to associate with the zone using the create-vpc-association-authorization command.
AWS security boundaries require explicit authorization before a Private Hosted Zone can be associated with a VPC belonging to a different AWS account.
2
Complete the VPC association in the consumer account.
The owner of the consumer VPCs (Account B) associates the VPCs with the Private Hosted Zone hosted in Account A using the associate-vpc-with-hosted-zone command.
This allows resources inside the application VPCs to directly resolve internal resource hostnames in the shared zone without routing queries through resolver endpoints.
3
Deploy Resolver endpoints and share the forwarding rule.
A Route 53 Resolver outbound endpoint is created in Account A's Shared Services VPC. A forwarding rule for the on-premises domain is configured and shared with Account B using AWS Resource Access Manager (RAM). The rule is then associated with the application VPCs.
Sharing the central forwarding rule allows the application VPCs in Account B to utilize the shared services infrastructure to resolve on-premises hostnames over Direct Connect.

Anahtar Kavram

Cross-account Private Hosted Zone association and Route 53 Resolver rule sharing via AWS Resource Access Manager in hybrid networks.
Tahmini Süre:2m 0s
Soru 469Soru

A solutions architect needs to share a Transit Gateway from a production AWS account with an external partner's AWS account that is not part of the company's AWS Organization. Which of the following approaches is required to successfully share this resource using AWS Resource Access Manager (RAM)?

Cevabı ve açıklamayı göster

Cevap: Enable sharing with external principals in the AWS RAM settings, create a resource share targeting the external partner's AWS account ID, and have the partner accept the resource share invitation.

Cevap

Enable sharing with external principals in the AWS RAM settings, create a resource share targeting the external partner's AWS account ID, and have the partner accept the resource share invitation.
To share resources like a Transit Gateway with an external account not part of your AWS Organization, you must first enable sharing with external principals in the AWS RAM console settings. Once enabled, you can create a resource share targeting the external account. Because the account is external to the organization, an invitation is sent and must be explicitly accepted by the partner account before the shared resource can be accessed.

Adım Adım Çözüm

1
Enable external sharing in the AWS RAM settings.
AWS RAM is permitted to share supported resources with AWS accounts outside of its AWS Organization.
By default, AWS RAM restricts sharing to accounts within the same AWS Organization for security.
2
Create a resource share, select the Transit Gateway, and add the external partner's AWS account ID as the principal.
A resource share is created and an invitation is sent to the external partner's AWS account.
Sharing resources outside the AWS Organization requires specifying the individual destination account ID.
3
Have the external partner log into their AWS console, navigate to AWS RAM, and accept the resource share invitation.
The shared Transit Gateway becomes visible and usable in the partner's AWS account.
External accounts must explicitly accept resource shares to prevent unauthorized or unexpected resource placements.

Anahtar Kavram

AWS Resource Access Manager (RAM) external sharing requirements and workflow.
Tahmini Süre:1m 0s
Soru 470Soru

A solutions architect is designing a hybrid network architecture where multiple spoke VPCs in a single AWS Region need to access the internet through a centralized egress VPC using AWS Transit Gateway. To ensure high availability and prevent a single point of failure for outbound traffic, how should the NAT Gateways be deployed in the egress VPC?

Cevabı ve açıklamayı göster

Cevap: Deploy one NAT Gateway in each Availability Zone of the egress VPC, and configure the egress VPC route tables to direct internet-bound traffic from each private subnet to the NAT Gateway in its respective Availability Zone.

Cevap

Deploy one NAT Gateway in each Availability Zone of the egress VPC, and configure the egress VPC route tables to direct internet-bound traffic from each private subnet to the NAT Gateway in its respective Availability Zone.
The correct architecture requires deploying one NAT Gateway in each Availability Zone of the egress VPC. This alignment ensures that an outage in one Availability Zone does not impact outbound traffic from other zones, satisfying the high availability constraint.

Adım Adım Çözüm

1
Analyze the egress routing requirement.
Egress traffic from spoke VPCs must go through a centralized egress VPC via AWS Transit Gateway.
Centralizing egress traffic simplifies security monitoring and minimizes public IP usage.
2
Design for high availability across Availability Zones.
Deploy at least two NAT Gateways, one in each Availability Zone (AZ) of the egress VPC.
A single NAT Gateway creates a single point of failure if its AZ goes down.
3
Configure internal VPC routing inside the egress VPC.
Ensure route tables in each private subnet point to the NAT Gateway within the same AZ.
This guarantees that traffic remains zoned and isolated, ensuring high availability and fault tolerance.

Anahtar Kavram

Multi-AZ NAT Gateway Redundancy in Centralized Egress Architectures
Tahmini Süre:1m 30s
Soru 471Soru

A multinational enterprise is designing a hybrid network architecture to connect two corporate offices in London and Paris to a multi-account AWS environment. The AWS infrastructure consists of 40 spoke VPCs distributed across the eu-west-1 (Ireland) and eu-west-3 (Paris) Regions. The architecture must satisfy the following requirements:
- High availability: All VPCs in both Regions must have redundant hybrid connectivity to both offices.
- Path preference: Primary traffic must use AWS Direct Connect. An IPsec VPN over the public internet must serve as a failover path.
- Traffic localization: Under normal operations, traffic from the London office to eu-west-1 must flow through the London Direct Connect connection, and traffic from the Paris office to eu-west-3 must flow through the Paris Direct Connect connection. Cross-region hybrid routing should only occur during a link failure.
- Minimal administrative overhead for routing.

Which TWO options should the solutions architect select to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy an AWS Transit Gateway in both regions to interconnect local spoke VPCs, and peer the two Transit Gateways. Associate both Transit Gateways with a single Direct Connect Gateway connected to Transit Virtual Interfaces (Transit VIFs) at both offices, and terminate the backup Site-to-Site VPN connections directly on the Transit Gateways.; On the customer gateway routers, advertise local office CIDR blocks to the local Direct Connect connection with no AS path prepending, and advertise them to the remote Direct Connect connection with AS path prepending. Set a lower BGP local preference on the customer gateways for prefixes received via the VPN tunnels.

Cevap

Deploy an AWS Transit Gateway in both regions peered together, associate both with a single Direct Connect Gateway, terminate the backup Site-to-Site VPNs directly on the Transit Gateways, and configure BGP routing on the customer gateways to enforce path preference and traffic localization using AS path prepending and local preference.
To build a highly available, multi-region hybrid network with minimum administrative overhead, regional Transit Gateways must be deployed and peered. The Transit Gateways are associated with a single Direct Connect Gateway using Transit VIFs to handle primary traffic. Since the Direct Connect Gateway cannot terminate VPN connections, the backup Site-to-Site VPN connections are terminated directly on the regional Transit Gateways. Egress traffic localization is achieved by using BGP AS path prepending, which makes the local Direct Connect connection appear as the shortest path to AWS. Ingress traffic path preference is established by configuring a lower BGP local preference on the customer gateways for prefixes received over VPN, ensuring the routers prefer the Direct Connect connection.

Adım Adım Çözüm

1
Deploy regional Transit Gateways in eu-west-1 and eu-west-3, peer them to enable inter-VPC routing, and attach the local spoke VPCs to their respective regional Transit Gateway.
Establishes scalable, low-overhead hub-and-spoke VPC networking in both regions.
Allows all 40 spoke VPCs to communicate across accounts and regions without the administrative complexity of full-mesh VPC peering.
2
Create a central Direct Connect Gateway and associate it with both regional Transit Gateways. Create Transit VIFs from London and Paris Direct Connect connections and attach them to the Direct Connect Gateway.
Enables primary hybrid network connectivity from both corporate offices to all AWS VPCs.
Direct Connect Gateway enables multi-region transitive routing between on-premises environments and Transit Gateways.
3
Establish Site-to-Site VPN connections from the customer gateways at both locations to the Transit Gateways in both regions.
Provides backup paths that bypass the Direct Connect infrastructure.
Direct Connect Gateway does not terminate VPN tunnels; hence, the backup VPN tunnels must terminate directly on the Transit Gateways.
4
Configure BGP path attributes on the customer gateways to advertise local networks to the local region's DX connection with a shorter AS path and remote DX with AS path prepending, while configuring a lower local preference for VPN routes.
Ensures primary traffic prefers Direct Connect, backups use VPN, and cross-region routing only occurs during link failures.
Ensures traffic localization and automatic failover by influencing BGP path selection for both ingress and egress routing.

Anahtar Kavram

Multi-region hybrid connectivity using AWS Transit Gateway, Direct Connect Gateway, and Site-to-Site VPN failover with BGP path selection controls.
Soru 472Soru

An enterprise is designing a multi-account structure using AWS Organizations. The architecture includes a Production Organizational Unit (OU) containing several workload accounts, and a Shared Services OU. The security team has established the following requirements:

1. Workloads in the Production OU must be restricted to deploying resources only in the `eu-west-1` and `us-east-1` Regions, with exemptions for global services such as Amazon Route 53, AWS IAM, and Amazon CloudFront.
2. Local administrators in member accounts within the Production OU must be prevented from deleting or modifying a centralized administrative IAM role named `CentralAuditRole` that is deployed in all member accounts.
3. No member account within the organization must be permitted to leave the organization.
4. The solution must minimize administrative overhead and avoid complex per-account manual configurations.

Which approach should the solutions architect recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Attach an SCP at the Organization Root to deny organizations:LeaveOrganization. Attach an SCP at the Production OU that denies resource creation if aws:RequestedRegion is not eu-west-1 or us-east-1 (exempting global services), and denies write and delete actions on the CentralAuditRole ARN using a wildcard for the account ID.

Cevap

The correct design uses a Service Control Policy (SCP) at the root level to prevent accounts from leaving the organization, and a separate SCP at the Production OU to restrict regions (with global service exemptions) and block modifications to the specific IAM role across all member accounts using a wildcard resource ARN.
The correct solution uses a Root-level SCP to prevent member accounts from leaving the organization, and a Production OU-level SCP to enforce region boundaries and protect the administrative role. SCPs are effective policy boundaries that cannot be bypassed by local administrators. Using a wildcard in the resource ARN allows a single policy to protect the role across all member accounts, minimizing administrative overhead.

Adım Adım Çözüm

1
Evaluate enforcement mechanism for organization member policy.
Identify that organizations:LeaveOrganization must be denied at the root level to prevent any member account in the organization from leaving.
An SCP applied at the Root OU automatically inherits down to all OUs and accounts, providing a global policy guardrail.
2
Evaluate regional deployment restrictions.
Determine that an SCP denying actions where the condition key aws:RequestedRegion is not eu-west-1 or us-east-1 (with exemptions for global services) should be applied to the Production OU.
Applying this at the Production OU ensures sandbox or shared services OUs are not unnecessarily restricted, and exempting global services prevents breaking IAM, CloudFront, and Route 53 operations.
3
Determine how to protect the central audit role from local administrators.
Deny write/delete operations (e.g., iam:DeleteRole, iam:PutRolePolicy) on the CentralAuditRole resource ARN using a wildcard for the account ID field (arn:aws:iam::*:role/CentralAuditRole).
SCPs apply to all principals in the member accounts, including the root user and administrators. Using a wildcard in the account ID part of the ARN allows one policy to protect the role across all accounts in the Production OU without individual account hardcoding.

Anahtar Kavram

Multi-Account Governance and Organizational Structure
Tahmini Süre:3m 0s
Soru 473Soru

A company is setting up a new multi-account environment using AWS Organizations to host its workloads. The solutions architect needs to establish basic governance and security guardrails across all accounts while organizing the accounts based on their environments (production and development). Which two actions should the solutions architect take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enable all features in AWS Organizations and use Organizational Units (OUs) to group accounts based on their environment type.; Apply Service Control Policies (SCPs) to the Organizational Units (OUs) to establish maximum permission guardrails.

Cevap

Enable all features in AWS Organizations and use Organizational Units (OUs) to group accounts based on their environment type, and apply Service Control Policies (SCPs) to the OUs to establish maximum permission guardrails.
The correct approach involves enabling all features in AWS Organizations to group accounts by environment using OUs, and then applying Service Control Policies (SCPs) to those OUs to establish maximum permission boundaries. This matches the standard AWS multi-account governance framework.

Adım Adım Çözüm

1
Identify the organizational requirements for grouping accounts and setting permission limits.
Determined that OUs should be used for grouping by environment type, and SCPs should be used for guardrails.
AWS Organizations requires 'All Features' enabled to use SCPs, and OUs are the primary administrative boundary for applying these policies collectively.
2
Determine the correct target for SCP application.
SCPs are applied at the Root, OU, or Account level, not to individual IAM users.
SCPs are organization-level policy constructs rather than identity-based policies.
3
Evaluate the limitations of AWS-managed KMS keys and Route 53 Private Hosted Zones.
Recognized that AWS-managed keys cannot be shared cross-account, and PHZs require explicit VPC association.
Standard AWS cross-account resource limitations require customer-managed keys for KMS sharing and explicit association for private DNS resolution.

Anahtar Kavram

Multi-account governance using AWS Organizations, OUs, and Service Control Policies (SCPs)
Soru 474Soru

A media streaming company manages a multi-account AWS environment connected to its on-premises data center via AWS Transit Gateway. The Shared Services account hosts a Route 53 Private Hosted Zone (PHZ) for `media.internal` associated with the Shared Services VPC. The company is deploying new application VPCs in separate member accounts. Resources in the application VPCs must resolve names in `media.internal` and also resolve domains hosted on-premises (`onprem.local`). How should a Solutions Architect design the DNS architecture to meet these requirements with the minimum administrative overhead?

Cevabı ve açıklamayı göster

Cevap: Authorize the cross-account association of the `media.internal` private hosted zone with the application VPCs from the Shared Services account, and then associate the VPCs. Create a Route 53 Resolver outbound endpoint in the Shared Services VPC, configure a resolver rule for `onprem.local` pointing to the on-premises DNS servers, share this rule using AWS Resource Access Manager (RAM), and associate it with the application VPCs.

Cevap

Authorize the cross-account association of the `media.internal` private hosted zone with the application VPCs from the Shared Services account, and then associate the VPCs. Create a Route 53 Resolver outbound endpoint in the Shared Services VPC, configure a resolver rule for `onprem.local` pointing to the on-premises DNS servers, share this rule using AWS Resource Access Manager (RAM), and associate it with the application VPCs.
The correct answer provides a hybrid DNS design that addresses both private hosted zone resolution and on-premises resolution with minimal endpoints. First, to allow cross-account VPCs to resolve the private hosted zone `media.internal`, cross-account association must be authorized from the owner account and then accepted from the consumer accounts. Second, a centralized Route 53 Resolver outbound endpoint is created in the Shared Services VPC. A forwarding rule for the on-premises domain is created, pointing to the on-premises DNS IPs. This forwarding rule is shared via AWS RAM with the other member accounts in the AWS Organization. Once associated with the application VPCs, resources in those VPCs can route their DNS queries through the centralized outbound endpoint, avoiding the cost and overhead of provisioning endpoints in every VPC.

Adım Adım Çözüm

1
Authorize the cross-account VPC association for the private hosted zone.
The application VPCs in the member accounts are authorized to associate with the private hosted zone owned by the Shared Services account.
Route 53 Private Hosted Zones cannot be shared via AWS RAM; cross-account association authorization is required.
2
Associate the application VPCs with the private hosted zone from the member accounts.
Resources in the application VPCs can now resolve DNS records within the `media.internal` domain.
Completes the cross-account DNS resolution setup for the private AWS domain.
3
Create a Route 53 Resolver outbound endpoint in the Shared Services VPC and a forwarding rule for `onprem.local` pointing to the on-premises DNS servers.
A centralized outbound resolver path is established.
Directs DNS queries for on-premises domains from AWS to the on-premises DNS servers over the Transit Gateway connection.
4
Share the forwarding rule using AWS Resource Access Manager (RAM) and associate it with the application VPCs.
The application VPCs in member accounts can resolve `onprem.local` domains without needing local outbound endpoints.
Minimizes cost and administrative overhead by using a single outbound resolver endpoint.

Anahtar Kavram

Centralized hybrid and multi-account DNS resolution using Route 53 Resolver endpoints, forwarding rules shared via RAM, and cross-account Private Hosted Zone association.
Tahmini Süre:2m 30s
Soru 475Soru

A biopharmaceutical company is migrating its clinical trial management platform to a multi-account AWS environment managed under AWS Organizations. The environment consists of a central Network Account (Account A) hosting a shared services VPC, and two separate application accounts (Account B and Account C) hosting production application VPCs. The shared services VPC is connected to the on-premises corporate network via AWS Transit Gateway and an AWS Direct Connect connection. The on-premises DNS domain is `corp.local`. The application accounts host Route 53 Private Hosted Zones (PHZs) for `clinical.aws` (Account B) and `trials.aws` (Account C). The company requires that all VPCs and the on-premises network can resolve all internal domains. DNS queries must remain private and highly available. Which TWO actions should a Solutions Architect take to implement this hybrid DNS resolution architecture? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: In Account A, deploy Route 53 Resolver inbound and outbound endpoints in the shared services VPC. Create an outbound resolver rule for the `corp.local` domain pointing to the on-premises DNS servers. Share the outbound resolver rule with Accounts B and C using AWS Resource Access Manager (RAM), and associate the rule with the shared services VPC and all application VPCs.; For the private hosted zones `clinical.aws` (Account B) and `trials.aws` (Account C), submit a cross-account VPC association authorization to the shared services VPC in Account A using the AWS CLI or Route 53 API. In Account A, accept the authorization and associate the shared services VPC with both private hosted zones. Associate each private hosted zone with the application VPCs in their respective accounts.

Cevap

Deploy Route 53 Resolver inbound and outbound endpoints in Account A, creating an outbound rule for `corp.local` that is shared via RAM. In parallel, perform a cross-account private hosted zone association for `clinical.aws` and `trials.aws` with the shared services VPC using the AWS CLI or Route 53 API.
To build a highly available, secure, and compliant hybrid DNS resolution architecture: 1) Deploying central Route 53 Resolver endpoints in Account A enables centralized ingress and egress of DNS traffic. The outbound resolver rule for `corp.local` is shared via AWS RAM, allowing application VPCs to forward queries through the central outbound endpoint. 2) For inbound queries from on-premises to resolve `clinical.aws` and `trials.aws`, the central inbound endpoint in Account A must have access to these zones. This is achieved by creating a cross-account VPC association authorization using the Route 53 API/CLI (since RAM is not supported for PHZs) to associate the shared services VPC in Account A with the PHZs in Accounts B and C.

Adım Adım Çözüm

1
Deploy Route 53 Resolver endpoints in the hub VPC (Account A) to enable hybrid DNS resolution.
Inbound and outbound resolver endpoints are provisioned in the shared services VPC, using subnets in multiple Availability Zones for high availability.
Centralizing endpoints simplifies governance, reduces cost, and leverages the existing hybrid network connectivity (Transit Gateway/Direct Connect).
2
Configure outbound forwarding for the on-premises domain `corp.local`.
An outbound resolver rule for `corp.local` pointing to the on-premises DNS servers is created, shared via AWS RAM with Accounts B and C, and associated with all VPCs.
This allows resources in both the shared services VPC and application VPCs to forward queries for `corp.local` to the central outbound endpoints, which send them to the on-premises DNS servers.
3
Associate cross-account Private Hosted Zones with the central shared services VPC.
The owners of the PHZs (`clinical.aws` in Account B and `trials.aws` in Account C) authorize association with the shared services VPC in Account A using the AWS CLI or Route 53 API, which is then accepted in Account A.
The central inbound resolver endpoint in Account A can only resolve PHZs that are associated with its VPC. Because PHZs cannot be shared via RAM, this CLI/API-based authorization and association workflow is required.
4
Configure on-premises DNS forwarders.
On-premises DNS servers are configured with conditional forwarding rules for `clinical.aws` and `trials.aws` pointing to the IP addresses of the inbound resolver endpoints in Account A.
This routes on-premises DNS requests for AWS private zones to the inbound endpoints, which can now resolve them because the zones are associated with the shared services VPC.

Anahtar Kavram

Centralized Hybrid DNS with Route 53 Resolver Endpoints and Cross-Account Private Hosted Zone Associations
Tahmini Süre:3m 0s
Soru 476Soru

An enterprise manages a multi-account environment using AWS Organizations. The security team is configuring federated single sign-on (SSO) to target AWS accounts using an external, SAML 2.0-compliant corporate Identity Provider (IdP). The team has created a SAML provider entity named 'CorporateIdP' in the target member accounts. In the target member accounts, they also created an IAM role named 'ReadOnlyAuditor' to be assumed by the federated users. However, during the initial testing phase, users receive access denied errors immediately after authentication at the IdP portal when redirecting to the AWS console. The security team verifies that the corporate IdP is successfully generating SAML assertions containing the user's attributes. Which of the following configurations represents the correct setup to resolve this issue and establish federated access?

Cevabı ve açıklamayı göster

Cevap: Configure the IAM role's trust policy in each target account to allow the action sts:AssumeRoleWithSAML for the Federated principal referencing the ARN of the 'CorporateIdP' provider. Ensure the SAML assertion includes attributes for https://aws.amazon.com/SAML/Attributes/Role (containing the comma-separated role ARN and SAML provider ARN) and https://aws.amazon.com/SAML/Attributes/RoleSessionName.

Cevap

Configure the IAM role's trust policy in each target account to allow the action sts:AssumeRoleWithSAML for the Federated principal referencing the ARN of the 'CorporateIdP' provider, and ensure the SAML assertion contains the Role and RoleSessionName attributes.
The correct configuration uses the 'sts:AssumeRoleWithSAML' action in the IAM role's trust policy, pointing to the SAML provider ARN as the federated principal. It also requires the SAML assertion to contain the specific attributes 'https://aws.amazon.com/SAML/Attributes/Role' and 'https://aws.amazon.com/SAML/Attributes/RoleSessionName' so that AWS can map the authenticated user to the correct role in the member account.

Adım Adım Çözüm

1
Examine the IAM role's trust policy in the target member accounts.
Ensure the trust policy allows the action 'sts:AssumeRoleWithSAML' and targets the Federated SAML provider ARN as the principal.
SAML 2.0 federation requests to AWS must call the AssumeRoleWithSAML API operation, which requires the trust policy to explicitly permit this action for the specific SAML provider principal.
2
Configure the SAML assertion attributes on the corporate Identity Provider.
Include the mandatory attributes: 'https://aws.amazon.com/SAML/Attributes/Role' and 'https://aws.amazon.com/SAML/Attributes/RoleSessionName'.
AWS relies on these specific SAML attributes to identify which IAM role to assume and what the session name should be. The 'Role' attribute must contain both the target role ARN and the SAML provider ARN separated by a comma.
3
Ensure no organizational guardrails or local policies deny the federation request.
Verify that no Service Control Policies (SCPs) deny the 'sts:AssumeRoleWithSAML' action in the target accounts.
An SCP can act as a filter and block the action if it is explicitly denied, even though SCPs cannot be used to grant the federated access directly.

Anahtar Kavram

SAML 2.0 Federation Trust and Assertion Requirements
Tahmini Süre:2m 30s
Soru 477Soru

A financial services company is implementing a multi-account strategy using AWS Organizations. The organization contains three main Organizational Units (OUs): CoreServicesOU, SecurityOU, and WorkloadsOU. The WorkloadsOU has two child OUs: ProductionOU and DevelopmentOU.

The security team has the following requirements:
1. No IAM user or role within any member account in the WorkloadsOU should be able to delete or modify the configurations of an IAM role named SecurityComplianceRole.
2. Developers in the DevelopmentOU must be allowed to deploy and test new AWS services freely, but they must be restricted from launching Amazon EC2 instances of any type other than the t3 or m5 families.
3. The administration of resources within the SecurityOU must not be impacted by these policies.

Which combination of Service Control Policies (SCPs) and OU attachments will meet these requirements with the least operational overhead?

Cevabı ve açıklamayı göster

Cevap: Attach a Service Control Policy (SCP) to the WorkloadsOU that denies iam:DeleteRole, iam:DeleteRolePolicy, and iam:DetachRolePolicy actions on the SecurityComplianceRole resource. Attach another SCP to the DevelopmentOU that denies ec2:RunInstances if the ec2:InstanceType is not like t3.* or m5.*. Keep the default FullAWSAccess SCP attached at all levels.

Cevap

Attach a Service Control Policy (SCP) to the WorkloadsOU that denies iam:DeleteRole, iam:DeleteRolePolicy, and iam:DetachRolePolicy actions on the SecurityComplianceRole resource. Attach another SCP to the DevelopmentOU that denies ec2:RunInstances if the ec2:InstanceType is not like t3.* or m5.*. Keep the default FullAWSAccess SCP attached at all levels.
The correct solution attaches the role protection policy to the WorkloadsOU, ensuring the restriction inherits to both Production and Development OUs without affecting the SecurityOU. The EC2 restriction is attached to the DevelopmentOU to target only developers. The default FullAWSAccess policy is kept at all levels to prevent blocking other services that developers need to test.

Adım Adım Çözüm

1
Analyze the scope of the IAM role protection requirement.
The restriction must apply to all member accounts in the WorkloadsOU (Production and Development) but must not affect the SecurityOU or CoreServicesOU.
Attaching the role-protection SCP to the WorkloadsOU target ensures that both child OUs (ProductionOU and DevelopmentOU) inherit the restriction without impacting other top-level OUs.
2
Analyze the EC2 instance type constraint.
The constraint must only restrict the DevelopmentOU, allowing other OUs (like ProductionOU) to use other instance types, and must not prevent developers from using other services.
Attaching a deny policy to the DevelopmentOU that blocks ec2:RunInstances unless the instance type matches the approved families ensures only the target environment is restricted. Keeping FullAWSAccess ensures developers can still use other services.
3
Evaluate explicit deny behavior in SCPs.
An explicit deny in an SCP overrides any allow permissions granted by IAM policies within the accounts.
This guarantees that local administrators cannot override the restriction, satisfying the governance requirement.

Anahtar Kavram

AWS Organizations Service Control Policies (SCPs) act as permission guards that inherit down the OU hierarchy, where explicit denies override any allows without granting permissions directly.
Soru 478Soru

A financial services company is establishing a multi-account AWS environment. A central Shared Services account hosts a Route 53 Private Hosted Zone (PHZ) for internal service discovery. A security policy requires that database workloads running in a separate Production account VPC must be able to resolve names within this central PHZ, without deploying duplicate hosted zones.

Which TWO steps are required to associate the central Private Hosted Zone with the VPC in the Production account? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: From the Shared Services account, create a VPC association authorization using the AWS CLI or API to authorize the Production account VPC.; From the Production account, associate the VPC with the Shared Services private hosted zone using the AWS CLI or API.

Cevap

To associate a Route 53 Private Hosted Zone with a VPC in a different AWS account, you must first create a VPC association authorization from the account that owns the hosted zone, and then associate the VPC from the account that owns the VPC.
Associating a Route 53 Private Hosted Zone in one AWS account with a VPC in another AWS account is a two-step process that must be done using the AWS CLI or API. The hosted zone owner must first authorize the VPC association, and the VPC owner must then accept and associate the VPC.

Adım Adım Çözüm

1
Authorize the association from the hosted zone owner account.
An association authorization is created for the target VPC.
Route 53 requires explicit permission from the hosted zone owner before a cross-account VPC can be associated.
2
Submit the association request from the VPC owner account.
The VPC is associated with the hosted zone, allowing resources within the VPC to resolve records in that hosted zone.
This completes the handshake and links the VPC to the Private Hosted Zone.

Anahtar Kavram

Cross-account Route 53 Private Hosted Zone association requires a two-step handshake via CLI/API: creating an association authorization from the hosted zone owner's account, and then performing the association from the VPC owner's account.
Soru 479Soru

A company manages its multi-account environment using AWS Organizations. The administration wants to consolidate billing to leverage volume discounts and share VPC subnets from a central network account to application accounts. Which of the following statements are correct regarding AWS consolidated billing and resource sharing? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Consolidated billing aggregates usage across all member accounts in the organization, allowing the company to qualify for volume pricing discounts on services like Amazon S3.; AWS Resource Access Manager (RAM) allows the central network account to share VPC subnets with application accounts, enabling application resources to be deployed directly in the shared subnets.

Cevap

Consolidated billing aggregates usage across all member accounts in the organization, allowing the company to qualify for volume pricing discounts. AWS Resource Access Manager (RAM) allows the central network account to share VPC subnets with application accounts, enabling application resources to be deployed directly in the shared subnets.
The correct answer combines the concepts of consolidated billing and AWS RAM. Consolidated billing aggregates usage across all member accounts in the organization, allowing them to qualify for volume pricing discounts (such as S3 storage tiers). AWS Resource Access Manager (RAM) allows a central network account to share subnets with other member accounts, allowing resources in those accounts to be deployed directly within the same subnets without duplicating the underlying VPC infrastructure.

Adım Adım Çözüm

1
Analyze consolidated billing rules
Consolidated billing combines usage across all member accounts in the AWS Organization to qualify for volume tier discounts.
This confirms consolidated billing works at the organization level for cost optimization.
2
Analyze resource sharing capabilities via AWS RAM
AWS RAM natively supports sharing subnets within an AWS Organization.
This allows resources in separate member accounts to be provisioned within the same subnet, reducing duplicate VPC infrastructure and administrative overhead.
3
Verify SCP functionality
SCPs only restrict permissions and cannot grant access across accounts.
This rules out using SCPs as a mechanism to grant cross-account S3 access.
4
Verify KMS key sharing rules
AWS-managed keys cannot be shared cross-account because their policies cannot be modified.
This rules out using aws/s3 for cross-account S3 access, requiring customer managed keys instead.

Anahtar Kavram

AWS Organizations consolidated billing and resource sharing via AWS Resource Access Manager (RAM) are key mechanisms for managing multi-account cost optimization and network administration.
Tahmini Süre:1m 30s
Soru 480Soru

A multi-national corporation uses AWS Organizations to manage a multi-account structure with hundreds of member accounts. The corporation uses an external SAML 2.0 compliant Identity Provider (IdP) for federating access to the AWS Management Console and AWS CLI. The security team has implemented a tagging standard where all IAM roles in member accounts must be tagged with a Department key indicating which team owns the role. To enforce strict security boundaries, the security team requires that federated users can only assume an IAM role if their department membership in the corporate directory (sent as a SAML attribute) matches the Department tag of the IAM role. Additionally, this matching policy must be enforced centrally such that member account administrators cannot bypass it or misconfigure their local roles to allow unauthorized cross-department access. Which configuration strategy will meet these requirements while allowing successful federation?

Cevabı ve açıklamayı göster

Cevap: Configure the SAML IdP to release the department attribute as a SAML attribute named https://aws.amazon.com/SAML/Attributes/PrincipalTag:Department. In each member account, configure the target IAM roles' trust policies to trust the SAML provider and allow both the sts:AssumeRoleWithSAML and sts:TagSession actions. Attach a Service Control Policy (SCP) to the root of the AWS Organization that denies the sts:AssumeRoleWithSAML action if the value of aws:RequestTag/Department does not match the value of the role's Department tag.

Cevap

The configuration strategy that maps the department attribute to a PrincipalTag SAML attribute, permits both sts:AssumeRoleWithSAML and sts:TagSession in the IAM role trust policies, and uses a centralized SCP to deny the sts:AssumeRoleWithSAML action if the request tag does not match the resource tag.
The correct configuration requires mapping the department attribute in the Identity Provider (IdP) to a session tag by naming it https://aws.amazon.com/SAML/Attributes/PrincipalTag:Department. The IAM role's trust policy in the member accounts must allow both sts:AssumeRoleWithSAML and sts:TagSession to authorize STS to apply these tags to the federated session. Finally, a Service Control Policy (SCP) must be attached at the organization root to deny the role assumption if the incoming department tag (aws:RequestTag/Department) is not equal to the role's Department tag. This denies the request before the session is established and ensures compliance centrally.

Adım Adım Çözüm

1
Configure the SAML Identity Provider (IdP) to pass the user's department attribute as a session tag.
The SAML assertion includes the attribute mapped to the claim https://aws.amazon.com/SAML/Attributes/PrincipalTag:Department.
This prefix is required by AWS STS to ingest the attribute as a session tag that can be evaluated during role assumption.
2
Configure the local IAM role trust policies in the member accounts to permit trust relationship actions.
The trust policies allow both sts:AssumeRoleWithSAML and sts:TagSession actions for the SAML provider principal.
Allowing sts:TagSession is mandatory whenever session tags are passed in the SAML assertion; omitting it results in an Access Denied error.
3
Implement a Service Control Policy (SCP) at the root level of the AWS Organization.
The SCP contains a Deny statement on sts:AssumeRoleWithSAML with a condition checking if aws:RequestTag/Department matches the dynamic resource tag value ${aws:ResourceTag/Department}.
This centrally enforces the department matching boundary across all member accounts, preventing local administrators from bypassing the security requirements.

Anahtar Kavram

SAML 2.0 Session Tagging and Policy Guardrails in Multi-Account Organizations
Tahmini Süre:3m 0s
ÖncekiSayfa 24 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin