Q&A - ITIL 4 Foundation - Exam preparation

Sumário

Questions for Section 4.1: Service Value System Overview

1. What are the key inputs to the ITIL Service Value System (SVS)?
2. What are the elements of the ITIL SVS?
3. What is the main purpose of the ITIL SVS?
4. How does the ITIL SVS enable value creation for an organization?
5. What are the outputs of the ITIL SVS?
6. How can the components and activities of the SVS be configured?
7. Why is integration and coordination important in the ITIL SVS?
8. What challenges can organizational silos present to an organization?
9. How can silos affect the efficiency and decision-making of an organization?
10. What does the architecture of the ITIL SVS enable in terms of flexibility and siloed working?
11. How should practices within the ITIL SVS interact with each other?
12. What does the continual improvement model help to structure in the ITIL SVS?
13. How do the ITIL guiding principles shape the overall operation of an organization?
14. What is the importance of a shared culture within the ITIL SVS?
15. How does the ITIL SVS support various work approaches such as Agile, DevOps, and Lean?

Answers

1. The key inputs to the ITIL Service Value System (SVS) are opportunity and demand. (Page 37)

2. The elements of the ITIL SVS include guiding principles, governance, service value chain, practices, and continual improvement. (Page 37)

3. The main purpose of the ITIL SVS is to ensure that the organization continually co-creates value with all stakeholders through the use and management of products and services. (Page 37)

4. The ITIL SVS enables value creation for an organization by describing how all components and activities work together as a system. (Page 37)

5. The outputs of the ITIL SVS are the achievement of organizational objectives and value for the organization, its customers, and other stakeholders. (Page 36)

6. The components and activities of the SVS can be configured and reconfigured in multiple combinations as circumstances change. (Page 37)

7. Integration and coordination are important in the ITIL SVS to ensure that activities, practices, teams, authorities, and responsibilities work together effectively. (Page 37)

8. Organizational silos can prevent easy access to information and specialized expertise, reduce efficiency, increase costs, and hinder effective decision-making. (Page 37)

9. Silos can limit visibility and create hidden agendas, making it difficult for an organization to act quickly and optimize resource use. (Page 37)

10. The architecture of the ITIL SVS enables flexibility and discourages siloed working by allowing service value chain activities and practices to be combined in various value streams. (Page 37)

11. Practices within the ITIL SVS should have multiple interfaces with one another and exchange information at key points in the workflow. (Page 37)

12. The continual improvement model helps to structure continual improvement activity at all levels of the organization. (Page 37)

13. The ITIL guiding principles shape the overall operation of an organization by creating a foundation for a shared culture and supporting collaboration and cooperation. (Page 37)

14. A shared culture within the ITIL SVS is important for supporting collaboration and removing the need for constraints and controls provided by silos. (Page 37)

15. The ITIL SVS supports various work approaches such as Agile, DevOps, and Lean by providing a flexible value-oriented operating model. (Page 37)

    ---

    Questions for Section 4.2: Opportunity, Demand, and Value

16. What triggers activities within the ITIL Service Value System (SVS)?

17. What does opportunity represent within the ITIL SVS?

18. How should organizations prioritize new or changed services?

19. What does demand represent in the context of the ITIL SVS?

20. How are opportunity and demand related to the creation of value?

21. What is the key message of Section 4.2 regarding opportunity and demand?

Answers

1. Opportunity and demand trigger activities within the ITIL Service Value System (SVS). (Page 38)

2. Opportunity represents options or possibilities to add value for stakeholders or otherwise improve the organization. (Page 39)

3. Organizations should prioritize new or changed services with opportunities for improvement to ensure their resources are correctly allocated. (Page 39)

4. Demand represents the need or desire for products and services from internal and external customers. (Page 39)

5. Opportunity and demand trigger activities within the ITIL SVS, leading to the creation of value. (Page 38)

6. The key message of Section 4.2 is that opportunity and demand trigger activities within the ITIL SVS, and these activities lead to the creation of value. (Page 38)

   ---

   Questions for Section 4.4: Governance

7. What is the primary responsibility of a governing body in an organization?

8. What are the three main governance activities?

9. How does the governing body evaluate the organization and its environment?

10. What is the purpose of the "Direct" activity in governance?

11. How does the governing body ensure compliance with strategic direction and policies?

12. What is the role of monitoring in governance?

13. How does governance fit within the ITIL Service Value System (SVS)?

14. What flexibility do organizations have in positioning governance within the SVS?

15. How do ITIL guiding principles support governance activities?

16. Why is continual improvement important for governance and management?

Answers

1. The primary responsibility of a governing body in an organization is to be accountable at the highest level for the organization's performance and compliance. (Page 81)

2. The three main governance activities are Evaluate, Direct, and Monitor. (Page 81)

3. The governing body evaluates the organization and its environment by continuously assessing stakeholder needs, external circumstances, and the organization's strategy, portfolios, and relationships with other parties. (Page 81)

4. The purpose of the "Direct" activity in governance is to assign responsibility and direct the preparation and implementation of organizational strategy and policies. (Page 81)

5. The governing body ensures compliance with strategic direction and policies through the "Direct" activity, which guides organizational activity and investments and establishes behavioral requirements. (Page 81)

6. The role of monitoring in governance is to oversee the organization's performance and practices to ensure they align with policies and direction set by the governing body. (Page 81)

7. Governance fits within the ITIL Service Value System (SVS) by directing and controlling all aspects of the organization to ensure alignment with its objectives. (Page 82)

8. Organizations have flexibility in positioning governance within the SVS, as the role and position of governance depend on how the SVS is applied to the organization or its units. (Page 82)

9. ITIL guiding principles support governance activities by providing a set of shared principles and objectives that guide decision-making and actions at all levels of the organization. (Page 82)

10. Continual improvement is important for governance and management because it ensures that practices and strategies remain effective and aligned with stakeholder expectations and changing environments. (Page 82)

    ---

    Questions for Section 4.5: Service Value Chain

11. What is the central element of the Service Value System (SVS)?

12. How many key activities are included in the ITIL service value chain?

13. What are the six value chain activities in the ITIL service value chain?

14. What is the purpose of the "Plan" value chain activity?

15. What are the key inputs to the "Plan" value chain activity?

16. What are the key outputs of the "Plan" value chain activity?

17. What is the purpose of the "Improve" value chain activity?

18. What are the key inputs to the "Improve" value chain activity?

19. What are the key outputs of the "Improve" value chain activity?

20. What is the purpose of the "Engage" value chain activity?

21. What are the key inputs to the "Engage" value chain activity?

22. What are the key outputs of the "Engage" value chain activity?

23. What is the purpose of the "Design and Transition" value chain activity?

24. What are the key inputs to the "Design and Transition" value chain activity?

25. What are the key outputs of the "Design and Transition" value chain activity?

26. What is the purpose of the "Obtain/Build" value chain activity?

27. What are the key inputs to the "Obtain/Build" value chain activity?

28. What are the key outputs of the "Obtain/Build" value chain activity?

29. What is the purpose of the "Deliver and Support" value chain activity?

30. What are the key inputs to the "Deliver and Support" value chain activity?

31. What are the key outputs of the "Deliver and Support" value chain activity?

32. What are service value streams?

33. What should value streams be subject to?

34. Give an example of a service value stream.

35. How does the service value chain adapt to different approaches like DevOps and centralized IT?

Answers

1. The central element of the Service Value System (SVS) is the service value chain. Page 57

2. The ITIL service value chain includes six key activities. Page 57

3. The six value chain activities are Plan, Improve, Engage, Design and Transition, Obtain/Build, and Deliver and Support. Page 57

4. The purpose of the "Plan" value chain activity is to ensure a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across the organization. Page 61

5. The key inputs to the "Plan" value chain activity are policies, requirements, and constraints provided by the organization’s governing body, consolidated demands and opportunities provided by engage, value chain performance information, improvement status reports, and improvement initiatives from improve, knowledge and information about new and changed products and services from design and transition, and obtain/build, and knowledge and information about third-party service components from engage. Page 62

6. The key outputs of the "Plan" value chain activity are strategic, tactical, and operational plans, portfolio decisions for design and transition, architectures and policies for design and transition, improvement opportunities for improve, a product and service portfolio for engage, and contract and agreement requirements for engage. Page 62

7. The purpose of the "Improve" value chain activity is to ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management. Page 62

8. The key inputs to the "Improve" value chain activity are product and service performance information provided by deliver and support, stakeholders’ feedback provided by engage, performance information and improvement opportunities provided by all value chain activities, knowledge and information about new and changed products and services from design and transition, and obtain/build, and knowledge and information about third-party service components from engage. Page 62

9. The key outputs of the "Improve" value chain activity are improvement initiatives for all value chain activities, value chain performance information for plan and the governing body, improvement status reports for all value chain activities, contract and agreement requirements for engage, and service performance information for design and transition. Page 63

10. The purpose of the "Engage" value chain activity is to provide a good understanding of stakeholder needs, transparency, and continual engagement and good relationships with all stakeholders. Page 63

11. The key inputs to the "Engage" value chain activity are a product and service portfolio provided by plan, high-level demand for services and products provided by internal and external customers, detailed requirements for services and products provided by customers, requests and feedback from customers, incidents, service requests, and feedback from users, information on the completion of user support tasks from deliver and support, marketing opportunities from current and potential customers and users, cooperation opportunities and feedback provided by partners and suppliers, contract and agreement requirements from all value chain activities, knowledge and information about new and changed products and services from design and transition, and obtain/build, knowledge and information about third-party service components from suppliers and partners, product and service performance information from deliver and support, improvement initiatives from improve, and improvement status reports from improve. Page 63

12. The key outputs of the "Engage" value chain activity are consolidated demands and opportunities for plan, product and service requirements for design and transition, user support tasks for deliver and support, improvement opportunities and stakeholders’ feedback for improve, change or project initiation requests for obtain/build, contracts and agreements with external and internal suppliers and partners for design and transition, and obtain/build, knowledge and information about third-party service components for all value chain activities, and service performance reports for customers. Page 64

13. The purpose of the "Design and Transition" value chain activity is to ensure that products and services continually meet stakeholder expectations for quality, costs, and time to market. Page 64

14. The key inputs to the "Design and Transition" value chain activity are portfolio decisions provided by plan, architectures and policies provided by plan, product and service requirements provided by engage, improvement initiatives provided by improve, improvement status reports from improve, service performance information provided by deliver and support, and improve, service components from obtain/build, knowledge and information about third-party service components from engage, knowledge and information about new and changed products and services from obtain/build, and contracts and agreements with external and internal suppliers and partners provided by engage. Page 64

15. The key outputs of the "Design and Transition" value chain activity are requirements and specifications for obtain/build, contract and agreement requirements for engage, new and changed products and services for deliver and support, knowledge and information about new and changed products and services to all value chain activities, and performance information and improvement opportunities for improve. Page 64

16. The purpose of the "Obtain/Build" value chain activity is to ensure that service components are available when and where they are needed, and meet agreed specifications. Page 64

17. The key inputs to the "Obtain/Build" value chain activity are architectures and policies provided by plan, contracts and agreements with external and internal suppliers and partners provided by engage, goods and services provided by external and internal suppliers and partners, requirements and specifications provided by design and transition, improvement initiatives provided by improve, improvement status reports from improve, change or project initiation requests provided by engage, change requests provided by deliver and support, knowledge and information about new and changed products and services from design and transition, and knowledge and information about third-party service components from engage. Page 65

18. The key outputs of the "Obtain/Build" value chain activity are service components for deliver and support, service components for design and transition, knowledge and information about new and changed service components to all value chain activities, contract and agreement requirements for engage, and performance information and improvement opportunities for improve. Page 65

19. The purpose of the "Deliver and Support" value chain activity is to ensure that services are delivered and supported according to agreed specifications and stakeholders’ expectations. Page 65

20. The key inputs to the "Deliver and Support" value chain activity are new and changed products and services provided by design and transition, service components provided by obtain/build, improvement initiatives provided by improve, improvement status reports from improve, user support tasks provided by engage, knowledge and information about new and changed service components and services from design and transition, and obtain/build, and knowledge and information about third-party service components from engage. Page 65

21. The key outputs of the "Deliver and Support" value chain activity are services delivered to customers and users, information on the completion of user support tasks for engage, product and service performance information for engage and improve, improvement opportunities for improve, contract and agreement requirements for engage, change requests for obtain/build, and service performance information for design and transition. Page 65

22. Service value streams are specific combinations of activities and practices designed to carry out a certain task or respond to a particular situation. Page 59

23. Value streams should be subject to continual improvement. Page 59

24. An example of a service value stream is the resolution of a user incident, where the value stream is designed specifically to resolve the issue and provides a complete guide to the activities, practices, and roles involved. Page 59

25. The service value chain adapts to different approaches like DevOps and centralized IT by being flexible enough to be combined in many ways, forming multiple value streams, which can address changing demands from stakeholders in the most effective and efficient ways. Page 66

    ---

    Questions for Section 4.6: Continual Improvement

26. What is the main purpose of continual improvement in ITIL?

27. How does continual improvement integrate with the ITIL Service Value System (SVS)?

28. What structured approach does the ITIL continual improvement model provide?

29. How does the continual improvement model support ITSM initiatives?

30. What are the seven steps of the continual improvement model?

31. What is the key focus of the first step in the continual improvement model?

32. How should the organization’s vision and objectives be translated during the first step?

33. What is assessed during the second step, "Where are we now?" of the continual improvement model?

34. Why is an objective measurement important in the second step of the continual improvement model?

35. What is the purpose of defining the target state in the third step, "Where do we want to be?"?

36. How is a gap analysis performed in the third step of the continual improvement model?

37. What considerations are involved in planning the improvement initiative in the fourth step, "How do we get there?"?

38. Why might it be necessary to design experiments in the fourth step of the continual improvement model?

39. What is the focus of the fifth step, "Take action," in the continual improvement model?

40. How can Agile methods be applied during the "Take action" step of the continual improvement model?

41. Why is it important to measure progress towards the vision during the "Take action" step?

42. What should be evaluated during the sixth step, "Did we get there?"?

43. What actions should be taken if the desired results were not achieved in the sixth step?

44. What is the key message of the seventh step, "How do we keep the momentum going?"?

45. How should successes be marketed and new methods reinforced during the seventh step?

46. What should be done if the improvement initiative did not deliver the expected value?

47. How do the ITIL guiding principles apply to the continual improvement model?

48. Which ITIL guiding principles are particularly relevant to the continual improvement model?

49. How does the theory of constraints (ToC) relate to continual improvement?

50. What is the purpose of a continual improvement register (CIR)?

51. How should improvement ideas be captured and documented according to ITIL?

52. How does the problem management practice contribute to continual improvement?

53. Why is it important for everyone in the organization to participate in continual improvement?

54. What role does leadership play in embedding continual improvement into organizational culture?

55. How should training and enablement assistance be provided to staff for continual improvement?

Answers with Page References

1. The main purpose of continual improvement in ITIL is to align the organization’s practices and services with changing business needs through the ongoing improvement of products, services, and practices (p. 80) .

2. Continual improvement integrates with the ITIL Service Value System (SVS) by embedding continual improvement into every aspect of the organization and its activities (p. 66) .

3. The ITIL continual improvement model provides a structured approach to implementing improvements (p. 66) .

4. The continual improvement model supports ITSM initiatives by increasing the likelihood of success, focusing on customer value, and linking improvement efforts to the organization’s vision (p. 66) .

5. The seven steps of the continual improvement model are: What is the vision?, Where are we now?, Where do we want to be?, How do we get there?, Take action, Did we get there?, and How do we keep the momentum going? (p. 67) .

6. The key focus of the first step in the continual improvement model is to define the vision of the initiative, providing context for all subsequent decisions and linking actions to the organization’s vision for the future (p. 67) .

7. The organization’s vision and objectives should be translated for the specific business unit, department, team, and/or individual to ensure the context, objectives, and boundaries for any improvement initiative are understood (p. 67) .

8. During the second step, "Where are we now?" the current state, including existing services, user perceptions, skills, processes, and technological capabilities, is assessed (p. 68) .

9. Objective measurement is important in the second step to allow for accurate understanding of the issues and to enable proper measurement of the improvement achieved (p. 68) .

10. The purpose of defining the target state in the third step is to perform a gap analysis and set improvement objectives, critical success factors (CSFs), and key performance indicators (KPIs) (p. 69) .

11. A gap analysis in the third step involves evaluating the distance from the current state to the desired future state and setting measurable goals (p. 69) .

12. In the fourth step, planning the improvement initiative involves defining the route to the target state, which may include designing experiments to test options and iterating the plan as needed (p. 70) .

13. Designing experiments in the fourth step may be necessary to test which options have the most potential for successful improvement (p. 70) .

14. The focus of the fifth step, "Take action," is to execute the plan for improvement, which could involve traditional or Agile approaches (p. 71) .

15. Agile methods can be applied during the "Take action" step by iterating, experimenting, and being open to change throughout the improvement process (p. 71) .

16. It is important to measure progress towards the vision during the "Take action" step to ensure the improvement is on track and to manage risks (p. 71) .

17. During the sixth step, "Did we get there?" both progress towards the objectives and the relevance of those objectives should be evaluated to confirm success (p. 71) .

18. If the desired results were not achieved, additional actions should be selected and undertaken, often resulting in a new iteration of the improvement initiative (p. 71) .

19. The key message of the seventh step, "How do we keep the momentum going?" is to market successes, reinforce new methods, and ensure the progress made is sustained (p. 72) .

20. Successes should be marketed and new methods reinforced by embedding changes into the organization and ensuring new behaviors are institutionalized (p. 72) .

21. If the improvement initiative did not deliver the expected value, the reasons for failure should be analyzed, documented, and communicated to inform future efforts (p. 72) .

22. The ITIL guiding principles apply to the continual improvement model by increasing the chances for success at every step of an improvement initiative (p. 73) .

23. The ITIL guiding principles particularly relevant to the continual improvement model include "Focus on value," "Start where you are," and "Progress iteratively with feedback" (p. 73) .

24. The theory of constraints (ToC) relates to continual improvement by focusing on the weakest link in the value chain and organizing all other steps around it to improve flow and throughput (p. 74) .

25. The purpose of a continual improvement register (CIR) is to track and manage improvement ideas from identification through to final action (p. 82) .

26. Improvement ideas should be captured and documented in a CIR, which helps to make the status and progress of improvements visible (p. 82) .

27. The problem management practice contributes to continual improvement by identifying improvement opportunities and managing them through continual improvement techniques (p. 82) .

28. It is important for everyone in the organization to participate in continual improvement because it ensures active contribution to improvement activities at all levels (p. 82) .

29. Leadership plays a crucial role in embedding continual improvement into organizational culture by demonstrating visible commitment and integrating improvement into daily work practices (p. 82) .

30. Training and enablement assistance should be provided to staff to help them feel prepared to contribute to continual improvement and develop the necessary skills (p. 82) .

    ---

    Questions for Section 5.1 General Management Practices

31. What is the purpose of the architecture management practice?

    • Answer: The purpose is to provide an understanding of all the different elements that make up an organization and how those elements interrelate, enabling the organization to effectively achieve its current and future objectives. (Page 78)

32. Which domains should a complete architecture management practice address?

    • Answer: Business, service, information, technology, and environment. (Page 78)

33. How does architecture management help an organization?

    • Answer: It helps to increase efficiency, manage complexity, achieve organizational agility, and maintain resilience. (Page 78)

34. What is the role of the business architecture in architecture management?

    • Answer: It allows the organization to look at its capabilities in terms of how they align with all the detailed activities required to create value for the organization and its customers. (Page 79)

35. What is the primary goal of continual improvement?

    • Answer: To ensure that IT services and the practices used to manage them can continue to meet changing business needs. (Page 80)

36. How does continual improvement support ITIL practices?

    • Answer: By providing a structured approach to identifying and implementing improvements. (Page 80)

37. What are the key activities of information security management?

    • Answer: Ensuring the confidentiality, integrity, and availability of information, and managing risks related to information security. (Page 83)

38. Why is knowledge management important?

    • Answer: It maintains and improves the effective use of information and knowledge within the organization. (Page 85)

39. What is the primary function of measurement and reporting?

    • Answer: To support good decision-making and continual improvement by collecting and analyzing data. (Page 87)

40. What are the components of organizational change management?

    • Answer: Clear and relevant objectives, strong and committed leadership, willing and prepared participants, and sustained improvement. (Page 89)

41. What is the main focus of portfolio management?

    • Answer: To manage the organization's investments in services and products to achieve desired business outcomes. (Page 91)

42. How does project management contribute to ITIL practices?

    • Answer: By ensuring that projects achieve their goals within constraints of time, cost, and quality. (Page 94)

43. What is the role of relationship management?

    • Answer: To establish and nurture links between the organization and its stakeholders, enhancing stakeholder satisfaction. (Page 96)

44. What are the primary goals of risk management?

    • Answer: To understand and handle risks effectively, ensuring the ongoing sustainability of the organization and creating value for its customers. (Page 97)

45. What does service financial management focus on?

    • Answer: On managing budgeting, accounting, and charging requirements for services. (Page 100)

46. What is the purpose of strategy management?

    • Answer: To define the organization’s direction and allocate resources accordingly to achieve its objectives. (Page 103)

47. How does supplier management ensure value delivery?

    • Answer: By managing relationships and performance to ensure suppliers meet contractual and service level agreements. (Page 105)

48. What is the role of workforce and talent management?

    • Answer: To ensure the organization has the right people with the appropriate skills and knowledge in the correct roles to support its business objectives. (Page 109)

49. How does workforce and talent management contribute to organizational success?

    • Answer: By proactively understanding and forecasting future demand for services and ensuring the right talent is available at the right time. (Page 109)

50. What is the significance of the business architecture?

    • Answer: It helps in aligning the organization's capabilities with the detailed activities required to create value. (Page 79)

51. How does the information architecture benefit an organization?

    • Answer: It describes the logical and physical data assets and data management resources, ensuring information is complete, accurate, and accessible. (Page 79)

52. What is the role of technology architecture?

    • Answer: To define the software and hardware infrastructure needed to support the portfolio of products and services. (Page 79)

53. How does the environmental architecture impact the organization?

    • Answer: It describes the external factors impacting the organization and the drivers for change, including all aspects and levels of environmental control. (Page 79)

54. What activities are included in knowledge management?

    • Answer: Ensuring valuable information is available and accessible, and encouraging sharing within the organization. (Page 85)

55. What is the purpose of the heat maps in ITIL practices?

    • Answer: To show the contribution of each practice to the service value chain activities. (Various pages, e.g., 78, 80)

56. How does measurement and reporting contribute to continual improvement?

    • Answer: By providing accurate and reliable data for managing services, supporting performance assessments, and improvement initiatives. (Page 87)

57. What is the role of sponsor management in organizational change management?

    • Answer: To provide strong and committed leadership for the change initiatives. (Page 89)

58. What does resistance management entail in organizational change management?

    • Answer: Addressing and managing resistance to change to ensure willing participants. (Page 89)

59. How does portfolio management align with organizational strategy?

    • Answer: By balancing the portfolio to achieve desired outcomes and maximize value. (Page 91)

60. What is the importance of project management in achieving ITIL goals?

    • Answer: It ensures projects are planned, executed, and closed effectively, monitoring and controlling project progress and performance. (Page 94)

      ---

      Questions and Answers for Section 5.2: Service Management Practices

Questions

1. What is the purpose of availability management?
2. How does availability management contribute to the service value chain activities?
3. What is the role of business analysis in ITIL?
4. How does business analysis ensure solutions meet business needs effectively?
5. What are the main objectives of capacity and performance management?
6. How does capacity and performance management ensure services achieve expected performance?
7. What is the focus of change control in ITIL?
8. How does change control safeguard services from unnecessary disruptions?
9. What is the primary goal of incident management?
10. How does incident management restore normal service operation?
11. What is the purpose of IT asset management?
12. How does IT asset management plan and manage the lifecycle of IT assets?
13. What is the key objective of monitoring and event management?
14. How does monitoring and event management systematically observe services?
15. What are the main goals of problem management in ITIL?
16. How does problem management reduce the likelihood and impact of incidents?
17. What is the role of release management in ITIL?
18. How does release management control the movement of releases to different environments?
19. What is the focus of service catalogue management?
20. How does service catalogue management provide consistent information on services?
21. What is the purpose of service configuration management?
22. How does service configuration management ensure accurate service information?
23. What are the main objectives of service continuity management?
24. How does service continuity management maintain service availability during disruptions?
25. What is the role of service design in ITIL?
26. How does service design ensure services meet customer needs?
27. What is the primary function of the service desk?
28. How does the service desk handle incidents and service requests?
29. What is the focus of service level management?
30. How does service level management set and achieve service performance targets?
31. What is the role of service request management?
32. How does service request management handle user-initiated service requests?
33. What are the main objectives of service validation and testing?
34. How does service validation and testing ensure new or changed services meet requirements?

Answers

1. The purpose of availability management is to ensure that services deliver agreed levels of availability to meet business needs.

   • Page: 112

2. Availability management contributes to service value chain activities by defining, analyzing, planning, measuring, and improving all aspects of service availability.

   • Page: 113

3. The role of business analysis in ITIL is to analyze business needs and ensure solutions meet these needs effectively.

   • Page: 114

4. Business analysis ensures solutions meet business needs effectively by identifying requirements and ensuring the IT service provider understands them.

   • Page: 115

5. The main objectives of capacity and performance management are to ensure services achieve agreed and expected performance.

   • Page: 117

6. Capacity and performance management ensure services achieve expected performance by monitoring and managing service performance and capacity.

   • Page: 118

7. The focus of change control in ITIL is to ensure changes are made effectively, safeguarding services from unnecessary disruptions.

   • Page: 118

8. Change control safeguards services from unnecessary disruptions by evaluating change risks, authorizing changes, and ensuring smooth implementation.

   • Page: 119

9. The primary goal of incident management is to restore normal service operation as quickly as possible and minimize the impact on business operations.

   • Page: 121

10. Incident management restores normal service operation by managing incidents throughout their lifecycle, ensuring efficient diagnosis, escalation, and resolution.

    • Page: 122

11. The purpose of IT asset management is to plan and manage the full lifecycle of all IT assets.

    • Page: 124

12. IT asset management plans and manages the lifecycle of IT assets by ensuring assets are properly accounted for and maximizing their value.

    • Page: 125

13. The key objective of monitoring and event management is to systematically observe services and service components, and record and report selected changes of state.

    • Page: 128

14. Monitoring and event management systematically observe services by identifying significant events and ensuring appropriate responses.

    • Page: 129

15. The main goals of problem management in ITIL are to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents.

    • Page: 130

16. Problem management reduces the likelihood and impact of incidents by managing the lifecycle of problems, identifying root causes, and resolving them.

    • Page: 131

17. The role of release management in ITIL is to make new and changed services and features available for use.

    • Page: 134

18. Release management controls the movement of releases to different environments by planning, scheduling, and ensuring the integrity of the live environment.

    • Page: 135

19. The focus of service catalogue management is to provide a single source of consistent information on all services and service offerings.

    • Page: 137

20. Service catalogue management provides consistent information on services by ensuring the service catalogue is accurate and accessible to approved users.

    • Page: 138

21. The purpose of service configuration management is to ensure accurate and reliable information about the configuration of services is available.

    • Page: 139

22. Service configuration management ensures accurate service information by maintaining and controlling records of service assets and configurations.

    • Page: 140

23. The main objectives of service continuity management are to ensure the availability and performance of a service are maintained at sufficient levels in case of a disaster.

    • Page: 143

24. Service continuity management maintains service availability during disruptions by providing a framework for building organizational resilience and effective response capabilities.

    • Page: 144

25. The role of service design in ITIL is to design services that meet customer needs.

    • Page: 145

26. Service design ensures services meet customer needs by translating strategic objectives into portfolios of services and service assets.

    • Page: 146

27. The primary function of the service desk is to capture demand for incident resolution and service requests.

    • Page: 149

28. The service desk handles incidents and service requests by being the main point of contact for users, managing incidents, and fulfilling service requests.

    • Page: 150

29. The focus of service level management is to set clear business-based targets for service performance and ensure delivery meets these targets.

    • Page: 152

30. Service level management sets and achieves service performance targets by establishing a shared view of services with customers and monitoring service performance against agreed metrics.

    • Page: 153

31. The role of service request management is to support the agreed quality of a service by handling all predefined, user-initiated service requests.

    • Page: 156

32. Service request management handles user-initiated service requests by following standardized procedures for initiation, approval, and fulfillment.

    • Page: 157

33. The main objectives of service validation and testing are to ensure new or changed services meet defined requirements.

    • Page: 158

34. Service validation and testing ensure new or changed services meet requirements by validating service components and systems through testing activities.

    • Page: 159

These answers are based on the ITIL 4 Foundation document provided by the user. The page numbers indicate where the information can be found in the document.

---

Questions on Section 5.3: Technical Management Practices

Deployment Management

1. What is the purpose of the deployment management practice? (p. 160)
2. How does deployment management relate to release management and change control? (p. 160)
3. What are the distinct approaches that can be used for deployment? (p. 160-161)
4. What is phased deployment? (p. 161)
5. What is continuous delivery in the context of deployment management? (p. 161)
6. What is big bang deployment? (p. 161)
7. What is pull deployment? (p. 161)
8. What are definitive media libraries and definitive hardware stores? (p. 161)
9. How are deployment tools often integrated? (p. 161)
10. What role does communication around deployments play in release management? (p. 161)
11. In what environments might changes be deployed incrementally? (p. 162)
12. How does deployment management contribute to the service value chain activities? (p. 162)
13. Provide an example of how deployment management was applied in Axle's booking app. (p. 162)

Infrastructure and Platform Management

14. What is the purpose of the infrastructure and platform management practice? (p. 163)
15. What is included in IT infrastructure? (p. 163)
16. What types of services can IT infrastructure be managed as? (p. 163)
17. What does the infrastructure and platform management practice provide? (p. 163)
18. What technologies might be included under the infrastructure and platform management practice? (p. 163)
19. Why must each organization develop its own strategy for infrastructure and platform management? (p. 163)
20. How does infrastructure and platform management contribute to the service value chain activities? (p. 163)
21. How does infrastructure and platform management provide information for strategic and tactical planning? (p. 163)

Software Development and Management

22. What is the purpose of the software development and management practice? (p. 166)
23. What types of software can the term 'software' describe in ITIL? (p. 166)
24. Why are software applications important in technology-enabled business services? (p. 166)
25. What activities are encompassed by the software development and management practice? (p. 166)
26. What are the two generally accepted approaches to software development? (p. 166)
27. What does software management encompass? (p. 166)
28. Describe the software lifecycle as depicted in ITIL. (p. 167)
29. How does software development and management contribute to the service value chain activities? (p. 167)
30. How does software development and management facilitate service improvements involving software components? (p. 167)

Answers

Deployment Management

1. The purpose of the deployment management practice is to move new or changed hardware, software, documentation, processes, or any other component to live environments. It may also be involved in deploying components to other environments for testing or staging. (p. 160)
2. Deployment management works closely with release management and change control, but is a separate practice. (p. 160)
3. The distinct approaches that can be used for deployment include phased deployment, continuous delivery, big bang deployment, and pull deployment. (p. 160-161)
4. Phased deployment is when the new or changed components are deployed to just part of the production environment at a time, and this operation is repeated until the deployment is complete. (p. 161)
5. Continuous delivery is when components are integrated, tested, and deployed when they are needed, providing frequent opportunities for customer feedback loops. (p. 161)
6. Big bang deployment is when new or changed components are deployed to all targets at the same time, sometimes needed when dependencies prevent the simultaneous use of both the old and new components. (p. 161)
7. Pull deployment is when new or changed software is made available in a controlled repository, and users download the software to client devices when they choose. (p. 161)
8. Definitive media libraries and definitive hardware stores are secure locations where components available for deployment are maintained to ensure they are not modified before deployment. (p. 161)
9. Deployment tools are often integrated with configuration management tools and can provide support for audit and change management. (p. 161)
10. Communication around deployments is part of release management, ensuring that individual deployments are effectively communicated to users and customers. (p. 161)
11. Changes can be deployed incrementally in environments, especially common in DevOps environments using a complete automated toolchain for continuous integration, delivery, and deployment. (p. 162)
12. Deployment management contributes to the service value chain activities by supporting design and transition, obtain/build, and deliver and support. (p. 162)
13. In Axle's booking app, deployment management was applied by releasing changes to a test environment before making them available to users and customers. (p. 162)

Infrastructure and Platform Management

14. The purpose of the infrastructure and platform management practice is to oversee the infrastructure and platforms used by an organization. (p. 163)
15. IT infrastructure includes physical and/or virtual technology resources such as servers, storage, networks, client hardware, middleware, and operating systems software. (p. 163)
16. IT infrastructure can be managed as dedicated, shared, or cloud services. (p. 163)
17. The infrastructure and platform management practice provides the technology needed to support activities that create value for the organization and its stakeholders. (p. 163)
18. Technologies included under this practice can be machine learning, chatbots, artificial intelligence, mobile device management, and enterprise mobility management. (p. 163)
19. Each organization must develop its own strategy for infrastructure and platform management to align with business goals and intended service quality and operational efficiency. (p. 163)
20. Infrastructure and platform management contributes to the service value chain activities by supporting plan, improve, design and transition, obtain/build, and deliver and support. (p. 163)
21. This practice provides information about technology opportunities and constraints used for strategic and tactical planning. (p. 163)

Software Development and Management

22. The purpose of the software development and management practice is to ensure that applications meet internal and external stakeholder needs in terms of functionality, reliability, maintainability, compliance, and auditability. (p. 166)
23. The term 'software' can describe anything from a single program to larger constructs such as an operating system, operating environment, or database. (p. 166)
24. Software applications are important in technology-enabled business services because they are critical in delivering customer value. (p. 166)
25. The software development and management practice encompasses activities such as solution architecture, solution design, software development, software testing, management of code repositories, package creation, version control, and ongoing management of software. (p. 166)
26. The two generally accepted approaches to software development are waterfall and Agile methods. (p. 166)
27. Software management encompasses the ongoing activities of designing, testing, operating, and improving software applications. (p. 166)
28. The software lifecycle includes ideation, development, deployment, use, and ongoing improvement, eventually leading to retirement. (p. 167)
29. Software development and management contribute to the service value chain activities by supporting plan, improve, design and transition, obtain/build, and deliver and support. (p. 167)
30. This practice facilitates service improvements involving software components by providing necessary information and support for design, development, and transition activities. (p. 167)

These answers reference the corresponding pages in the ITIL Foundation ITIL 4 Edition document.

link de compartilhamento