QuestionQ45

VerifiedSection 2A: Marketo Data Architecture Design

Refer to the case study.

Unicorn Fintech hits its Salesforce API limit every day, creating a backlog of issues across systems and significantly disrupting the workflow of employees who depend on them. It currently takes hours to days for accurate data to flow into Adobe Marketo Engage and Salesforce, even though newly created leads need to sync as quickly as possible. After investigation, the IT team believes Marketo Engage is the source of the excessive API usage.

Before requesting an increase to the API limit, which two tasks should an Architect perform to resolve this issue?

Choose two
Explanation

When multiple Smart Campaigns each contain their own 'Sync to SFDC' workflow step, every one of those campaigns generates separate, often redundant calls to the Salesforce API, quickly exhausting the daily limit. The recommended remediation is to centralize the sync logic: keep a single dedicated Smart Campaign responsible for syncing to Salesforce, remove the 'Sync to SFDC' steps from all other Smart Campaigns, and instead have those other campaigns use 'Request Campaign' to trigger the dedicated sync campaign on a scheduled (e.g., daily) basis. This consolidates and batches the API calls instead of firing them repeatedly and individually, reducing overall API consumption without needing to raise the platform's API limit.

Community Discussion

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