The Bottom Line (Direct Answer): answer: C, D - C (User Stories); D (Functional requirements specification (FRS)). This maps the scenario to the Salesforce-native capability that owns the requirement.
The Core Concept Explained: Document automation reduces manual review by turning files into governed records, checklist items, extracted fields, or signature events. The design must preserve traceability from upload through review.
Step-by-Step Technical Analysis: Separate document intake from record processing. Configure the document type, checklist, extraction, signature, or IDA/IFR behavior, map the captured values to the application record, and test with real sample files. Confirm exception handling for unreadable documents, missing uploads, and resubmission cycles. Produce User Stories to describe who needs a capability, what they need, and why it matters. For exam preparation, validate the answer by tracing the record lifecycle, the user persona, and the automation owner from intake through reporting.
Why the Incorrect Options Are Wrong: A does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario. B does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario.

Use Action Plans on Accounts to define due diligence steps, related tasks, and documents to collect. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Start by separating repeatable reviewer work from ad hoc instructions. Action Plans standardize repeatable work. They package tasks, dependencies, due dates, and document checklist requirements so staff do not rely on memory or one-off manual steps.
Step-by-Step Technical Analysis: Start by defining the target object that owns the operational work. Build or select the Action Plan Template, add the required tasks or Document Checklist Items, publish the template, and then automate or guide its association to the live record. Test that owners, due dates, dependencies, and applicant-facing upload prompts behave correctly. Configure an Action Plan Template targeted to Account, then generate Action Plans from that template for each organization or applicant account.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. B may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C depends on manual adoption instead of codifying the process into auditable, repeatable Salesforce configuration.

2; One to contain the percentages in each prioritization pool and the second to contain the Federal Income limits to evaluate. This maps the scenario to the Salesforce-native capability that owns the requirement.
The Core Concept Explained: Business Rules Engine externalizes decision logic from custom code.
Expression Sets orchestrate calculations and can call decision assets so policy thresholds remain maintainable by authorized business users.
Step-by-Step Technical Analysis: Identify the inputs that drive the decision, declare them as Expression Set resources, and use Decision Matrices or Decision Tables where business users must maintain rule thresholds.
Execute representative samples before activation, then confirm the output and Decision Explainer history match the expected eligibility, fee, or prioritization result. Use two decision matrices: one for the Federal Income Limits and one for the prioritization pool percentages.
Why the Incorrect Options Are Wrong: A is useful for functional validation, but it does not prove capacity under the expected production load. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

A (Create three Document Checklist Items specifying the..); B (Create a flow automation to auto-associate the..); D (Create an Action Plan Template with Target Object as..). This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
The Core Concept Explained: Action Plans standardize repeatable work. They package tasks, dependencies, due dates, and document checklist requirements so staff do not rely on memory or one-off manual steps.
Step-by-Step Technical Analysis: Start by defining the target object that owns the operational work. Build or select the Action Plan Template, add the required tasks or Document Checklist Items, publish the template, and then automate or guide its association to the live record. Test that owners, due dates, dependencies, and applicant-facing upload prompts behave correctly. Create an Action Plan Template targeted to Business License Application.
Why the Incorrect Options Are Wrong: C does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario. E does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario.

A (A homepage widget to quickly launch common processes.); D (A widget to aggregate complex data models for..). This is the lowest-customization answer that still satisfies the business, security, and lifecycle requirements.
The Core Concept Explained: OmniStudio separates guided interaction, data mapping, orchestration, and UI presentation. That separation is critical for high-volume public-sector intake because each asset can be tested and reused independently.
Step-by-Step Technical Analysis: Design the user journey first, then decide which OmniStudio asset owns each responsibility. OmniScript captures guided input, DataRaptors map Salesforce data, Integration Procedures orchestrate server-side work, and FlexCards expose summarized context. After assembly, validate data payloads, error handling, security, and performance with realistic application records. Use FlexCards for a homepage widget that launches common processes and for quick-glance aggregation of complex data models.
Why the Incorrect Options Are Wrong: B may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.