Google Workspace Professional Administrator — Question 63

Your organization recently bought 1,000 licenses for Cloud Identity Premium. The company’s development team created an application in the enterprise service bus (ESB) that will read user data in the human resources information system (HRIS) and create accounts via the Google Directory REST API.

While doing the original test before production use, the team observes a 503 error coming from Google API response after a few users are created. The team believes the ESB is not the cause, because it can perform 100 requests per second without any problems. What advice would you give the development team in order to avoid the issue?

Answer options

• A. Use an exponential back-off algorithm to retry failed requests.
• B. Use the domain-wide delegation API to avoid the limitation per account.
• C. Use the batch request architecture, because it can pack 1,000 API calls in one HTTP request.
• D. Switch from REST API to gRPC protocol for performance improvement.

Correct answer: A

Explanation

The correct answer is A, as utilizing an exponential back-off algorithm helps manage API request limits by waiting progressively longer between retries after encountering a failure. Options B and C do not address the immediate issue of the 503 error, which indicates a service unavailability rather than an account limitation, while D may not resolve the error related to API request limits since the issue isn't solely about performance.