Practice Test 3 | Google Cloud Certified Professional Data Engineer | Dumps | Mock Test
Your team built an online service which allows users to upload a set of images to convert them into a single PDF file. The service became popular and more users continue to submit their images on the web page. This led to more requests to be processed by backend instances and in return more pending requests are facing timeouts calling the API. If the team uses Google Cloud as the main platform, how would you solve this issue?
A. Build a Dataflow pipeline to process requests sequentially.
B. Increase timeout for API at peak times to 120 seconds. If it keeps failing, try increasing the timeout until the issue is resolved.
C. Use Cloud SQL to store incoming requests. Backend instances can read the requests in order and mark each as complete when done.
D. Use Pub/Sub to handle users’ requests when submitted using the service web page. Subscribe backend instances to Pub/Sub topic collecting the requests and process both.
Correct Answer: D
Cloud Pub/Sub is a service to ingest event streams at any scale. It’s scalable and reliable for stream analytics and event-driven computing systems.
Pub/Sub is a good product to de-couple a system’s components so they communicate with each other asymmetrically. From the scenario shown here, instead of directly calling the API, the platform can “publish” messages to a “topic.” The API can be switched to be a “subscriber” which receives the requests submitted and processes each message asymmetrically.
Option A is incorrect: Dataflow does not help in solving the increasing API requests.
Option B is incorrect: Increasing timeout isn’t a scalable solution and it may continue occurring eventually when more and more users are using the service.
Option C is incorrect: The problem with this solution is, writing and reading records and managing each record’s status may require more development to be done making sure no two instances are processing the same request. Managing Cloud SQL can be another issue required to be handled by the team whereas Pub/Sub is a fully managed service does not require maintenance.
Source(s):
Google Pub/Sub:
Comments are closed, but trackbacks and pingbacks are open.