New Year Sale 2026! 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

LPI 701-100 Exam - Topic 4 Question 60 Discussion

Actual exam question for LPI's 701-100 exam
Question #: 60
Topic #: 4
[All 701-100 Questions]

Which of the following kinds of data are suitable as artifacts in a continuous delivery pipeline? (Choose three correct answers.)

Show Suggested Answer Hide Answer
Suggested Answer: C, D, E

by Sherita at Mar 06, 2024, 02:26 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Margurite
3 months ago
I disagree with B, it feels redundant to include source code.
upvoted 0 times
...
Vicky
3 months ago
A and D are must-haves for sure!
upvoted 0 times
...
Graciela
3 months ago
Wait, are we really considering copies of source code as artifacts?
upvoted 0 times
...
Lonny
4 months ago
I think B is also a good choice.
upvoted 0 times
...
Marlon
4 months ago
Definitely A, C, and E!
upvoted 0 times
...
Sabine
4 months ago
Docker images definitely count as artifacts, but I can't recall if compiled packages for Linux are also included.
upvoted 0 times
...
Devora
4 months ago
I remember practicing with build configuration files; they seem essential for the pipeline, right?
upvoted 0 times
...
Beatriz
4 months ago
I'm not so sure about the copies of source code repositories being artifacts. I feel like they might not fit the definition.
upvoted 0 times
...
Lewis
5 months ago
I think executable applications like .exe files are definitely artifacts we would use in a continuous delivery pipeline.
upvoted 0 times
...
Hassie
5 months ago
This is a good test of my understanding. I'll methodically go through each option and think about whether it aligns with the goals and practices of continuous delivery.
upvoted 0 times
...
Dexter
5 months ago
I'm a bit unsure about some of these options. I'll need to review my notes on continuous delivery to make sure I understand which artifacts are appropriate and why.
upvoted 0 times
...
Renay
5 months ago
Okay, let's see. I know executable applications and compiled packages are common artifacts, but what about the other options? I'll need to consider how they fit into the continuous delivery process.
upvoted 0 times
...
Noah
5 months ago
Hmm, this question seems straightforward. I'll need to think about the key characteristics of a continuous delivery pipeline and what kinds of artifacts would be suitable.
upvoted 0 times
...
Lakeesha
5 months ago
I'm pretty confident about this one. Copies of source code, build configuration files, and Docker container images all seem like they would be great artifacts to include in a continuous delivery pipeline.
upvoted 0 times
...
Rolland
5 months ago
Based on the question, it seems like using the CELLCLI CALIBRATE command as the celladmin user is the way to go. And the ILOM hardware monitoring is also a valid option. I feel pretty confident about this one.
upvoted 0 times
...
Elmira
5 months ago
Hmm, I'm a bit unsure about this one. The question is asking about filling skill gaps, but there are a lot of factors to consider. I'll need to really think through the options and make sure I understand the requirements.
upvoted 0 times
...
Vallie
10 months ago
Haha, I bet the folks who wrote this question were just trying to trip us up with those other options. A, C, and E are clearly the way to go. Who would ever want to deploy a .exe file through a continuous delivery pipeline?
upvoted 0 times
Desmond
8 months ago
I think the other options are just there to throw us off. Stick with A, C, and E for sure.
upvoted 0 times
...
Belen
8 months ago
Yeah, those options make the most sense. Executable applications and Docker container images are perfect for deployment.
upvoted 0 times
...
Virgina
9 months ago
I agree, A, C, and E are definitely the most suitable artifacts for a continuous delivery pipeline.
upvoted 0 times
...
...
Elroy
10 months ago
This is a tricky one, but I think A, D, and E are the right answers. Compiled packages can definitely be part of the delivery process, even if they're not the final artifacts.
upvoted 0 times
...
Polly
10 months ago
I agree with A, C, and E. Putting source code in the pipeline would be way too much data to handle. Plus, the pipeline should be about delivering artifacts, not the raw source code.
upvoted 0 times
Susana
9 months ago
E) Docker container images which contain an application.
upvoted 0 times
...
Johnna
10 months ago
C) Build configuration files such as Makefiles or Maven configurations.
upvoted 0 times
...
Alica
10 months ago
A) Executable applications such as .exe files or .jar packages.
upvoted 0 times
...
...
Dominic
10 months ago
I believe B, C, and D are also important artifacts to include in the pipeline.
upvoted 0 times
...
Bev
11 months ago
A, C, and E seem like the obvious choices here. I can't imagine trying to deploy executable files or package manager files through a continuous delivery pipeline.
upvoted 0 times
...
Lottie
11 months ago
I agree with Leana. Those artifacts are essential for a continuous delivery pipeline.
upvoted 0 times
...
Leana
11 months ago
I think A, C, and E are suitable artifacts.
upvoted 0 times
...

Save Cancel