Backup Integrity Testing is the process of verifying that backed-up data remains safe, secure, and readable after operations such as updates, restores, or retrievals. This involves checking for corruption, ensuring data consistency, and confirming that the backup can be successfully restored. In disaster recovery, this is a critical step to ensure that backups are reliable when needed.

Option A (Database Authentication): Refers to verifying user access, not data integrity.

Option B (Database Consolidation): Involves merging databases, not testing backup integrity.

Option C (Database Integrity Testing): Focuses on database consistency, not specifically backup verification.

“Backup Integrity Testing ensures that data backups remain uncorrupted and usable post-operation. This process includes validation checks after updates or restores to guarantee recoverability, a key component of data protection strategies” (Module: Data Backup and Recovery, Section: Backup Validation Techniques).

Domain Controller Servers manage user accounts and security policies within a domain (e.g., Active Directory).

Option B (IIS): Web servers, not domain management.

Option C (File Servers): Store files, not security policies.

Option D (Global Catalog): Directory subset, not policy enforcement.

“Domain Controller Servers store account data and enforce domain security policies, central to network management” (Module: Server Management, Section: Server Roles).

System Recovery is the process of restoring a system’s applications and data to a previous state within an acceptable timeframe, as described.

Option A (System Migration): Moving systems, not restoring.

Option B (System Backup): Creating copies, not restoration.

Option C (System Replication): Duplicating data, not recovery.

“System Recovery restores applications and data to a prior state within defined timeframes, ensuring operational continuity post-disaster” (Module: System Recovery, Section: Recovery Processes).

In virtualization (e.g., VMware, Hyper-V), deleting snapshots may not free space if dependent child disks (differencing disks) remain. Deleting these child disks consolidates space, resolving Remus’s issue.

Option B: Deleting the VM database risks data loss, not space recovery.

Option C (Uninstall Hypervisor): Drastic, loses all VMs.

Option D (Shutdown/Restart): Temporary, doesn’t free space.

“Deleting child disks of snapshots in VMs consolidates storage, freeing space when snapshot deletion alone is insufficient” (Module: Virtualization and Recovery, Section: Storage Management).

Recovery Time Objective (RTO) is the target time to restore a system (primary server) after a disruption, here four hours, to avoid exceeding the secondary server’s capacity.

Option A (WRT): Time to resume work post-recovery, not restoration time.

Option C (MTD): Maximum tolerable downtime, broader than RTO.

Option D (RPO): Data loss window, not recovery time.

“RTO defines the acceptable time to restore systems post-disaster, ensuring operations resume before secondary capacity is exceeded” (Module: Recovery Metrics, Section: RTO Definition).

N-Tier Architecture combines client-server principles with multiple layers (e.g., presentation, application, data), enhancing scalability and flexibility.

Option B: Not a standard term.

Option C: Basic client-server, not layered.

Option D: Refers to dependency, not architecture type.

“N-Tier Architecture merges client-server with layered design, supporting robust, scalable systems for DR” (Module: Network Architectures, Section: Architecture Types).

Qualitative Impact assesses non-measurable effects, such as morale, productivity, and reputation, which align with the scenario’s focus on slowed progress and team morale.

Option A (Semi-Qualitative): A hybrid term, less precise here.

Option C (Quantitative): Measurable losses (e.g., financial), not the primary focus.

Option D (Industrial): Too broad, not specific to impact type.

“Qualitative Impact evaluates intangible consequences like morale and operational delays following a breach, critical for BIA” (Module: Business Impact Analysis, Section: Impact Types).

Scalability refers to a system’s ability to handle increased demand by adding resources, such as Joan’s addition of virtual memory to accommodate traffic spikes and reduce delays.

Option A (Transparency): Hides system complexity, not resource expansion.

Option B (Openness): Relates to system accessibility, not capacity.

Option D (Monotonicity): A mathematical property, irrelevant here.

“Scalability enhances system performance by adding resources like memory or nodes to manage increased loads, critical for maintaining service levels” (Module: System Resilience, Section: Scalability Concepts).

Tier 5 in the disaster recovery tier model (e.g., SHARE or IBM models) typically involves backing up data over a Wide Area Network (WAN) to a remote site, providing offsite redundancy with minimal data loss.

Option B (Tier 3): Basic offsite backup, often tape-based, not WAN-specific.

Option C (Tier 0): No backup, not applicable.

Option D (Tier 6): Advanced, often with zero data loss, beyond simple WAN backup.

“Tier 5 utilizes WAN connections for remote data backups, enhancing resilience with offsite replication and moderate RPO” (Module: Disaster Recovery Tiers, Section: Tier Definitions).

Network Attached Storage (NAS) is a centralized storage solution connected to a network, allowing multiple users and devices to access and back up data efficiently. It’s ideal for Tom’s needs across multiple branches, offering centralized storage and simplified backup/recovery processes.

Option A (DAS): Direct Attached Storage is local to a single server, not centralized across a network.

Option C (PAS): This appears to be a typo; no such standard technology exists (possibly meant SAN or similar).

Option D (RAID): Redundant Array of Independent Disks enhances reliability but isn’t a centralized network solution.

EDRP v3 discusses NAS as a scalable, centralized storage option for backup and recovery in distributed environments (Module: Storage Technologies).