You need to create the technical architecture for hybrid connectivity from your data center to Google Cloud This will be managed by a partner. You want to follow Google-recommended practices for production-level applications. What should you do?
29 comments · newest first
CO
Colton
6 months ago
I’m leaning towards C as well. More connections mean better failover.
MA
Marilynn
7 months ago
D is interesting, but I prefer C for global routing benefits.
OR
Oretha
7 months ago
A is too basic for production. We need more reliability.
JA
Jamal
7 months ago
Option B could work too, but I feel it lacks the extra metro connections.
BA
Barrett
7 months ago
I think option C is the best. It offers redundancy across different metros.
AL
Alease
7 months ago
Two connections in different metros? Is that really necessary?
EF
Effie
8 months ago
D sounds overkill, but I guess it covers all bases.
KR
Kristel
8 months ago
Wait, why not just go with A? Seems simpler.
AL
Alfreda
8 months ago
I think C is the best choice for global reach!
TA
Taryn
8 months ago
Option B is solid for redundancy.
BR
Britt
9 months ago
Option B? Really? That's like trying to build a house with one hand tied behind your back.
SE
Selma
9 months ago
Option D has my vote. Redundancy is key, and this option covers all the bases.
JE
Jeffrey
9 months ago
Option A is a bit too simple for a production-level setup. Gotta go with the more robust solutions.
SU
Sue
9 months ago
I’m a bit confused about the routing configurations. I thought regional dynamic routing was sufficient, but maybe global is better for redundancy?
FL
Flo
9 months ago
I practiced a similar question about interconnects, and I feel like option D might be overkill with the regional routing.
KI
King
9 months ago
I'm not entirely sure, but I think having connections in different metro areas could help with failover. Maybe option C is the best?
AD
Adelle
10 months ago
I remember that Google recommends having redundancy, so options B and C seem more aligned with that principle.
IO
Iola
10 months ago
I've got a strategy in mind. I think the best approach is to go with option D, as it seems to hit all the key requirements - two Partner Interconnect connections in separate metros, VLAN attachments in two regions, and regional dynamic routing. This should provide the redundancy and reliability that the question is looking for.
KR
Kris
10 months ago
Hmm, this is a tricky one. I'm a bit confused about the differences between the Partner Interconnect options and how the VLAN attachments and dynamic routing work. I'll need to do some research to make sure I fully understand the implications of each approach.
NI
Nickole
10 months ago
I'm leaning towards Option C. Spreading out the Interconnect connections across multiple metros seems like a smart move.
TH
Thaddeus
11 months ago
I agree, C seems solid. Global dynamic routing is a plus.
NI
Nieves
11 months ago
Option D seems like the most comprehensive and reliable solution. Gotta love that regional dynamic routing!
CA
Carmelina
11 months ago
Okay, let's see. We need to create a hybrid connectivity solution from the data center to Google Cloud, and it needs to be managed by a partner. I think the key is to follow the Google-recommended practices, so I'll focus on that as I review the options.
DO
Dorinda
11 months ago
This question seems straightforward, but I want to make sure I understand the requirements correctly. I'll need to review the Google-recommended practices for production-level applications to ensure I'm following the best approach.
FA
Fairy
6 months ago
Yeah, but we should double-check the requirements first. Can't rush this!
JO
Josephine
6 months ago
I like option D for its balance. Two in each metro is a strong choice.
LI
Linette
6 months ago
True, but it might complicate things. Regional routing seems simpler.
AN
Antonio
6 months ago
Agreed! But what about option C? More redundancy could be better.
LY
Lynna
10 months ago
I think option B is solid. Two connections in different availability domains make sense.