What Is ITIL?
What Is ITIL?
What Is ITIL?
2. What is ITSM?
ITSM or Information Technology Service Management is the act of taking the support of
people, processes, and technology to deliver IT services and support internal
customers.
Service strategy: It provides a plan/ strategy for the overall life cycle of the
project. In this stage, it ensures the strategy to be in sync with the business’
objectives to ensure that the customers can derive value from the customers.
Service Design: This stage involves the design of services and additional
components that need to be introduced into the live environment.
The next phase is the Service Transition. In this phase, IT services are built
and deployed. It also ensures that changes to the service and service
management process happen in a coordinated manner.
Service Operations focus on making sure that the expectations of the end-user
are met, making sure that costs and potential issues are managed.
People: These represent the individuals who are associated with the processes and
procedures.
Products: These focus on the service itself, along with its underlying technology.
Partners: The partners who work with the IT organization to ensure that the service
works properly.
Service Value Chain: It is a model used for creating, delivering, and continually
improving services. It involves six activities, all of which can be combined in
different ways to create multiple value streams.
We design the guiding principles to guide the organization's decisions and actions to
make sure they can make the most of ITIL. These principles work regardless of the
scenario, objective, goal, strategy, type of work, management, or structure. The seven
guiding principles are:
Focus on value
7. Explain the objective of ‘Design and Transition’ on the Service Value Chain.
The service value chain consists of 6 activities that enable the creation of value. The
design and transition component will help organizations ensure the products and
services are up to the quality, cost, and other requirement standards set by the
stakeholders.
Progress: This layer deals with the progress of the current service operations.
Effectiveness: This layer makes sure that it maintains the effectiveness of the
service.
Efficiency: This is the layer that focuses on maintaining the workflow and
performing service maintenance.
ITIL Certification in
ITIL Certification in Pune ITIL Certification in Atlanta
Brisbane
11. Explain how Availability, Agreed Service Time, and Downtime are related.
Availability: It is the ability of an IT service or any of the other configuration
items to perform its expected functions when required.
Agreed Service Time: It is the expected time during which the service is to be
operational.
Downtime: It is the time during the agreed service time that your service isn’t
operational.
Corporate SLAs cover the issues relevant to the organization. These are the
same across the organization.
Service SLAs deal with issues relevant to a specific service (in relation to the
customer) that can be covered. Applies to all customers that contract the
same service.
14. What are the Service Portfolio, Service Catalog, and Service Pipeline?
The service portfolio is a repository of all the information related to the IT
services in the organization.
The service pipeline includes references to services that are still not live yet.
These plans could be proposed or under development.
Shared Services: These are autonomous special units that act as internal
service providers.
The service desk acts as a point of contact between the service provider and the users.
It acts as a communication point where users can report operational issues, queries,
and other requests. For the service desk to be successful, the service desk needs to
have great customer service skills like empathy and emotional intelligence.
An IT asset represents any component that’s financially valuable that eases the delivery
of an IT product or service.
Problem identification
Problem control
Error control
27. Explain how incidents, problems, and known errors are different from one
another.
Incidents: These are parts of the process that were not expected during the
planning phase and not were supposed to be part of the standard operation.
Known errors: A known error is a problem that’s already been diagnosed, and a
workaround or a permanent solution has already been found.
A workaround is a temporary solution that resolves issues temporarily. In this case, the
issue’s reason has not been identified. The time frame for a workaround isn’t usually
defined and could range from a few seconds to many years.
Fast recovery: This recovery takes place within 24 hours (hot standby).
Intermediate recovery: The recovery process is completed within 3 days
(warm standby).
Moving forward in this article on ITIL Interview Questions, we’ll cover topics like
emergency changes, change enablement, PDCA cycle, PIR, and so on.
Emergency changes are changes that need to be incorporated as soon as possible. The
changes, in this case, aren’t tested, and it makes certain decisions balancing risks and
rewards
33. What’s the difference between a Change Request and a Service Request?
A known error refers to a problem that has been analyzed and has not been resolved.
Businesses use the PDCA cycle for the control and continuous improvement of
products and processes. The parts of the cycle are:
Plan: In this stage, the improvements are planned. Here the measure of
success is measured. After performing gap analysis, it makes a plan to reduce
the gap through improvements
Check: This stage involves monitoring, measuring, and reviewing. The results
obtained here are compared to the factors that make up success, discussed in
the planning stage
The post-implementation review or PIL is an evaluation and analysis of the final working
solution. After a change request is made, the review takes place and checks if the
change and its implementation were successful. PIL helps answer questions like:
The RACI Model is a tool that helps identify different roles and responsibilities with ease
during a project. It stands for:
Responsible: The people who perform the work to complete the task.
Depending on their tasks, responsibilities are assigned to them.
Accountable: The person or people responsible for the thorough and correct
completion of the task.
Consulted: The person or people who provide information about the task and
are consulted as it progresses. This usually involves back-and-forth
communication.
Informed: These people are kept informed regarding how the task is
progressing. Communication, in this case, is usually one-way.
Incident management is part of the IT Service Management that ensures normal service
is restored as soon as possible. The objectives of incident management are:
Reporting and resolving the incident with the IT service as soon as it happens.
Ensuring that approved and regulated methods are applied to all processes.
This practice focuses on the service's agreed quality by managing service requests in
an effective and user-friendly manner. These depend on processes and procedures to
maximize the efficiency of the practice with the help of tracking and automation tools
This form of management makes sure that the organization’s suppliers and their
performance are properly supported to ensure continuous quality products and
services. The objectives of supplier management are:
KEDB (Known Error Database): Known Errors are managed by the Problem
Management process, with the details of each known error recorded in a
Known Error Record, which is in turn stored in the Known Error Database
(KEDB).
Information Security Management Systems help align business and IT security while
also ensuring information is handled effectively across services and service
management activities. These ensure that:
Information is available and can be used when required. It also plays a role in
ensuring that these systems can resist, recover, or prevent failures.
Access to information is only for individuals who have the right to know it.
1. What is ITIL?
It helps businesses to achieve their mission with the best way to plan, manage, and
deliver.
Subscribe to explore the latest tech updates, career transformation tips, and
much more.
Subscribe
Now
The main objectives of the incident management process are listed below:
Assure that regulated methods and procedures are used for the prompt and
efficient response, reporting of incidents, documentation, analysis, and ongoing
management
Progress visibility and communication of incidents to IT support staff and
business
Improve the business perception of IT by resolving and reporting incidents when
they occur
Align Incident Management activities and priorities accordingly
Manage user satisfaction with the quality of IT services
7. How an Incident Management System Works?
Records incidents
Lists them depending on their impact and urgency
Authorizes the incident to the relevant responding personnel
Resolution and recovery
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.
Step1: Incident identification
Step2: Incident logging
Step4: Incident prioritization
Step5: Incident response
Step6: Initial diagnosis
Step7: Incident escalation
Step9: Incident closure
9. What is an SLA?
A Known Error is a problem that has a recorded root cause and a workaround.
Status
Error description
Root cause
Workaround
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.
The PDSA cycle is a 4-step management method used for control and continuous
improvement of a product/process in a business. It is also known as the Deming cycle/
circle/wheel.
The major difference between reactive and proactive problem management is reactive
problem management identifies and eliminates the root cause of known incidents,
whereas proactive problem management prevents incidents by finding potential
problems and errors in the IT infrastructure.
The primary objective of change management is to minimize the risk and disruption in
business operations by establishing standardized procedures in managing change
requests in an agile and effective manner.
24. What is the main objective of Capacity Management and what are
its subprocesses?
The main objective of Capacity Management is to ensure the IT services and resources
are right-sized to meet the service level targets for current and future business
requirements in a cost-effective and timely manner.
ISO/IEC 27002 is a code of best practices that deliver guidelines for organizational
information security standards and information security management for
implementing information security controls.
The importance of Information security policy is protecting the information and data of
the organization from security risks.
Service Requests are formal requests from a user for some type of service or
information.
The incident is something that an unplanned interruption or reduction to an IT
service.
34. What are the Service portfolio, Service Catalog, and service
pipeline?
It is a time period in the development process after which the rules for creating
changes to the source code become more severe.
Change Request.
39. Name two Service Management processes that use a risk analysis
and management methodology?
Manual workaround
Reciprocal arrangements
Gradual recovery
Intermediate recovery
Fast recovery
Immediate recovery
Change Manager
46. what are the 4 P’s that facilitate effective Service Management in
ITIL?
47. Any item including service component or asset which is under the
control of Configuration Management is known as what?
Configuration Item.
48. Who is responsible to maintain and protect the Known Error
Database?