BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

CloudBees Exam CCJE Topic 4 Question 71 Discussion

Actual exam question for CloudBees's CCJE exam
Question #: 71
Topic #: 4
[All CCJE Questions]

You are the administrator of a base Jenkins master with the recommended set of plugins installed. You want to protect the Jenkins master against malicious (or bad) usages of Groovy methods. You also want your users to be able to share their Pipeline code via Globa Pipeline Libraries housed on a git repository under your company's Github Organization. Which of the following statements is TRUE?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Elizabeth at Aug 06, 2024, 10:01 PM

Limited Time Offer

25%

Off

Get Premium CCJE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Lino
3 months ago
Ooh, option B sounds spicy! Giving all the developers free rein to execute privileged methods? That's a bold move, but I kinda like it. Yolo, amirite?
upvoted 0 times
Martha
2 months ago
Yeah, it's definitely a bold move. We should prioritize security over convenience.
upvoted 0 times
...
Kimberlie
2 months ago
Option B does sound tempting, but it might be risky to give all developers that much power.
upvoted 0 times
...
...
Rolande
3 months ago
Haha, option D is just asking for trouble! I'm not letting any 'trusted' code anywhere near my Jenkins master. Security first, am I right?
upvoted 0 times
Rebecka
2 months ago
Let's go with option A then, configuring Global Pipeline Libraries at the Github Organization level for 'untrusted' code.
upvoted 0 times
...
Beckie
2 months ago
I agree, we can't afford to compromise the integrity of our Jenkins master.
upvoted 0 times
...
Melodie
2 months ago
Option D is definitely risky. We should always prioritize security.
upvoted 0 times
...
...
Ngoc
3 months ago
Hmm, I'm not sure about that. Doesn't option C sound better? Running the libraries as 'untrusted' code might be a bit risky, but at least the developers can still use the sandbox.
upvoted 0 times
Anglea
2 months ago
I see your point. It's important to balance security with usability when setting up Global Pipeline Libraries.
upvoted 0 times
...
Kirk
2 months ago
That's true. Option A ensures the libraries are running as 'untrusted' code, but still allows developers to share their Pipeline code.
upvoted 0 times
...
Leota
2 months ago
But wouldn't it be safer to configure Global Pipeline Libraries at the Github Organization level?
upvoted 0 times
...
Dierdre
2 months ago
Option C sounds better. Running the libraries as 'untrusted' code allows developers to use the sandbox.
upvoted 0 times
...
...
Lavelle
3 months ago
I agree with Cordell, option A seems like the best choice to protect against malicious usage of Groovy methods.
upvoted 0 times
...
Cordell
3 months ago
But configuring Global Pipeline Libraries at the Github Organization level makes more sense for security.
upvoted 0 times
...
Lynda
3 months ago
I disagree, I believe the answer is B.
upvoted 0 times
...
Leandro
3 months ago
Option A seems like the way to go. We can keep our developers safe while still letting them share their awesome Pipeline code.
upvoted 0 times
Shayne
3 months ago
Definitely, we want to prioritize security while also promoting collaboration among our developers.
upvoted 0 times
...
Judy
3 months ago
I agree, configuring Global Pipeline Libraries at the Github Organization level as 'untrusted' code is a good security measure.
upvoted 0 times
...
Ronna
3 months ago
Option A seems like the best choice. It allows us to protect against malicious Groovy methods while still enabling code sharing.
upvoted 0 times
...
...
Cordell
4 months ago
I think the answer is A.
upvoted 0 times
...

Save Cancel