What is the benefit of assigning projects to appropriate groups or subgroups?

It automatically creates epics for each project

It guarantees that the project will be included in the portfolio's roadmap

It prevents users from accessing the project without a special invitation

It ensures that the projects inherit the group's permissions and visibility settings

A portfolio manager is responsible for tracking progress across multiple teams. The teams are organized into subgroups under a top-level group 'Engineering'. The portfolio manager needs to see the progress of epics that span multiple projects within different subgroups. What is the most effective way to achieve this?

Create epics at the top-level group 'Engineering' and link issues from projects in the subgroups to these epics.

Create epics in each subgroup and link issues from projects within that subgroup.

Create a separate top-level group for epics and link issues from all projects to those epics.

Use labels to track progress across projects and subgroups.

What is the purpose of configuring group-level permissions in GitLab?

To set the default branch name for all projects in the group

To determine the maximum number of projects allowed in the group

To control which users can access and perform actions on projects within the group

To configure the group's CI/CD pipeline variables

In GitLab, how do you create a subgroup within an existing group?

Send an email to the GitLab administrator to request a subgroup

Navigate to the group, click 'New subgroup', and fill in the details

Use the 'Fork' feature to duplicate the group

Create a new project and then move it into the group

How does the group hierarchy support portfolio management in GitLab?

It allows epics to be created at the group level, aggregating work from multiple projects

It automatically generates a Gantt chart for all projects in the group

It restricts epics to a single project, simplifying tracking

It requires all projects to be in the same subgroup to be part of a portfolio

GitLabCertified Agile Portfolio Management Associate

Domain 1Objective 2

Set up the Organizational Hierarchy for Portfolio Management GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 2)

Part of the Organizational Structure domain, which makes up ~10% of our current practice bank.

13questions here

3free pages

6concepts

Questions 6–10

6foundation · easy
What is the benefit of assigning projects to appropriate groups or subgroups?
Select an answer first
7expert · hard
A portfolio manager is responsible for tracking progress across multiple teams. The teams are organized into subgroups under a top-level group 'Engineering'. The portfolio manager needs to see the progress of epics that span multiple projects within different subgroups. What is the most effective way to achieve this?
Select an answer first
8foundation · easy
What is the purpose of configuring group-level permissions in GitLab?
Select an answer first
9foundation · easy
In GitLab, how do you create a subgroup within an existing group?
Select an answer first
10foundation · easy
How does the group hierarchy support portfolio management in GitLab?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE” is a trademark of its owner, used for identification only.