Drill 12 ยท
AP Cybersecurity Drill 12: Placing a Public Web Server is a practice drill. It contains 5 original questions created by Brian Stewart, a Barron's test prep author with over 20 years of tutoring experience.
An IT lead at a college decides where to place a public web server and an internal records server so that outsiders cannot reach private data; this drill uses an invented company and original figures.
Garnsey Technical Institute is redesigning its network. The IT lead lists the servers, what each one does, and who must be able to reach it.
| Server | Purpose | Who must reach it |
|---|---|---|
| Web server | Hosts the public course catalog and admissions pages | Anyone on the internet |
| Records server | Stores student grades and financial-aid files | Only registrar staff, from inside the network |
| Internal file server | Stores staff documents | Only staff, from inside the network |
In the current plan, all three servers sit on the same internal network, and the firewall forwards web requests from the internet straight to the web server sitting beside the records server. The IT lead wants the public web server reachable from the internet without giving outsiders any permitted path to the records or file servers.
Question 1. Reading the table and the current plan, what is the main risk of leaving the public web server on the same internal network as the records server?
Explanation: Choice B is correct. The web server is exposed to the whole internet, so if it is compromised it becomes a foothold; because it sits on the internal network next to the records server, the attacker can then try to reach grades and financial-aid files. Choice A is incorrect. Shared bandwidth is a performance detail, not the security risk the lead is trying to remove. Choice C is incorrect. Placement on the internal network does not cause a private records server to be indexed by search engines. Choice D is incorrect. Printing is unrelated to the exposure created by co-locating a public server with sensitive data.
Question 2. Which network design best lets outsiders reach the web server while keeping them away from the records and file servers?
Explanation: Choice A is correct. A screened subnet, also called a DMZ, is a separated segment for public-facing systems; placing the web server there and keeping the records and file servers on the internal network lets the internet reach only the DMZ, not the private data. Choice B is incorrect. Putting the records and file servers on the public internet exposes exactly the data the lead wants to protect. Choice C is incorrect. Sharing an address does not separate the servers and would break routing. Choice D is incorrect. Disabling the firewall removes the boundary that keeps outsiders away from internal systems.
Question 3. With the web server in the DMZ, which firewall rule arrangement matches the access needs in the table?
Explanation: Choice D is correct. Permitting inbound internet traffic only to the DMZ web server on the required web service port, such as HTTPS/443, while blocking internet-initiated traffic to the internal servers, gives the public access to the catalog while keeping outsiders away from grades and staff files. Choice A is incorrect. Allowing the internet to reach every server on every port exposes the sensitive servers, the opposite of the goal. Choice B is incorrect. Blocking the web server and exposing the records server inverts what each server needs. Choice C is incorrect. The records server should never be reachable from the internet; a weekend window still exposes it.
Question 4. Why does placing the web server in a DMZ reduce risk even if that web server is eventually compromised?
Explanation: Choice C is correct. The value of the DMZ is the boundary behind it: even a fully compromised web server is still separated from the internal network by the inner firewall, so reaching the records and file servers is not automatic. Choice A is incorrect. No placement makes a server impossible to hack; the DMZ limits the damage, it does not prevent compromise. Choice B is incorrect. Servers in a DMZ still require patching; being public-facing makes patching more important. Choice D is incorrect. A DMZ is a placement and filtering concept; it does not automatically encrypt a server's stored files.
Question 5. After the redesign, which monitoring step would most directly help the IT lead detect an attacker trying to pivot from the DMZ web server toward the internal records server?
Explanation: Choice B is correct. In this design, the public web server has no stated need to start connections to the internal records server, so reviewing the inner firewall's logs for DMZ-to-internal attempts is the most direct way to catch a pivot. Choice A is incorrect. Confirming the public pages load checks availability, not whether the web server is reaching toward internal systems. Choice C is incorrect. Visitor counts measure traffic volume, not lateral movement. Choice D is incorrect. Verifying the web server's address is unchanged does not reveal connection attempts toward the records server.