DCA practice question 12 of 25

You add a new user to the engineering organization in DTR. Will this action grant them read/write access to the engineering/api repository? Solution: Add them to a team in the engineering organization that has read/write access to the engineering/api repository.

Full set: 191 questions
Answer options
A: Yes
B: No Correct answer
Correct Answer:
B. No
Explanation

The question asks if the action of adding a user to an organization will grant them repository access. The answer is no. This action alone is insufficient. While the provided "Solution" describes the correct subsequent step to grant access (adding the user to a team with permissions), it is a separate action. The initial act of adding a user to the 'engineering' organization does not, by itself, confer any permissions to the 'engineering/api' repository. Access must be explicitly configured via teams or direct user permissions.

Why Incorrect

A. Yes: This is incorrect because adding a user to an organization is only the first step; it does not grant repository-level permissions without further configuration.

References

1. Mirantis Kubernetes Engine Documentation, "Manage access to your repositories". The documentation outlines a multi-step process: users are added to organizations, then organized into teams, and finally, teams are granted permissions on repositories. This workflow demonstrates that adding a user to an organization does not automatically grant repository access.

2. Mirantis Kubernetes Engine Documentation, "Create and manage teams". This section details how teams are the primary mechanism for implementing role-based access control (RBAC) for repositories within an organization.

Scroll to Top