Drag and Drop Question Answer:

Question

Exhibit

Answer Area

Explanation

Drag-and-Drop Explanation: Service Incident Management Requirements

This question asks you to match functional requirement statements to their corresponding capability categories in a service management system.

Item 1 → "Manage service incident alerts and notifications"

"Ability for customers to subscribe and receive mobile SMS messages for all service incident status updates for which they are the owner."

Why it fits: This requirement is explicitly about alerting and notification delivery. The keywords - subscribe, receive, SMS messages, and status updates - all describe how stakeholders are informed of changes. Subscribing is a notification mechanism; SMS is a notification channel.

Common mistake: Confusing this with "collaborative engagements" because it involves customers. The distinction is that this is one-way push communication (system → user), not two-way collaboration.

Item 2 → "Manage service incident routing"

"Service incident ownership assignment rules will be implemented via the company's centralized business rules engine."

Why it fits: Routing in ITSM means directing incidents to the correct owner or team. Ownership assignment rules is precisely the logic that determines who gets an incident. A business rules engine automates this routing decision.

Common mistake: Confusing routing with notifications. Routing determines where an incident goes; notifications inform who about what happened.

Item 3 → "Rate, rank, and share reusable support content"

"The system must enable user-generated document publishing via an open source wiki markup language that supports upload/download for relevancy, value, and collaboration."

Why it fits: User-generated document publishing = creating and sharing content. The explicit terms relevancy and value directly map to rating and ranking. Wiki-based collaboration is a standard mechanism for maintaining a reusable knowledge base.

Common mistake: Placing this under "collaborative engagements." While wikis are collaborative tools, this requirement specifically describes content management with quality assessment (relevancy/value), not incident-specific collaboration.

Item 4 → "Provide service incident collaborative engagements"

"Ability to access links/URLs, and exchange data with partners in a secure manner over the public internet and over any device."

Why it fits: Exchanging data with partners describes bi-directional collaboration between parties. Accessing shared links/URLs is a collaboration mechanism. The emphasis on secure, cross-device, internet-accessible exchange describes a collaborative engagement platform, not just notifications.

Common mistake: Placing this under notifications or routing. The key differentiator is "exchange data with partners" - this implies two-way interaction with external stakeholders, which is the definition of collaborative engagement.

Summary Table

No community discussion yet for this question.