What should the Architect recommend to their client regarding field creation best practices?

An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.

What should the Architect recommend to their client regarding field creation best practices?
A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
B. Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
C. Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.

View Answer

Answer: A

Explanation:

Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.

https://experienceleague.adobe.com/docs/marketo/using/home.html