Examkin

Question

Difficulty: HardDocumentation and Ticketing System Workflows

A support technician responds to an escalated helpdesk ticket where a remote user cannot access shared network drives following a recent department VLAN migration. The technician runs `ipconfig /all` and `nslookup` on the client machine, determining that the workstation is receiving an Automatic Private IP Addressing (APIPA) address because the DHCP relay agent on the new VLAN router interface was omitted. Reconfiguring the router requires specialized privileges held only by the Network Infrastructure Team. Which of the following is the most appropriate action for the technician to take NEXT within the ticketing system workflow?

  1. Record all diagnostic steps, command output, and root-cause analysis in the ticket work log, escalate the ticket to the Network Infrastructure Team queue, and update the ticket status accordingly.Answer
  2. B
    Mark the ticket as resolved with a note explaining that the issue stems from an infrastructure error, and instruct the end user to submit a separate ticket directly to the Network Infrastructure Team.
  3. C
    Immediately reassign the ticket to the Network Infrastructure Lead without attaching diagnostic notes so that senior engineers can address the network outage as quickly as possible.
  4. D
    Change the ticket status to Pending User Info and request that the user verify whether co-workers on the same VLAN are experiencing identical IP assignment failures.

Answer

The technician should thoroughly record all diagnostic results and command outputs in the ticket work log, update the status, and escalate the ticket to the Network Infrastructure Team queue.
The correct action is to document all completed diagnostic commands, specific error findings, and isolated root causes in the ticketing system's internal work log before reassigning the ticket to the appropriate escalation queue (Network Infrastructure). In IT service management and CompTIA operational standards, thorough documentation at the point of handoff ensures seamless escalation, preserves historical data, and prevents secondary technicians from repeating work.

Step-by-Step Solution

1
Analyze the technical scenario and isolation results.
The technician confirmed through command outputs (`ipconfig /all`) that the host has an APIPA address due to a missing DHCP relay on the router.
Establishing root cause determines which specialized team owns the remediation step.
2
Identify the required ticketing system escalation workflow step.
Standard operational procedures mandate documenting all troubleshooting steps taken and empirical data collected into the internal ticket work log prior to reassignment.
Complete documentation maintains audit trails, prevents redundant diagnostic work by escalation teams, and adheres to IT service management best practices.
3
Reassign and update ticket state.
Escalate to the Network Infrastructure queue while updating the ticket lifecycle status to reflect active escalation.
Ensures ownership is formally transferred without closing the ticket or placing inappropriate responsibility back onto the user.

Key Concept

Incident Lifecycle Management & Escalation Documentation Workflows
Rate this question

Topics

Documentation and Ticketing System Workflows

More questions from this topic