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

PeopleCert Exam DevOps-Engineer Topic 4 Question 28 Discussion

Actual exam question for PeopleCert's PeopleCert DevOps Engineer exam
Question #: 28
Topic #: 4
[All PeopleCert DevOps Engineer Questions]

Which or the following commonly adoptee DevOps team approaches is the BEST example of a DevOps teaming model that does not fully support the overall goals of DevOps?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

I think the answer is A, DevOps as a tools team.
upvoted 0 times
...
Penney
22 days ago
You're probably right, Alishia. They're testing our understanding of the DevOps philosophy, not just our knowledge of the terminology.
upvoted 0 times
...
Alishia
24 days ago
Haha, I bet the exam writers are trying to trick us with this one. They probably want us to think really deeply about how each approach aligns with DevOps principles.
upvoted 0 times
...
Lai
25 days ago
Hmm, that's a good point, Sharee. A 'DevOps as a tools team' approach could create a siloed mentality, which goes against the principles of DevOps.
upvoted 0 times
...
Sharee
26 days ago
From my understanding, a 'DevOps as a tools team' approach is where a dedicated team is responsible for selecting and managing the DevOps tools. This doesn't seem to fully support the collaborative and cross-functional nature of DevOps.
upvoted 0 times
...
Freida
28 days ago
I agree, Lai. The wording of the question is a bit confusing. We need to really understand the nuances of each approach to determine which one doesn't align with the overall goals of DevOps.
upvoted 0 times
...
Lai
30 days ago
This question seems a bit tricky. I'm not sure I fully understand the context of these different DevOps team approaches.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77