Governance, hub-spoke, private endpoints, SNAT, identity, HA, cost
Practise these as flashcards. One or two lines each; the ones you miss come back first.
Start freeA private network in the cloud, split into subnets, with your own IP ranges, routing and firewall rules. You can connect it to on-prem with VPN or ExpressRoute/Direct Connect.
An NSG is a free, stateful Layer 4 allow/deny list on a subnet or NIC. Azure Firewall is a paid, managed firewall with FQDN rules, threat intelligence and central logging, usually placed in a hub network.
Azure's virtual platform IP. It provides DNS, DHCP, load balancer health probes and VM agent communication. Blocking it breaks name resolution, health probes and extensions.
No. If A peers with hub and B peers with hub, A can't reach B through the hub by default. Route via a firewall/NVA in the hub with UDRs, peer A and B directly, or use Virtual WAN.
RBAC decides who can do what (a person can create VMs). Policy decides what's allowed regardless of who (VMs must have tags, no public IPs, only approved regions). They work together.
A set spreads VMs across fault and update domains inside one datacenter, protecting against rack failure and host maintenance. Zones spread VMs across separate datacenters in a region, with a higher SLA.
Give the VM a managed identity and grant that identity a Key Vault role. The VM gets tokens automatically; no credentials in config files.
Azure Update Manager or AWS Systems Manager Patch Manager: schedules, maintenance windows and compliance reports. Or Ansible if it's hybrid with on-prem.
Lift-and-shift moves VMs as they are: fast, same operations. Re-platform swaps parts for managed services (SQL VM → Azure SQL, app → App Service) to cut operational work.
Right-size from monitoring data, auto-shutdown non-prod at night, reserved instances or savings plans for steady workloads, tag everything by owner and cost center, and set budget alerts.
A service endpoint keeps traffic on the Azure backbone and lets the service firewall allow your subnet, but the service keeps its public IP. A private endpoint gives the service a private IP inside your VNet, reachable from peered VNets and on-prem; it needs private DNS. Private endpoints are the enterprise default.
DNS. The name must resolve to the private IP via the privatelink zone. Check nslookup from the app host: if it returns a public IP, the Private DNS zone isn't linked to that VNet, or the custom/on-prem DNS isn't forwarding to Azure DNS (via the DNS Private Resolver). Also check public network access is disabled on the server.