A (Business Profile); B (Regulatory Authority); C (Regulatory Authorization Type). 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. Set up Business Profile, Regulatory Authority, and Regulatory Authorization Type. 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: D uses the wrong packaged object or module boundary for this scenario. E uses the wrong packaged object or module boundary for this scenario.