I'm leaning towards option D - a user-defined route assigned to the GatewaySubnet in Vnet2 and Vnet3. That seems like the most logical way to configure the default route.
Okay, let me think this through. The question says the solution must meet the virtual networking requirements, so I'm guessing a user-defined route is the way to go since it's the most direct approach.
Azure Cosmos DB is definitely the way to go. It's designed for low-latency, high-throughput scenarios exactly like this. I'm pretty confident that's the right answer.
Okay, let me think this through. We use connect() to establish a connection, bind() to bind a socket to an address, and sendto() to send data to a specific IP. I'll go with A.
I'm leaning towards C. Configuring the default route in the GatewaySubnet of Vnet1 could work, and it might be simpler than setting it up in multiple VNets.
I think the answer is D. A user-defined route assigned to the GatewaySubnet in Vnet2 and Vnet3 seems like the most straightforward way to configure the default route.
Shay
3 months agoTijuana
3 months agoMirta
4 months agoCharlena
4 months agoTwila
4 months agoLenna
4 months agoJeanice
4 months agoMarilynn
4 months agoAnnmarie
5 months agoShenika
5 months agoMable
5 months agoArtie
5 months agoJamie
5 months agoThomasena
5 months agoGeorgene
5 months agoKatie
5 months agoHerminia
9 months agoKristian
9 months agoErasmo
8 months agoTandra
8 months agoFlorinda
8 months agoWynell
9 months agoScot
9 months agoFrancis
10 months agoSharan
8 months agoLing
8 months agoSerina
9 months agoKara
10 months agoRyan
10 months agoMarjory
10 months agoFelicitas
10 months agoJame
9 months agoReuben
9 months agoLenna
10 months agoElly
10 months agoKallie
10 months agoCherry
11 months agoRolande
11 months ago