312-76 ECCouncil EC-Council Disaster Recovery Professional v3 (EDRP) Free Practice Exam Questions (2025 Updated)

Overall Program Governance in a BCP audit evaluates the plan’s alignment with resilience and continuity goals, including funding adequacy, ensuring it supports organizational objectives effectively.

Option A (Ongoing Program Management):Focuses on day-to-day execution, not funding review.

Option C (Management of Process Changes):Tracks updates, not resilience or funding.

Option D (Overall Testing of the Plan):Validates functionality, not governance.

“Overall Program Governance assesses BCP effectiveness, resilience promotion, and funding balance to ensure sustainable continuity” (Module: Business Continuity Planning, Section: BCP Audit Phases).

ISO 22301:2012 is the international standard for Business Continuity Management Systems (BCMS), specifying requirements for planning, implementing, and auditing a BCP to ensure it meets continuity objectives. An internal audit of a BCP would align with this standard.

Option B (ISO/IEC 27005:2011):Focuses on information security risk management, not BCP auditing.

Option C (ISO/IEC 27031:2011):Addresses ICT continuity, narrower than BCP.

Option D (ISO 22313):A guidance document for ISO 22301, not the auditable standard.

“ISO 22301:2012 defines the auditable framework for BCP, ensuring compliance and effectiveness through internal audits” (Module: Business Continuity Management, Section: Standards and Compliance).

Walkthrough Testing involves team members reviewing the DR plan in a structured discussion to confirm effectiveness, identify bottlenecks, and uncover weaknesses, as Joan did.

Option B (Full Interruption):Live shutdown test, not discussion-based.

Option C (Parallel):Runs recovery alongside primary, not weakness-focused.

Option D (Simulation):Mimics disasters, not confirmation-based.

“Walkthrough Testing engages team members to validate DR plan effectiveness and pinpoint weaknesses through detailed review” (Module: Testing Disaster Recovery Plans, Section: Test Types).

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