Authorization strategies (Matrix, role-based) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Matrix-based Authorization Strategy

In Jenkins, the Matrix-based security allows you to assign permissions to users or groups in a grid format. Which of the following best describes how permissions are assigned in this strategy?

A Permissions are assigned individually to each user or group by checking boxes in a matrix grid.

B Permissions are assigned only through predefined roles that users inherit automatically.

C Permissions are assigned randomly by Jenkins based on user activity.

D Permissions are assigned by editing the Jenkins core source code.

💡 Hint

Think about how a grid or table might be used to assign permissions.

Matrix-based security uses a grid where you check boxes to assign specific permissions to users or groups. This allows fine-grained control.

💻 Command Output

intermediate

Role-based Authorization Plugin Output

After configuring the Role-based Authorization Strategy plugin in Jenkins, you run a command to list all roles. What is the expected output format when you run jenkins-cli list-roles?

A A list of roles with their names and assigned permissions in plain text.

B A JSON object containing user passwords and roles.

C An error message saying 'Command not found'.

D A list of all Jenkins jobs with their build statuses.

💡 Hint

Think about what a role listing command should show.

The list-roles command outputs the roles defined in Jenkins along with their permissions in a readable plain text format.

🔀 Workflow

advanced

Configuring Role-based Authorization for a New Team

You want to create a new role called 'dev-team' in Jenkins with permissions to build and read jobs but not to configure system settings. Which sequence of steps correctly achieves this using the Role-based Authorization Strategy plugin?

A 3,1,2,4

B 1,3,2,4

C 2,1,3,4

D 1,2,3,4

💡 Hint

Think about first creating the role, then assigning it.

You first create the role with desired permissions, then assign it to users. Managing roles and assigning roles are separate steps.

❓ Troubleshoot

advanced

Troubleshooting Matrix Authorization Permission Denied

A user reports they cannot configure a job even though they are listed in the Matrix-based security with 'Job Configure' permission checked. What is the most likely cause?

A Jenkins is offline and cannot apply permissions.

B The user's browser cache is outdated.

C The user is not part of the group assigned the permission in the matrix.

D The Jenkins server needs a restart to apply matrix changes.

💡 Hint

Check if the user is actually included in the permission assignment.

Even if the permission is checked for a group, the user must belong to that group to have the permission. If not, they will be denied access.

✅ Best Practice

expert

Best Practice for Combining Matrix and Role-based Authorization

In a Jenkins environment with multiple teams and complex permission needs, what is the best practice for combining Matrix-based and Role-based Authorization strategies?

A Avoid using Role-based Authorization and rely only on Matrix-based for all permissions.

B Use Role-based Authorization for broad role definitions and Matrix-based for fine-grained permission tweaks within roles.

C Use both strategies simultaneously on the same Jenkins instance without restrictions.

D Disable all authorization and rely on external firewall rules.

💡 Hint

Think about how roles and detailed permissions complement each other.

Role-based Authorization is good for grouping users with common permissions, while Matrix-based allows detailed control. Combining them carefully provides flexibility and security.