MENU
How can you configure a Declarative Pipeline to record the fingerprint of an artifact?
Suggested Answer: D
Get Premium CJE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Authorization and authentication are different but related concepts. They don't vary or indicate a level of strictness.
38 comments · newest first
EA
Earnestine
11 months ago
I thought fingerprints were automatic in Declarative Pipelines, but maybe not?
GL
Glennis
11 months ago
Wait, so there's an 'enableFingerprints' option? Sounds new!
JI
Jimmie
11 months ago
I agree with D, that's how I've always done it.
DO
Dortha
11 months ago
Definitely not E, that's a common misconception!
CA
Cathrine
11 months ago
I think it's option D, setting 'fingerprint: true' for archiveArtifacts.
MA
Martin
12 months ago
I thought Declarative Pipelines automatically recorded fingerprints, but that seems too simple. Maybe there's more to it?
VO
Vonda
12 months ago
I practiced a question similar to this, and I feel like calling the fingerprintArtifact() step after archiving could be the right approach.
LA
Lashonda
1 year ago
I remember something about enabling fingerprints in the Declarative Pipeline options, but I can't recall the exact syntax.
LA
Lai
1 year ago
I think we might need to use the 'fingerprint: true' argument with the archiveArtifacts step, but I'm not entirely sure.
WA
Wai
1 year ago
I'm a bit confused by this question. I'm not entirely sure how to configure a Declarative Pipeline to record an artifact fingerprint. I'll have to review the relevant documentation and examples to see if I can figure out the best way to approach this. Hopefully, I can come up with a solid strategy before the exam.
SH
Shantell
1 year ago
I feel pretty good about this one. I think the answer is D - setting the 'fingerprint: true' argument for the archiveArtifacts step. That seems like the most straightforward way to record the artifact fingerprint in a Declarative Pipeline. I'll double-check my work, but I'm confident that's the right approach.
OR
Ora
1 year ago
Ah, this is a tricky one. I'm leaning towards A, calling the fingerprintArtifact() step after archiveArtifacts(), but I'm not totally convinced that's the correct solution. I'll have to think this through carefully.
AL
Alex
1 year ago
Hmm, I'm not entirely sure about this one. I was thinking maybe B, enabling the 'enableFingerprints' option, but I'm not 100% confident that's the right approach. I'll have to review the Declarative Pipeline documentation again to be sure.
TA
Tamekia
1 year ago
I think the answer is D. Setting the 'fingerprint: true' argument for the archiveArtifacts step seems like the most straightforward way to configure the Declarative Pipeline to record the fingerprint of an artifact.
AL
Alpha
1 year ago
This seems like a good opportunity to showcase my knowledge of storage system design. I'll carefully consider each option and select the ones that best match the high-reliability features described in the prompt.
KE
Kenneth
1 year ago
Hmm, I'm a bit unsure about this one. The wording is a little tricky, and I'm not totally confident in my understanding of the terms used. I'll have to think it through carefully.
TA
Tamesha
1 year ago
Hmm, I'm not too familiar with this API, so I'll need to think it through. The options mention managing ruleapp projects, ruleset resources, and creating/listing/removing RuleApps and rulesets. I'll need to consider which of these functionalities best describes the purpose of this API.
VA
Vallie
1 year ago
I'm going to go with option A. It sounds like the most direct way to record the fingerprint right after archiving the artifact. Gotta love those explicit steps!
ED
Edelmira
1 year ago
Haha, option E is like the 'easy mode' of artifact fingerprinting. Just let the pipeline do all the work for you? Sign me up!
DO
Dottie
1 year ago
User 3: Option E does seem like the easiest choice. Just let the pipeline take care of it.
JU
Juan
1 year ago
User 2: I prefer the simplicity of option E too. Less work for me to do.
LE
Leandro
1 year ago
User 1: Yeah, option E sounds like the way to go. Let the pipeline handle it.
CH
Chanel
1 year ago
Ooh, options B and C sound interesting. I wonder if they're part of some global configuration that needs to be set up beforehand. I'll have to test that out.
FL
Florinda
1 year ago
Delsie: Let me know how it goes. I might test out option C as well.
DE
Delsie
1 year ago
User 2: Yeah, that sounds like it could work. I'll give it a try.
LI
Lisbeth
1 year ago
User 1: I think option B is the way to go. Enable the 'enableFingerprints' option.
NA
Natalya
1 year ago
Option D seems the most straightforward, but I'm not sure if it's the right way to do it in a Declarative Pipeline. I'll have to look into the documentation more.
GA
Garry
1 year ago
D) Set the 'fingerprint: true' argument for the archiveArtifacts() step.
KR
Kristine
1 year ago
C) Set the Fingerprint Artifacts global configuration option.
PA
Pamella
1 year ago
B) Enable the Declarative Pipeline 'enableFingerprints' 'option'.
FR
Francesco
1 year ago
User2: I'm not sure, maybe we should check the documentation first.
JA
Jamal
1 year ago
User1: I think option D is the way to go.
RY
Ryan
1 year ago
User2: I'm not sure, maybe we should check the documentation first.
HE
Helaine
1 year ago
A) CaII the fingerprintArtifact() step immediately after the archiveArtifacts( ) step.
EA
Earlean
1 year ago
User1: I think option D is the way to go.
IR
Irene
2 years ago
But wouldn't setting the 'fingerprint: true' argument for archiveArtifacts() also work?
MI
Mitsue
2 years ago
I disagree, I believe the correct answer is B) Enable the 'enableFingerprints' option.
IR
Irene
2 years ago
I think the answer is A) Call the fingerprintArtifact() step after archiveArtifacts().