MENU
Refer to the exhibit.
A network engineer developed an Ansible playbook and committed it to GitLab. A GitLab CI pipeline is started but immediately fails. What is the issue?
Suggested Answer: B
Get Premium 350-901 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
PA
Paris
11 months ago
Surprised that no one mentioned the runner task; that could be a big deal!
LE
Leanna
11 months ago
Wait, are we sure it's not just a simple parameter mistake (option A)?
PA
Paulina
11 months ago
The runner using the wrong Docker version sounds plausible too (option D).
SI
Simona
11 months ago
I disagree, it could easily be a formatting issue (option B).
GI
Giuseppe
12 months ago
I think it's option C, undefined variable issues are common.
ST
Stephaine
12 months ago
I feel like the formatting issue is a strong contender, but I also wonder if it could be related to the parameters used in the runner task.
SA
Sang
1 year ago
This question feels familiar; I practiced one where the runner had the wrong Docker version, but I can't remember if that was a common cause for failure.
HI
Hildegarde
1 year ago
I think undefined variables are a common issue in Ansible, but I can't recall if that's what usually causes a CI pipeline to fail right away.
PO
Pok
1 year ago
I remember something about formatting issues causing playbooks to fail, but I'm not sure if that's the main problem here.
CI
Ciara
1 year ago
Alright, time to put my Ansible and GitLab CI knowledge to the test. I'll carefully examine the code and the pipeline setup to identify the root cause.
BO
Bong
1 year ago
I'm a bit confused by the options. Is there any additional information I can use to narrow down the problem? I want to make sure I don't miss something important.
LE
Leoma
1 year ago
I'm feeling pretty confident about this one. The formatting issue or undefined variable seem like the most likely culprits, so I'll start there.
IS
Isadora
1 year ago
Okay, let's see. The options mention a few potential problems, so I'll need to methodically go through each one and see if I can spot the issue.
AS
Asha
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the Ansible playbook and the GitLab CI pipeline to identify the issue.
FR
Frank
1 year ago
Come on, it's gotta be the runner task! That's the easiest thing to mess up. I can just picture the engineer typing the wrong parameter and then facepalming.
DA
Dallas
1 year ago
My money's on the undefined variable. Ansible can be picky about that, and it's an easy mistake to make when you're working across multiple files.
LE
Leslie
1 year ago
Haha, the runner running the wrong Docker version? That's a classic. I've seen that trip up so many people, they forget to check the environment.
MA
Marylou
1 year ago
Ah, the dreaded formatting issue! I bet that's it. Those Ansible playbooks can be finicky with the whitespace and indentation.
DE
Denae
1 year ago
User 4: Could be the issue with the playbook's indentation.
AU
Audra
1 year ago
User 3: Maybe the playbook task has a formatting problem.
IL
Ilona
1 year ago
User 2: Yeah, Ansible playbooks can be picky about whitespace.
SH
Shawana
1 year ago
User 1: I think it's a formatting issue.
TR
Tran
1 year ago
The runner task using an incorrect parameter seems like the most likely issue here. I've seen that happen before when the playbook was working fine locally but failed in the CI pipeline.
PA
Paola
1 year ago
Maybe the runner is running the wrong Docker version, that could be another reason for the pipeline to fail.
LI
Lilli
1 year ago
I think it might be a formatting issue in the Ansible playbook task, that can also cause failures in the pipeline.
LE
Leoma
1 year ago
I agree, the runner task using an incorrect parameter could definitely cause the pipeline to fail.
VE
Verda
2 years ago
I believe the problem could be with the runner task using an incorrect parameter.
TR
Trinidad
2 years ago
I agree with Sol, there could be a formatting issue in the playbook.
SO
Sol
2 years ago
I think the issue might be with the Ansible playbook task.