Read the stem as an implementation requirement. The proper configuration is D. Record-triggered flow. The requirement in the stem is: Universal Containers asked the app builder to ensure when an Account type changes to ' Past-Customer ' the contacts directly related to That account get an updated status of ' Re-Market '
. Which automation should the app. The selected option addresses that requirement at the point where Salesforce actually evaluates the behavior.
The underlying concept is Lightning page configuration. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars. That is why this answer is more defensible than a workaround. It can be reviewed in Setup, included in the correct deployment path, and tested by impersonating or logging in as a representative user where appropriate.
The wrong answers confuse adjacent platform concepts. A (Validation rule) is only a partial match because A validation rule blocks saves; it does not create records, route approvals, display components, or grant access.
B (Lightning component) misses the mark because A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. C (Screen flow) is not enough: Flow is broad, but it is not correct unless the requirement is specifically about guided or automated logic. This keeps the build declarative, traceable in Setup, and easier to support when the org changes later.
---