Given the Project Risk and Customer Requirement, Explain How to Assess the Benefits and Risks of the Different Development Methodologies and Recommend the Appropriate Methodology Based on the Customer Environment. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   When justifying a recommended methodology, what should the rationale link the methodology to?

   • AThe cost of the methodology alone
   • BThe specific project risks and customer requirements
   • CThe personal preference of the project manager
   • DThe number of features in the methodology
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A customer is implementing Salesforce for a large enterprise with multiple business units. The project has a high degree of complexity, and the requirements are not fully defined. The customer's IT department is experienced with Waterfall and is resistant to Agile. The business stakeholders want to see progress early. The architect must recommend a methodology. What is the most important risk to address in the recommendation?

   • AThe business stakeholders' desire for early progress is unrealistic, so the architect should set expectations for a longer timeline.
   • BThe lack of defined requirements is a risk that cannot be mitigated, so the architect should recommend a phased approach with no fixed timeline.
   • CThe IT department's resistance to Agile may undermine the adoption of Scrum, so the architect should recommend a hybrid approach that introduces iterative practices gradually.
   • DThe complexity of the project makes Waterfall the only viable option, so the architect should recommend Waterfall despite the business's desire for early progress.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which benefit is most directly associated with the Agile methodology?

   • AHigh predictability of cost and schedule from the start
   • BAbility to adapt to changing requirements quickly
   • CComprehensive documentation at each phase
   • DMinimal need for customer involvement
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A customer's organization has a strong hierarchical culture where decisions are made by a small executive group. The project involves a complex Salesforce integration with multiple external systems. The business users are not empowered to make decisions during development. Which methodology is most likely to fail in this environment, and why?

   • AKanban, because it requires continuous prioritization by the business, which the culture does not support.
   • BDevOps, because it requires developers to make deployment decisions independently, which the culture does not support.
   • CScrum, because it requires empowered product owners and frequent stakeholder collaboration that the culture does not support.
   • DWaterfall, because it requires frequent sign-offs from business users at each phase, which the culture does not support.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A customer in the healthcare industry is implementing Salesforce for patient case management. The project has a fixed budget and a strict go-live date tied to a government reporting deadline. The customer's business users have conflicting requirements that have not been fully resolved, and they expect to see progress early. Which methodology offers the best balance of early visibility and adherence to the fixed constraints?

   • AKanban, because it allows the team to deliver features continuously without the overhead of sprint planning.
   • BScrum, because it provides regular demonstrations of working functionality while allowing the team to manage scope within the fixed timeline.
   • CWaterfall, because the fixed budget and deadline require a detailed plan that cannot accommodate changes.
   • DDevOps, because automation will reduce the time required for each release, helping meet the deadline.
   Reveal Solution Discussion Select an answer first