ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 237 - DOP-C02 discussion

Report
Export

A company has an organization in AWS Organizations for its multi-account environment. A DevOps engineer is developing an AWS CodeArtifact based strategy for application package management across the organization. Each application team at the company has its own account in the organization. Each application team also has limited access to a centralized shared services account.

Each application team needs full access to download, publish, and grant access to its own packages. Some common library packages that the application teams use must also be shared with the entire organization.

Which combination of steps will meet these requirements with the LEAST administrative overhead? (Select THREE.)

A.
Create a domain in each application team's account. Grant each application team's account lull read access and write access to the application team's domain
Answers
A.
Create a domain in each application team's account. Grant each application team's account lull read access and write access to the application team's domain
B.
Create a domain in the shared services account Grant the organization read access and CreateRepository access.
Answers
B.
Create a domain in the shared services account Grant the organization read access and CreateRepository access.
C.
Create a repository in each application team's account. Grant each application team's account lull read access and write access to its own repository.
Answers
C.
Create a repository in each application team's account. Grant each application team's account lull read access and write access to its own repository.
D.
Create a repository in the shared services account. Grant the organization read access to the repository in the shared services account. Set the repository as the upstream repository in each application team's repository.
Answers
D.
Create a repository in the shared services account. Grant the organization read access to the repository in the shared services account. Set the repository as the upstream repository in each application team's repository.
E.
For teams that require shared packages, create resource-based policies that allow read access to the repository from other application teams' accounts.
Answers
E.
For teams that require shared packages, create resource-based policies that allow read access to the repository from other application teams' accounts.
F.
Set the other application teams' repositories as upstream repositories.
Answers
F.
Set the other application teams' repositories as upstream repositories.
Suggested answer: B, D, E

Explanation:

* Step 1: Creating a Centralized Domain in the Shared Services Account To manage application package dependencies across multiple accounts, the most efficient solution is to create a centralized domain in the shared services account. This allows all application teams to access and manage package repositories within the same domain, ensuring consistency and centralization. Action: Create a domain in the shared services account. Why: A single, centralized domain reduces the need for redundant management in each application team's account.

This corresponds to Option B: Create a domain in the shared services account. Grant the organization read access and CreateRepository access.

* Step 2: Sharing Repositories Across Teams with Upstream Configurations To share common library packages across the organization, each application team's repository can point to the shared services repository as an upstream repository. This enables teams to access shared packages without managing them individually in each team's account.

Action: Create a repository in the shared services account and set it as the upstream repository for each application team.

Why: Upstream repositories allow package sharing while maintaining individual team repositories for managing their own packages.

This corresponds to Option D: Create a repository in the shared services account. Grant the organization read access to the repository in the shared services account. Set the repository as the upstream repository in each application team's repository.

* Step 3: Using Resource-Based Policies for Cross-Account Access For teams that need to share their packages with other application teams, resource-based policies can be applied to grant the necessary permissions. These policies allow cross-account access without having to manage permissions at the individual account level.

Action: Create resource-based policies that allow read access to the repositories across application teams.

Why: This simplifies management by centralizing permissions in the shared services account while allowing cross-team collaboration.

This corresponds to Option E: For teams that require shared packages, create resource-based policies that allow read access to the repository from other application teams' accounts.

asked 16/09/2024
PATRICK ADUSEI
45 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first