41. Responsive movement with an authoritative server
In a server-authoritative shooter with 100 ms ping, players complain movement feels delayed. What is the standard solution?
- A.Make the client authoritative for position and damage
- B.Send inputs less often to reduce load
- C.Increase the server tick rate to 1000 Hz
- D.Client-side prediction: apply input locally right away, then reconcile with the server state by replaying unacknowledged inputs
Show answer
Answer: D. Client-side prediction: apply input locally right away, then reconcile with the server state by replaying unacknowledged inputs
With prediction, the client moves the player immediately using the same movement code as the server. Each input has a sequence number; when a server state arrives, the client resets to it and replays inputs the server has not processed yet. This feels instant while the server stays in control and prevents cheating.
42. Friends cannot join a hosted game
In a peer-hosted co-op game, some players cannot connect to friends even with the right join code. What is the robust solution?
- A.Ask players to disable their antivirus
- B.Switch the game to TCP
- C.Use NAT punch-through where possible, with a relay service as fallback when direct connection fails
- D.Lower the tick rate to make packets smaller
Show answer
Answer: C. Use NAT punch-through where possible, with a relay service as fallback when direct connection fails
Home routers use NAT, so an unsolicited packet from outside is dropped. Punch-through via a rendezvous server works for many routers but not symmetric NATs or strict networks. Relay services like Unity Relay, Steam Datagram Relay or Epic Online Services forward traffic so everyone can play, at some latency cost.
43. Estimating server time on a client
Clients need a good estimate of server time to schedule events and interpolate. Which approach is sound?
- A.Use each client's system clock directly
- B.Send the client time to the server and trust it
- C.Sync once at connection and never again
- D.Exchange timestamped pings, estimate offset as server time plus half the round-trip time, filter out spiky samples and smooth adjustments over time
Show answer
Answer: D. Exchange timestamped pings, estimate offset as server time plus half the round-trip time, filter out spiky samples and smooth adjustments over time
Device clocks differ and can be changed by players, so they cannot be trusted. Ping exchanges give round-trip time; assuming roughly symmetric latency, the offset is server time plus RTT / 2. Taking the samples with the lowest RTT and slewing the clock gradually avoids visible jumps.
44. Transitive routing between VPCs
VPC A is peered with VPC B, and VPC B is peered with VPC C. Instances in A cannot reach C. You will soon have 30 VPCs that all need to talk to each other. What is the best design?
- A.Add routes in A pointing to C through the A-B peering connection
- B.Use a transit gateway (hub and spoke) and attach all VPCs to it
- C.Run a proxy instance in VPC B to forward traffic
- D.Merge all VPCs into a single VPC with overlapping CIDR ranges
Show answer
Answer: B. Use a transit gateway (hub and spoke) and attach all VPCs to it
VPC peering is not transitive, so A cannot route through B to C. A full mesh of peering for 30 VPCs would need 435 connections. A transit gateway acts as a regional hub with route tables for segmentation, scaling cleanly to many VPCs and on-premises links. Proxy instances add a bottleneck and single point of failure, and overlapping CIDRs break routing.
45. Unexpected data transfer bill
After spreading a chatty microservice system across three AZs for high availability, the monthly bill jumps even though instance counts did not change. What is the most likely cause and a good mitigation?
- A.Cross-AZ data transfer charges; use zone-aware routing so services prefer same-AZ targets while keeping multi-AZ capacity
- B.Internet gateway hourly charges; remove the internet gateway
- C.Elastic Load Balancer idle charges; delete the load balancer
- D.IAM API call charges; cache IAM credentials
Show answer
Answer: A. Cross-AZ data transfer charges; use zone-aware routing so services prefer same-AZ targets while keeping multi-AZ capacity
Most clouds charge for data moving between availability zones in both directions. Chatty services that call each other across AZs can create large transfer costs. Zone-aware or topology-aware routing (for example Kubernetes topology-aware routing or same-AZ preference in a service mesh) keeps most traffic local while still allowing failover. Internet gateways and IAM calls have no such charges.
46. CDN cache hit ratio of 4 percent
A CloudFront distribution has a 4 percent cache hit ratio. Its cache policy includes all headers, all cookies and all query strings in the cache key. What is the main problem?
- A.The origin server responds too slowly for CloudFront to cache
- B.Every header, cookie and query variation is a separate cache entry
- C.The TTLs are set too long, so objects expire unpredictably
- D.CloudFront only caches image files and skips other content types
Show answer
Answer: B. Every header, cookie and query variation is a separate cache entry
Anything in the cache key splits the cache, and headers like User-Agent or session cookies make almost every request unique. Include only values the origin really varies on, and forward other values with an origin request policy instead. Normalizing query strings also helps.
47. Exposing one API to 200 customer VPCs
You must expose one internal API privately to 200 customer VPCs, many with overlapping CIDRs, without giving them access to the rest of your network. What fits best?
- A.A separate VPC peering connection with each of the customers
- B.A public ALB with an IP allow-list for every customer NAT address
- C.A PrivateLink endpoint service behind a Network Load Balancer
- D.One transit gateway shared with all customers through RAM
Show answer
Answer: C. A PrivateLink endpoint service behind a Network Load Balancer
PrivateLink exposes a single service through interface endpoints in each consumer VPC, so CIDR overlap does not matter and traffic is one-way to that service. Peering and transit gateways connect whole networks and need unique CIDRs. A public ALB sends traffic over the internet, which the requirement rules out.
48. One link full, three idle
Four equal-cost paths connect two data centres. One link is saturated while the others are almost idle. A nightly backup uses one huge TCP stream. Why?
- A.ECMP only balances UDP traffic, never TCP
- B.The backup software ignores the routing tables
- C.Three of the four links must have failed
- D.ECMP hashes each flow onto a single path
Show answer
Answer: D. ECMP hashes each flow onto a single path
ECMP balances by hashing flow fields (IPs, ports, protocol) so packets of one flow stay in order on one path. A single elephant flow cannot spread out. Splitting the backup into parallel streams lets the hash spread them.
49. A floating IP that moved but no one noticed
A virtual IP moves from server A to server B during failover, but neighbours keep sending traffic to A for minutes. What should the new owner do?
- A.Restart the DHCP client on every neighbour
- B.Send gratuitous ARP so neighbours update caches
- C.Change the DNS TTL for the virtual IP to zero
- D.Lower its MTU so neighbours pick new paths
Show answer
Answer: B. Send gratuitous ARP so neighbours update caches
Neighbours cache IP-to-MAC mappings. When an IP moves, the new holder sends a gratuitous ARP announcing its MAC, so caches update at once. Tools like keepalived do this on failover; without it, stale entries expire slowly.
50. Fixing MTU on a site-to-site tunnel
An IPsec tunnel between a Dubai office and a cloud VPC adds about 70 bytes of overhead. You cannot change MTU on every laptop. What is the usual fix?
- A.Raise every laptop's MTU to 9,000
- B.Switch all traffic to UDP
- C.Clamp TCP MSS on the tunnel endpoints
- D.Disable TCP window scaling
Show answer
Answer: C. Clamp TCP MSS on the tunnel endpoints
MSS clamping rewrites the MSS value in TCP SYNs passing through the gateway, so both ends send segments small enough to fit the tunnel. It avoids fragmentation and PMTUD problems without touching every host. UDP traffic still needs care.
51. Latency jumps when someone uploads
Office video calls are smooth until someone uploads a big file; then ping times rise from 20 ms to 800 ms with little loss. What is this and the usual fix?
- A.Bufferbloat; use queue management like fq_codel
- B.DNS overload; add a second resolver for the office
- C.Packet loss; replace the office network cable
- D.IP conflict; renew every DHCP lease in the office
Show answer
Answer: A. Bufferbloat; use queue management like fq_codel
Oversized buffers in a router fill up under load, so every packet waits in a long queue, adding huge delay without much loss. Active queue management such as fq_codel or CAKE, with shaping slightly below the link rate, keeps queues short.
52. One IP announced from many cities
A DNS provider announces the same IP from Mumbai, Dubai and London. How does a user's packet reach a site?
- A.It is sent to all three sites at once for redundancy
- B.BGP routes it to the nearest site in routing terms
- C.DNS picks the site using the user's GPS location
- D.The user's router picks one of the three at random
Show answer
Answer: B. BGP routes it to the nearest site in routing terms
With anycast, many sites announce the same prefix, and BGP delivers each packet to the "closest" one by routing policy and path, which is usually but not always the nearest geographically. It suits short UDP exchanges like DNS and DDoS absorption.
53. Traffic takes a long way round
Traffic from a Mumbai office to a Dubai server goes via Europe, adding 120 ms, even though a direct link exists between the ISPs. Why can this happen?
- A.Routers always pick the slowest path first
- B.DNS sends traffic through Europe
- C.TCP chooses the path during the handshake
- D.BGP picks paths by policy and AS path, not latency
Show answer
Answer: D. BGP picks paths by policy and AS path, not latency
BGP route selection uses business policy (local preference), AS path length and other attributes, with no measure of latency. A provider may prefer a cheaper transit route. Fixes include working with ISPs, different transit or a private interconnect.
54. A domain that breaks only for some users
After changing DNS providers, your domain resolves for some users but returns SERVFAIL for users of validating resolvers like 1.1.1.1. The old DS record is still at the registry. What happened?
- A.The new provider does not support A or AAAA records
- B.Validating resolvers block new domains
- C.The TTL was set to zero by mistake
- D.The old DS no longer matches the new DNSSEC keys
Show answer
Answer: D. The old DS no longer matches the new DNSSEC keys
The DS record at the parent must match a key in the child zone. Moving providers without updating or removing the DS breaks validation, and validating resolvers return SERVFAIL. Remove the DS first, wait out TTLs, then re-enable DNSSEC with the new keys.
55. Geo DNS sends users to the wrong region
Your geo-DNS routes Indian users to Mumbai, but many Indian users of a public resolver land in Singapore. What is a likely reason?
- A.Indian users always prefer Singapore servers
- B.Geo DNS sees the resolver's location, not the user's
- C.DNS cannot tell countries apart at all
- D.The Mumbai servers are failing health checks
Show answer
Answer: B. Geo DNS sees the resolver's location, not the user's
Authoritative servers see the resolver's IP. If the resolver's nearest site is elsewhere and it does not send EDNS Client Subnet, geo decisions are based on the wrong location. Anycast-based or latency-based routing can avoid this dependency.
56. New instances fall over on arrival
When auto scaling adds instances, they immediately get a full share of traffic and time out for a minute while caches and JIT warm up. Which load balancer feature helps?
- A.Slow start mode that ramps traffic up gradually
- B.Stickiness so old users stay on old instances
- C.A longer deregistration delay
- D.Cross-zone load balancing turned off
Show answer
Answer: A. Slow start mode that ramps traffic up gradually
Slow start gives a newly healthy target a gradually increasing share of requests over a set window, letting caches, connection pools and JIT compilation warm up. Warm-up logic before passing the readiness check also helps.
57. Removing a rule did not cut the attacker off
You remove a security group rule that allowed SSH from an attacker's IP, but their existing session stays open. Why?
- A.Security group changes take 24 hours to apply
- B.Existing tracked connections are not cut by rule changes
- C.SSH bypasses security groups entirely
- D.You must also delete the subnet route table
Show answer
Answer: B. Existing tracked connections are not cut by rule changes
Security groups are stateful. Removing a rule stops new connections, but already tracked flows can continue. To cut an active session immediately, use a network ACL deny (stateless) or isolate the instance.
58. Private endpoint created, traffic still public
You add an Azure private endpoint for a storage account and disable public access. VMs now get "access denied", and nslookup shows the public IP. What is missing?
- A.Private endpoints only work for SQL databases
- B.The privatelink private DNS zone is not linked to the VNet
- C.The VM needs a public IP to use private endpoints
- D.The storage account must move to another region
Show answer
Answer: B. The privatelink private DNS zone is not linked to the VNet
Private endpoints rely on DNS: the service name must resolve to the endpoint's private IP via a privatelink.* private DNS zone linked to the VNet, or via custom DNS forwarding. Otherwise clients still resolve and use the public address.
59. Phishing on your own subdomain
Phishing pages appear at promo.company.example. DNS shows a CNAME to an old cloud app the marketing team deleted last year. What happened?
- A.DKIM replay against the main domain
- B.An open redirect on the main company website
- C.A homograph attack using punycode
- D.Subdomain takeover via a dangling CNAME
Show answer
Answer: D. Subdomain takeover via a dangling CNAME
The CNAME still points to a cloud resource name that no longer exists, so an attacker claimed that name and now serves content on your real subdomain. Users and filters trust it. Remove DNS records when services are deleted, and audit for dangling records.
60. New load balancer nodes get no traffic
During a long test, the cloud load balancer scales out and adds new IP addresses to its DNS name. The test keeps hitting only the original IPs and they overload. What is the cause?
- A.The new nodes are broken and must be removed
- B.DNS cannot return more than one IP address
- C.The load tool cached old DNS results; lower its DNS cache time
- D.The servers are rejecting new connections on purpose
Show answer
Answer: C. The load tool cached old DNS results; lower its DNS cache time
Load tools and the JVM can cache DNS answers for a long time, so they never see new addresses. Real clients resolve more often, spreading traffic. Configure the tool's DNS TTL (k6 has a dns option; JMeter has a DNS Cache Manager) so the test follows the load balancer like real users.