The OmniStudio Developer for Cumulus Cloud Corp receives a requirement to create a new claims...

The first responsible action is to validate the Data Mapper query design before committing to the implementation. Prefilling 15 user-based fields can be efficient, but only if the query is selective, returns only needed fields, and uses appropriate filters. Salesforce’s Data Mapper best practices warn developers to avoid server performance problems and to ensure filtering and sorting operations use indexed fields where possible. A Data Mapper Load is wrong because the requirement is to read current user data, not write data back to the User object. Converting the process to a FlexCard does not solve the prefill query risk. A Formula element cannot query Salesforce records. Therefore, option A is the correct risk-reduction step before development proceeds.