Learn how to resolve 503 errors in the Google Directory API by implementing domain-wide delegation for efficient user provisioning and management.
Table of Contents
Question
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?
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.
Answer
B. Use the domain-wide delegation API to avoid the limitation per account.
Explanation
The 503 error likely indicates exceeding the per-user rate limit for Directory API calls. Domain-wide delegation allows the application to impersonate a service account with broader API access, bypassing per-user limitations.
Google Professional Google Workspace Administrator certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Google Professional Google Workspace Administrator exam and earn Google Professional Google Workspace Administrator certification.