nerdexam
Google

GOOGLE-WORKSPACE-ADMINISTRATOR · Question #150

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…

The correct answer is A. Use an exponential back-off algorithm to retry failed requests. https://developers.google.com/admin-sdk/admin-settings/limits

Google Workspace APIs and Integration

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?

Options

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

How the community answered

(41 responses)
  • A
    83% (34)
  • B
    5% (2)
  • C
    10% (4)
  • D
    2% (1)

Explanation

https://developers.google.com/admin-sdk/admin-settings/limits

Topics

#Directory API#exponential backoff#rate limiting#503 error

Community Discussion

No community discussion yet for this question.

Full GOOGLE-WORKSPACE-ADMINISTRATOR Practice