An analyst should avoid asking customers for information they have already provided. Repetition of previously supplied information can give the impression that the analyst has not listened, has not reviewed the interaction record, or is not taking ownership of the issue. It creates unnecessary effort for the customer and can contribute directly to frustration.

The remaining activities can all be appropriate when performed professionally. Briefly placing a customer on hold while consulting a colleague may be necessary to obtain accurate information or progress resolution, provided the customer understands what is happening. Remote-support methods can improve diagnostic efficiency and allow an analyst to resolve an issue directly. Paraphrasing is particularly valuable because it enables the analyst to verify that the customer's explanation has been understood correctly.

SDA v9 explicitly includes the benefits of active listening, different communication methods, rapport, problem-solving, and methods of delivering support such as remote support. These competencies reinforce the principle that analysts should make effective use of information already obtained rather than make the customer repeat it unnecessarily.

Service Desk metrics analysis provides the strongest operational evidence for managing staffing levels. Metrics can reveal interaction volumes, arrival patterns, peak periods, average handling times, backlog levels, abandonment, resolution performance, channel demand, and workload distribution. Analysing these patterns allows management to determine when additional analysts are required and when staffing can be adjusted to match expected demand.

An SLA target defines an agreed performance expectation but does not, by itself, provide sufficient information about actual workload or resource utilisation. Customer-satisfaction statistics measure customer perception and are valuable for quality assurance, but they are not a direct workforce-planning mechanism. An ongoing survey can provide useful qualitative information but again lacks the operational demand data needed for staffing decisions.

The SDA v9 qualification identifies quality assurance, customer satisfaction surveys, and the benefits of metrics as important areas of knowledge. Metrics provide management with measurable workload evidence that can be converted into practical staffing and scheduling decisions.

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.