Read the stem as an implementation requirement. 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 proper configuration is A. Lookup field. This is the option that best matches the Salesforce responsibility being tested under Data Modeling and Management.
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 wrong answers confuse adjacent platform concepts. B (Text field) misses the mark because That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. C (Picklist field) is not enough: That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. D (Multi-select picklist field) handles a different concern; That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. This keeps the build declarative, traceable in Setup, and easier to support when the org changes later.
---