A retailer's store prefixes change several times a month. Each change must reach an Azure virtual network without a ticket to edit static routes on the VPN. Which routing choice fits?
Select an answer to reveal the explanation.
Short Explanation
If the map changes every week, you stop mailing a new paper map and you start sending updates. You run BGP across the route-based VPN so a store prefix change is advertised. A ticket to edit a static route is the work you are trying to retire, and Azure will not learn this by OSPF.
Full Explanation
BGP advertises and withdraws prefixes as they change, which matches a retailer whose store prefixes move several times a month and who refuses a ticket for every static edit. The Azure gateway has to be route-based so BGP is available. A single static route on the VPN works for a tiny stable set and fails this requirement the moment someone must edit it by hand. OSPF to the Azure VPN gateway is not supported. That gateway will not flood store prefixes. Host routes on PCs are not a routing protocol Azure reads through the tunnel. The VPN learns what the router advertises or what was typed as a static route. Exam caveat: BGP still needs a sane filter. Advertising every internal prefix automatically can overwhelm the session or leak ranges the virtual network should not see. Operational check: add a store prefix on the router, confirm it is advertised, and confirm Azure installs it without anyone editing the local network gateway static address space.