Deal of The Day! 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 CJE Exam - Topic 1 Question 29 Discussion

A freestyle job is set up to "Enable concurrent builds if necessary" and configured to run on a single node. How can you ensure that multiple concurrent runs share the same workspace?
D) Define a 'Custom workspace' path for the job.
A) Pass the argument -Dhuason.model .Run. lockworkspace=false in the Jenkins master Invocation.
B) Check 'Do not lock workspace' In the Advanced Project Options of the project.
C) Multiple concurrent runs can never share the same workspace.

CloudBees CJE Exam - Topic 1 Question 29 Discussion

Actual exam question for CloudBees's CJE exam
Question #: 29
Topic #: 1
[All CJE Questions]

A freestyle job is set up to "Enable concurrent builds if necessary" and configured to run on a single node. How can you ensure that multiple concurrent runs share the same workspace?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Marguerita at May 04, 2022, 12:10 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Stephen
10 months ago
Huh, I didn't know you could do that with the workspace settings!
upvoted 0 times
...
Nina
10 months ago
I usually set a custom workspace, so option D makes sense.
upvoted 0 times
...
Lucina
10 months ago
Definitely not option C, that's just wrong.
upvoted 0 times
...
Sang
10 months ago
Wait, are you sure multiple runs can share the same workspace? Sounds risky.
upvoted 0 times
...
Lavina
11 months ago
I think option B is the way to go!
upvoted 0 times
...
Tasia
11 months ago
I’m pretty sure option C is incorrect because I’ve seen setups where multiple builds can share a workspace, but I can’t recall the exact method.
upvoted 0 times
...
Colby
11 months ago
I remember practicing a question similar to this, and I feel like locking the workspace is a key factor, so maybe option A is the right choice?
upvoted 0 times
...
Celeste
11 months ago
I think option B sounds familiar, but I'm not entirely sure if it really allows concurrent builds to share the same workspace.
upvoted 0 times
...
Tyisha
11 months ago
Option D seems plausible, but I wonder if defining a custom workspace would really allow concurrent builds to share it.
upvoted 0 times
...
Lucy
11 months ago
I recall a practice question where we had to choose between locking and sharing workspaces, but I can't remember if multiple runs can actually share them.
upvoted 0 times
...
Isidra
11 months ago
I'm not entirely sure, but I feel like option A might be related to some command line argument we discussed in class.
upvoted 0 times
...
Salena
11 months ago
I think option B sounds familiar; I remember something about not locking the workspace in the advanced settings.
upvoted 0 times
...
Kasandra
11 months ago
Option D seems plausible, but I wonder if defining a custom workspace would actually help with concurrent runs sharing it.
upvoted 0 times
...
Novella
11 months ago
Hmm, I'm a bit confused on this one. I think it might be C, where all the metrics in a base search are used by one service. But I'm not totally sure.
upvoted 0 times
...
France
11 months ago
Ah, the Microsoft 365 Roadmap! That's definitely the way to go. It's designed to track and communicate new feature releases, so that's got to be the best choice here.
upvoted 0 times
...

Save Cancel