Free Practice Questions for the PeopleCert SDI Qualifications SDA Exam (2026 Updated)

The definition describes Automation.

Automation uses technology to execute a defined process, procedure, or sequence of activities with limited human intervention. In a Service Desk context, automation can be applied to routine activities such as notifications, ticket routing, monitoring responses, account workflows, standard request fulfilment, and other repetitive tasks where reliable rules or workflows can be established.

Artificial Intelligence is different. AI can provide capabilities such as natural-language understanding, pattern recognition, prediction, classification, and generated responses. AI may enable or enhance automation, but the two concepts are not synonymous. A workflow can be automated without using AI.

Self-service allows customers to obtain information or fulfil certain requirements without direct analyst assistance, while self-logging is a narrower capability that allows customers to create their own incident or service-request records. Both can use automation, but neither represents the general definition given. SDA v9 treats AI and automation as related but distinct concepts, requiring analysts to recognise their applications, benefits, and challenges within service management. Accordingly, the phrase “performed with minimal human interaction” identifies Automation, making B the correct answer.

The definition describes Conflict Management. Conflict management is the structured handling of disagreements so that they can be understood, addressed, and resolved constructively while preserving effective working or customer relationships.

Conflict can occur between an analyst and a customer, between colleagues, or between different teams. Effective conflict management therefore requires the analyst to identify the underlying disagreement, listen to each relevant perspective, control emotional reactions, communicate clearly, and work toward an acceptable outcome.

De-escalation is related but narrower. Its immediate purpose is generally to reduce the emotional intensity or tension of an interaction so productive communication can continue. Negotiation concerns reaching agreement where parties may have differing needs, positions, or priorities. Interaction management is broader still and covers the overall professional structure and control of customer interactions. SDA v9 explicitly groups emotional intelligence with conflict management and negotiation, reflecting the importance of recognising emotions and maintaining constructive communication when disagreements occur. Accordingly, the wording “identifying, addressing and resolving disagreements in a constructive manner” corresponds most directly to Conflict Management.

Both statements correctly describe the value of Diversity, Equity, Inclusion and Belonging (DEIB) within a Service Desk.

Internally, effective DEIB practices contribute to an environment where employees can participate, contribute ideas, ask questions, and develop professionally without inappropriate exclusion or discrimination. Employees who feel respected and included are better positioned to collaborate, learn, challenge constructively, and remain engaged with their work.

Externally, a diverse and culturally aware Service Desk is better equipped to understand and serve customers who have different backgrounds, abilities, communication styles, expectations, and perspectives. This does not mean delivering inconsistent service. It means maintaining common professional standards while communicating sensitively and recognising legitimate differences in customer needs.

SDA v9 incorporates modern workforce and culture expectations including wellbeing, inclusivity, customer experience, and human-centred service delivery. Consequently, DEIB contributes both to a healthier employee environment and to more effective engagement with a diverse customer community. Both statements are true.

Keeping customers informed of incident and service request status changes reduces avoidable inbound contacts because customers do not need to repeatedly contact the Service Desk simply to ask for an update.

Proactive communication is an important element of professional interaction management. Once a customer understands that progress, delays, escalations, expected actions, and resolution status will be communicated appropriately, uncertainty is reduced. This improves customer confidence while decreasing “chase calls,” duplicate emails, messages, and additional contacts that consume Service Desk capacity without advancing resolution.

Option A improperly transfers responsibility to colleagues who may not be authorised or qualified to provide support. Option B creates an inappropriate barrier to service and contradicts the Service Desk's role as an accessible support function. Option C—recording incidents—is essential operational practice, but logging alone does not directly prevent customers from contacting the desk again for progress information. SDA v9 places strong emphasis on professional customer interactions, communication, service excellence, Incident Management, Service Request Management, and managing customer needs and expectations. Therefore, proactive status communication is the most appropriate demand-reduction action.

An effective Service Catalogue reduces ambiguity by providing analysts with clear, consistent information about the services available and how those services should be supported or requested.

A well-maintained catalogue establishes what the organisation offers, relevant service descriptions, request routes, dependencies, support arrangements, and other information needed to handle customer contacts consistently. This prevents analysts from having to invent service-delivery approaches or interpret unclear service boundaries independently.

Option B undermines consistency because service delivery should follow agreed practices rather than individual analyst preference. Option C would increase ambiguity because removing service definitions leaves analysts and customers without a reliable reference point. Option D is too narrow: a Service Catalogue supports understanding of services and service offerings rather than functioning purely as an Incident Management performance report.

SDA v9 requires analysts to understand IT Service Management and the importance of practices, processes, procedures, and accurate documentation. A service catalogue provides consistent service information to the relevant audience and therefore directly reduces uncertainty.

The principal benefit represented by the options is real-time updates. A Super Channel brings collaborative support activity into an environment where analysts, customers, and relevant specialists can exchange information more dynamically. Real-time communication can make it easier to share current status, obtain specialist input, coordinate troubleshooting activity, and keep the support conversation current.

The other options describe disadvantages rather than benefits. A collaborative support channel should increase rather than reduce collaboration. It should also improve access to Subject Matter Experts where the support model allows this, rather than deliberately restricting that access. Although any collaboration platform requires effective management, increased workload is not the intended benefit of the approach.

This aligns with the modern SDA v9 view of support as multi-channel and collaborative. The curriculum includes service delivery through collaboration tools and chat and identifies Support Channels as a formal learning area covering different methods of delivering support. Real-time visibility is therefore the only answer that represents a genuine operational advantage of this type of collaborative support method.

Statement C is incorrect because resolving incidents as quickly as possible is primarily an Incident Management objective, not the defining purpose of Continual Improvement.

Continual Improvement takes a broader and longer-term perspective. Its purpose is to keep services, products, practices, and other service-management elements aligned with changing organisational and business needs through ongoing identification and implementation of improvements. These improvements can increase quality, efficiency, effectiveness, customer experience, and overall business alignment.

Incident Management, by contrast, responds to service interruption or degradation and aims to restore normal service as rapidly as appropriate while reducing adverse business impact. Information gained from incidents may subsequently become an input into improvement activity, but performing incident resolution itself does not define Continual Improvement. SDA v9 establishes IT Service Management practices and effective service operation as core analyst knowledge, requiring analysts to distinguish the objectives of different practices rather than treating them as interchangeable.

The most fundamental reason for following agreed processes and procedures is that they help ensure consistent service delivery.

Processes define coordinated activities used to achieve an outcome, while procedures provide more detailed instructions for carrying out particular activities. When analysts follow them consistently, customers receive a predictable level of service regardless of which analyst handles the interaction. This improves quality, supports compliance, reduces avoidable variation, and makes performance easier to measure and improve.

Option A is a valid secondary benefit because documented and consistently followed procedures provide evidence for auditing. Option C can also result from well-designed processes, particularly when documentation supports knowledge transfer. Option D applies specifically to activities such as Incident Management and record keeping rather than explaining the broader purpose of following processes and procedures.

SDA v9 emphasises mature, consistent processes as an essential foundation of Service Desk quality. Best-practice training gives teams a shared, consistent process set so collaboration, efficiency, and continual improvement become embedded. Therefore, consistent service delivery is the strongest overarching answer.

Voice of the Customer initiatives provide direct customer evidence about the experience being delivered, making B the correct answer.

Operational measures can show whether a service met response times, resolution targets, availability levels, or other technical objectives. However, those measures cannot independently establish how customers perceived the service or whether the interaction created unnecessary friction. VoC mechanisms capture customer perspectives and allow the organisation to identify expectations, pain points, satisfaction drivers, and opportunities for improvement.

VoC does not eliminate perception measurement; it is itself a major mechanism for understanding perception. It is not concerned solely with operational efficiency, and it does not replace appropriate customer-experience training. Instead, VoC complements performance information by introducing the customer's perspective into decisions.

SDA v9 places greater emphasis on customer experience, Voice of the Customer, outcome-based measurement, and proactive customer engagement. Modern service management must move beyond operational dashboards and understand whether services actually work for the people relying on them. Accordingly, VoC is essential because a CX programme needs evidence from customers themselves rather than relying exclusively on internal performance assumptions.

Integration with other departments is an important benefit of an effective ITSM tool because service delivery frequently involves multiple technical and business functions rather than the Service Desk operating in isolation.

Integrated tooling supports structured assignment, escalation, collaboration, information sharing, status updates, and workflow coordination across resolver groups. It can also connect Service Desk records with monitoring, asset, configuration, knowledge, collaboration, and other operational systems. Strong integration improves collaboration, routing, context, communication, and consistent service management.

Option B is unrealistic: a good ITSM platform can automate appropriate repetitive activities, but not all work or decision-making. Option C may be a feature in some environments, but a personalised knowledge base is not the strongest general benefit in this question. Option D is undesirable because good support technology should enable customers and analysts rather than unnecessarily increasing customer dependency on the Service Desk.

SDA v9 expects analysts to understand modern Service Desk tools and technologies alongside AI, automation, ITSM practices, remote support, and self-service. Therefore, A is the best answer.

Statement 2 only is false. Effective employee wellbeing initiatives are intended to support engagement, resilience, sustainable performance, and personal development rather than discourage them.

Statement 1 is a legitimate benefit. Employees who are adequately supported are better positioned to maintain concentration, handle demanding customer interactions, collaborate effectively, and sustain productive performance. Service Desk environments can involve high interaction volumes, time pressure, emotionally difficult conversations, and frequent context switching. Wellbeing therefore has a direct relationship with an analyst's ability to deliver consistent service.

Statement 2 describes the opposite of a healthy employee experience. Wellbeing should encourage people to participate, develop their capabilities, communicate concerns, and remain engaged with the team and organisation. Practices that suppress development or disengage staff would weaken both employee experience and customer-facing service.

SDA v9 explicitly includes resilience, including the capability to detect and manage positive and negative emotions and signs of stress. Therefore, statement 1 is true and statement 2 is false, making C correct.

Option A contains clear examples of AI-enabled IT service management. Natural-language chatbots use technologies such as NLP to interpret and generate human language. Automated incident classification can use machine-learning models trained on historical support records to predict categories or routing destinations. Predictive analysis can identify patterns that suggest emerging failures or service disruption risks.

Options B and C primarily describe rules-based workflows and conventional automation. These activities can be valuable, but predefined escalation logic, priority matrices, catalogue workflows, and approval chains do not necessarily require artificial intelligence. Option D describes traditional human-led Problem Management and Continual Improvement activity.

SDA v9 explicitly includes AI and automation, covering their benefits, challenges, and common applications in service management. Technologies such as NLP, speech recognition, robotic process automation, virtual agents, automated categorisation, and predictive capabilities are all relevant to modern Service Desk operations. Therefore, A is the only option where all listed examples are recognisably AI-oriented applications.

Unconscious bias can create a significant barrier to effective communication because it can influence how an analyst interprets another person's behaviour, competence, communication style, or needs without the analyst being consciously aware of that influence. Assumptions based on accent, age, role, culture, technical ability, or other characteristics can cause an analyst to listen selectively, make premature conclusions, or communicate differently with particular customers.

The other options support, or can support, effective service delivery. Remote-support tools provide a legitimate support method when used appropriately. Speaking clearly and concisely improves comprehension, while avoiding slang reduces ambiguity and makes communication more accessible across different cultures and customer groups.

The SDA v9 course places communication alongside cultural awareness and professional relationship management. Analysts should understand cultural awareness from a global perspective and develop effective verbal, non-verbal, formal, and informal communication skills. These competencies require analysts to recognise factors that interfere with objective, respectful communication. Therefore, A is the only option that represents an actual communication barrier.

Statement D is incorrect because the Service Desk contributes important operational insight to Continual Improvement, but it does not normally own organisational improvement strategy or approve funding.

Service Desk Analysts are uniquely positioned to identify recurring incidents, common customer pain points, weak knowledge, process friction, and patterns in feedback because they interact directly with users. These observations can be recorded and escalated as improvement opportunities. Management then evaluates such information alongside business objectives, costs, risks, priorities, and available resources.

Statements A, B, and C therefore reflect an appropriate division of responsibility. The Service Desk generates evidence and improvement ideas; management provides governance, prioritisation, authorisation, and strategic alignment. SDA v9 includes customer feedback, quality assurance, metrics, ITSM practices, and professional Service Desk responsibilities. Continual improvement is an organisational discipline supported by operational evidence rather than a funding or strategy function owned by frontline analysts. Therefore, assigning organisational strategy and funding approval to the Service Desk misrepresents the analyst's role.

Emotional intelligence is the strongest skill to apply when an analyst detects that a customer is becoming annoyed. Emotional intelligence involves recognising emotional signals, understanding how those emotions may influence the interaction, regulating one's own response, and adapting communication appropriately.

The SDA v9 curriculum specifically links emotional intelligence with rapport, conflict management, and negotiation. An analyst who recognises increasing frustration can change tone, acknowledge the customer's concern, demonstrate appropriate empathy, clarify what is happening, and focus the conversation on constructive next steps. This can prevent irritation from developing into open conflict.

Assertiveness can be useful for maintaining appropriate boundaries or communicating clearly, but it does not provide the broader emotional awareness required in this situation. Call management provides structure to an interaction but does not specifically address the customer's emotional state. Closed questioning is principally an information-gathering technique used to obtain specific facts. SDA v9 identifies emotional intelligence as important to conflict management, while the curriculum includes rapport, communication, conflict management, and negotiation as connected analyst competencies.