Common ITSM Consultant Interview Questions Guide | SPOTO

Look for: Organizational and time management skills, with a focus on prioritization based on urgency and impact.

This is a closing interview question to understand the candidate's priorities and fit with the company.

Effective communication during incident resolution involves: - Establishing clear lines of communication. - Providing regular updates to stakeholders. - Using a standardized communication plan. - Ensuring information accuracy and clarity.

Look for: Detailed account of the project, challenges faced, solutions implemented, and results achieved. Mention of lessons learned.

The main difference between a Service Desk and a Help Desk lies in their scope and purpose. While a Service Desk provides a broader range of IT services, managing incidents and service requests, a Help Desk focuses primarily on troubleshooting and resolving immediate technical issues. The primary focus of a Service Desk is IT service delivery, managing incidents and requests, while a Help Desk focuses on troubleshooting and resolving user issues. The scope of a Service Desk is broader, including IT services, incidents, requests, and communication, whereas a Help Desk has a narrower scope, focusing on fixing technical issues. A Service Desk is more proactive, helping improve overall IT service management, while a Help Desk is mainly reactive, dealing with user-reported issues. A Service Desk is often integrated with other ITSM processes (e.g., Change, Incident Management), while a Help Desk primarily handles immediate issues with less integration. A Service Desk acts as a single point of contact for multiple IT services and processes, while a Help Desk primarily handles troubleshooting and support queries. The strategic role of a Service Desk supports long-term service improvement and IT alignment with business goals, whereas a Help Desk focuses on short-term issue resolution.

Compare SLAs to actual performance data and resource levels. Explain risks and practical limitations to stakeholders. Propose adjusted SLAs or staged targets that are achievable. Update ServiceNow configurations once new agreements are made.

Service Continuity Management in ITSM focuses on ensuring that critical IT services are maintained or rapidly restored during a major disruption, such as a disaster or system failure. It involves creating and implementing disaster recovery plans, developing business continuity strategies, and conducting regular testing to validate the effectiveness of these plans. The process ensures organizations can continue operations with minimal downtime, safeguarding essential services and data. Service Continuity Management helps minimize business risk by ensuring that IT services can withstand or quickly recover from unforeseen disruptions.

This is an opening question to help candidates feel comfortable and set the stage for a productive conversation. Allowing the interviewee to talk about themselves creates a more conversational atmosphere.

Start from business view: what types of issues users usually have, and which services they care about. Keep categories simple and intuitive; avoid long, complex trees. Use impact and urgency to define priority matrix and agree rules with stakeholders. Configure categories and priority logic in ServiceNow so they are easy for Service Desk to use.

A Business Rule was chosen because it runs server-side directly on the database operation (insert/update) with minimal overhead and is ideal for simple, synchronous logic like calculating priority based on impact and urgency. Flow Designer is better suited for complex, multi-step automations or when integration with other systems is needed.

- Access Management ensures authorized users have appropriate access to services. - It protects against unauthorized access and security breaches. - Access Management maintains confidentiality, integrity, and availability of services. - It defines and monitors access rights, roles, and privileges. - Access Management helps ensure compliance with security policies and regulations.

// Business Rule: Before Insert/Update, Condition: current.priority == 1 if (current.priority == 1) { var gr = new GlideRecord('sys_user_group'); if (gr.get('name', 'Major Incident Group')) { current.assignment_group = gr.sys_id; } }

- ITIL Access Management ensures authorized users have appropriate access to IT services. - It defines policies, processes, and procedures for granting, modifying, and revoking access rights. - Implements controls to prevent unauthorized access and protect sensitive information. - Facilitates compliance with regulatory requirements and security standards. - Provides a secure and efficient access management system for IT services.

Address resistance by: - Communicating benefits clearly. - Involving stakeholders in decision-making. - Providing training and support during implementation.

Service Strategy defines how IT services contribute to realizing business objectives. Understanding customer needs and market opportunities is integral to Service Strategy, Which Also guides decision-making regarding service offerings and differentiation. Alignment of IT resources with business priorities and value creation is pivotal in Service Strategy.

Methods for collecting and analyzing user feedback, identifying improvement opportunities, and implementing changes based on feedback.

When conflicts arise, I encourage open communication and try to understand different perspectives. I believe in finding a solution that is fair and acceptable to all parties involved.

Tailor message based on audience: leadership, Service Desk, other IT teams, and end users. Explain why the change is happening, what will change, and how it benefits them. Use simple language and examples rather than pure process jargon. Provide channels for questions and feedback.

I have extensive experience developing custom ITSM solutions. I have been working in the ITSM space for over 5 years, and have developed a wide range of solutions for various clients. I have experience developing solutions for incident management, problem management, change management, service request management, asset management, and service level management. I have also developed custom solutions for reporting, analytics, and automation. I have experience working with a variety of ITSM tools, including ServiceNow, BMC Remedy, and HP Service Manager. I am also familiar with the ITIL framework and have experience developing solutions that adhere to ITIL best practices. I have a strong understanding of the development process, from requirements gathering to design, development, testing, and deployment. I am also experienced in working with stakeholders to ensure that the solutions I develop meet their needs.

To determine if field values have changed, you can use the 'changes()' method in a Business Rule or Client Script. For example: if (current.changes('field_name')) { // logic } Alternatively, compare the 'previous' and 'current' values using GlideRecord.

- Detect and log the problem - Categorize and prioritize the problem - Investigate and diagnose - Identify a workaround for the problem - Raise a known error record - Resolve the problem - Close the problem - Review the problem.

A Standard Change is a low-risk, pre-approved change that follows a defined procedure, such as password resets. A Normal Change is a change that requires formal review and approval by the Change Advisory Board (CAB) because it involves higher risk or complexity.

SLA is a legal agreement between the service provider of IT services and the customer. It states service expectations, performance parameters, and responsibilities. Underwriting the SLA will ensure the accountability and quality of services.

Adopting IT Service Management (ITSM) brings numerous advantages to organizations by optimizing how IT services are delivered and managed. Here are the key benefits of implementing ITSM: - Improved service delivery and customer satisfaction: ITSM ensures services are delivered efficiently, meeting customer expectations and improving overall satisfaction - Reduced downtime and faster incident resolution: ITSM helps minimize service disruptions and ensures quicker recovery from incidents, reducing operational downtime - Enhanced productivity through standardized processes: ITSM provides structured workflows, leading to more consistent and efficient IT operations - Better alignment of IT services with business goals: ITSM ensures that IT services directly support and align with organizational objectives and strategies - Increased transparency and accountability: ITSM improves visibility into IT processes, making it easier to track performance and hold teams accountable

ITIL® refers to the Information Technology Infrastructure Library. It's a framework that outlines best practices for IT service management (ITSM).ITIL® offers guidance on aligning IT services with business objectives. It comprises practices to enhance the efficiency and effectiveness of IT service delivery. Widely adopted globally, ITIL® fosters improved service quality and customer satisfaction.

First, check the 'SLA Definition' table to ensure the SLA is active and correctly configured. Then, check the 'SLA' table to see if any records are created. Review the 'syslog' table for errors related to SLA processing, and check the 'Task SLA' table for the specific incident.

The incident management process can be used for bugs in an application, system downs, printer issues, and storage space alerts.

Look for: Understanding of the ITIL framework and practical examples. What to Expect: Discuss principles like service value system, service lifecycle, and continual improvement. Application in various ITSM processes.

This is a challenging question to evaluate conflict resolution and client management skills.

I implement data governance policies, use validation rules, enforce mandatory fields, and conduct regular data audits. Integration with discovery tools also helps maintain accurate and up-to-date CMDB data.

The primary purpose of Configuration Management is to collect, store, manage, update, and verify data on IT assets and configurations in the enterprise.

Look for: Communication skills, empathy, and negotiation abilities. What to Expect: Effective communication, demonstrating benefits, involving stakeholders early in the process, and addressing concerns.

The logic uses a 2D array or a switch statement to map Impact (High, Medium, Low) and Urgency (High, Medium, Low) to Priority (1-4). For example: if (impact == 1 && urgency == 1) { priority = 1; } else if (impact == 1 && urgency == 2) { priority = 2; } etc. This follows the standard ITIL priority matrix.

Key technical skills include knowledge of ITSM frameworks like ITIL, experience with ITSM tools (e.g., ServiceNow), and familiarity with service desk management. Additionally, understanding incident response and IT governance is essential for effective ITSM.

The purposes of Problem Management are:

This is a light-hearted question to assess communication simplicity and creativity.

Subnetting is the process of splitting up a single TCP/IP network into several unique network segments. The advantage of this is that it makes the network infrastructure easier to manage and improves performance. It also prevents errors or problems in one of the subnets from impacting the entire network. I often recommend that clients subnet their network if it is large or involves communicating between multiple locations.

Capture requirements and scope clearly at the start, including what is out of scope. Use a backlog or list of change requests for new ideas that come later. Discuss impact of scope changes with project manager and stakeholders. Agree priorities and phases instead of trying to add everything at once.

When developing an ITSM system, I use a variety of strategies to ensure that the system is user-friendly. First, I focus on creating a user-friendly interface. This includes making sure that the system is intuitive and easy to navigate, with clear labels and instructions. I also make sure that the system is visually appealing, with a modern design and attractive colors. Second, I strive to make the system as efficient as possible. This includes streamlining processes and reducing the number of steps required to complete tasks. I also look for ways to automate certain processes, such as setting up automated notifications or reminders. Third, I make sure that the system is secure and reliable. This includes implementing the latest security protocols and ensuring that the system is regularly updated with the latest patches and bug fixes. Finally, I strive to provide users with the best possible support. This includes providing detailed documentation and tutorials, as well as offering support through various channels such as email, phone, and live chat. By following these strategies, I am able to ensure that the ITSM system I develop is user-friendly and meets the needs of the users.

Financial Management ensures cost-effective service delivery. Appropriately budgeting and allocating resources and monitoring and controlling IT expenditures provide stakeholders with financial transparency and support decision-making by assessing IT investments' economic impact and optimizing financial resources' use for maximum organizational value.

A Client Script runs on the client side (browser) and is used to manipulate form fields, validate data, or show messages based on user actions. A UI Policy also runs on the client side but is declarative and does not require scripting; it can show/hide fields, make fields mandatory, or set read-only state based on conditions without writing code.

Guide the interviewer through a holistic journey, commencing with the identification and classification of incidents, progressing through prioritization, and culminating in the resolution phase, underscoring the significance of consistent communication and meticulous documentation.

Any component that must be controlled to provide an IT service is called a configuration item (CI). CIs can range from hardware and software to documentation and people.ITIL maintains a Configuration Management Database (CMDB) to store information about CIs and their relationships.CIs are uniquely identified and tracked throughout their lifecycle to ensure accurate configuration management.

The CAB is responsible for processing major IT changes. It evaluates risks, and impact on business and ensures minimalistic disruption to service. It helps ensure that service reliability is kept intact while changes are being made.

Listen to the reasons behind resistance; often it is fear of extra work or loss of control. Show how the new process reduces manual work or improves visibility. Involve key users as champions and show quick wins. Adjust where possible without breaking overall design.

IT Service Management (ITSM) is a set of structured policies, processes, and procedures that govern IT services' planning, delivery, operation, and control to meet business needs. ITSM aligns IT services with business objectives to enhance efficiency, customer satisfaction, and performance. It covers all aspects of IT service lifecycle management, ensuring that services are delivered in a cost-effective, reliable, and scalable manner.

I'm graduating this June with a degree in business and a focus on marketing. Through my internships and extracurricular activities, I've honed strong leadership, data analysis, and problem-solving skills that set me up for a consulting career. For example, I served as the President of my college's Consulting Club, where I organized events to help students gain exposure to the consulting industry. This experience taught me how to effectively communicate with others and lead a team. Last summer, I completed a marketing internship at a tech startup where I developed their social media strategy and analyzed user engagement data. This experience taught me the importance of data-driven decision-making and how to effectively communicate insights to my managers. In addition, I've also served as a Residence Advisor for my college's dorm program. Through this role, I honed my problem-solving skills and learned how to resolve conflicts effectively. Overall, I'm excited about the opportunity to bring my skills to consulting, where I can continue to learn and grow while making a meaningful impact.

var gr = new GlideRecord('incident'); gr.addQuery('active', true); gr.addQuery('sys_created_on', '<', gs.daysAgoStart(3)); gr.query(); while (gr.next()) { gs.eventQueue('incident.reminder', gr, gr.operation(), ''); }

Oversees interactions with outside vendors and suppliers.Ensures suppliers meet agreed-upon service levels and quality standards.Coordinates procurement activities and contracts with suppliers.Identifies and mitigates risks associated with supplier relationships.Facilitates cost-effective sourcing and supplier performance evaluation.Supports overall service delivery and quality assurance.

This is a situational consultant interview question to evaluate the candidate's ability to handle urgent requests and communicate effectively.

Look for: Conflict resolution skills and ability to manage team dynamics.

Offer a detailed strategy for effective Service Transition, encompassing crucial aspects such as meticulous planning, rigorous testing, and comprehensive end-user training to ensure minimal disruption during the implementation phase.

A project has a finite lifespan. A process is continuous and has no end date.

A Known Error is a problem that has been diagnosed and for which a workaround or permanent solution has been identified but not yet implemented. It is documented in the Known Error Database (KEDB).

Data migration to ServiceNow involves mapping legacy data fields to ServiceNow tables, using import sets and transform maps to load data, validating data quality, and performing testing. Tools like the ServiceNow Import Set API, Excel import, or third-party ETL tools can be used. It is important to clean and deduplicate data before migration.

Understand what they liked about the old tool and what pain points they had. Explain the benefits of using ServiceNow's standard patterns and capabilities. Show where replicating the old tool would cause complexity or maintenance issues. Propose a design that gives familiar experience but uses ServiceNow strengths.

To identify which notification is firing, check the 'sys_email' table for the sent emails and review the 'Notification' field. You can also enable notification logging or use the 'Email Log' to trace the notification source. Additionally, review all active notifications for the same table and event.

This is a challenging question to assess self-awareness and problem-solving for potential difficulties.

- The Service Owner is accountable for the delivery of a specific IT service. - They represent the interests of stakeholders and ensure service requirements are met. - Service Owners oversee service strategy, design, transition, and operation. - They manage the lifecycle of the service and its associated assets. - Service Owners collaborate with other ITIL roles to ensure service excellence.

Discussion on key performance indicators (KPIs) such as incident resolution time, SLA compliance, user satisfaction, and system uptime.

You can close a Know Error depending on the following conditions:

The key components of ITIL include: - Service Strategy: Focuses on understanding organizational objectives and customer needs. - Service Design: Designs new or changed services for introduction into the live environment. - Service Transition: Manages changes to the IT infrastructure and the introduction of new or changed services into the environment. - Service Operation: Manages services in operation, ensuring they meet agreed service levels. - Continual Service Improvement (CSI): Achieves incremental and large-scale improvements in service quality, operational efficiency, and business continuity.

No, GlideRecord was not necessary because the Business Rule operates on the current record (current object). The Impact and Urgency values are directly accessible from the current record, and the priority can be set using current.setValue(). GlideRecord would only be needed if querying other tables was required.

The four phases in the PDSA Cycle are: - Plan: Involves the identification and analysis of the problem. - Do: Development and testing of a solution. - Check: Check how effective the solution is and look for areas for improvement. - Act: Implementation of the improved solution.

This is a personality question to glimpse how the candidate thinks and what motivates them, assessing cultural fit.

The pace of innovation in the IT industry is very rapid, and staying informed about new technologies and developments is challenging. I do this by subscribing to several industry news services, blogs, and newsletters. I also attend several industry events each year where I meet with some of the leading technology providers. I am a member of a few local user groups, and I take time to meet with other consultants frequently to share information. This has helped me stay abreast of developments in the industry, and I feel confident that I am up to date on current technology.

Show that you can relate to differing points of view, build a case for your point of view, and be persuasive. Do not sound dictatorial or difficult to work with.

This is a qualification-based question to dig into the candidate's experience, leadership, and project outcomes.

This is a personality interview question to assess the candidate's ideal working conditions and cultural fit.

Incident Management is the process of managing the lifecycle of incidents that are reported. It consists of several steps that must be carried out to resolve and document the incidents.

Service Level Management (SLM) is the process of negotiating, documenting, monitoring, and reviewing service level agreements (SLAs) and service level targets. It ensures that IT services meet agreed-upon performance levels and addresses any breaches.

Service Portfolio Management makes certain that IT Services follow the Business Strategy. Usually, it manages the entirety of a service's lifecycle, from planning to retirement. This ensures efficient resource allocation.

A configuration baseline is a kind of a baseline that is particular to configuration management. It is used for a configuration, which has been formally agreed upon and managed by the change management process.

ITIL-certified professionals have expertise in ITSM best practices. They help organizations optimize IT processes, cut costs, and deliver better services. Therefore, organizations treasure their presence.

Keep skills updated by: - Participating in training programs and certifications (e.g., ITIL). - Reading industry publications and attending conferences. - Engaging in online forums and networking with peers in the ITSM community.

A project tends to have a fixed time span whereas a process is continuous with no end date.

Automated processes like: - Incident routing and prioritization based on impact and urgency. - Self-service portals for common service requests. - Automated reporting and notification systems to improve response times and efficiency.

This is a qualification-based interview question to assess the candidate's technical skills and practical application.

Evaluating the ROI of a technology investment is crucial for justifying expenditure and demonstrating value. My process involves both quantitative and qualitative analysis. Quantitatively, I identify direct costs such as hardware, software, implementation, and training and project tangible benefits like reduced operational expenses, increased revenue, or cost avoidance. Qualitatively, I consider benefits like improved employee morale, enhanced customer satisfaction, better data insights, and increased agility. I present these in a clear business case, often using a projected payback period or net present value, and establish KPIs to track actual ROI post-implementation.

The ITIL (Information Technology Infrastructure Library) is one of the frameworks of best practices for IT service management (ITSM). ITIL processes and procedures help streamline IT operations and enhance the efficiency of service delivery. Thus, ITIL effectively connects IT services to business.

These types of behavioral questions require specific examples from your experience. Here's a template you can adapt, focusing on the STAR method (Situation, Task, Action, Result) for each scenario: Example 1: Resolving a Critical Incident - Situation: Describe a specific critical incident you faced. What service was affected? What was the business impact? What was your role? - Example: "At my previous company, a critical e-commerce platform used by our sales team went down unexpectedly during a peak sales period. This resulted in immediate revenue loss and potential damage to customer relationships. I was the lead on-call engineer for this system." - Task: Explain your responsibility in resolving the incident. What were your objectives? - Example: "My primary objective was to restore the platform as quickly and efficiently as possible to minimize the financial and reputational impact. I also needed to communicate effectively with stakeholders about the situation and progress." - Action: Detail the steps you took to address the incident. What specific actions did you take? What tools or processes did you use? Did you collaborate with others? - Example: "I immediately accessed the monitoring dashboard to confirm the outage and identify any initial error messages. I then initiated a conference call with the relevant technical teams (database, network, application). Following our incident management process, we began systematically diagnosing the issue. I focused on reviewing application logs and recent deployments. I identified a recent code push that seemed to correlate with the outage timeframe. Working with the development team, we quickly rolled back to the previous stable version. Throughout this, I provided regular updates to the IT manager and the sales leadership team on our progress and estimated time to resolution." - Result: Describe the outcome of your actions. How was the incident resolved? What was the impact of your efforts? What did you learn? - Example: "The rollback successfully restored the e-commerce platform within 45 minutes of the initial outage. This significantly reduced the potential revenue loss. Following the incident, I led a post-incident review to determine the root cause (a previously untested edge case in the new code). We implemented stricter testing procedures and improved our rollback process to be even faster and more reliable. This experience reinforced the importance of thorough testing and clear communication during critical incidents." Example 2: Managing Misaligned IT Services with Business Goals - Situation: Describe a situation where an IT service was not effectively supporting a key business goal. What was the service? What was the business goal? Why was there a misalignment? What was your role? - Example: "At my previous organization, we had a legacy CRM system that was heavily relied upon by the marketing team for lead management. However, the system was outdated, lacked key integration capabilities with our new marketing automation platform, and was hindering the marketing team's ability to effectively track and nurture leads, ultimately impacting our sales growth targets. I was the IT Business Analyst responsible for supporting the marketing department." - Task: Explain your responsibility in addressing this misalignment. What were your objectives? - Example: "My objective was to identify the root causes of the misalignment, understand the marketing team's needs, and propose a solution that would better support their lead management process and contribute to achieving the sales growth targets." - Action: Detail the steps you took to understand the issue and drive change. What did you do to gather information? How did you collaborate with stakeholders? What solutions did you propose? How did you manage the implementation? - Example: "I conducted several workshops and interviews with the marketing team to understand their pain points and future requirements. I analyzed the capabilities and limitations of the existing CRM and the new marketing automation platform. I then researched potential solutions, including upgrading the existing CRM, implementing a new CRM, or finding integration solutions between the two platforms. I presented a business case to IT leadership and the marketing director, highlighting the benefits and costs of each option, ultimately recommending the implementation of a new CRM that would integrate seamlessly with the marketing automation platform. I then worked closely with the marketing team to define the requirements for the new CRM, participated in the vendor selection process, and collaborated with the implementation team to ensure the successful deployment and data migration." - Result: Describe the outcome of your efforts. How was the misalignment addressed? What was the impact on the business goal? What did you learn about stakeholder management and business alignment? - Example: "The new CRM was successfully implemented and integrated with the marketing automation platform. This resulted in improved lead tracking, enhanced marketing campaign effectiveness, and a noticeable increase in qualified leads passed to the sales

Talk about a project where you played an important role as a teammate.

- Service Catalog Management - Service Level Management - Capacity Management - Availability Management - IT Service Continuity Management - Information Security Management - Supplier Management - Design Coordination

SLAs define response and resolution targets. You create SLA definitions with conditions (e.g., Priority = 1), associate them with workflows, and use timers to track progress. Escalations can be triggered if SLAs breach.

Look for: Critical thinking, technical skills, and ability to handle complex issues. What to Expect: A detailed description of the problem, the analytical approach taken, tools used, and the resolution. Highlight the candidate's problem-solving and analytical skills.

- Customer-based SLA: Tailored to meet the specific needs of individual customers. - Service-based SLA: Applies uniformly to all customers using a particular service. - Multi-level SLA: Involves different SLAs catering to various levels of service. - Operational-level SLA: Focuses on day-to-day operational processes. - Underpinning Contract (UC) SLA: Agreement with third-party vendors or suppliers supporting service delivery. - Corporate-level SLA: Encompasses agreements spanning the entire organization.

The major benefits of ITIL are:

Open the fridge, put the giraffe in, close the fridge. Nobody says how big the giraffe or the fridge is.

ITSM (IT Service Management) in ServiceNow refers to a suite of applications designed to manage IT services efficiently. Core modules include: - Incident Management – for restoring services quickly. - Problem Management – for identifying and eliminating root causes. - Change Management – for managing changes with minimal risk. - Request Management – for handling service requests. - Knowledge Management – for sharing solutions and documentation. - CMDB – for tracking Configuration Items and their relationships.

An operational-level agreement (OLA) is a contract that describes how the various IT groups within a company design their processes and services to support a service-level agreement (SLA).

The success of ITIL implementation is measured through key performance indicators (KPIs) such as incident resolution time and customer satisfaction. Regular audits and stakeholder feedback are also crucial for continuous improvement.

I added a Client Script (onChange or onLoad) that refreshes the priority field on the form after the Business Rule runs. Alternatively, I used a UI Policy or a script that triggers a g_form.setValue() to update the field client-side based on the server-side calculation.

ITIL facilitates creating, documenting, and disseminating knowledge across the organization. Processes for capturing and managing tacit and explicit knowledge are established. Relevant stakeholders are ensured access to insights and best practices. ITIL promotes a culture of learning and continuous improvement. Utilizing knowledge assets enhances problem-solving and decision-making capabilities.

This is a personality question to identify key strengths and their practical application in a consulting context.

The main difference between a Service Desk and a Help Desk lies in their scope and purpose. While a Service Desk provides a broader range of IT services, managing incidents and service requests, a Help Desk focuses primarily on troubleshooting and resolving immediate technical issues. | Aspect | Service Desk | Help Desk | |---|---|---| | Primary Focus | IT service delivery, managing incidents, and requests | Troubleshooting and resolving user issues | | Scope | Broader scope, including IT services, incidents, requests, and communication | Narrower scope, focusing on fixing technical issues | | Proactive/Reactive | More proactive, helping improve overall IT service management | Mainly reactive, dealing with user-reported issues | | Service Integration | Often integrated with other ITSM processes (e.g., Change, Incident Management) | Primarily handles immediate issues with less integration | | User Interaction | Acts as a single point of contact for multiple IT services and processes | Primarily handles troubleshooting and support queries | | Strategic Role | Supports long-term service improvement and IT alignment with business goals | Focuses on short-term issue resolution |

A Configuration Management Database (CMDB) is a centralized repository that stores detailed information about all the components, assets, configurations, and relationships within an organization's IT infrastructure. It includes data about hardware, software, networks, and other resources. The CMDB is crucial for managing IT resources, as it provides a comprehensive view of the IT environment, helping IT teams troubleshoot issues, track dependencies, and plan for changes. By maintaining an accurate CMDB, organizations can ensure better decision-making, minimize service disruptions, and enhance the efficiency of IT operations.

It is where all IT assets, their configurations, and inter-relationships are housed. CMDB allows IT teams to keep track of changes, troubleshoot issues, and provide better service management. Hence, a well-maintained CMDB increases the effectiveness of IT.

Steps involved in change management: request submission, assessment, approval, implementation, and review. Focus on minimizing risks and service disruptions.

Look for: Familiarity with various RCA tools and examples of successful applications. What to Expect: Mention of tools like Ishikawa (fishbone) diagrams, Pareto Analysis, and the 5 Whys technique. Discussion on how these tools help in identifying underlying causes.

The Client Script is added to provide immediate client-side feedback (e.g., updating the Priority field visually) without requiring a page reload. The Business Rule handles the server-side logic, while the Client Script ensures the UI reflects the change in real-time.

Mentioned below are the few knowledge management systems

Exhibit your adeptness by elucidating the significance of SLAs in defining service expectations, outlining performance metrics, and emphasizing the symbiotic relationship between IT operations and broader business objectives.

To get all active and inactive records from a table, you can use a GlideRecord query without filtering on the 'active' field. For example: var gr = new GlideRecord('incident'); gr.query(); This retrieves all records regardless of their active status.

1) Incident is created with Impact=1, Urgency=1, Priority=1. 2) A Business Rule auto-assigns the incident to the Major Incident Group. 3) An SLA is attached (e.g., 15 min response, 1 hour resolution). 4) A Flow Designer flow triggers notifications to the on-call team. 5) The incident is worked on, and updates are logged. 6) When resolved, a post-implementation review may be triggered. 7) The incident is closed after verification.

ITSM deployment models vary based on how the IT service management software is hosted and managed, offering flexibility depending on the organization's needs. Below are the main types of ITSM deployment models commonly used. - On-premises: ITSM software is installed and managed on the company's servers - Cloud-based: ITSM solutions are hosted in the cloud, offering scalability and ease of access - Hybrid: A combination of both on-premises and cloud-based ITSM deployments

The 'set workflow(e)' function is used to start a workflow on a record. It triggers the specified workflow process, which can automate tasks, approvals, and notifications based on the record's data and state.

Within ITSM, the end user tends to refer to the direct recipient of a service or product, whereas a customer refers to someone who can choose from various products, suppliers, and services.

Implemented ITIL practices: - Improved incident response times by 30%. - Enhanced service availability and customer satisfaction. - Reduced operational costs through streamlined processes.

ISO/IEC 27002 is a code of best practices that delivers guidelines for organizational information security standards and information security management for implementing information security controls.

Option 1 (Basic Cloning - Not Recommended): var grInc = new GlideRecord('incident'); if (grInc.get('sys_id_of_the_incident')) { grInc.insert(); } This keeps the same Incident Number, causing duplication issues. Option 2 (Safe Cloning): var grInc = new GlideRecord('incident'); if (grInc.get('sys_id_of_the_incident')) { grInc.number = ''; grInc.insert(); } Clearing the number field allows ServiceNow to auto-generate a new number.

Answers to this question should follow the same rules as the previous one. Remember to be sincere - blatant flattering does not make good impressions. Preparation is simple – pay attention to your surroundings when you enter their office. Consulting firms appreciate people who can notice the small but important details. Here is an example answer: 'I like the way this building uses glass to maximize natural lighting. It must really be easing on the eyes, I prefer that to artificial lights. Is it the same for you?'

Change Management in ITSM ensures that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT infrastructure, minimizing the impact on service quality and availability.

Metrics and KPIs measure: - Performance and efficiency of ITSM processes. - Customer satisfaction and service quality. - Valuable metrics include incident resolution time, first-call resolution rate, and SLA compliance, as they reflect service delivery effectiveness.

If this was a real project, I would find industry reports to gain an initial understanding of the market trends, and in case I needed more and deeper insights, I would try to contact a local industry expert. The former method is quick and widely available but everyone can gain access to industry reports – including the competitors – and the information is not too insightful. Industry experts, on the other hand, can give unique insights that are not always accessible.

There are three types of SLA. - Service-based SLA - Customer-based SLA - Multi-level SLA

Key fields include Change Number, Short Description, Description, Category (Standard, Normal, Emergency), Risk Level, Impact, Priority, Planned Start and End Dates, Assignment Group, Assigned To, Approval, and State (Draft, Assess, Authorize, Scheduled, Implement, Review, Closed).

This is a situational consultant interview question to evaluate the candidate's risk management skills.

To streamline a company's information systems, I'd advise a phased, data-driven approach. First, we'd conduct a comprehensive discovery phase to map all current systems, data flows, and pain points, identifying redundancies and manual processes. Next, we'd analyze this data to prioritize areas for improvement based on business impact and feasibility. This might involve consolidating duplicate applications, automating workflows, or migrating to more integrated cloud platforms. Finally, we'd develop a clear roadmap with measurable KPIs, focusing on incremental improvements that deliver quick wins while building towards a more efficient, unified future state.

- Incident Management focuses on restoring normal service operation as quickly as possible to minimize business impact. It is reactive and deals with the symptoms of problems. - Problem Management, on the other hand, aims to prevent incidents from happening by identifying and addressing the root causes of incidents. It is proactive and focuses on finding permanent solutions to recurring issues.

Continual Service Improvement (CSI) is a key process in ITSM that aims to review and improve IT services, processes, and overall service quality on an ongoing basis. By regularly assessing performance, CSI helps identify areas for improvement, whether through increased efficiency, better resource use, or enhanced service delivery. The process is data-driven, aligning IT services with evolving business needs and ensuring that IT can adapt to environmental changes. CSI ensures that organizations maintain high-quality service while remaining competitive and agile.

An Incident Management System categorizes, prioritizes, and resolves incidents reported by users or detected through monitoring tools. Incidents are logged, assigned priority, and investigated according to predefined procedures and service level agreements. Communication with affected users and stakeholders is maintained throughout, providing updates on incident status and resolution progress.

A Service Level Objective (SLO) is a specific, measurable target within a Service Level Agreement (SLA), such as '99.9% uptime' or 'response time under 4 hours.' SLOs define the expected performance and quality of a service.

This is a client communication skills interview question to evaluate the candidate's post-project resolution and client recovery skills.

Ensure the adoption of standardized methods and procedures for handling changes efficiently and promptly. Minimize the adverse impact of changes on IT services by appropriately assessing and managing risks. Facilitate effective communication and coordination among stakeholders involved in the change process. Record, evaluate, authorize, prioritize, plan, test, implement, document, and review changes meticulously in a controlled manner.

In which context and where the image you need to populate.

Key Performance Indicators (KPIs) are metrics used to measure the performance of IT services and processes. Common ITSM KPIs include: - Incident resolution time: Measures how quickly incidents are resolved to restore normal service operations - SLA compliance rate: Tracks the percentage of IT services that meet the agreed Service Level Agreement standards - Change success rate: Indicates the percentage of changes implemented without causing new incidents or disruptions - Customer satisfaction score: Gauges user satisfaction with the IT services provided, typically through surveys - Mean time to recovery (MTTR): Calculates the average time taken to restore services after an incident or disruption

SLAs define commitments to customers/end users. OLAs define internal expectations between support teams. Underpinning Contracts define expectations with external vendors. In ServiceNow, you focus on SLAs and sometimes OLAs; vendor SLAs may be tracked via vendor queues and reports.

OLA delineates the agreed operational level of service among internal support groups. It specifies each support group's responsibilities in delivering IT services.OLAs reinforce SLAs by ensuring internal support groups fulfill their service obligations. Details such as response times, escalation procedures, and service availability may be included in OLAs.While not legally binding contracts, OLAs serve as internal agreements.

The Business Rule was configured as 'Before' because the priority needs to be calculated and set before the record is saved to the database. This ensures the priority value is stored correctly and is available for other processes like SLA timers and assignment rules.

This is a client communication question to assess clarity and simplification skills.

- Change Managers oversee the Change Management process. - We are assessing change requests for potential impact and risk. - Ensuring changes align with business objectives and policies. - I am coordinating change implementation and communication. - We are monitoring the progress of the change and addressing any issues. - We are facilitating continuous improvement of the change process.

The information related to the cause of the problem is required to identify the known error.

Change management ensures that changes to the IT environment are carried out with minimal disruption. Any change requires a structured assessment of risks and approvals. This process enhances stability and; therefore, reduces downtime for services.

Thank you for this very interesting question. Before diving into the estimations, I would like to first clarify a few terms to make sure we are both on the same page regarding the important details. There are three points I would like to clarify: - Earl Grey tea is any tea marketed as such, regardless of the ingredients. - British people consist of inhabitants of the UK. - The consumption is measured in tea cups. Do you agree with me on these assumptions? 'It's great to see we understand the question the same way. I'd like to take a few moments to gather my thoughts and draw up my issue tree – so may I take a timeout?' 'Thanks for your patience. Now, to estimate the consumption of Earl Grey tea by British people on a typical afternoon, I'd like to break it down into three determinants – the population of the UK, the number of tea cups each UK resident drinks in an afternoon, and the chance of those cups being Earl Grey. For the population of the UK, I'd take a rounded number of 65 million. Considering that UK people are very famous for their love of tea, I assume about 80% of the UK population drinks tea, which means there is 52 million tea drinkers in UK. Each of these 52 million people drinks one cup of tea in their afternoon tea meal. Earl Grey is among the top five popular teas in the UK, and I estimate this group to take up 50% of all UK tea, considering so many other types in the market. The chance of an afternoon tea cup being Earl Grey is 10% - this number is taken to simplify the calculations. Combining these numbers, I estimate that on a typical afternoon, British people consume 5.2 million cups of Earl Grey tea – quite an attractive number for any business operating in the tea industry.

Key Performance Indicators (KPIs) are metrics used to measure the performance of IT services and processes. Common ITSM KPIs include metrics such as system uptime, response times, resolution times, and service availability.

Illuminate the intricacies of the CMDB, elucidating how it serves as a repository for crucial information pertaining to IT assets and their interrelationships, and underscore its role in both Change Management and Configuration Management processes.

Incidents are prioritized based on factors such as: - Impact on business operations. - Urgency of resolution. - SLA commitments. - Customer or user priority.

Use incident, problem, and change data to identify recurring issues and bottlenecks. Track improvement actions as tasks or stories and follow them through. Adjust processes, SLAs, or responsibilities based on data and feedback. Review results in regular service reviews.

A business rule is a server-side script in ServiceNow that runs when a record is inserted, updated, deleted, or queried. It is used to automate business logic, validate data, or perform actions without user intervention.

No, GlideRecord was not necessary because the Business Rule operates on the current record directly using the 'current' object. There was no need to query other records.

ITSM professionals align IT services with business goals by collaborating with leaders to understand strategic objectives. They ensure services are efficient, adaptable, and continuously improved to meet evolving business needs and enhance service delivery.

The CMDB (Configuration Management Database) in ServiceNow stores information about IT assets and configuration items (CIs), their attributes, and relationships. It helps in impact analysis, incident management, change management, and ensuring accurate visibility into the IT environment.

Every organization has a unique style and culture. This defines how members of the organization collaborate, its communication styles, and how it prioritizes the work they do. Adapting to the organization's style helps the IT consultant fit into their culture quickly and be perceived as one of their team. I do this by interviewing multiple people within the company to get a clear understanding of the culture and then adapt my style to meet theirs.

Service Continuity Management in ITSM focuses on ensuring that critical IT services are maintained or rapidly restored during a major disruption, such as a disaster or system failure. It involves creating and implementing disaster recovery plans, developing business continuity strategies, and conducting regular testing to validate the effectiveness of these plans. The process ensures organizations can continue operations with minimal downtime, safeguarding essential services and data. Service Continuity Management helps minimize business risk by ensuring that IT services can withstand or quickly recover from unforeseen disruptions.

Knowledge Management makes sure that both the IT teams and users have access to the right information. It enables people to make better decisions and makes services more efficient. This leads to a reduction in recurring incidents and enhances the entire support process.

This is a closing question to understand the candidate's career trajectory and alignment with the role.

This is a personality question to understand how the candidate engages with constructive criticism and professional growth.

The ITIL guiding principle 'Focus on Value' emphasizes that everything an organization does should deliver value to its stakeholders. In ITSM, this means designing and managing services that meet customer needs and provide measurable business outcomes.

This is a situational question to assess project recovery and diagnostic skills.

Service Validation and Testing verify that services meet business requirements, ensure they're fit for purpose, and meet quality standards. They also identify and mitigate risks associated with service changes, validate service designs, and ensure they align with business needs: service Validation and Testing support Service Transition activities.

Techniques for monitoring and analyzing service capacity and performance. Mention of proactive measures to prevent capacity-related issues.

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT', 'assignment_group'); ga.groupBy('assignment_group'); ga.query(); while (ga.next()) { gs.info('Group: ' + ga.assignment_group.getDisplayValue() + ' Count: ' + ga.getAggregate('COUNT', 'assignment_group')); }

ITIL helps with the alignment of IT services and business needs. It establishes consistency and gives businesses a competitive advantage. ITIL also betters customer relationships through improved customer satisfaction with service delivery. Other notable benefits include improved cost-effective use of resources, better management of risk, and better handling of change.

A ServiceNow ITSM Business Analyst acts as a bridge between business stakeholders and technical teams, gathering requirements, analyzing business processes, and configuring ServiceNow ITSM modules to align with ITIL best practices.

Listed below are the few components of SKMS: - Availability management system. - Configuration management system. - Service portfolio.

I check the SLA definition table (contract_sla) to ensure the SLA is active and correctly configured. I review the SLA Conditions and the 'Time Conditions' tab. I also check the 'syslog' table for SLA-related errors and the 'task_sla' table to see if any SLAs are attached.

ITSM (IT Service Management) is a structured approach focused on managing and delivering IT services through well-defined processes, such as Incident, Problem, and Change Management. It emphasizes control, efficiency, and aligning IT services with business needs. DevOps, on the other hand, focuses on continuous delivery, automation, and fostering collaboration between development and operations teams. DevOps aims to improve software delivery speed, reduce silos, and enable faster release cycles, whereas ITSM is more process-driven with a focus on service stability and governance.

IT Asset Management (ITAM) focuses on managing and tracking the lifecycle of all IT assets, including hardware, software, and related components, to ensure they are used efficiently and cost-effectively. In the context of ITSM, ITAM ensures that the organization's IT assets are accurately inventoried and maintained, supporting other ITSM processes like Configuration Management and Change Management. By keeping detailed records of assets, ITAM helps reduce costs, optimize resource use, and improve IT investment and compliance decision-making.

Explanation of CMDB's role in maintaining information about hardware, software, and configuration items. Discussion on its support for change management, incident management, and asset management.

This refers to a time period when changes to the source code are no longer allowed.

Yes, I applied a UI Policy to make the Priority field read-only for most users, except for users with specific roles (e.g., 'admin' or 'incident_manager') who may need to override it.

- The Change Advisory Board (CAB) evaluates and approves proposed changes. - It assesses potential impacts and risks associated with changes. - CAB ensures that changes align with business objectives and IT strategies. - It provides expert advice and guidance to change initiators.

Plans and processes to ensure service continuity in case of disasters or major incidents. Mention of backup, recovery, and regular testing.

To prevent duplicate notifications, ensure that notification conditions are specific and non-overlapping. Use the 'Already notified' condition or check for existing notifications in the 'sys_email' table. Also, avoid multiple notifications with the same table and condition that could fire simultaneously.

The purpose of the Service Level Management process is to ensure that all IT services are delivered to agreed-upon targets. It involves negotiating, monitoring, and reporting on service levels to meet business requirements.

The five stages are: Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement (CSI). Each of these stages helps in effectively managing IT services, and when completed with utmost efficiency, all stages will guarantee that the IT services delivered to support the business objectives of the organization.

To update resolved state incidents to closed state, you can run a scheduled job or a background script that queries all incidents in 'Resolved' state and sets their state to 'Closed'. For example: var gr = new GlideRecord('incident'); gr.addQuery('state', 6); // 6 is Resolved state gr.query(); while (gr.next()) { gr.state = 7; // 7 is Closed state gr.close_notes = 'Bulk closure via script'; gr.update(); }

Provide clear, detailed user stories and functional specs with acceptance criteria. Discuss design options and listen to technical constraints. Review early demos and prototypes and give feedback. Validate that delivered solution matches the agreed process and user needs.

Adopting IT Service Management (ITSM) brings numerous advantages to organizations by optimizing how IT services are delivered and managed. Key benefits of implementing ITSM include improved efficiency, enhanced customer satisfaction, better alignment of IT services with business goals, reduced downtime, cost savings, and improved risk management.

Capacity Management is the process of ensuring that IT resources (such as servers, storage, and network bandwidth) are sufficient to meet current and future business demands. It involves forecasting, monitoring, and optimizing capacity to avoid performance issues.

- Log, categorize and prioritize incidents - Investigate and diagnose - Incident resolution - Handling of major incidents - Incident management reporting.

Domain Separation is a ServiceNow feature that allows multiple logical domains (e.g., different business units or customers) to share a single instance while keeping their data, configurations, and users isolated from each other.

This is a personality interview question to assess the candidate's adaptability and problem-solving approach.

Start with identifying common services and requests that users ask for. Group items logically by service or department (IT, HR, Facilities, etc.). Design simple, user‑friendly forms with only necessary questions. Align fulfilment workflows with existing teams and processes, and use SLAs where needed.

I think Yes. but wil it work as expected I doubt.

I used a Client Script (onChange or onLoad) to refresh the Priority field after the Business Rule updates it. Alternatively, I used the 'g_scratchpad' object in a Display Business Rule to pass the updated value to the client.

This is a qualification-based interview question to understand the candidate's adaptability and client-centric approach.

An SLA in ServiceNow is defined using SLA definitions, which specify conditions, timers, and metrics for tasks like incidents or requests. It includes start and stop conditions, breach times, and escalation actions. SLAs are applied via SLA policies and can be tracked in the SLA dashboard.

Yes, the Priority will update again if the Business Rule is configured to run on 'update' and when the Urgency field changes. I ensured this by adding a condition like 'current.urgency.changes()' in the Business Rule.

- The Service Catalog serves as a centralized repository for available services. - Detailed information about service offerings is provided. - We are assisting users in understanding available services. - We are facilitating service request and fulfillment processes. - It is aligning IT services with business requirements and priorities.

Key modules include Incident Management, Problem Management, Change Management, Service Catalog, Service Request Management, Configuration Management (CMDB), and Knowledge Management.

Aligning IT services with business goals is a critical aspect of ITSM. My approach to achieving this alignment involves several key strategies: - Understanding Business Strategy and Objectives: The first step is to thoroughly understand the organization's overall business strategy, goals, priorities, and challenges. This involves engaging with business stakeholders, reviewing strategic documents, and participating in relevant business planning discussions. Understanding the "why" behind the business helps to contextualize IT's role. - Translating Business Needs into Service Requirements: Once business goals are clear, I would work with business stakeholders to translate these high-level objectives into specific requirements for IT services. This involves identifying the services that are critical to achieving business outcomes and defining the required service levels, functionalities, and performance metrics. - Defining and Maintaining a Service Catalog: A comprehensive service catalog that clearly articulates the IT services offered and their business value is essential. The catalog should be written in business language, highlighting how each service supports specific business processes and objectives. - Establishing Service Level Agreements (SLAs): SLAs should be directly linked to business requirements and expectations. They should define measurable targets for service availability, performance, and support, ensuring that IT is accountable for delivering services that meet business needs. Regular review and alignment of SLAs with evolving business priorities are crucial. - Prioritization Based on Business Value: When managing incidents, problems, changes, and service requests, prioritization should be driven by the potential impact on business operations and the contribution to strategic goals. This ensures that IT resources are focused on the activities that provide the most value to the organization. - Regular Communication and Collaboration: Maintaining open and ongoing communication with business stakeholders is vital. This includes regular meetings, progress updates, and feedback sessions to ensure that IT understands evolving business needs and that the business understands the value and capabilities of IT services. - Measuring and Reporting on Business Outcomes: IT service performance should be measured not just in technical terms but also in terms of how it contributes to business outcomes. This involves tracking KPIs that demonstrate the value IT services provide, such as increased efficiency, reduced costs, improved customer satisfaction, or faster time-to-market. - Continual Service Improvement (CSI) Focused on Business Value: The CSI process should be aligned with business priorities, focusing on identifying and implementing improvements that will have the greatest positive impact on business outcomes. This could involve optimizing existing services, introducing new services, or streamlining processes. By consistently applying these strategies, I would aim to ensure that IT is viewed as a strategic partner that actively contributes to the achievement of business goals, rather than just a cost center.

A major incident denotes a significant service disruption. It impacts many users or critical business processes, requiring swift response and resolution. Special procedures and resources are activated during such incidents, intensifying communication and coordination. The primary objective is to restore regular service operations.

ITIL manages Service Portfolios to align services with business needs. It involves categorizing services based on value, risk, and strategic importance. Service Port Olios undergoes continual evaluation and optimization.ITIL ensures transparency and accountability in Service Portfolio management. It enables me to form decisions regarding service investments and retirements.

Description of the lifecycle of a service request, including logging, categorization, prioritization, approval, fulfillment, and closure. Focus on efficiency and user satisfaction.

ServiceNow executes Business Rules in order of their defined order (a numeric field). The last Business Rule to run will overwrite the Priority value set by earlier rules. To avoid conflicts, I ensure only one rule updates the Priority and set its order appropriately.

- Document Management Systems (DMS) - Knowledge Bases - Wikis - Forums or Discussion Boards - Expert Systems - Lessons Learned Databases

A change is raised for modifications to IT infrastructure or services that may impact the environment, requiring formal approval and planning. A request (service request) is for standard, pre-defined services like access requests or hardware provisioning that are low-risk and follow a catalog-based fulfillment process. Changes are raised when there is a need to alter the environment, while requests are for predefined services.

I created a test script or used a test instance to create incidents with all nine combinations of Impact and Urgency values. I then verified that the Priority was set correctly according to the defined matrix.

The ITIL (Information Technology Infrastructure Library) framework is a globally recognized set of best practices for ITSM. It provides: - Guidelines for managing IT services - Focusing on improving service quality - Managing risks - Enhancing customer relationships - Optimizing resource use ITIL helps organizations implement standardized processes for service management, covering key areas like incident management, problem management, change management, and service design to ensure IT services align with business goals.

This is an opening question to understand the candidate's motivations and interest in consulting, helping to create a genuine and insightful discussion.

The incident management team controls the flow of incident information.

This is a qualification-based question to evaluate the candidate's knowledge of consulting frameworks and practical application.

The sequence is: 1) Display Business Rules (server-side, first to run), 2) ACLs (server-side, determine field access), 3) onLoad Client Scripts (client-side, run after form loads), 4) UI Policies (client-side, applied last to set mandatory/read-only/visible properties).

This is a closing question to allow the candidate to inquire about the role or company, indicating their engagement and interest.

To configure an SLA in ServiceNow, you need to define SLA definitions, set conditions for when the SLA starts and stops, specify time metrics like response and resolution times, and associate the SLA with a specific table such as Incident or Request. You also need to create SLA schedules and define escalation rules.

Help define test scenarios based on real‑world use cases. Support UAT by guiding business testers and clarifying expected behaviour. Verify that processes, SLAs, and reporting work as designed. Log defects clearly and work with developers to get them fixed.

I'm excited to pursue consulting for its diverse projects, the opportunity to work with talented colleagues, and problem-solving opportunities. As President of the Consulting Club, I've gained exposure to different industries and learned about the exciting projects firms work on, like mining or private equity. Working in a team environment is exciting to me, as I believe diverse perspectives lead to better results. In my past marketing internship, I worked cross-functionally with data scientists and learned a lot from them. Consulting is a good way to hone my problem-solving skills across many industries. Growing up, I played chess competitively and enjoyed the strategy behind the game.

Change Management involves planning, approving, and implementing changes. You configure change types: - Standard – pre-approved. - Normal – requires CAB approval. - Emergency – expedited process. Workflows manage approvals, risk assessments, and implementation tasks. CAB meetings can be scheduled using the CAB Workbench.

Known Error closes depending on the following conditions: - When all the Request for Change (RFC) records are closed. - The Known Error Details section must have information about a Root Cause, Solution, and Workaround before you can close the known error record. - When a record is in the Error Closure phase.