Salesforce-Marketing-Cloud-Engagement-Developer Practice Test

Salesforce Spring 25 Release
196 Questions

When do synchronous REST API calls to Marketing Cloud time out? (Choose 2.)

A. 240 seconds for tracking and data retrieve operations.

B. 300 seconds for tracking and data retrieve operations.

C. 120seconds for non-tracking operations.

D. 240 seconds for non-tracking operations.

B.   300 seconds for tracking and data retrieve operations.
C.   120seconds for non-tracking operations.

Explanation:

✅ B. 300 seconds for tracking and data retrieve operations
Marketing Cloud REST API allows longer timeouts (up to 5 minutes / 300 seconds) for tracking and data retrieval operations. These types of calls might involve large datasets and need extended processing time.

✅ C. 120 seconds for non-tracking operations
For other types of synchronous operations (like data manipulation, triggered sends, etc.), the timeout is 120 seconds. These operations are expected to be faster and more transactional in nature.

❌ A. 240 seconds for tracking and data retrieve operations
This is not accurate—although 240 seconds seems plausible, the correct limit for tracking/data operations is 300 seconds.

❌ D. 240 seconds for non-tracking operations
The timeout for non-tracking REST API calls is 120 seconds, not 240. This ensures system resources aren’t held unnecessarily long.

Salesforce-Marketing-Cloud-Engagement-Developer Practice-Test - Home Previous
Page 5 out of 196 Pages