Examkin

Question

Difficulty: Very hardDocumentation and Ticketing System Workflows

An enterprise systems auditor is conducting a compliance review of closed high-priority incident tickets within an organization's IT Service Management (ITSM) platform. The audit reveals several records where core service outages were marked as resolved, yet the ticket entries lack specific hardware identification numbers, comprehensive root-cause analysis, and documented confirmation of restoration from affected department leads. Which of the following operational ticketing workflow requirements MUST be enforced to establish a compliant resolution record and maintain configuration management database (CMDB) integrity?

  1. Mandate that ticket resolution entries record specific asset tag identification, itemized work logs detailing the root cause and remedy, and verified confirmation of service restoration prior to final closure.Answer
  2. B
    Permit technicians to close infrastructure tickets immediately upon applying a temporary workaround, omitting individual hardware asset tags as long as the affected network subnet is documented.
  3. C
    Configure the ITSM platform to automatically transition all unresolved high-priority tickets to a closed status after 48 hours to preserve service level agreement (SLA) compliance metrics.
  4. D
    Require technicians to generate a new ticket for each diagnostic command executed during troubleshooting and cross-reference the new ticket numbers in the master incident record.

Answer

Mandate that ticket resolution entries record specific asset tag identification, itemized work logs detailing the root cause and remedy, and verified confirmation of service restoration prior to final closure.
Enforcing mandatory entry of unique asset tags, detailed work notes describing the root cause and final remedy, and formal resolution verification ensures compliance with enterprise documentation standards and maintains proper CMDB data integrity.

Step-by-Step Solution

1
Identify missing compliance parameters in the audited ticketing records.
Found missing hardware asset identifiers, absent root-cause work logs, and unverified service restoration.
CompTIA A+ operational procedures mandate complete documentation throughout the ticket lifecycle to ensure operational traceability and configuration management accuracy.
2
Evaluate standard documentation and ticketing workflow requirements.
A compliant incident resolution entry requires unique asset tracking (asset tag ID/serial number), itemized work notes (troubleshooting steps, root cause, and remediation), and confirmed customer/owner sign-off.
Recording asset tags updates the CMDB accurately, while detailed work logs create a searchable knowledge base and maintain audit compliance.
3
Select the correct mandatory workflow policy.
Enforcing complete asset logging, root-cause documentation, and user verification prior to ticket closure satisfies all operational compliance standards.
This policy prevents premature ticket closure and guarantees full operational transparency.

Key Concept

Incident Documentation and Ticket Resolution Lifecycle
Rate this question

Topics

Documentation and Ticketing System Workflows

More questions from this topic