What should be included in a request queue configuration? (Select two.)

Question

Options

• AQueue topics
• BPredefined project timelines
• CCustom form associations
• DApproval workflows

• A
  86% (48)
• B
  4% (2)
• D
  11% (6)

Explanation

A request queue configuration requires queue topics (A) to categorize and organize incoming requests into logical groupings, and custom form associations (C) to collect the specific information needed for each request type. These two elements define both the structure of the queue and what data is gathered when a request is submitted.

Predefined project timelines (B) are incorrect because timelines belong to project planning, not queue setup - a queue captures demand before a project even begins. Approval workflows (D) are incorrect because approvals are a separate process layer that may be triggered after a request is received, not a core component of the queue's configuration itself.

Memory tip: Think of a request queue like a customer service desk - you need topics (which department handles this?) and a custom form (what info do we need from you?). Timelines and approvals come later, once the request is already in the system.

No community discussion yet for this question.