Práctica GCP Network Engineer

A VPC is a global virtual network that contains subnets, routes, and firewalls. VMs, buckets, and DNS records are resources inside it.

Subnets are IP ranges within a VPC. Cables, firewalls, and load balancers are different.

Firewall rules allow or deny traffic based on source, destination, ports, and protocols. Buckets, DNS records, and machine types are different.

VPC peering connects two VPC networks. Subnets, DNS zones, and billing are different.

Shared VPC centralizes network administration by sharing subnets. Public networks, DNS, and backups are different.

Routes define where traffic is forwarded. Containers, firewalls, and DNS records are different.

Static routes are manually configured. Learned routes come from BGP, and DNS or firewalls are different.

Dynamic routes are exchanged through BGP. Static routes are manual, and DNS records are different.

IP addresses identify resources on a network. Hardware serials, passwords, and cables are different.

VPC is a virtual network, subnets are IP ranges, firewall rules filter traffic, and peering connects VPCs.

Cloud Load Balancing distributes traffic. DNS resolves names, NAT provides outbound access, and Interconnect is connectivity.

Backend services define backend groups and health checks. Firewall rules, DNS zones, and buckets are different.

Health checks verify backend readiness. DNS records, firewalls, and load balancers are different.

Forwarding rules route traffic to targets. DNS records, subnets, and firewalls are different.

Target pools group instances for load balancing. Firewall rules, DNS zones, and buckets are different.

URL maps route HTTP traffic by path and host. DNS records, firewalls, and subnets are different.

Session affinity keeps client sessions on the same backend. Firewall rules, DNS zones, and tests are different.

Global load balancers route across regions. Regional balancers stay in one region, and DNS or firewalls are different.

Regional load balancers serve traffic within a single region. Global balancers span regions, and DNS or firewalls are different.

Health checks verify, forwarding rules route, URL maps route HTTP, and session affinity keeps clients on one backend.

Cloud Armor provides WAF and DDoS protection. CDN caches content, DNS resolves names, and NAT provides outbound access.

IAP uses identity and context to control access. Firewalls, DNS records, and load balancers are different.

Private Google Access lets VMs reach Google APIs without public IPs. Public IPs, DNS records, and firewalls are different.

Cloud NAT gives private instances outbound internet access. Load balancers, DNS servers, and firewalls are different.

VPC Service Controls creates security perimeters. Firewall rules, DNS zones, and load balancers are different.

Packet mirroring copies traffic for security tools. Blocking, DNS resolution, and IP assignment are different.

Firewall policies apply rules across the hierarchy. DNS records, subnets, and load balancers are different.

Security policies contain WAF rules. Firewall rules, DNS zones, and load balancers are different.

TLS protects data in transit. At-rest encryption protects files, masking hides values, and backups copy data.

Armor protects web apps, IAP controls identity access, NAT provides outbound access, and Service Controls creates perimeters.

Cloud VPN creates encrypted tunnels over the internet. Load balancers, DNS servers, and firewalls are different.

Interconnect provides private physical connectivity. VPN uses the internet, and DNS or firewalls are different.

Dedicated Interconnect provides direct physical links. VPN tunnels, DNS zones, and load balancers are different.

Partner Interconnect uses partner providers for private connectivity. Public internet, DNS records, and firewalls are different.

Cloud Router dynamically exchanges routes with on-premises via BGP. Physical routers, DNS servers, and firewalls are different.

BGP exchanges routes between networks. DNS, storage, and firewall are different.

Peering connects networks directly. VPN tunnels, DNS records, and load balancers are different.

Network Connectivity Center manages connectivity hubs. DNS servers, firewalls, and buckets are different.

Hybrid networks connect on-premises and cloud. Public-only, private-only, and local LANs are not hybrid.

VPN creates tunnels, Interconnect provides private connections, Cloud Router exchanges routes, and BGP is the protocol.

Flow Logs capture traffic metadata. Application logs, DNS records, and backups are different.

Packet capture records traffic for inspection. Blocking, DNS resolution, and IP assignment are different.

Cloud Monitoring collects metrics and alerts. DNS resolves names, Storage stores data, and CDN caches content.

Cloud Logging stores and queries logs. DNS, NAT, and Armor are networking services, not log storage.

Uptime checks verify endpoints from multiple locations. Firewall rules, DNS records, and load balancers are different.

Traceroute shows the packet path. DNS resolution, IP assignment, and filtering are different.

Ping tests reachability. DNS resolves, routers forward, and encryption protects.

Latency tests measure delay. Firewall rules, DNS records, and backups are different.

Network intelligence provides diagnostics and insights. Firewalls, DNS zones, and load balancers are different.

Flow Logs capture metadata, Monitoring collects metrics, traceroute shows paths, and packet capture records traffic.

Optimization improves performance and cost. Deleting routes, disabling monitoring, or increasing latency are not optimization.

Cloud CDN caches content at edge locations. DNS servers, firewalls, and load balancers are different.

Caches store content for fast delivery. Firewall rules, DNS records, and routes are different.

Cache hits serve content from cache. Misses fetch origin, and DNS or firewall events are different.

Bandwidth measures capacity. Latency measures delay, and routes or DNS records are different.

Latency measures delay. Capacity is bandwidth, and DNS records or firewall rules are different.

Quotas limit resources. DNS records, firewall rules, and load balancers are different.

Cost optimization balances spend and performance. Deleting resources, disabling monitoring, or increasing latency are not optimization.

Premium tier routes traffic over Google backbone for lower latency. Basic tier, DNS zones, and firewalls are different.

Cloud CDN delivers content, caches store fast, latency is delay, and quotas limit resources.