Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Architect (PR000213) Exam - Topic 2 Question 104 Discussion

For this question, refer to the Dress4Win case study.As part of their new application experience, Dress4Wm 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 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.
B) Store image files in a Google Cloud Storage bucket. Add custom metadata to the uploaded images in Cloud Storage that contains the customer's unique ID.
C) Use a distributed file system to store customers' images. As storage needs increase, add more persistent disks and/or nodes. Assign each customer a unique ID, which sets each file's owner attribute, ensuring privacy of images.
D) Use a distributed file system to store customers' images. As storage needs increase, add more persistent disks and/or nodes. Use a Google Cloud SQL database to maintain metadata that maps each customer's ID to their image files.

Google Professional Cloud Architect (PR000213) Exam - Topic 2 Question 104 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 104
Topic #: 2
[All Professional Cloud Architect (PR000213) Questions]

For this question, refer to the Dress4Win case study.

As part of their new application experience, Dress4Wm 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?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://cloud.google.com/appengine/docs/standard/go/how-requests-are-handled

by Man at Mar 23, 2025, 05:53 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Fannie
9 months ago
Wait, a distributed file system? That sounds overkill for this!
upvoted 0 times
...
Lina
9 months ago
D could work, but why not just stick with Cloud Storage?
upvoted 0 times
...
Herman
9 months ago
C sounds complicated, not sure about that one.
upvoted 0 times
...
Erick
9 months ago
I think B is better for keeping it simple with metadata.
upvoted 0 times
...
Bronwyn
9 months ago
Option A seems solid for quick access and control.
upvoted 0 times
...
Jackie
10 months ago
I recall that using a SQL database for metadata can add complexity. I wonder if that’s necessary here since we need quick access to images.
upvoted 0 times
...
Barney
10 months ago
I think we practiced a similar question where we had to choose between using a distributed file system and Cloud Storage. I feel like Cloud Storage is simpler for this case.
upvoted 0 times
...
Charisse
10 months ago
I'm a bit unsure about the metadata part. Should we really be using Cloud Datastore or is custom metadata in Cloud Storage enough?
upvoted 0 times
...
Ena
10 months ago
I remember we discussed using Google Cloud Storage for image uploads in class. It seems like a good fit for minimizing latency.
upvoted 0 times
...
Lavonna
11 months ago
The distributed file system options seem interesting, but I'm not sure how they compare to the cloud storage approach in terms of latency and scalability. I'll need to research those a bit more.
upvoted 0 times
...
Gertude
11 months ago
Option A looks like the most straightforward solution, using Google Cloud Storage and Datastore to handle the image files and metadata. I think I'll go with that one.
upvoted 0 times
...
Alisha
11 months ago
Hmm, I'm a bit confused by the different storage options. I'll need to make sure I understand the pros and cons of each approach before deciding.
upvoted 0 times
...
Valentine
11 months ago
This seems like a straightforward question about storing and managing customer images. I'll need to carefully consider the tradeoffs between the different options presented.
upvoted 0 times
...
Yvette
1 year ago
Hold up, Option D with the distributed file system and Cloud SQL sounds like a real fashion show backstage. Gotta have that database to keep track of all the image divas, am I right?
upvoted 0 times
Kip
1 year ago
D) Use a distributed file system to store customers' images. As storage needs increase, add more persistent disks and/or nodes. Use a Google Cloud SQL database to maintain metadata that maps each customer's ID to their image files.
upvoted 0 times
...
Yvonne
1 year ago
B) Store image files in a Google Cloud Storage bucket. Add custom metadata to the uploaded images in Cloud Storage that contains the customer's unique ID.
upvoted 0 times
...
Myong
1 year ago
A) 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.
upvoted 0 times
...
...
Willow
1 year ago
Option B all the way! Cloud Storage is like a digital closet for your customers' fashion pics. And the custom metadata is the stylish little tag that keeps track of who owns what. Easy peasy!
upvoted 0 times
Yuette
1 year ago
Definitely! Using Cloud Storage with custom metadata is a smart way to handle the image uploads. It's a win-win for both the customers and Dress4Win.
upvoted 0 times
...
Kendra
1 year ago
I agree! Option B sounds like the best choice for Dress4Win. It's efficient and ensures privacy for the customers' images.
upvoted 0 times
...
Lovetta
1 year ago
Option B all the way! Cloud Storage is like a digital closet for your customers' fashion pics. And the custom metadata is the stylish little tag that keeps track of who owns what. Easy peasy!
upvoted 0 times
...
...
Rosendo
1 year ago
I don't know, Option A with the Cloud Storage and Datastore combo seems a bit overkill. Why not just use the Cloud Storage bucket with the custom metadata? That seems like the simplest and most efficient solution.
upvoted 0 times
Kristofer
1 year ago
Yeah, Option B with custom metadata in Cloud Storage sounds like the way to go.
upvoted 0 times
...
Jamal
1 year ago
I agree, Option B seems like the most straightforward solution.
upvoted 0 times
...
Cordelia
1 year ago
Option B sounds like the best choice. It's simple and efficient.
upvoted 0 times
...
...
Nelida
1 year ago
Hmm, Option C with the file system and owner attributes is an interesting idea. It's a bit more complex than the other options, but it could provide good privacy and control for the customers. Definitely worth considering.
upvoted 0 times
Gilma
1 year ago
That's true, it would be a simpler option but still effective for managing the images.
upvoted 0 times
...
Daniela
1 year ago
I think using Google Cloud Storage with custom metadata could also work well for this.
upvoted 0 times
...
Pamella
1 year ago
I agree, it might be a bit more complex but it could be worth it for the added control.
upvoted 0 times
...
Tyisha
1 year ago
Option C with the file system and owner attributes sounds like a good choice for privacy.
upvoted 0 times
...
...
Geraldine
1 year ago
I'm leaning towards Option D. Using a distributed file system for the images and a Cloud SQL database for the metadata sounds like a more scalable and robust solution. The database will make it easier to manage and query the image data.
upvoted 0 times
...
Truman
1 year ago
Option B seems like the most straightforward approach. Storing the images in a Cloud Storage bucket and adding custom metadata with the customer's ID is a simple and effective way to maintain control and privacy.
upvoted 0 times
...
Wenona
1 year ago
That's a good point, Kiley. Scalability is important for a growing application like Dress4Win. Option C does seem like a good choice.
upvoted 0 times
...
Kiley
1 year ago
I disagree, I believe option C would be better. Using a distributed file system can provide scalability as storage needs increase.
upvoted 0 times
...
Wenona
1 year ago
I think Dress4Win should use option A. It seems like a simple and efficient way to store and manage the images.
upvoted 0 times
...

Save Cancel