PeopleCert Updated SDA Exam Questions and Answers by gideon

Automation is best described as using technology to carry out repetitive, predictable, or routine activities with minimal human intervention, making C correct.

Automation does not require the elimination of humans. Instead, it is normally applied where defined activities can be executed reliably by technology, allowing analysts to devote more attention to complex, judgement-intensive, or customer-sensitive work. Examples in Service Desk environments include ticket routing, notifications, standard request fulfilment, monitoring responses, password-reset workflows, and repetitive administrative tasks.

Option A incorrectly equates automation with complete workforce replacement. Option B describes technology-assisted manual work rather than genuine automation because a person must still execute every step. Option D is also incorrect because transferring every decision to technology regardless of risk or complexity would eliminate necessary governance and human oversight.

SDA v9 explicitly includes AI and automation, requiring candidates to understand common examples, benefits, and challenges. These technologies are intended to reduce avoidable workload, increase efficiency, and improve consistency rather than indiscriminately eliminate human involvement. Therefore, C is the professionally correct definition.

An effective Service Desk Analyst contributes actively to team performance rather than working as an isolated technical resource. Statements 1, 2, and 3 correctly describe this responsibility.

First, analysts should collaborate openly and effectively. Service Desk work depends on information sharing, coordinated resolution, escalation, and cooperation with colleagues and specialist teams. Second, analysts should help create a safe and supportive workplace where colleagues can ask questions, raise concerns, learn from errors, and contribute ideas without unnecessary fear. Third, analysts can support colleagues during onboarding through buddying and skill development, accelerating integration into the team and transferring practical knowledge.

Statement 4, “retaining knowledge and information,” is inconsistent with effective team behaviour if it means keeping useful information to oneself. Modern service management depends on knowledge sharing, documentation, and collaborative learning. Useful knowledge should be captured and made available to colleagues where appropriate. The SDA v9 specification develops collaboration with colleagues, rapport, communication skills, and professional Service Desk behaviour. Therefore, 1, 2, and 3 form the correct combination.

A Service Desk Analyst may encounter customers displaying impatience, embarrassment, pre-judgement, or anger, so the intended answer is all of them.

Customers normally contact the Service Desk because something is preventing or disrupting an activity. That context can create impatience when progress appears slow, embarrassment when users believe they may have caused the issue, pre-judgement when previous experiences influence expectations, or anger when disruption is significant. The analyst's responsibility is not to judge these reactions but to recognise the customer's condition and manage the interaction professionally.

This requires emotional intelligence, active listening, appropriate empathy, confident communication, and controlled interaction management. The analyst should identify the emotional signals, avoid becoming defensive, acknowledge legitimate concerns, clarify the situation, and guide the interaction toward useful actions or next steps. SDA v9 learning includes emotional intelligence, rapport, conflict management, communication, resilience, and the management of positive and negative emotions. Accordingly, all four conditions may need to be managed during Service Desk interactions.

A problem is a cause, or potential cause, of one or more incidents. Therefore, C is correct.

Incident Management and Problem Management have different purposes. An incident is an unplanned interruption to a service or reduction in service quality that requires restoration. Problem Management addresses underlying causes and potential causes of incidents so that their likelihood or impact can be reduced.

A known error is a problem that has been analysed sufficiently for relevant information—such as a cause or workaround—to be documented and managed. It is therefore not synonymous with every problem. An asset is any resource or capability that contributes value to products or services and is unrelated to this definition.

SDA v9 includes Problem Management as one of the core ITSM practices an analyst must understand. The distinction is important because analysts should not confuse restoration of an individual incident with investigation of its underlying cause. Problem Management reduces the likelihood and impact of incidents by identifying actual and potential causes and managing workarounds and known errors.