Adobe Workfront AD0-E902 Question # 15 Topic 2 Discussion

Understanding the Issue:

The scenario is making too many API requests, causing the third-party API to return a429 "Too Many Requests"error, which indicates that the rate limit has been exceeded.

The solution needs to reduce unnecessary or redundant API requests to prevent hitting the API limits.

Why Option B is Correct:

Avoid Redundant Requests:

PlacingSearchandGETmodules earlier in the scenario ensures that all required data is retrieved in one batch or in fewer requests, rather than repeatedly querying the same record later in the scenario.

This technique reduces the overall number of API requests sent to the third-party system.

Efficient Data Flow:

By structuring the scenario to retrieve all necessary data at the beginning, subsequent modules can reuse the retrieved data instead of making additional API calls.

Why the Other Options are Incorrect:

Option A ("Using a Search module and then a Read Record module"):

This approach can increase API requests, as theSearch moduleretrieves record IDs, and theRead Record modulemakes separate API requests for each record. This often results in more requests than necessary.

Option C ("Adding a Retry error handling directive"):

Adding aRetry directivedoes not reduce the number of requests. Instead, it retries failed requests, which could worsen the problem by increasing API traffic.

Best Practices to Reduce API Requests:

Consolidate data retrieval into a single module or a smaller number of requests.

Use caching or intermediate storage (like Fusion Data Stores) to avoid re-fetching the same data.

Limit the scope of Search modules by using filters or pagination to process smaller, relevant data sets.

References and Supporting Documentation:

Adobe Workfront Fusion Best Practices: Managing API Rate Limits

Workfront Community: Error 429 Solutions