📘 Module 1: Service Strategy & Financial Management
Focus: Defining services, managing the portfolio, financial justification, and business relationships.
Service Portfolio & Strategy
Q1: How does the Service Portfolio interact with the service lifecycle?
A: It interacts with all five stages (Strategy, Design, Transition, Operation, and CSI). The portfolio tracks every service from its initial conception (Pipeline) through to retirement.
Q2: What is the primary purpose of Service Portfolio Management? A: To ensure the service provider maintains the optimal mix of services to balance IT investment against the ability to meet business outcomes and maximize value.
Q3: How do the different catalog views map to their descriptions? A:
- Business Catalog: Shows customer-facing services delivered directly to the client.
- Technical Catalog: Shows the supporting services required to deliver the customer-facing ones.
- Multi-view Catalog: Provides a consolidated view of all services (both business and technical).
Q4: What is the precise definition of the Service Catalog? A: It is a database or structured document containing information about all live (operational) IT services available to customers. It is a subset of the Service Portfolio.
Q5: Which services are included in the Service Catalog? A: It includes customer-facing services and supporting services that are currently live. It excludes services still in the pipeline (strategic) or those already retired.
Q6: What is the relationship between the Service Catalog and the Service Portfolio? A: The Service Catalog is a component of the Service Portfolio. The Portfolio contains the Catalog plus the Pipeline (future services) and Retired Services.
Q7: What is the scope of information within the Service Catalog? A: It maps IT services to the business processes they support. It generally does not include services under development (which belong in the Pipeline).
Q8: How interconnected is Service Catalog Management? A: It is highly connected to the majority of lifecycle processes, including Incident, Problem, Change, SLA Management, and Financial Management, serving as a central source of truth.
Q9: In which lifecycle stage does Service Portfolio Management reside? A: It is a core process of Service Strategy.
Q10: Who is primarily responsible for marketing the Service Portfolio to stakeholders? A: The Service Portfolio Process Owner (or sometimes the Service Manager/BRM depending on organization), who ensures the strategic value of the portfolio is communicated effectively.
Financial Management & Valuation
Q11: How is “Service Valuation” defined? A: It is the ability to understand and compare the costs of delivering a service relative to the business value it generates.
Q12: Which statement regarding IT Financial Management is correct? A: IT spending requires business justification. IT financial management should be integrated with enterprise finance, and while charging is common, it is not mandatory for all providers (some operate as cost centers).
Q13: What is a key objective of Financial Management? A: To help the business articulate the value of IT services, translating technical costs into business benefits.
Q14: How is “Budgeting” defined? A: The activity of predicting and controlling future spending to ensure funds are available and utilized correctly.
Q15: Which task is NOT a responsibility of the Business Relationship Manager (BRM)? A: Maintaining an operational focus. The BRM role is strategic; day-to-day operational delivery is handled by Service Operation teams.
Q16: What is a key responsibility of the BRM? A: Building business cases for new services and identifying opportunities where IT can enable business outcomes.
Q17: Are the Customer Portfolio and Customer Agreement Portfolio distinct repositories? A: True. The Customer Portfolio lists who the customers are, while the Customer Agreement Portfolio manages the specific contracts and agreements (SLAs) with them.
Q18: Which of the following is NOT a typical trigger for BRM activities? A: Internal ROI variances (e.g., ROI being lower than predicted). This is typically a trigger for Financial Management or CSI. BRM is triggered by strategic shifts, new opportunities, or direct customer feedback/complaints.
Q19: Which data repositories are primarily used by the BRM? A: The Customer Portfolio and the Customer Agreement Portfolio.
Q20: Which item is NOT a direct output of Financial Management? A: Compliance. While Financial Management aids compliance, “Compliance” itself is a state or requirement, not a specific process output like “Service Valuation Reports” or “Investment Analyses.”
📙 Module 2: Service Design
Focus: Designing solutions, architectures, processes, and metrics; managing suppliers and levels of service.
Design Principles & Coordination
Q21: What are the “4 Ps” of Service Design? A: People, Processes, Products (Technology), and Partners.
Q22: What three elements must be balanced in a effective service design? A: Resources, Utility (fit for purpose), and Warranty (fit for use).
Q23: What does “Holistic Service Design” mean? A: It means the design considers all five aspects: Service Solutions, Architectures, Processes, Measurement Systems, and People/Organizations.
Q24: Which of the following is NOT a risk associated with poor service design? A: The statement “Insufficient time on warranty makes the service unfit for purpose” is incorrect. Lack of Warranty makes a service unfit for use; lack of Utility makes it unfit for purpose.
Q25: What must a complete Service Design include? A: It must include details on underpinning contracts, technology components, required staff skills, and governance requirements.
Q26: Which activity is NOT performed by Service Design before handing over to Transition? A: Developing (building/coding) the solution. Design creates the blueprint and business case; Transition/Build executes the actual development.
Q27: Which is NOT a primary purpose of Service Design? A: Evaluating the financial impact of high-level corporate strategies. That is the role of Service Strategy. Design focuses on the cost-effective provision of specific services.
Q28: Which item is NOT one of the five explicit aspects of Service Design? A: Risk Management. While risk is considered within the aspects, it is a separate process, not one of the top-level five design aspects (Solutions, Architectures, Processes, Metrics, People).
Q29: What documents are valid inclusions in a Service Design Package (SDP)? A: Technical designs, draft SLAs, acceptance criteria, business requirements, and testing plans. (Note: The live CMS and Change Schedule are not part of the design package).
Q30: Which process is accountable for creating the Service Design Package (SDP)? A: Design Coordination.
Service Level & Supplier Management
Q31: What is the core purpose of Service Level Management (SLM)? A: To ensure all current and planned services are delivered against agreed, achievable targets (SLAs).
Q32: What are the key objectives of SLM? A: To define, document, agree, monitor, measure, report, and review service levels continuously.
Q33: Which item would NOT appear in a Service Level Agreement (SLA)? A: The organization’s Business Strategy. SLAs are tactical agreements about specific services, hours, and continuity, not high-level strategy.
Q34: Which agreements support an SLA? A: Operational Level Agreements (OLAs) (internal) and Underpinning Contracts (UCs) (external).
Q35: How is an Underpinning Contract (UC) defined? A: A contract between the IT service provider and an external third-party supplier to support service delivery.
Q36: What is the standard color scheme for SLA monitoring reports? A: Red, Amber, Green (RAG) indicating breached, at-risk, and on-target status.
Q37: What are the responsibilities of Supplier Management? A: Negotiating with external suppliers, monitoring contract performance, and ensuring value for money. (Internal negotiations are handled via OLAs).
Q38: What are the standard categories of suppliers in ITIL? A: Strategic, Tactical, Operational, and Commodity. (“Trusted” is not a standard category).
Q39: On what basis are suppliers categorized? A: Based on the risk/importance of the service they provide and the impact/value of their potential failure.
Q40: What data is stored in the Supplier and Contract Management Information System (SCMIS)? A: Both supplier policies and contract details.
Capacity, Availability, Continuity & Security
Q41: What are the responsibilities of Capacity Management? A: Monitoring capacity, forecasting future needs, negotiating requirements for SLAs, and resolving capacity issues.
Q42: What are the three sub-processes of Capacity Management? A: Business Capacity Management (future needs), Service Capacity Management (end-to-end performance), and Component Capacity Management (individual IT assets).
Q43: What is the focus of Business Capacity Management? A: Translating future business plans and requirements into IT capacity needs.
Q44: Does Capacity Management involve both reactive and proactive activities? A: True. It proactively forecasts/tunes and reactively troubleshoots performance issues.
Q45: What is the key purpose of Information Security Management? A: To create and maintain the Information Security Policy that governs security across the organization.
Q46: Where does Information Security Management store its specific data? A: In the Information Security Database (ISDB).
Q47: What are the key concepts of Availability Management? A: Reliability, Resilience, Maintainability, and Serviceability.
Q48: What does VBF stand for in Availability Management? A: Vital Business Function. These are the critical processes that dictate availability priorities.
Q49: What is the primary responsibility of IT Service Continuity Management (ITSCM)? A: Ensuring IT services can continue during a disaster, conducting risk assessments, and ensuring IT staff know their roles. (Note: Creating business contingency plans is the role of BCM, not ITSCM).
Q50: What does BIA stand for? A: Business Impact Analysis. It identifies vital functions and the impact of disruption to determine Recovery Time Objectives (RTO).
Q51: What is the relationship between BCM and ITSCM? A: BCM defines the business requirements (what is needed); ITSCM is responsible for delivering the IT solution to meet those requirements.
Q52: What are valid KPIs for ITSCM? A: Frequency of plan testing, regular reviews of plans with the business, and overall reduction in risk/impact. (Counting major incidents is an Incident Management metric).
Q53: When does testing of continuity plans occur? A: During Implementation and continuously throughout Ongoing Operation.
Demand Management
Q54: What do Patterns of Business Activity (PBA) track? A: The activity of the business required to deliver outcomes (e.g., month-end processing), allowing IT to align capacity accordingly.
Q55: What is the goal of Demand Management? A: To match Supply (capacity/resources) to Demand (user activity).
Q56: What sources inform Demand Management? A: All business plans, including marketing forecasts, production schedules, sales projections, and new product launches.
Q57: How are User Profiles (UP) defined? A: Based on user roles and responsibilities, as users in similar roles exhibit similar demand patterns.
Q58: Which statement about Demand Management is incorrect? A: The idea that “consumption consumes demand” in a perfectly synchronized pattern. In reality, demand and production are rarely perfectly synchronized, requiring management buffers.
📗 Module 3: Service Transition
Focus: Building, testing, deploying, and managing changes, assets, and knowledge.
Transition Overview & Coordination
Q59: Which is NOT an objective of Service Transition? A: Documenting how to optimize performance based on usage. Optimization is the realm of CSI and Capacity Management. Transition focuses on building/testing/deploying correctly.
Q60: Which statements about Service Transition are correct? A: All of them. It turns strategy into deliverables, realizes design in the real world, delivers identified value, and implements CSI improvements.
Q61: Which situation is OUT of scope for Service Transition? A: Producing a business case for outsourcing. This is a Service Strategy activity. Transition handles the actual transfer/migration once the decision is made.
Q62: Is the purpose of Transition to ensure services are designed according to strategy? A: False. Ensuring design matches strategy is the job of Service Design. Transition ensures the build matches the design.
Q63: Which is NOT an aspect of successful Service Transition? A: Developing capacity plans to identify needs. This is a Design/Capacity Management task. Transition utilizes these plans but does not create them.
Q64: Which process is uniquely focused on Service Transition? A: Change Evaluation. While Change Management exists across the lifecycle, the formal “Change Evaluation” process for major changes is specific to Transition.
Q65: Does Service Transition cover new service introductions and provider transfers? A: Yes, both.
Q66: Which sourcing models are managed during Transition? A: All of them: Insourcing, Outsourcing, Co-sourcing, and Offshoring.
Q67: Which statement correctly describes the Service Lifecycle roles? A: Service Transition provides the guidance and capabilities to introduce new services into the live environment.
Q68: Does Transition integrate with CSI using PDCA? A: True. Transition processes are continually improved using the Plan-Do-Check-Act cycle.
Change Management
Q69: Which is NOT a purpose of SACM (Service Asset & Configuration Management)? A: Managing the changes to assets. SACM controls and records assets; Change Management manages the workflow of changing them.
Q70: Which lifecycle stages does SACM support? A: All five stages. It is a foundational process used everywhere from Strategy to CSI.
Q71: What is a Configuration Record? A: The set of attributes and relationships about a Configuration Item (CI) stored in the CMS/CMDB.
Q72: Which statement about the value of the CMS is incorrect? A: That it ensures service desk staff have the knowledge to resolve incidents. The CMS provides data on structure; the SKMS/KEDB provides the knowledge on how to fix issues.
Q73: Which is NOT a danger of implementing SACM? A: The statement that “Ineffective Change Management makes accurate CMS impossible” is actually a true risk, so in the context of “which is not a direct implementation danger of SACM itself,” this is often the outlier as it’s an external dependency. However, all listed options are genuine risks.
Q74: Who belongs on the Emergency CAB (ECAB)? A: Senior decision-makers with authority and technical expertise, such as the Senior IT Manager, Senior Technical Manager, and Service Desk Manager. (Customers and general support staff are usually excluded for speed).
Q75: What triggers the Change Management process? A: A Request for Change (RFC) or a Change Proposal. (Incident calls or Project docs may lead to an RFC, but the RFC is the formal trigger).
Q76: Which statement about Change Management is false? A: That there must be a single CAB for all changes. Large organizations often have multiple delegated CABs.
Q77: Which is NOT a valid type of change in ITIL? A: “Urgent.” The three types are Standard, Normal, and Emergency. “Urgent” is a priority level, not a change type.
Q78: How does Change Management NOT deliver value? A: By guaranteeing that business changes deliver strategic benefits. That is the role of Strategy/BRM. Change Management ensures changes are implemented safely and efficiently.
Release, Deployment & Testing
Q79: What is a Release Package? A: A set of Configuration Items (CIs) built, tested, and deployed together as a single unit.
Q80: What is Early Life Support (ELS)? A: The period of enhanced support immediately after deployment where the transition team assists operations to stabilize the new service before full handover.
Q81: Which item is NOT part of a Release Policy? A: Defining the CMS naming convention. That is the responsibility of Configuration Management. Release Policy covers release naming, roles, and frequency.
Q82: Which is NOT a phase of Release and Deployment? A: “Verification and Audit” as a standalone phase. These are activities performed within the phases (Build/Test, Deploy, Review).
Q83: During which phase does Early Life Support occur? A: The Deployment phase (specifically post-deployment stabilization).
Q84: Match the DIKW hierarchy: A:
- Data: Discrete facts.
- Information: Data with context.
- Knowledge: Experience, insights, and judgment applied to information.
- Wisdom: Using knowledge to make value-driven decisions.
Q85: What tool supports Knowledge Management? A: The Service Knowledge Management System (SKMS).
Q86: How does Knowledge Management function across the lifecycle? A: It is used across the entire lifecycle to ensure informed decision-making at every stage.
Q87: What is an alternative title for a Knowledge Management Practitioner? A: Knowledge Librarian.
Q88: What is the role of the Knowledge Management Process Owner? A: Creating the architecture and strategy for knowledge capture and maintenance. (Updating records is a practitioner task).
Validation & Testing
Q89: What is NOT part of a Test Model? A: The Test Report. The model includes the plan, scope, and scripts. The report is an output generated after execution.
Q90: What is the correct order of testing actions? A: Design Tests → Verify Plan → Prepare Environment → Perform Tests → Evaluate Exit Criteria/Report → Cleanup/Closure.
Q91: Where are testing entry/exit criteria defined? A: In the Service Design Package (SDP).
Q92: What diagram maps tests to development stages? A: The Service V-Model.
Q93: What are valid outcomes of evaluating test results? A: Pass, Fail, or Pass with higher risk/cost than planned (conditional acceptance).
Q94: What is an objective of Change Evaluation? A: To provide assurance that a release is fit for purpose and safe to deploy.
Q95: Which factor is least likely considered by Change Evaluation? A: The financial cost of the change project. Evaluation focuses on performance, impact, risk, and compliance.
Q96: What might an Evaluation Report contain? A: All of the above: Risk profiles, deviation reports, recommendations, and qualification statements.
Q97: What is a Performance Model? A: A representation/simulation of a service used to predict performance before deployment.
Q98: Which process triggers Change Evaluation? A: Change Management.
📕 Module 4: Service Operation
Focus: Day-to-day management, incident resolution, request fulfillment, and operational functions.
Functions of Service Operation
Q99: Which activity is NOT the responsibility of Facilities Management? A: Defining infrastructure requirements (e.g., server specs). Facilities manages the physical plant (power, cooling, space); Technical Management defines IT hardware/software needs.
Q100: Match the activities to the correct Function: A:
- Console Management: Operations Management.
- App Requirements: Application Management.
- Single Point of Contact (SPOC): Service Desk.
- Infrastructure Design/Mgmt: Technical Management.
Q101: What are the two sub-functions of IT Operations Management? A: Operations Control and Facilities Management.
Q102: What is an objective of Technical Management? A: Planning and designing the technical infrastructure aspects of new or changed services.
Q103: What are the objectives of Application Management? A: All of the above: Designing apps, advising on purchases, and agreeing on support arrangements.
Q104: How is Technical Management best described? A: Groups providing technical expertise and overall management of the IT Infrastructure.
Q105: What are the objectives of Technical Management? A: Maintaining stability, improving service/reducing costs, and swiftly diagnosing/resolving failures. (Planning app deployment is primarily App Management).
Q106: What are the responsibilities of Application Management? A: All of the above: Defining requirements, overseeing security, supporting/improving apps, and assisting deployment.
Q107: Do Technical Management teams include both designers and support staff? A: Yes (Both statements). They provide resources for both Service Design (architects) and Service Operation (support engineers).
Q108: Which function is primarily responsible for consistent routine tasks to maintain stability? A: IT Operations Management.
Service Desk & Incident Management
Q109: What is the Service Desk NOT responsible for? A: Preventing incidents from recurring. That is the goal of Problem Management. The Desk focuses on restoration and communication.
Q110: Which two processes does the Service Desk primarily execute? A: Incident Management and Request Fulfillment.
Q111: What skills should Service Desk staff possess? A: All of the above: Interpersonal skills, technical ability, business knowledge, and application knowledge.
Q112: Which is NOT a standard Service Desk structure? A: Matrix. Standard structures include Local, Centralized, Virtual, Follow-the-Sun, and Specialized.
Q113: What information sources must be available to the Service Desk? A: All of the above: Change schedule, CMS, KEDB, and diagnostic scripts.
Q114: What are valid KPIs for the Service Desk? A: First Contact Resolution rate, accuracy of categorization, and Customer Satisfaction scores. (Total volume of hardware incidents is a metric, not a performance indicator).
Q115: What is a direct benefit of having a Service Desk? A: It allows technical specialists to focus on complex issues by filtering out simple incidents.
Q116: What are the benefits of using Super Users? A: They handle simple queries locally, act as communication coordinators, and understand business context. (They should not bypass the Service Desk to contact support teams directly).
Q117: What defines a Virtual Service Desk? A: Using technology to make geographically dispersed staff appear as a single unified entity to the caller.
Q118: In an outsourced Service Desk model, who is accountable? A: The Organization’s Senior Management remains accountable; the supplier is only responsible for delivery.
Q119: What is the definition of an Incident? A: An unplanned interruption to a service or reduction in its quality.
Q120: When should an Incident be closed? A: When the user confirms that the service has been restored.
Q121: Which is NOT a satisfactory incident resolution? A: Running diagnostics to monitor for future occurrences without restoring the current service. The priority is immediate restoration.
Q122: How is “Normal Service Operation” defined? A: By the levels specified in the Service Level Agreement (SLA).
Q123: What are templates for common incidents called? A: Incident Models.
Q124: Which incidents should be logged? A: All incidents, regardless of severity.
Q125: How is Incident Priority calculated? A: Based on Impact and Urgency.
Q126: What are the two types of Escalation? A: Functional (to experts) and Hierarchical (to management).
Problem, Event & Access Management
Q127: What is the best definition of a Problem? A: The underlying cause of one or more incidents.
Q128: What outputs does Problem Management produce? A: Known Errors, Workarounds, and Requests for Change (RFCs).
Q129: When is automation appropriate for Event Management? A: For detecting security intrusions and monitoring backup jobs. (Not for hierarchical escalation or business batch processing like sales figures).
Q130: What can Event Management monitor? A: Environmental conditions, system messages, and license usage. (Not HR staff rosters).
Q131: What are the types of Event Monitoring? A: Active (polling) and Passive (listening for traps).
Q132: What is Request Fulfillment suitable for? A: Common, low-risk requests with documented procedures (e.g., password resets).
Q133: Who fulfills service requests? A: Primarily Service Desk and Second-line staff.
Q134: Which statement about Requests is incorrect? A: That they need CAB authorization. Standard requests are pre-authorized; only Changes go to the CAB.
Q135: What is the definition of Access Management? A: Granting authorized users the right to use a service while preventing unauthorized access.
Q136: Why is Access Management important? A: For legal compliance, protecting reputation/data, maintaining customer trust, and ensuring business (not IT) decides access rights.
Q137: Which is NOT a challenge for Access Management? A: Tracking users with name changes or duplicate names. Modern systems use unique IDs, making this a non-issue.
Q138: When might access be reduced or removed? A: All of the above: Long-term leave, leaving the organization, investigations, or role changes.
📒 Module 5: Tools, Technology & Continual Improvement
Focus: Selecting tools, automation, and the philosophy of improvement.
Tools & Technology Selection
Q139: What is the correct philosophy regarding Tools and Processes? A: Tools should assist good processes, not replace them or define them. Automating a bad process yields bad results faster.
Q140: Is integration with SKMS and CMS essential for a service management tool? A: Yes (Both statements). A true service management tool must integrate configuration data (CMS) and knowledge (SKMS).
Q141: What is the first step in selecting a tool? A: Understand the requirements. You cannot select or research tools until you know what you need.
Q142: What are generic requirements for a service management tool? A: All of the above: Remote access, integration capabilities, record linking (incident/problem), and web-based access.
Q143: What is the MoSCoW technique used for? A: Categorizing and prioritizing requirements (Must have, Should have, Could have, Won’t have).
Q144: What features belong in a Self-Service Portal? A: Password resets, logging requests, and downloading approved software. (Authorizing changes is a management function, not self-service).
Q145: What is the ideal reporting capability for a tool? A: A selection of generic reports supported by the ability to easily create custom reports.
Q146: What is the direct benefit of Management Commitment to tools? A: Providing Leadership, Funding, and Supporting Commitment. (Operational improvements like “reduced outages” are the result of using the tools, not the commitment itself).
Q147: Which is NOT a benefit of using Project Management for operational changes? A: The assumption that it will automatically be funded by Transition/Project Office to save Operations money. Funding models vary; the benefit is visibility, consistency, and quality.
Q148: Which is NOT a standard software license option? A: “Shared.” Standard terms are Dedicated (Named User), Concurrent, Time-limited, or Web-based/SaaS.
Q149: What is the correct order for tool selection? A: Identify Requirements → Identify Products → Agree Criteria → Evaluate → Shortlist → Score → Rank → Select.
Q150: Which is NOT an advantage of using tools in Service Design? A: That they reduce the need for testing. Tools do not eliminate the need for rigorous validation.
Q151: Which approach to tools and processes is untrue? A: Buying the tool first and then writing processes to fit it. Processes should drive tool selection.
Q152: What factors matter in tool selection? A: Vendor support quality is critical. Capabilities alone are not the only factor.
Q153: What aspects should be evaluated in design tools? A: All of the above: Standards conformity, flexibility, usability, SLA support, data conversion, and security.
Q154: What additional costs must be budgeted for tool implementation? A: All of the above: Training, portal setup, configuration, and reporting setup. These are project costs, not BAU.
Q155: What are advantages of SaaS (Software as a Service)? A: No extra hardware, no client software installation, and less management overhead. (Training is still required).
Continual Service Improvement (CSI) & Operations Context
Q156: What triggers changes to Service Operation? A: All of the above: Business requirements, process improvements, tool enhancements, staff changes, SLA changes, and provisioning method changes.
Q157: Should Operation staff be involved in Design and Transition? A: True. Early involvement ensures operability and prevents design flaws.
Q158: How should changes in Service Operation be managed? A: Larger changes should use a Project Management approach, while all changes follow ITIL guidelines. Not every change needs full project management, but disciplines are valuable.
Q159: When should Operation staff be involved in Design? A: Early in the stages to ensure operational issues (monitoring, backup) are designed in.
Q160: What are risks in Service Operation? A: Introduction of known errors, supplier failure, and security breaches. (Market competition is a Strategy risk, not an Operation risk).
Q161: Why use Communities of Practice? A: To enable collaboration and knowledge sharing across time zones and boundaries.
Q162: Which are collaborative knowledge sharing tools? A: Shared calendars, threaded discussions, and video conferencing. (DML and Event Management are not collaboration tools).
Q163: What is the relationship between Discovery Tools and the CMS? A: Discovery tools populate data into the CMS automatically, though they are not the sole source of data.
Copy
Ask Qwen
Explain
Translate(en-US)
generate the rest of the questions as well
Here are the remaining questions from our session, covering Service Strategy (Demand/Capacity details), Service Design (Risk/Architecture), Service Transition (Configuration/Release details), and General Service Operation/CSI topics that hadn’t been fully categorized in the previous summary.
📘 Module 6: Advanced Service Strategy & Demand
Focus: Deep dive into Capacity, Demand, and Business Activity patterns.
Q164: What is the definition of “Patterns of Business Activity” (PBA)? A: PBAs describe the activity of the business required to deliver specific outcomes (e.g., monthly billing runs, seasonal sales spikes). They are used to predict IT demand based on business workflows, not just raw IT usage stats.
Q165: How does Demand Management utilize User Profiles (UP)? A: It groups users based on their roles and responsibilities. Users in similar roles typically exhibit similar consumption patterns, allowing IT to forecast demand more accurately than by tracking individuals.
Q166: What is the relationship between “Utility” and “Warranty”? A:
- Utility = Fit for Purpose (Does the service do what the customer needs?).
- Warranty = Fit for Use (Is the service available, secure, and reliable enough?).
- Note: A service must have both to provide value.
Q167: Which aspects constitute “Warranty” in ITIL? A: The four key pillars are Availability, Capacity, Continuity, and Security.
Q168: What is the primary goal of Demand Management regarding supply? A: To match Supply to Demand. It involves influencing user behavior (e.g., via differential charging) to smooth out peaks and ensure capacity is available when needed.
Q169: Which information sources are critical for accurate Demand Management? A: All business-facing plans, including marketing forecasts, production schedules, sales targets, and new product launch timelines. IT cannot predict demand in a vacuum.
Q170: Is “Consumption consumes demand” a valid concept? A: No. This is a nonsensical statement. Consumption satisfies demand; it does not “consume” the concept of demand. Furthermore, production and consumption are rarely perfectly synchronized, which is why capacity buffers are needed.
📙 Module 7: Advanced Service Design & Risk
Focus: Holistic design, risk assessment, and architecture.
Q171: What distinguishes a “Holistic” design from a standard technical design? A: A holistic design explicitly addresses all five aspects: Service Solutions, Architectures, Processes, Metrics/Measurement, and People/Organizations. It avoids the trap of designing only the technology while ignoring support processes or staff skills.
Q172: What is a common misconception about Risk in Service Design? A: Confusing Utility and Warranty risks.
- Incorrect: “Insufficient warranty makes the service unfit for purpose.”
- Correct: Insufficient warranty makes it unfit for use; insufficient utility makes it unfit for purpose.
Q173: What must be included in a comprehensive Service Design? A: It must cover Underpinning Contracts (supplier agreements), Technology Components, Staff Skills/Training, and Governance Requirements. Leaving any of these out creates gaps in delivery.
Q174: What is the role of Design Coordination regarding the Service Design Package (SDP)? A: Design Coordination is accountable for ensuring the SDP is produced, consistent, and complete. They manage the process, though they may not perform the actual technical design work themselves.
Q175: Why is “Risk Management” not listed as one of the five aspects of Service Design? A: Because Risk Management is a cross-cutting process integrated into all five aspects (e.g., assessing risk in architecture, processes, and suppliers), rather than being a standalone design aspect like “Service Solutions.”
Q176: What is the correct sequence of activities before a design moves to Transition? A: Evaluate alternatives → Develop Business Case → Procure Solution. Developing (building) the solution happens during Transition, not Design.
📗 Module 8: Advanced Service Transition & Configuration
Focus: SACM details, Release types, and Testing models.
Q177: What is the precise difference between a Configuration Item (CI) and a Configuration Record? A:
- CI: The actual asset (e.g., a server, a license).
- Configuration Record: The database entry containing the attributes and relationships of that CI within the CMS.
Q178: Why is the CMS valuable for Cost Management? A: It prevents unnecessary purchases by identifying spare assets that can be reused and ensures license compliance to avoid fines. It also enables accurate impact assessments to prevent costly failed changes.
Q179: What are the dangers of implementing SACM poorly? A:
- Gathering too much detail (cost outweighs benefit).
- Staff not understanding the importance (leading to poor data quality).
- Process bottlenecks (checking every CI slows down changes).
- Note: Ineffective Change Management is an external risk that makes SACM impossible to maintain.
Q180: Who should sit on the Emergency CAB (ECAB)? A: A small group with high authority and technical knowledge: Senior IT Managers, Senior Technical Managers, and the Service Desk Manager. General support staff or customers are usually excluded to ensure speed.
Q181: What are the valid triggers for starting the Change Management process? A: A formal Request for Change (RFC) or a high-level Change Proposal. An incident call or project document initiates the need for change, but the RFC is the formal trigger.
Q182: What are the three official types of Change in ITIL? A: Standard, Normal, and Emergency. (“Urgent” is a priority level, not a change type).
Q183: What is the definition of a “Release Package”? A: A collection of Configuration Items (CIs) that are built, tested, and deployed together as a single unit.
Q184: What is “Early Life Support” (ELS)? A: A period of heightened support immediately following deployment where the project/transition team works alongside operations to stabilize the service before full handover.
Q185: What is the “V-Model” in testing? A: A diagram mapping development stages (left side) to corresponding testing stages (right side), ensuring that every level of requirement (business, service, technical) has a specific verification test.
Q186: What are the possible outcomes of a Test Evaluation against Exit Criteria? A:
- Pass (Meets all criteria).
- Fail (Does not meet criteria).
- Pass with Risks/Exceptions (Works but with known limitations or higher risk/cost).
Q187: What is the purpose of “Change Evaluation”? A: To provide an independent assessment ensuring a major change is fit for purpose and fit for use before it is deployed, optimizing business risk.
Q188: What data sources feed the Configuration Management System (CMS)? A: Discovery tools automatically scan and populate data, but they are not the only source. Manual entries, project data, and other integrations also contribute.
📕 Module 9: Service Operation Functions & Roles
Focus: Detailed responsibilities of Tech Mgmt, App Mgmt, Ops Mgmt, and Facilities.
Q189: What is the specific scope of Facilities Management? A: Managing the physical environment: power, cooling, physical security, and environmental controls. It does not define IT infrastructure requirements (like server specs), which is Technical Management’s role.
Q190: How do Technical Management and Application Management differ? A:
- Technical Management: Focuses on the Infrastructure (hardware, OS, network, storage).
- Application Management: Focuses on the Software Applications throughout their lifecycle (design, buy, support, improve).
Q191: What are the two sub-functions of IT Operations Management? A:
- Operations Control: Console management, job scheduling, backup monitoring.
- Facilities Management: Physical plant management.
Q192: Do Technical Management teams include architects? A: Yes. Technical Management is a resource pool that includes both designers/architects (for Service Design) and support engineers (for Service Operation).
Q193: What is the primary objective of IT Operations Management regarding stability? A: To ensure routine tasks (backups, batch jobs) are carried out consistently to maintain service stability.
Q194: What skills are essential for Service Desk staff? A: A balance of Interpersonal Skills (communication), Technical Ability (troubleshooting), Business Knowledge (understanding impact), and Application Knowledge.
Q195: What is the role of “Super Users”? A: They act as a local bridge between IT and the business, handling simple queries and communicating major incident updates. However, they must still log incidents via the Service Desk; they should not bypass the SPOC.
Q196: In an outsourced Service Desk model, who holds Accountability? A: The Organization’s Senior Management. You can outsource responsibility (doing the work), but you cannot outsource accountability (answering to the business/customers).
Q197: What is the difference between Functional and Hierarchical Escalation? A:
- Functional: Moving the ticket to a team with more technical expertise (e.g., Level 1 → Level 2).
- Hierarchical: Involving higher management due to severity, SLA breaches, or customer complaints.
Q198: What is the definition of a “Problem”? A: The unknown root cause of one or more incidents. Problem Management seeks to find this cause to prevent recurrence.
Q199: What outputs does Problem Management generate? A: Known Errors (documented root causes), Workarounds (temporary fixes), and RFCs (to implement permanent fixes).
Q200: When should Access be revoked or modified? A: In all cases of Leavers (immediate revocation), Movers (role change – remove old access, grant new), Long-term leave (suspend), or Investigations (suspend pending outcome).
📒 Module 10: Tools, Automation & Continual Improvement
Focus: Implementation strategies, licensing, and the philosophy of improvement.
Q201: What is the “Golden Rule” of Tool Implementation? A: Define your processes first, then select the tool. Never buy a tool and then rewrite your processes to fit the tool’s limitations.
Q202: What are the hidden costs of tool implementation? A: Beyond software licenses, you must budget for Training, Configuration, Customization, Data Migration, and Report Development. These are project costs, not BAU.
Q203: What are the advantages of SaaS (Software as a Service)? A: Reduced hardware footprint, no client-side software installation, and lower management overhead (vendor handles patches/backups). Note: Training costs still apply.
Q204: What is the MoSCoW method? A: A prioritization technique for requirements:
- Must have
- Should have
- Could have
- Won’t have (this time)
Q205: What features define a good Self-Service Portal? A: Password resets, request logging, and software downloads. It should not allow general users to authorize changes (a governance function).
Q206: How should reporting be handled in service management tools? A: The tool should offer standard generic reports out-of-the-box but must also allow easy creation of custom reports to meet unique business needs.
Q207: What is the role of “Communities of Practice”? A: To facilitate knowledge sharing and collaboration among experts across different geographical locations and time zones, breaking down silos.
Q208: What collaborative tools support Knowledge Management? A: Threaded discussions, shared calendars/tasks, and video conferencing. (The Definitive Media Library is a secure store, not a collaboration tool).
Q209: What is the relationship between Discovery Tools and the CMS? A: Discovery tools automate the population of the CMS by scanning the network, reducing manual entry errors. However, they are not the sole source of truth (manual adjustments and other integrations are still needed).
Q210: Does Continual Service Improvement (CSI) apply to Service Transition? A: Yes. CSI applies to every stage of the lifecycle. Transition processes themselves should be regularly reviewed and improved using the PDCA (Plan-Do-Check-Act) cycle.