A project requires the automatic addition of a custom form whenever a specific template is used. What is the best approach?

Question

Options

• AAssign the custom form directly to the queue topic
• BAdd the custom form to the project template settings
• CEnable dependency mapping on the form
• DCreate a calculated field to trigger form addition

• A
  12% (6)
• B
  80% (40)
• C
  2% (1)
• D
  6% (3)

Explanation

Adding the custom form to the project template settings (Option B) is correct because templates serve as the blueprint for new projects - any configuration embedded there, including custom forms, is automatically inherited every time that template is applied, ensuring consistent form inclusion without manual intervention.

Why the distractors are wrong:

• A - Queue topics control how work items are routed or assigned, not what forms appear; linking a form to a queue topic won't tie it to a specific template's lifecycle.
• C - Dependency mapping defines relationships between tasks or items; it has no mechanism to trigger form additions.
• D - Calculated fields derive or display values dynamically; they cannot instantiate or attach additional forms to a project.

Memory tip: Think "Template = Blueprint." Whatever you bake into the template is automatically stamped onto every project built from it - so for anything that should appear automatically and consistently, the template settings are always your first stop.

No community discussion yet for this question.