Exam Professional Cloud Architect topic 8 question 7 discussion

c) Multi-Region Name Multi-Region Description asia Data centers in Asia eu Data centers in the European Union1 us Data centers in the United States multi-region is a large geographic area, such as the United States, that contains two or more geographic places.

I think answer is C. Use a multi-region when you want to serve content to data consumers that are outside of the Google network and distributed across large geographic areas, or when you want the higher availability that comes with being geo-redundant.

They currently have over 500 dealers and service centers in 100 countries

Option C is the best choice. It leverages Google Cloud Multi-Regional Storage buckets, which ensures faster global access, improves reliability, and minimizes data transfer time, especially for cellular connections. Using Google APIs over HTTP(S) for transfer further improves the overall transfer speed and reliability, as HTTP(S) supports automatic retries and resumable uploads, which significantly reduces the impact of intermittent connectivity issues on data transfers.

Everyone voting C are missing the point, you are not serving the data, merely ingesting it. For that , regional buckets provide better latency and bandwidth with lower costs. Multi-regions can be considered for redundancy in the case of regional failures , but it's costly and extremely unlikely for an entire region to go down , zonal replication is good enough in this case

in option D imagine you have 1 regional bucket in US-west and the client is in US-east... latency problems right? with multiregional you don't have the issue... I go for C

Go for D. Telemetry data stored in regional (US, Europe and Asia) bucket.

At the beginning I was for B, since it was not clear for me that resumable uploads were available in cloud storage, but they are: https://cloud.google.com/storage/docs/resumable-uploads

I would say it is C

C is correct,

The real debate is C vs D. Lets look at some docs: Low cost is one of the business requirements. Also, regional has higher Performance than multi-regional https://cloud.google.com/storage/docs/locations#considerations Multi regional will be an overkill for analytics as mentioned by Google. https://cloud.google.com/storage/docs/locations#location_recommendations

Option C seems right here. Directly transferring the files to a different Google Cloud Regional Storage bucket location in US, EU, and Asia using Google APIs over HTTP(S), would not be an effective solution as it would not improve the reliability of the solution. Using Google Cloud Multi-Regional Storage, which stores the data in multiple locations, would be a more reliable solution.

Multi-region

just look at this: https://cloud.google.com/storage/docs/locations#location_recommendations

Can someone explain why A and B are incorrect ? All the responses focus on C and D.

D, multi-region increases latency

By directly transferring the files to Google Cloud Multi-Regional Storage buckets using Google APIs over HTTP(S), you will improve the reliability of the solution and minimize data transfer time on the cellular connections.