The main concept is that alarm records stay on the Action List and Alarm List until the situation is resolved. When an alarm is secured—meaning the issue is verified as addressed and the area or asset is safe—the entry is cleared from both lists. This reflects that no further action is needed on that event and the system can return to normal monitoring. Why this fits best: securing an alarm confirms completion of the necessary steps (verification, containment, restoration) and allows the logs to show only active issues. Time-based removal, maintenance due, or never removing are not accurate drivers for clearing an alarm; those options don’t reflect the need to acknowledge completion of the event.

When multiple alarms arrive, the system uses urgency to decide which one to focus on. The alarm with the highest priority is designated as the current selected alarm because priority levels convey how critical or time-sensitive a condition is. This ensures the most important issue gets attention first, regardless of when it occurred or how many sensors are involved. Oldest or most recent timing doesn’t automatically reflect danger, and an alarm from many sensors isn’t inherently more critical than a single, more severe alert. If several alarms share the same top priority, other tie-breaking rules may apply, but the key idea is to surface the most urgent condition first.

Postponing items means delaying their handling for later without removing them or changing their read status. To apply that delay to every item in the list, you need the batch action that targets all items at once. That option defers every item in the list, making it the correct choice. Defer would apply to a single item, Archive All moves items out of the active list, and Mark All as Read only changes their read status, not their postponement.

Alarms are received when a responder changes to alarm status. This means the system treats an alarm as active only after someone explicitly marks themselves or the incident as being in alarm, creating a clear, auditable record of who acknowledged it and when. This deliberate status change ensures proper accountability and enables immediate escalation to the right people, rather than assuming an alarm just from sensor activity. If alarms were automatically received, there wouldn’t be that direct, verifiable link to a specific responder. If reception happened only during staffed hours, coverage would be inconsistent. And if an alert came after a manual reset by the user, that describes clearing an alarm, not initiating it.

The main idea here is that a Summary Window is meant to give you a quick, at-a-glance status of what matters most for keeping the system running: power. It focuses on whether the device is powered by its battery and whether it’s connected to a power source. This lets you immediately see if backup power is in use or if a power issue could threaten uptime. That’s why the best choice is Battery Status and Power Source Only. The other descriptions point to more detailed or broader information found in other parts of the system—like a full event log, a map of devices, or a comprehensive list of system items—not the quick, health-at-a-glance snapshot that a Summary Window is designed to provide. If you need deeper details, you’d look to those other areas, but for a concise status of power readiness, the summary of battery and power source is the focus.