The requirement is for a repeatable document requirement , not one-off checklist records created manually on each application. The correct architecture therefore uses an Action Plan Template , document checklist items contained in that template, and automation to associate the template with every applicable Business License Application.

Salesforce documents that Document Checklist Items can be added to Action Plan Templates to standardize document-processing workflows. When an Action Plan is created from the template, the defined checklist items are automatically carried into that plan. Salesforce further requires the completed template to be published before operational use.

Option B establishes the reusable application-oriented template. Option E defines the three required document types within that template and publishes it. Option D ensures every newly created Business License Application receives the standardized Action Plan automatically, removing reliance on staff remembering to add the checklist manually.

Option C would create the checklist directly against an individual Business License Application. Salesforce supports that capability, but it doesn't satisfy the requirement to impose the same three-document package consistently on every application. Option A uses Tasks rather than Document Checklist Items, so it doesn't provide the dedicated applicant document-upload and tracking semantics.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Document Automation; Document Checklist Items; Action Plans; Action Plan Templates; Business License Applications.

================