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.)
Answer(s): A,D
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.
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
A company has a meeting with a third party that wants to begin submitting leads captured through various channels. These leads are aware that the third party will share their information with the company and have provided consent through their engagement. The third party will send the leads through a REST API.Which steps should the Adobe Marketo Engage Architect take to make sure that the REST API is set up correctly?
Answer(s): B
The steps that the Adobe Marketo Engage Architect should take to make sure that the REST API is set up correctly are to create API User Role, create a new API User, create new Launchpoint Service, and run a Call test with Identity and Endpoint. These steps will allow the Architect to configure and test the REST API integration with Marketo Engage. Creating API User Role will enable the Architect to define the permissions and access level for the API User. Creating a new API User will enable the Architect to generate a unique Client ID and Client Secret for authentication. Creating new Launchpoint Service will enable the Architect to register and manage the third-party service in Marketo Engage. Running a Call test with Identity and Endpoint will enable the Architect to verify that the API calls are working properly and that leads can be submitted through various channels.
https://developers.marketo.com/rest-api/https://docs.marketo.com/display/public/DOCS/Create+an+API+Only+User+Role https://docs.marketo.com/display/public/DOCS/Create+a+Custom+Service https://docs.marketo.com/display/public/DOCS/Webhooks
When reviewing completion of a REST API Webhook, two URLs can be used to perform an initial validation and make sure leads will pass correctly.Which two combinations of URL and associated parameters should be used to validate the REST API? (Choose two.)
Answer(s): C,E
The two combinations of URL and associated parameters that should be used to validate the REST API are Endpoint URL with Access Token and Your Email Address and Identity URL with Client ID and Client Secret. These combinations will allow the user to perform an initial validation and make sure leads will pass correctly through the REST API Webhook. The Endpoint URL with Access Token and Your Email Address will allow the user to test the functionality of the endpoint service and verify that the leads can be submitted successfully. The Identity URL with Client ID and Client Secret will allow the user to obtain an access token for authentication and authorization purposes.
https://developers.marketo.com/rest-api/https://docs.marketo.com/display/public/DOCS/Webhooks
An Adobe Marketo Engage Consultant is reviewing all programs in an instance. Each campaign in each program contains at least three flow steps:- If Acquisition Program is Empty, change Acquisition Program to the current program's name - Change the status in the program (based on the action) - Write an Interesting MomentThese flow steps happen in almost every campaign.How can the Consultant edit the programs for scalability and efficiency?
The Consultant can edit the programs for scalability and efficiency by creating a global program and coordinating campaigns to update the acquisition program to the latest program touched. This will allow the Consultant to streamline and optimize the process of updating the acquisition program for each lead, instead of having multiple flow steps in each campaign. The global program can use triggers and filters to capture leads from different sources and channels, and use tokens to dynamically update the acquisition program based on the latest program touched. This will also reduce the number of campaigns in the queue and improve the campaign performance.
https://docs.marketo.com/display/public/DOCS/Acquisition+Program https://docs.marketo.com/display/public/DOCS/Global+Programs
An Adobe Marketo Engage Architect notices that the smart campaigns run slowly. The Campaign Queue in Marketing Activities is full of backlog campaigns. The alerts fire with a delay. All alert smart campaigns are triggered based on the first step of Change Data Value. All Batch campaigns use the Advanced Wait Properties at the first step to run the campaign every Monday at 8:00 PM PT. Which steps should the Architect perform to scale the campaign execution?
The steps that the Architect should perform to scale the campaign execution are to move the Send Alert step to first for campaigns sending alerts, and to use batch campaign scheduler instead of Advanced Wait Properties for batch campaigns. These steps will help the Architect to improve the speed and efficiency of the smart campaigns, as well as reduce the backlog in the campaign queue. Moving the Send Alert step to first will ensure that alerts are sent immediately without waiting for other flow steps or triggers, which can cause delays or errors. Using batch campaign scheduler instead of Advanced Wait Properties will allow the Architect to schedule batch campaigns at a specific date and time, instead of using a wait step that can clog up the queue or run at suboptimal times.
https://docs.marketo.com/display/public/DOCS/Smart+Campaigns+Overview https://docs.marketo.com/display/public/DOCS/Schedule+a+Batch+Campaign https://docs.marketo.com/display/public/DOCS/Wait+Flow+Action
Post your Comments and Discuss Adobe AD0-E556 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AD0-E556 content, but please register or login to continue.