HPE0-V28 · Question #38
What is often the result of maintaining traditional development cycles?
The correct answer is D. Line-of-Business (LoB) managers create their own stealth IT projects. Traditional development cycles are typically slow, rigid, and IT-controlled, which frustrates Line-of-Business managers who need solutions quickly - so they bypass IT entirely and fund their own unauthorized "shadow IT" projects, making D correct. Option A is wrong because…
Question
What is often the result of maintaining traditional development cycles?
Options
- AOperating costs and overhead decrease.
- BCollaboration becomes more efficient.
- CIT moves from a support role to a business role in the company.
- DLine-of-Business (LoB) managers create their own stealth IT projects.
How the community answered
(62 responses)- A6% (4)
- B2% (1)
- C3% (2)
- D89% (55)
Explanation
Traditional development cycles are typically slow, rigid, and IT-controlled, which frustrates Line-of-Business managers who need solutions quickly - so they bypass IT entirely and fund their own unauthorized "shadow IT" projects, making D correct. Option A is wrong because traditional cycles are notoriously expensive, with high overhead from lengthy planning and approval processes. Option B is wrong because siloed, sequential workflows (waterfall-style) actively hinder collaboration between business and IT. Option C is wrong because traditional cycles reinforce IT's support role - it's agile and DevOps transformations that shift IT toward a strategic business partner role.
Memory tip: Think "slow IT = shadow IT." When the official channel moves too slowly, LoB managers create their own lane.
Topics
Community Discussion
No community discussion yet for this question.