Pass the ECCouncil EDRP 312-76 Questions and answers with ExamsMirror

Disaster Recovery (DR) encompasses restoring data, applications, and infrastructure post-disaster, ensuring business operations resume, aligning with the question’s broad scope.

Option A (Data Recovery):Limited to data, not applications or infrastructure.

Option C (Application Recovery):Focuses only on applications.

Option D (Recovery Management):A process, not the ability itself.

“Disaster Recovery restores data, applications, and infrastructure after a disaster, enabling business continuity” (Module: Disaster Recovery Planning, Section: DR Definition).

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).

Server Clustering connects multiple servers into a unified resource, improving scalability and protecting against failures, as Jack implemented.

Option A (Mirroring):Data duplication, not scalability-focused.

Option B (Deduplication):Storage optimization, not clustering.

Option C (Failover):Backup switching, not unified resource.

“Server Clustering unifies computing resources, enhancing scalability and resilience against application and site failures” (Module: Clustering Technologies, Section: Clustering Benefits).

Three-tier architecture in decentralized computing consists of Client (presentation), Application Server (logic), and Database Server (data), as standard layers.

Option A/B/C:Include unrelated or incorrect terms (e.g., Peer-to-Peer).

“Three-tier architecture comprises Client, Application Server, and Database Server, decentralizing functions for scalability” (Module: Network Architectures, Section: Tiered Architectures).

Assessment Scale: In risk management, an assessment scale is used to quantify the impact of a risk. This scale typically includes levels of severity (e.g., low, medium, high) and may assign numerical values to each level.

Recovery Time: Refers to the time it takes to restore systems or operations after a disruption.

Frequency: Refers to how often a risk is likely to occur.

Recovery Scale: While "recovery" is a related term, the scale used to determine the severity of the risk is the "assessment scale".

 RAID 1:Mirroring. Requires a minimum of 2 drives. Provides high redundancy but doesn't inherently increase read/write speed significantly on its own.

 RAID 5:Striping with parity. Requires a minimum of 3 drives. Offers a balance of performance and fault tolerance. Not high fault tolerance as asked.

 RAID 10 (RAID 1+0):A combination of mirroring and striping. Requires a minimum of 4 drives. Provides high performance and good fault tolerance.

 RAID 50 (RAID 5+0):A combination of RAID 5 striping with parity and RAID 0 striping. Requires a minimum of 6 drives. Provides high performance and higher fault tolerance than RAID 5.

A Warm Site is partially equipped with pre-installed hardware and pre-configured settings, requiring some setup time (e.g., a few days) to become operational, fitting Craig’s buffer and RTO needs.

Option A (Cold Sites):Basic facilities, requiring longer setup time.

Option B (Colocation Facilities):Shared data centers, not inherently recovery-focused.

Option D (Hot Sites):Fully operational, no downtime, too robust for Craig’s needs.

“Warm Sites offer pre-installed hardware and configurations, balancing cost and recovery time, suitable for operations tolerating brief downtime” (Module: Alternate Sites, Section: Site Types).

Load Balancing distributes web traffic across multiple servers (Zoe’s three) to optimize performance and prevent overload, as described.

Option A (Point in Time Recovery):Restores data, not traffic management.

Option C (Clustering):Groups servers for redundancy, not load distribution alone.

Option D (High-Availability):Ensures uptime, not necessarily load balancing.

“Load Balancing evenly distributes traffic across servers, enhancing efficiency and preventing crashes under high demand” (Module: System Resilience, Section: Traffic Management).

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).

Availability ensures a system is operational and can serve requests correctly and timely, directly matching the question’s focus.

Option B (Integrity):Ensures data accuracy, not service delivery.

Option C (Nonrepudiation):Prevents denial of actions, not request handling.

Option D (Precaution):A preventive measure, not a system property.

“Availability is the system’s capacity to respond to requests effectively, a cornerstone of disaster recovery and continuity” (Module: System Resilience, Section: Core Properties).