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

Cisco 350-901 Exam - Topic 5 Question 89 Discussion

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?
B) The Ansible playbook task has a formatting issue.
A) The runner task uses an incorrect parameter.
C) The Ansible playbook has an undefined variable.
D) The runner is running the wrong Docker version.

Cisco 350-901 Exam - Topic 5 Question 89 Discussion

Actual exam question for Cisco's 350-901 exam
Question #: 89
Topic #: 5
[All 350-901 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Carey at Jan 15, 2025, 03:27 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paris
9 months ago
Surprised that no one mentioned the runner task; that could be a big deal!
upvoted 0 times
...
Leanna
9 months ago
Wait, are we sure it's not just a simple parameter mistake (option A)?
upvoted 0 times
...
Paulina
10 months ago
The runner using the wrong Docker version sounds plausible too (option D).
upvoted 0 times
...
Simona
10 months ago
I disagree, it could easily be a formatting issue (option B).
upvoted 0 times
...
Giuseppe
10 months ago
I think it's option C, undefined variable issues are common.
upvoted 0 times
...
Stephaine
10 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.
upvoted 0 times
...
Sang
11 months 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.
upvoted 0 times
...
Hildegarde
11 months 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.
upvoted 0 times
...
Pok
11 months ago
I remember something about formatting issues causing playbooks to fail, but I'm not sure if that's the main problem here.
upvoted 0 times
...
Ciara
11 months 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.
upvoted 0 times
...
Bong
11 months 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.
upvoted 0 times
...
Leoma
11 months 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.
upvoted 0 times
...
Isadora
11 months 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.
upvoted 0 times
...
Asha
11 months 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.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
Denae
1 year ago
User 4: Could be the issue with the playbook's indentation.
upvoted 0 times
...
Audra
1 year ago
User 3: Maybe the playbook task has a formatting problem.
upvoted 0 times
...
Ilona
1 year ago
User 2: Yeah, Ansible playbooks can be picky about whitespace.
upvoted 0 times
...
Shawana
1 year ago
User 1: I think it's a formatting issue.
upvoted 0 times
...
...
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.
upvoted 0 times
Paola
1 year ago
Maybe the runner is running the wrong Docker version, that could be another reason for the pipeline to fail.
upvoted 0 times
...
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.
upvoted 0 times
...
Leoma
1 year ago
I agree, the runner task using an incorrect parameter could definitely cause the pipeline to fail.
upvoted 0 times
...
...
Verda
1 year ago
I believe the problem could be with the runner task using an incorrect parameter.
upvoted 0 times
...
Trinidad
1 year ago
I agree with Sol, there could be a formatting issue in the playbook.
upvoted 0 times
...
Sol
1 year ago
I think the issue might be with the Ansible playbook task.
upvoted 0 times
...

Save Cancel