The key is to separate behavior from appearance. The best answer is A. Schema Builder. The Platform App Builder role is to choose the standard Salesforce capability that owns the behavior: data structure, access, automation, user experience, reporting, or deployment.
The selected answer is stronger because it meets both the functional requirement and the maintainability requirement. In a Salesforce implementation, a solution that only works for one user, one page, or one data sample is not good enough. The correct feature has to behave consistently across the intended profiles, record types, apps, and devices that are part of the design.
None of the other options gives the same administrative control. B (Lightning Object Creator) is only a partial match because A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. C (Manage Field Permissions) misses the mark because Permission controls are essential for access, but they do not perform calculations or process automation. D (Developer Console) is not enough: it would require extra assumptions that the scenario does not support. This is the stronger design because it respects security, data quality, user experience, and lifecycle management at the same time.
For general platform design, the strongest answer is the native feature that can be enforced, audited, and maintained through Salesforce metadata.
---