Which two actions must the Marketo Engage Architect take to fulfill this request?

A company has a Contact Us form that contains a text field called "Comments" where prospects describe their needs to provide sales with context for follow-up. When this form is completed, a Marketing Qualified Lead (MQL) is generated and sent to sales. The "Comments" field is a custom text field. Leads often write lengthy descriptions that exceed 140 characters. The "Comments" field is not synced to CRM. Another field called "Notes" is synced to CRM. This is also a text field. The "Notes" field is often used by Sales and is commonly overwritten by Sales. Both Sales and Marketing agree that the "Comments" field is important and want to give the prospect space to describe their needs.

An Adobe Marketo Engage Architect needs to set up an interesting moment that is triggered upon the Contact Us form fill that contains the "Comments" value to give Sales immediate context of the inquiry.

Which two actions must the Marketo Engage Architect take to fulfill this request? (Choose

two.)

Which two actions must the Marketo Engage Architect take to fulfill this request? (Choose two.)
A . Use a token in the Interesting Moment to populate info from the "Comments" field
B. Change the "Comments" field type from text to string to capture longer comments
C. Have Marketo Support re-map the "Comments" field in Marketo to the "Notes" CRM field
D. Create the "Comments" field in CRM, sync it to Marketo, and have Marketo Support remap it
E. Switch the field mapping on the Marketo form from "Comments" to "Notes"

View Answer

Answer: A,D

Explanation:

The two actions that the Marketo Engage Architect must take to fulfill this request are to use a token in the Interesting Moment to populate info from the “Comments” field and to create the “Comments” field in CRM, sync it to Marketo, and have Marketo Support remap it. These actions will allow the Architect to set up an interesting moment that is triggered upon the Contact Us form fill that contains the “Comments” value to give Sales immediate context of the inquiry. Using a token in the Interesting Moment will enable the Architect to dynamically insert the value of the “Comments” field into the interesting moment description. Creating the “Comments” field in CRM, syncing it to Marketo, and having Marketo Support remap it will enable the Architect to preserve the value of the “Comments” field in both systems and avoid overwriting the “Notes” field that is used by Sales.

References:

https://docs.marketo.com/display/public/DOCS/Interesting+Moments

https://docs.marketo.com/display/public/DOCS/Use+Tokens+in+Interesting+Moments

https://docs.marketo.com/display/public/DOCS/Field+Mapping