A clean build puts the rule where Salesforce evaluates it. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars. Choose A. Path. This is the option that best matches the Salesforce responsibility being tested under User Interface.
A practical administrator would confirm the object context, the user action, and whether the result must be stored, calculated, displayed, automated, approved, or deployed. Here the selected answer is the one that acts at the correct point in that chain. It keeps the configuration declarative and avoids inventing a process around a problem that Salesforce already has a native feature to solve.
The remaining answers do not control the same Salesforce behavior. B (Chatter Publisher) is not enough: it would require extra assumptions that the scenario does not support. C (Journey Builder) handles a different concern; it handles only part of the requirement and leaves the controlling Salesforce behavior unresolved. D (Flow) is less defensible because Flow is broad, but it is not correct unless the requirement is specifically about guided or automated logic. The result is a cleaner app design because the behavior is handled by the feature Salesforce built for that purpose.
For Lightning pages, activation and assignment determine who sees the page. Component visibility then controls whether a specific component appears for a given condition.
---