Question-40: Any latency below 100 milliseconds (ms) is considered good, and below 50 ms is very good. Typical DSL or cable Internet connections have latencies of less than 100 ms, while satellite connections usually have latencies of 500 ms or higher. As part of their new application experience, QuickTechie Inc allows customers to upload images of themselves. The customer has exclusive control over who may view these images. Customers should be able to upload images with minimal latency and also be shown their images quickly on the main application page when they log in. Which configuration should Dress4Win use?
A. Store picture files in a bucket on Google Cloud Storage. Utilize Google Cloud Datastore to store information that associates each customer's ID with their picture assets.
B. Store picture files in a bucket on Google Cloud Storage. Add customer-specific information to the uploaded photographs in Cloud Storage, which includes the customer's unique identifier.
C. Use a distributed file system to store clients' photos. As the demand for storage grows, add additional persistent discs and/or nodes. Assign each client a unique ID, which sets the owner attribute of each file, protecting the confidentiality of photos.
D. Use a distributed file system to keep photos of customers. As the demand for storage grows, add additional persistent discs and/or nodes. Use a Google Cloud SQL database to keep information that connects each customer's ID to their picture files.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 1 Explanation: Question says The customer has exclusive control over who may view these images And I think it is easier to develop this feature having in cloud datastore a NOSQL database where you can manage the control of file's viewer. Using gsutil for this purpose makes querries on such metadata painful for application logic. The whole idea is simply build and maintain an external metadata service using NoSQL database to associate the GS object key with its metadata, in order to facilitate object findings based on attributes you pre defined in metatdata. Option-2 is not correct because we cannot search on bucket using metadata. So for now we have to get all files from the bucket and fiter on metadata ( very bad performance). Store image files in a Google Cloud Storage bucket. Use Google Cloud Datastore to maintain metadata that maps each customer's ID and their image files. Option-1 solves storage and access. What I do not like about Datastore is that it requires application support and the use case is not clear how far the Application team is in migration. But considering migration in GCP happening, Datastore is great database for this type of things