All alarm activations should be recorded in the blotter, including actual, accidental, or malfunction activations. Keeping a complete log creates an auditable history of every event, which is essential for investigations, identifying trends, and ensuring accountability. Recording every activation also helps distinguish real emergencies from false alarms and supports performance monitoring and QA. If only actual alarms were logged, or only accidental ones, or none at all, the record would be incomplete and could hinder proper review and compliance.

Focus on where the cameras are placed in the diagram. The cameras mounted on top of Building 47 are the ones drawn directly on the roof line of that building—the two rooftop icons perched along the building’s edge. That rooftop placement is unique to Building 47 in the diagram, so selecting the pair on the roof matches the description in the question. The other options point to cameras on different parts of the map (on other buildings or at lower levels) and aren’t on the roof of Building 47, so they don’t fit.

Video verification verifies an alarm by reviewing footage from the site to confirm whether an incident is real before dispatching responders. This approach is only workable when the customer has given consent for video monitoring and the site has an accessible video feed that the monitoring center can view. Without consent or a usable video feed, you can’t perform pre-dispatch video verification, so alternative checks (like telemetry or audio) would be used, and verification after dispatch would not meet the pre-dispatch requirement. This method helps reduce false dispatches and provides objective evidence from the scene.

Redundant data storage means keeping copies of logs and incident records in more than one place so data survives outages and remains accessible for investigations and audits. In alarm monitoring QC, you need to preserve every event and response for performance checks, regulatory requirements, and post-incident analysis. If data lives in a single location, a hardware failure, power outage, natural disaster, or ransomware could erase critical records, breaking your ability to review what happened or prove compliance. Storing data across on-site, off-site, and cloud locations provides robust protection. On-site storage allows fast access for daily operations and quick retrieval during routine reviews. Off-site storage guards against local disasters, ensuring you still have a copy if the primary site is compromised. Cloud storage adds scalable, geographically diverse redundancy and easier remote access for audits, while supporting long-term retention and versioning. Together, these multiple storage locations maintain data continuity during outages and create solid evidence trails for audits and investigations. A single location with local backups is vulnerable to losing data in a site-wide incident. Off-site backups alone may protect against some risks but can limit rapid access during outages. Cloud-only storage reduces local risk but introduces dependency on a third-party provider and potential access or regulatory concerns. The multiple-location approach offers resilience, accessibility, and auditability that a single-storage strategy cannot.