ITIL ITILFND V5 Practice Test 61
Question 600
Which characteristic of Continuous integration is accurate when discussing ITIL Foundation (Version 5)?
- Frequently combining development changes into a shared code base with automated build and checks.
- An unplanned interruption or reduction in the quality of a product or service.
- A problem whose underlying cause is known and documented but may still await permanent correction.
- Assess and reuse the current state before designing unnecessary replacements.
Explanation
Correct Answer
A:Frequently combining development changes into a shared code base with automated build and checks. This describes the correct concept, rather than a neighboring area of ITIL guidance. The key idea is Continuous integration: Frequently combining development changes into a shared code base with automated build and checks. The workplace context is: A digital-product team needs early warning of conflicting changes.
Incorrect Answers
B:An unplanned interruption or reduction in the quality of a product or service. This is the description of Incident and does not define Continuous integration. The key idea is Continuous integration: Frequently combining development changes into a shared code base with automated build and checks. The workplace context is: A digital-product team needs early warning of conflicting changes.
C:A problem whose underlying cause is known and documented but may still await permanent correction. This is the description of Known error and does not define Continuous integration. The key idea is Continuous integration: Frequently combining development changes into a shared code base with automated build and checks. The workplace context is: A digital-product team needs early warning of conflicting changes.
D:Assess and reuse the current state before designing unnecessary replacements. This is the description of Start where you are principle and does not define Continuous integration. The key idea is Continuous integration: Frequently combining development changes into a shared code base with automated build and checks. The workplace context is: A digital-product team needs early warning of conflicting changes.
Question 601
An ITIL Foundation team is reviewing this concept: Keeping software in a state suitable for controlled release through an automated delivery process. Which term matches this description?
- Critical success factors and metrics
- Keep it simple and practical principle
- Continuous delivery
- Continuous integration
Explanation
Correct Answer
C:Continuous delivery. This is the correct ITIL term for the stated definition. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: A service team wants every passing build to be ready for a controlled manual go-live.
Incorrect Answers
A:Critical success factors and metrics. That term addresses a different definition: Success conditions and measurements used to judge whether an objective is being met. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: A service team wants every passing build to be ready for a controlled manual go-live.
B:Keep it simple and practical principle. That term addresses a different definition: Use straightforward work methods that serve clear needs without unnecessary complexity. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: A service team wants every passing build to be ready for a controlled manual go-live.
D:Continuous integration. That term addresses a different definition: Frequently combining development changes into a shared code base with automated build and checks. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: A service team wants every passing build to be ready for a controlled manual go-live.
Question 602
A service team wants every passing build to be ready for a controlled manual go-live. Which response would apply Continuous delivery most directly?
- Engage relevant stakeholders and expose timely work information to support coordinated decisions.
- Coordinate the release of a defined version with appropriate readiness and change controls.
- Automate building and validation so authorized release can happen reliably when selected.
- Classify practices according to their organizational scope and purpose.
Explanation
Correct Answer
C:Automate building and validation so authorized release can happen reliably when selected. This is the appropriate application of the stated concept in the scenario. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:Engage relevant stakeholders and expose timely work information to support coordinated decisions. This would apply Collaborate and promote visibility principle instead; Involve the right people and share clear information about work and decisions. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:Coordinate the release of a defined version with appropriate readiness and change controls. This would apply Release instead; A version or collection of product components made available for use. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
D:Classify practices according to their organizational scope and purpose. This would apply Management practice groups instead; A grouping that distinguishes general management practices from product and service management practices. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 603
A service team wants every passing build to be ready for a controlled manual go-live. Which statement is NOT correct about Continuous delivery?
- A relevant application would be: Automate building and validation so authorized release can happen reliably when selected.
- The team can use this concept in a way that remains accountable to stakeholder needs and outcomes.
- Continuous delivery means exactly the same thing as Start where you are principle in every service-management context.
- Continuous delivery addresses this kind of need: Keeping software in a state suitable for controlled release through an automated delivery process.
Explanation
Correct Answer
C:Continuous delivery means exactly the same thing as Start where you are principle in every service-management context. Those concepts are not interchangeable; Continuous delivery refers to keeping software in a state suitable for controlled release through an automated delivery process. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:A relevant application would be: Automate building and validation so authorized release can happen reliably when selected. This choice is incorrect. That application directly addresses the described scenario. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:The team can use this concept in a way that remains accountable to stakeholder needs and outcomes. This choice is incorrect. ITIL use remains context sensitive and outcome oriented; this claim does not negate the concept. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
D:Continuous delivery addresses this kind of need: Keeping software in a state suitable for controlled release through an automated delivery process. This choice is incorrect. That statement matches the concept described in the syllabus-aligned study scope. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 604
A service team wants every passing build to be ready for a controlled manual go-live. Consider four statements about Continuous delivery: 1. Continuous delivery is identical to Product specification in every ITIL context. 2. Using this concept always eliminates any need to consider feedback and stakeholder outcomes. 3. Continuous delivery concerns keeping software in a state suitable for controlled release through an automated delivery process. 4. A sensible use in this case is to automate building and validation so authorized release can happen reliably when selected. Which pair contains the TWO correct statements?
- 1 and 3
- 1 and 4
- 3 and 4
- 1 and 2
Explanation
Correct Answer
C:3 and 4. Both numbered statements accurately describe this ITIL concept and how it applies in the situation. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:1 and 3. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:1 and 4. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
D:1 and 2. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 605
During a Version 5 refresher, a learner reads: Keeping software in a state suitable for controlled release through an automated delivery process. Which ITIL term is being described?
- Problem
- Continual improvement component
- Product specification
- Continuous delivery
Explanation
Correct Answer
D:Continuous delivery. This is the correct ITIL term for the stated definition. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: An online retailer requires approval to choose the deployment time for validated software.
Incorrect Answers
A:Problem. That term addresses a different definition: A cause or possible cause of one or more incidents that needs investigation. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: An online retailer requires approval to choose the deployment time for validated software.
B:Continual improvement component. That term addresses a different definition: Repeated evaluation and adaptation to improve products, services and ways of working. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: An online retailer requires approval to choose the deployment time for validated software.
C:Product specification. That term addresses a different definition: A documented description of expected features, requirements or characteristics. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process. The workplace context is: An online retailer requires approval to choose the deployment time for validated software.
Question 606
An online retailer requires approval to choose the deployment time for validated software. Which proposed activity best demonstrates Continuous delivery rather than an unrelated concept?
- Coordinate relevant activities to create and maintain stakeholder outcomes.
- Coordinate value-chain activities around demand and outcomes, not departmental boundaries.
- Fulfill the documented standard request path rather than treating it as an unexpected outage.
- Automate building and validation so authorized release can happen reliably when selected.
Explanation
Correct Answer
D:Automate building and validation so authorized release can happen reliably when selected. This is the appropriate application of the stated concept in the scenario. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:Coordinate relevant activities to create and maintain stakeholder outcomes. This would apply Value chain component instead; A set of linked activities through which an organization responds to demand and enables value. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:Coordinate value-chain activities around demand and outcomes, not departmental boundaries. This would apply Value chain coordination instead; Orchestrating relevant organizational activities as a coherent operating model. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
C:Fulfill the documented standard request path rather than treating it as an unexpected outage. This would apply Service request instead; A user-initiated request for a predefined service action, information or access. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 607
An online retailer requires approval to choose the deployment time for validated software. Which explanation best distinguishes Continuous delivery from other ITIL concepts?
- Continuous delivery primarily means setting organizational policy, priorities and boundaries for decisions.
- Continuous delivery primarily means an engineering approach that applies software practices to operational service reliability.
- Continuous delivery primarily means recommendations that inform decisions and actions across organizational circumstances.
- Continuous delivery is concerned with keeping software in a state suitable for controlled release through an automated delivery process. In this case, automate building and validation so authorized release can happen reliably when selected.
Explanation
Correct Answer
D:Continuous delivery is concerned with keeping software in a state suitable for controlled release through an automated delivery process. In this case, automate building and validation so authorized release can happen reliably when selected. The concept, its scope, and its use in this scenario are described consistently. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:Continuous delivery primarily means setting organizational policy, priorities and boundaries for decisions. This choice is incorrect. That describes Governance direction, not the specific meaning of Continuous delivery. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:Continuous delivery primarily means an engineering approach that applies software practices to operational service reliability. This choice is incorrect. That describes Site Reliability Engineering, not the specific meaning of Continuous delivery. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
C:Continuous delivery primarily means recommendations that inform decisions and actions across organizational circumstances. This choice is incorrect. That describes Guiding principles component, not the specific meaning of Continuous delivery. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 608
An online retailer requires approval to choose the deployment time for validated software. Consider four statements about Continuous delivery: 1. A sensible use in this case is to automate building and validation so authorized release can happen reliably when selected. 2. Continuous delivery is identical to Continuous deployment in every ITIL context. 3. Using this concept always eliminates any need to consider feedback and stakeholder outcomes. 4. Continuous delivery concerns keeping software in a state suitable for controlled release through an automated delivery process. Which pair contains the TWO correct statements?
- 2 and 3
- 2 and 4
- 3 and 4
- 1 and 4
Explanation
Correct Answer
D:1 and 4. Both numbered statements accurately describe this ITIL concept and how it applies in the situation. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Incorrect Answers
A:2 and 3. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
B:2 and 4. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
C:3 and 4. This choice is incorrect. At least one selected statement wrongly equates distinct concepts or discards the need for feedback and outcomes. The key idea is Continuous delivery: Keeping software in a state suitable for controlled release through an automated delivery process.
Question 609
A service manager needs the right vocabulary for this concept: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate. What should it be called?
- Value chain coordination
- Continuous deployment
- Service request
- Value chain component
Explanation
Correct Answer
B:Continuous deployment. This is the correct ITIL term for the stated definition. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate. The workplace context is: A low-risk digital service releases each qualified change automatically after testing.
Incorrect Answers
A:Value chain coordination. That term addresses a different definition: Orchestrating relevant organizational activities as a coherent operating model. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate. The workplace context is: A low-risk digital service releases each qualified change automatically after testing.
C:Service request. That term addresses a different definition: A user-initiated request for a predefined service action, information or access. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate. The workplace context is: A low-risk digital service releases each qualified change automatically after testing.
D:Value chain component. That term addresses a different definition: A set of linked activities through which an organization responds to demand and enables value. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate. The workplace context is: A low-risk digital service releases each qualified change automatically after testing.
Question 610
A low-risk digital service releases each qualified change automatically after testing. Which action is the best illustration of Continuous deployment in this situation?
- Apply software engineering and operational measurement to improve service reliability.
- Deploy qualifying pipeline changes automatically under established safety guardrails.
- Use adaptable guiding principles to evaluate choices rather than rigidly mandating one workflow.
- Establish direction and accountability before delegating day-to-day execution.
Explanation
Correct Answer
B:Deploy qualifying pipeline changes automatically under established safety guardrails. This is the appropriate application of the stated concept in the scenario. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate.
Incorrect Answers
A:Apply software engineering and operational measurement to improve service reliability. This would apply Site Reliability Engineering instead; An engineering approach that applies software practices to operational service reliability. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate.
C:Use adaptable guiding principles to evaluate choices rather than rigidly mandating one workflow. This would apply Guiding principles component instead; Recommendations that inform decisions and actions across organizational circumstances. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate.
D:Establish direction and accountability before delegating day-to-day execution. This would apply Governance direction instead; Setting organizational policy, priorities and boundaries for decisions. The key idea is Continuous deployment: Automatically releasing approved changes to users when pipeline checks pass without a separate manual release gate.