Protection Level resources are grouped by how much mission capability would be affected if the asset were lost, damaged, or compromised. Operational/mission support assets such as armories, the dining facility, and base banks fall into Protection Level 4 because their loss would degrade base operations and mission readiness, even though they are not the most sensitive or critical wartime assets. This level mirrors the idea that everyday support functions are essential to keeping the mission running, but their loss doesn’t equate to the highest national-security risk. So Protection Level 4 is the best fit for these examples.

This question tests who develops and manages security and access codes for the base. Security Forces Squadron handles base security, law enforcement, and protective services, which includes programs for access control. That role covers creating identification codes to verify personnel, duress codes for emergency assistance, and authentication codes to ensure only authorized individuals can access secured areas or systems. The other squadrons are focused on logistics, medical care, or mission operations, not on security code development, so they aren’t the ones responsible for these codes. Therefore, Security Forces Squadron is the best answer.

FPCON levels describe escalating protective postures in response to threat information. The level described—an attack has occurred or intelligence indicates an imminent threat directed at a specific location—fits the highest level, Delta, because it specifies a concrete target and an immediate risk, triggering the most stringent security actions. Earlier levels cover general or broader threats: Alpha signals a general threat of terrorism, Bravo reflects a more predictable or elevated threat with heightened measures, and Charlie indicates a credible and imminent threat but not necessarily tied to one particular location.

When a video loss alarm occurs, the priority is to determine the probable cause first. This quick triage guides what needs to be done next and helps avoid unnecessary actions if the issue is a transient or external to the equipment. Once you have an initial assessment, you record the fault and actions in the official maintenance documentation. Completing the AFTO 781A captures what happened and what maintenance or checks were performed, providing a formal trace for maintenance history. After documenting the fault, you fill out the AF IMT 340 to detail the event, symptoms, timing, suspected causes, and the actions taken. This creates a clear record of the issue and supports any follow-up maintenance work. Only after these steps should you notify ESS so they can coordinate further troubleshooting or repair with the right team. If you skip triage or documentation, you’d lose essential context and traceability, and unnecessary escalations could occur. Focusing first on cause, then on proper recording, and finally on notification ensures accurate, efficient handling of the video loss alarm.