AD0-E556: Adobe Certified Master - Adobe Marketo Engage ArchitectDemo

By Adobe · Question Mode

QuestionQ20

Section 2A: Marketo Data Architecture Design

A company is meeting with a third party that wants to start submitting leads collected through various channels. These leads are aware that the third party will share their information with the company and have given consent through their engagement with the third party. The third party will transmit these leads via a REST API.

What steps should the Adobe Marketo Engage Architect take to ensure the REST API is configured correctly?

  • A Create API User Role, Use an existing API User, Create new Launchpoint Service, Run a Call test with Identity and End point
  • B Create API User Role, Create a new API User, Create new Launchpoint Service, Run a Call test with Identity and Endpoint
  • C Create API User Role, Create a new API User, Create new Launchpoint Service, Run a Call test with Token and Endpoint
  • D Create API User Role, Use an existing API User, Create new Launchpoint Service, Run a Call test with Token and Identity
Explanation

Marketo's documented process for enabling a third-party REST API integration requires creating an API-only Role, creating a new API-only User assigned to that role specifically for the integration, creating a new LaunchPoint (custom) Service tied to that user to generate the Client ID and Client Secret, and then validating the configuration by making a test call against both the Identity URL (to retrieve an access token) and the REST API Endpoint URL (to confirm data can be exchanged). This ensures the credentials are unique to the new integration and that connectivity is verified end-to-end before the third party begins sending leads.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!