Scope, Schedule and Cost. This selection keeps the implementation declarative and within the intended Public Sector operating model.
The Core Concept Explained: The tested principle is to use the smallest native Salesforce capability that fully satisfies the requirement while preserving security, reuse, reporting, and upgradeability.
Step-by-Step Technical Analysis: Separate the business outcome from the implementation mechanism. Choose the packaged or declarative Salesforce capability that owns the lifecycle, configure it with the required permissions and data relationships, then validate the behavior with realistic records before user acceptance testing. Identify Scope, Schedule, and Cost as the three main constraints. 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. C does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario.
