9. Explain How Firewall, DNS, Load Balancers, and Reverse Proxy in Application Deployment 200-901 Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A company is deploying a new microservice. The service will be accessed by other internal services using the hostname service.internal.example.com. The operations team wants to ensure that the hostname always resolves to the current IP address of the service, even if the service is redeployed with a different IP. Which approach should they use?

   • AUse a reverse proxy and point the DNS record to the reverse proxy's IP.
   • BUse a load balancer and point the DNS record to the load balancer's virtual IP.
   • CCreate a static A record in the internal DNS server with the current IP address.
   • DConfigure the firewall to forward the hostname to the service's IP.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which statement best describes how a firewall protects an application in a deployment?

   • AIt inspects incoming and outgoing traffic and applies security rules to block or permit it
   • BIt stores frequently accessed data to reduce latency for users
   • CIt monitors server health and reroutes traffic away from failed servers
   • DIt resolves the application's domain name to the correct server IP address
   Reveal Solution Discussion Select an answer first
4. 18expert · hard

   A company deploys a web application with a reverse proxy and a firewall. The firewall is configured to allow only HTTPS traffic from the internet to the reverse proxy. The reverse proxy forwards traffic to the application servers over HTTP. The security team wants to add a web application firewall (WAF) to inspect HTTP requests for SQL injection. Where should the WAF be placed?

   • ABetween the firewall and the reverse proxy, inspecting HTTPS traffic.
   • BOn the application servers themselves, using host-based security.
   • CIn front of the firewall, inspecting all incoming traffic.
   • DBetween the reverse proxy and the application servers, inspecting HTTP traffic.
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A company runs a web application with a public load balancer and multiple backend servers. The security team wants to block traffic from a specific IP range, but the load balancer only sees the source IP of the reverse proxy or CDN, not the original client IP. The application team wants to maintain the original client IP for logging and security analytics. What is the best approach?

   • AConfigure the reverse proxy to drop requests from the IP range based on the X-Forwarded-For header, and do not change the load balancer configuration.
   • BUse DNS to block the IP range by returning a null route for requests from that range.
   • CConfigure the load balancer to use the X-Forwarded-For header to determine the original client IP and apply firewall rules based on that header.
   • DConfigure the firewall to block the IP range at the network layer, and configure the load balancer to preserve the original client IP using the PROXY protocol.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A company runs a web application with multiple backend servers. They want to use DNS-based load balancing to distribute traffic across the servers, but they also want to automatically remove a server from DNS rotation if it becomes unhealthy. Which approach should they use?

   • AUse a firewall to block traffic to unhealthy servers and rely on DNS round-robin.
   • BConfigure a load balancer and point DNS to the load balancer's IP.
   • CCreate multiple A records and manually update DNS when a server fails.
   • DUse a reverse proxy to route traffic and update DNS records automatically.
   Reveal Solution Discussion Select an answer first