MENU
You need to grant permissions, via matrix-based security, to run a specific command in a Jenkins pipeline. The project parameters will not allow you to create a specific user to run this task, and you have no relevant groups. Which of the following is an option?
Suggested Answer: C
Get Premium CJE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
You can set permissions for anonymous users with matrix-based security. Since this requires the least impact on existing workflows, it's the best solution.
40 comments · newest first
LE
Leonard
10 months ago
Wait, can you really let anonymous users run commands? That sounds off.
TH
Theola
10 months ago
Totally agree with D, it makes the most sense.
DO
Doug
10 months ago
I think D is the best choice here.
JA
Janella
11 months ago
A and B are not possible since we can't create a user.
DA
Dante
11 months ago
Option C seems risky, allowing anonymous users?
LA
Lavina
11 months ago
I thought setting permissions for anonymous users was risky, but it might be the only way if we can't create a group or user.
LI
Linsey
11 months ago
I feel like changing the workflow to require an existing user might be a solution, but I can't recall if that's the best option.
JE
Jesusita
11 months ago
I think we practiced a question similar to this, and creating a group seemed like the right approach, but we can't create one here.
RO
Rosendo
12 months ago
I remember something about matrix-based security, but I'm not sure if allowing anonymous users is a good idea.
CO
Corazon
12 months ago
I'm feeling pretty confident about this one. Option B is definitely the right choice - it's the only one that allows you to use an existing user without creating a new one.
DO
Dominga
12 months ago
Okay, I think I've got this. Option B is the way to go - create a group, add an existing user to it, and grant permissions to that group. Seems like the most straightforward solution.
AN
Angelyn
1 year ago
Hmm, I'm a bit confused by this question. I'm not sure if setting permissions for anonymous users is a good idea, but I'll have to think about it more.
TI
Tiffiny
1 year ago
This seems like a tricky one. I'm not sure if creating a group or reassigning the user will work, but option B looks like the best approach to me.
MA
Mattie
1 year ago
Hmm, I wonder if we could just bribe the Jenkins admin to create a new user for us. That would be a lot easier than all this security nonsense.
LO
Lonna
1 year ago
Hmm, I wonder if we could just bribe the Jenkins admin to create a new user for us. That would be a lot easier than all this security nonsense.
LY
Lyda
1 year ago
B) Create a group, add an existing user to the task, and grant permissions to that group
KI
Kimberely
1 year ago
A) Either creating a group or reassigning the user will work.
WI
Willie
1 year ago
That's a good point, Winifred. Option D does provide more control over who can run the command. It's important to consider security implications when setting up permissions in Jenkins.
EN
Ena
1 year ago
Option A? Really? That's like saying 'I can either fix the flat tire or just get a new car.' Not very helpful.
CL
Claudio
1 year ago
D) Change the workflow to require an existing user to run the task, and assign permissions to that user.
JI
Jina
1 year ago
B) Create a group, add an existing user to the task, and grant permissions to that group
WI
Winifred
1 year ago
I disagree, I believe option D is the way to go. Requiring an existing user to run the task ensures accountability and assigning permissions directly to that user is more straightforward.
JE
Jenise
1 year ago
Option D could work, but it might be a hassle to have to assign permissions to a specific user every time. Option B is probably the cleanest solution.
GR
Gregoria
1 year ago
Either creating a group or reassigning the user will work, so that's good to know.
IN
In
1 year ago
Creating a group and adding an existing user seems like the most efficient way to handle this.
LI
Linwood
1 year ago
I agree, Option B is probably the cleanest solution.
BE
Belen
1 year ago
Option D could work, but it might be a hassle to have to assign permissions to a specific user every time.
AL
Alona
2 years ago
I agree with Anastacia. Option B is the way to go here. Trying to use an anonymous user (Option C) sounds risky from a security standpoint.
RA
Raelene
1 year ago
I agree, creating a group and adding an existing user seems like the most secure option.
LO
Long
1 year ago
I think Option B is the best choice.
WI
Willie
2 years ago
I think option B is the best choice. Creating a group and adding an existing user seems like the most secure way to handle permissions.
AN
Anastacia
2 years ago
Option B seems like the most straightforward solution. Creating a group and adding an existing user to it makes sense when you can't create a new user.
WE
Weldon
1 year ago
Definitely. It's a workaround that can be effective in granting the necessary permissions.
MI
Michell
1 year ago
That's a good point. It's a practical way to handle permissions in this scenario.
ER
Ernest
1 year ago
Creating a group and adding an existing user to it makes sense when you can't create a new user.
ET
Ethan
1 year ago
Option B seems like the most straightforward solution.
DI
Dick
1 year ago
Definitely. It's a workaround that can be effective in granting the necessary permissions.
JA
Jackie
1 year ago
That's a good point. It's a practical way to handle permissions in this scenario.
AN
Annmarie
1 year ago
Creating a group and adding an existing user to it makes sense when you can't create a new user.
KA
Kasandra
1 year ago
Option B seems like the most straightforward solution.