4. Compare Software Development Methods (agile, Lean, and Waterfall) 200-901 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A network automation team is developing a new tool for zero-touch provisioning. The customer has a hard deadline in six months and a fixed budget. The team is split: some want to use Scrum to adapt to changing requirements, while others want to use Waterfall to ensure a predictable plan. The customer is willing to provide feedback every two weeks but also wants a clear cost commitment. Which approach best balances these conflicting needs?

   • AUse Scrum with a fixed-length sprint plan and a product backlog that is re-prioritized every two weeks, while tracking velocity to estimate the final cost
   • BUse Kanban with no fixed iterations and a variable cost based on actual work
   • CUse Waterfall with a detailed up-front design and a fixed cost contract
   • DUse a hybrid of Waterfall for planning and Scrum for implementation, but without a fixed budget
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A software team is building a new API for network device configuration. The product owner is available for daily feedback, and the team wants to release a new version every two weeks. They also want to avoid over-engineering by building only what is needed. Which combination of methods best fits this scenario?

   • AScrum with lean principles
   • BWaterfall with lean principles
   • CV-model with Scrum
   • DKanban with waterfall phases
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   What is the primary focus of the lean methodology in software development?

   • AEliminating waste and optimizing the flow of value to the customer
   • BUsing fixed-length iterations called sprints to deliver increments
   • CFollowing a strict sequential phase plan with formal reviews
   • DMaximizing documentation to ensure all requirements are captured
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A network automation team is using a lean approach to develop a new configuration validation tool. They have a limited budget and need to deliver value quickly. The team is considering whether to build a comprehensive tool with many features or a minimal tool that addresses the most critical validation checks. According to lean principles, which approach is preferred?

   • AUse a waterfall plan to ensure all features are delivered
   • BDelay development until all requirements are known
   • CBuild the comprehensive tool to avoid rework later
   • DBuild the minimal tool and iterate based on feedback
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A network automation project is using waterfall. During the testing phase, the team discovers that the requirements did not account for a new security policy, requiring significant rework. The project manager wants to minimize the impact. What is the most effective action?

   • AGo back to the requirements phase and update the documentation
   • BSwitch to agile mid-project
   • CProceed with the original requirements and document the gap
   • DAsk the customer to waive the security policy
   Reveal Solution Discussion Select an answer first