The answer comes from Salesforce's separation of responsibilities. Salesforce import tools differ by data volume, matching logic, and operation. Data Import Wizard is guided and duplicate-aware for supported objects; Data Loader is stronger for larger updates, upserts, and clearing values. Use B. Data Import Wizard.
A clean Platform App Builder answer should satisfy the complete scenario, not merely one phrase in it. This item requires the app builder to choose the configuration that produces the requested behavior in normal Salesforce use. The selected answer fits that requirement because it works with the platform model instead of fighting it.
The alternatives are plausible only if the requirement is read too narrowly. A (Data Loader.io) should be rejected because Data Loader is an administrative data tool; it does not replace metadata configuration or user- interface design. C (Data Loader) does not fit cleanly; Data Loader is an administrative data tool; it does not replace metadata configuration or user-interface design. D (Manual entry) is only a partial match because it does not provide the same direct administrative control as the selected option. A complete implementation should also check page assignment, field access, record ownership, and mobile behavior where those factors apply.
For imports, the builder should choose the tool based on record count, supported object, operation type, duplicate handling, and the presence of an external identifier.
---