Project Creation

Which of the following exists in both team-managed and company-managed Kanban Projects sidebar? (Choose two.) Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects

• Version releases

• A website link shortcut

• Project components

• Integration with Opsgenie for on-call and incident management.

Answer explanation

Which of the following are true about Jira board for a team-managed and a company-managed project? Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects.

• Users can have both team-managed and company-managed projects on the same team-managed board.

• Users cannot have multiple team-managed projects in a company-managed board.

• Users can only have a single board in the team-managed project.

• Users can only have a single board in the company-managed project.

Answer explanation

A team-managed project can only have a single board, which only belongs to that project. A company-managed project can have multiple boards, including mixed team-managed or company-managed projects.

Sarah is working on a financial project that involves sensitive information which should not be openly available to any users. She wants to create a new team-managed project for her assignment. Suggest the best access level for Sarah's project. Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects.

• Limited

• Restricted

• Private

• Open

Answer explanation

Since Sarah's project contains sensitive information, she should use private level access for her project. By using this access level, Sarah can control who can have access to manage issues in her project. These are the three access levels in team-managed Jira projects: Open - Anyone with access to the site can search, view, create, or edit this project's issues. Limited - Anyone with access to the site can search, view, and comment on this project's issues. Only people added to the project can create and edit its issues. Private - Only admins and people added to the project can search, view, create, or edit its issues.

Which of the following is not the default team-managed project role? Note - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects.

• Member

• User

• Administrator

• Viewer

Answer explanation

Team-managed software projects come with three roles by default:

-Administrator

- Member

- Viewer

Administrator - Admins can do most things, such as: update settings, add other admins to the project, manage features, customize issue types, and add rules on the board. Admins need product access to Jira Software to get the full benefit of this role.

Member - Members are a part of the team. They can create issues, edit them, comment on them, move them into different statuses, and generally collaborate on the project's work. Members need product access to Jira Software to get the full benefit of this role.

Viewer - Viewers can search through and view issues in the project, but not much else. You can give any registered user on your Jira site this role without extra product access.

New developers will join a team to work on a web application project. As a project administrator, Dom needs to ensure he has the proper access to control their permission. Which of the following should Dom add to the project permission scheme?

• Roles

• Groups

Answer explanation

Since Dom is not the site administrator, he cannot manage any group membership. As a project administrator, he can only manage roles membership. Group:

- Only site administrators have access to create groups and assign users to the group.

- Groups can be associated with global and project permissions.

- Groups can be used in multiple Jira projects.

Which Jira user type is the most suitable for Nash for the following responsibilities?

- Manage project roles membership.

- Update project details and basic settings.

- Manage boards and field layout.

• Jira Software users

• Project administrator

• Site administrator

• Jira administrator

Answer explanation

Site administrators:

- Usually someone that has the authority to manage the team's finances.

- Manage new users. - Manage billing and subscriptions.

- Manage site settings.

Jira administrators:

- Usually someone that has good technical knowledge in Jira.

- Manage Jira plugins. - Manage Jira global configurations (Global permissions, global settings, etc).

- Manage Jira schemes (Workflow, permissions, screens, notifications, etc).

Project administrators:

- Usually someone that is managing a specific Jira project.

- Manage project configurations (Roles, project details, etc).

Razi is the Jira administrator for the WINDOWS Jira project. He received a new request to create a new Jira project called LINUX, and both projects need to have the same configurations. Razi created the LINUX Jira project using the shared configuration option to ensure both projects have the same configurations. Assuming the WINDOWS project is already configured with all of the below configurations, which configurations does Razi have to update in the LINUX project manually? (Choose two.)

• Notification

• Project Avatar

• Priority

• Components

Answer explanation

Jira will not copy the below configurations if users created a project using the shared configuration option. These configurations are associated with a single Jira project and cannot be shared across other projects:

- Components

- Version

- Project role members

- Project avatar

- Project description

Nina recently joined as a finance manager. Her team already has a few Jira projects running that is related to finance projects. She needs to create a new project using the same configurations as the other finance projects. In the image is the configuration she used to create the project.

What will happen to Nina's Jira project (RMC) if the team that is managing the USC project changed their Jira configuration?

• Nothing will happen. Jira will only apply the configuration changes at the initial Jira project creation.

• Nina has permission to accept the configuration changes if she needs them.

• All answers are incorrect.

• Any changes with the other team's Jira project will automatically apply to Nina's Jira project.

Answer explanation

Jira has an option which allows users to create a Jira project using the existing project's configuration. In this example, any changes with the Jira project that shares the same configuration will also apply to Nina's Jira project. If users have 10 Jira projects using the shared configuration, any changes with one of the projects will be applied to all other projects.

Nick's Team is responsible for developing a new mobile application for their client. Each module will be delivered continuously to the client until they complete the project. Which of the following Jira Software template is suitable for Nick's Team?

• Project management

• Kanban

• Scrum

• Bug Tracking

Answer explanation

Kanban vs Scrum | Atlassian

Dom is working as a project manager for a Jira project called EPAY. The project has been deployed to production and transferred to another company for maintenance. Which of the following action allows Dom to hide the EPAY issues from the advanced search, but other users can still access the issues through direct links.

• Archive the Jira project.

• Permanently delete the Jira project.

• Hide the Jira project.

• Move the Jira project to trash.

Answer explanation

Users can archive inactive projects along with their issues, components, attachments, and versions. This won't affect associated schemes, workflows, issue types, or any content that is shared with other projects. When a project is archived, its issues won't appear in basic or advanced search results. Users can still access these issues through direct links, but you won't be able to edit them.

A hidden project will still be visible to people with admin permissions; regular users won't be able to search, view or modify any of the project's issues.

Users can get rid of projects that they don't need by moving them to trash. The projects along with its issues, components, attachments, and versions will be available in the trash for 60 days, after which they will be permanently deleted. Associated schemes, workflows, issues types, or any content that could be shared with other projects won't be affected. Issues from projects in trash won't appear in issue search results.

To permanently delete a project, users must first move the project to trash. Once they permanently delete a project from the trash, they won't be able to recover it. If they think that they might need the project later, it is recommended to either archive projects or hide projects instead.