nerdexam
Salesforce

PDII · Question #11

Recently a Salesforce org's integration failed because it exceeded the number of allowed API calls in a 24-hour period. The integration handles a near real-time, complex insertion of data into…

The correct answer is C. Write a custom Apex web service that, given an email address, does all of the logic the integration. See the full explanation below for the reasoning.

Question

Recently a Salesforce org's integration failed because it exceeded the number of allowed API calls in a 24-hour period. The integration handles a near real-time, complex insertion of data into Salesforce. The flow of data is as follows:

  • The integration looks up Contact records with a given email address

and, if found, the integration adds a Task to the first matching Contact it finds.

  • If a match is not found, the integration looks up Lead records with a

given email address and, if found, the integration adds a Task to the first matching Lead it finds.

  • If a match is not found, the integration will create a Lead and a

Task for that newly created Lead. What is one way in which the integration can stay near real-time, but not exceed the number of allowed API calls in a 24-hour period?

Options

  • AUse the REST API as well as the SOAP API to effectively double the API calls allowed in a 24-
  • BCreate an Inbound Message that, using Flow, can do all of the logic the integration code was
  • CWrite a custom Apex web service that, given an email address, does all of the logic the integration
  • DCreate several Apex InboundEmailHandlers to accept calls from the third-party system, thus

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    10% (3)
  • C
    83% (25)
  • D
    3% (1)

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PDII Practice