RTO measures the maximum amount of downtime a business can tolerate for a given process after a disruption. It sets the target time by which operations must be restored to an acceptable level, guiding what resilience and recovery steps are needed, what resources to have, and how to test the plan. This value is determined during a business impact analysis and is usually considered alongside the Recovery Point Objective, which defines how much data loss is acceptable. It’s about how long operations can be down, not about when an incident is detected, nor about data loss or any timing offsets.

VLANs segment broadcast domains. A VLAN creates a logical grouping where broadcast frames are confined to devices in that same VLAN, even if those devices share the same physical switch with devices in other VLANs. Devices in different VLANs don’t see each other’s broadcasts unless inter-VLAN routing is provided by a router or Layer 3 switch. So, each VLAN has its own separate broadcast domain, which is why the statement about every VLAN forming its own broadcast domain is correct. The other ideas don’t fit: sharing a broadcast domain across multiple VLANs would defeat the purpose of VLANs, and VLANs don’t turn broadcasts into unicast streams within the VLAN.

System imaging is creating a complete snapshot of a computer—the operating system, installed programs, all settings, and user data—that can be saved and later restored to reproduce that exact system state. In Army IT operations, this is highly valuable for rapid provisioning, disaster recovery, and maintaining standardized, secure baselines across many devices. With a full image, you can bare-metal restore a machine to a known-good configuration after hardware failures, malware incidents, or field deployments, minimizing downtime and ensuring consistency across units. This goes beyond backing up individual files or listing installed software, which would not recreate the full operating environment. Cloning only the boot sector wouldn’t capture the full OS, applications, or data needed to restore the system.

OS accessibility features are built into the operating system to help people with disabilities use the device more easily. Screen readers read on-screen text aloud, high-contrast mode sharpens the visual contrast to aid visibility, magnification enlarges portions of the screen for easier reading, and voice control lets you operate the device with spoken commands. These tools specifically address barriers in how information is presented and how the device is controlled, making technology usable for those with vision or motor impairments. The other options focus on security or system maintenance—firewall configuration and antivirus scans protect and manage safety, disk cleanup utilities tidy up storage, and automatic backups protect data. While important, they don’t provide features that assist users with disabilities, so they don’t fit the idea of OS accessibility features.

Mobile Device Management stands for a centralized system that configures, secures, and monitors the mobile devices used in Army operations. It enforces security policies such as strong passwords, device encryption, and automatic locks; controls which apps can be installed; pushes required settings; and can remotely wipe or lock a device if it’s lost or compromised. It also provides an up-to-date inventory of devices, OS versions, and installed applications. For Army mobile devices, this is crucial because it protects sensitive information on endpoints, ensures devices adhere to standard security baselines, enables secure access to networks and resources, and allows rapid response to incidents through remote actions. Other options describe data management, firmware distribution, or performance monitoring, which don’t address the full scope of security, policy enforcement, and device oversight that MDM provides.