A (Set Up Data Extraction); B (Enable Intelligent Form Reader); D (Map Form Types to Objects). This selection keeps the implementation declarative and within the intended Public Sector operating model.
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. Enable Intelligent Form Reader, then set up Data Extraction so OCR and field-recognition services can read the uploaded document.
Why the Incorrect Options Are Wrong: C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. E may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

Salesforce Shield. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Public-sector implementations must treat confidentiality, auditability, and legal retention as architecture requirements. The control must be applied at the platform layer that actually prevents unauthorized access or processing.
Step-by-Step Technical Analysis: Classify the protected data first, then apply the least-privilege control at the correct layer: object access, sharing, field security, encryption, event monitoring, or audit retention. Validate the design with a real external or internal user profile and confirm that reporting and integrations do not bypass the intended restriction. Recommend Salesforce Shield because it brings together Shield Platform Encryption, Event Monitoring, and Field Audit Trail.
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. D does not align with the Lightning-based managed package and Experience Cloud assumptions.

The Bottom Line (Direct Answer): answer: A, C, D - A (Implement CDN and waiting rooms); C (Identify expensive The Core Concept Explained: Experience Cloud design is driven by persona, authentication, scale, and sharing. The wrong template or license can create unnecessary cost, weak security, or excessive customization.
Step-by-Step Technical Analysis: Begin with the external persona, authentication requirement, and transaction volume. Select the Experience Cloud license or template that matches that access pattern, then configure sharing sets, external OWD, site visibility, and page access. Finish by testing the experience as anonymous, authenticated, and internal users. Use CDN and waiting rooms to protect the digital front door, identify expensive synchronous processes and move them to asynchronous processing, and run load testing against the expected volume.
Why the Incorrect Options Are Wrong: B limits access but does not solve surge capacity, performance, or queuing requirements for a public intake event. E is useful for functional validation, but it does not prove capacity under the expected production load.

Public Sector Case Analytics App, leveraging CRM Analytics' case duration formula. This maps the scenario to the Salesforce-native capability that owns the requirement.
The Core Concept Explained: Public-sector analytics should reuse packaged datasets and dashboards where possible. Prebuilt assets reduce implementation effort and give agencies consistent metrics across licensing, inspection, case, emergency, and grant operations.
Step-by-Step Technical Analysis: Confirm the operational records and datasets needed for the metric. Use the prebuilt Public Sector or CRM Analytics app when it already models the domain, assign the required admin/user permissions, and validate that prerequisite records exist. Then review dashboards against real licensing, inspection, case, or emergency-response data. Use the Public Sector Case Analytics app and leverage the CRM Analytics case duration formula.
Why the Incorrect Options Are Wrong: B adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. C adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. D adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement.

The Person Account model uses the standard Account object to hold the details about a person. This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
The Core Concept Explained: Inspection Management relies on a chain of reusable metadata and transaction records. Assessment definitions, visits, inspection results, and violations each serve a different purpose in the compliance lifecycle.
Step-by-Step Technical Analysis: Model the inspection lifecycle from the originating application to the Visit, assessment indicators, results, signatures, and any generated violations. Configure the reusable inspection metadata before inspectors begin work, then test a pass, fail, and issue scenario to confirm downstream records and regulatory references are created correctly. Use Person Accounts because the person record is held through the standard Account object while Salesforce maintains the supporting contact representation behind the scenes.
Why the Incorrect Options Are Wrong: A confuses sales-cloud opportunity data with the constituent/account model used by public-sector records. C is factually inconsistent with Salesforce setup behavior because record types can be used with Person Accounts. D points to a disablement approach that either is not supported for the tested feature or would remove a capability the scenario depends on.