NCP-BC
75 questions 120 min Pass: 3000 / 6000 Official Nutanix Website Nutanix University
About this course
Target exam: Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5
Software under test:
- Nutanix Disaster Recovery pc.7.5
- Prism Central pc.7.5
Exam facts:
- 75 multiple-choice / multiple-response questions
- 120 minutes
- passing score 3000 (scaled 1000–6000)
- English & Japanese
- $200 USD
- valid 3 years
Delivered in 4 lots (one per blueprint Section). Each lot is a full course chapter set plus its share of the 300-question practice bank - all in English, grounded in the official Nutanix reference corpus.
How this course is built
Each chapter follows the same structure, so it doubles as a study guide and a revision checklist:
- Objective & exam relevance - the blueprint objective(s) the chapter maps to.
- Core concepts - explained from the ground up, version-accurate to Nutanix DR pc.7.5 / PC pc.7.5.
- How-to / workflows - the administrative tasks the exam expects you to perform.
- Requirements, limits & gotchas - the numbers and constraints exams love to test.
- Key takeaways - a condensed revision box.
- Source references - the exact corpus documents the chapter is grounded in.
The practice questions: 4 options, one correct answer (with a subset of multiple-response "select TWO / THREE" items to match the real exam), every answer explained, each tagged with its objective. Any figure that could not be confirmed against the corpus is flagged ⚠️ rather than invented.
Preparation course
Log in to start & track your progress
Part I - Interpret and Configure BCDR Requirements
1 BCDR Schedule Prerequisites Obj 1.1
- 1.1 Relate RPO to a DR configuration (Async / NearSync / SyncRep / Metro)
- 1.2 Replication schedule details & transition behavior
- 1.3 Relate resource requirements to a DR configuration (CVM CPU/memory/SSD/node storage)
- 1.4 Relate system maximums (VMs per category, VMs per Protection Policy)
- 1.5 Determine replication requirements & prerequisites
- 1.6 Determine use and prerequisites for app-consistent snapshots
- 1.7 Determine the Independent Witness Service VM
2 Hardening a BCDR Solution Obj 1.2
- 2.1 Role-Based Access Control (RBAC) for Disaster Recovery operations
- 2.2 Synchronizing Flow Network Security policies across paired AZs
- 2.3 Network segmentation for DR traffic
- 2.4 Secure Snapshots via Approval Policy
3 Configuring Recovery Plans Obj 1.3
- 3.1 Recovery Plan fundamentals: purpose, stages, creation
- 3.2 Recovery Plan networking: production vs test networks, mappings
- 3.3 Configuration parameters by topology (scale-out vs single PC; Async/NearSync/Sync)
- 3.4 Entity synchronization between paired Availability Zones
- 3.5 Affinity / anti-affinity for DR: VM-Host and VM-VM; PC vs PD
4 Advanced BCDR Configurations: MST & NC2 Obj 1.4
- 4.1 DR using Multicloud Snapshot Technology (MST): zero-compute vs pilot-light
- 4.2 MST DR limitations and prerequisites
- 4.3 DR between on-prem AZ and Nutanix Cloud AZ: requirements
- 4.4 NC2 networking: Layer 2 subnet stretching
5 Network & Storage for BCDR Obj 1.5
- 5.1 Virtual network specifications for Disaster Recovery
- 5.2 Storage needs at remote sites: calculating exclusive usage
- 5.3 Configuring containers to ensure correct snapshot placement
- 5.4 Choosing the DR storage approach: MST vs pilot light vs bare metal
- 5.5 Conditions and limitations for multi-site configurations
Part II - Test BCDR Solutions
6 Testing DR Failover Obj 2.1
- 6.1 Planned failover (Async/NearSync/Sync): when and how; failback
- 6.2 Unplanned failover run as a test; failback
- 6.3 Test failover without impacting production workloads
- 6.4 Validating a recovery plan: the points checked
7 Testing Throughput & Connectivity Between Sites Obj 2.2
- 7.1 Verifying a VPN connection
- 7.2 DR Service Reachability Check (NCC)
- 7.3 Ports that must remain open: Disaster Recovery vs Protection Domains
- 7.4 Bandwidth throttling with PD-based DR
- 7.5 Logs and native tools; Metro Availability Witness; AZ pairing and Cerebro VIP
Part III - Perform BCDR Tasks
8 Self-Service Restore (SSR) Obj 3.1
- 8.1 SSR requirements and limitations
- 8.2 Enabling self-service data restore
- 8.3 Self-Service Restore for Windows VMs
- 8.4 Self-Service Restore for Linux VMs
9 Restore from a Recovery Point or Snapshot Obj 3.2
- 9.1 Cloning from a recovery point
- 9.2 Reverting a snapshot
- 9.3 Restoring a single VM/entity in PD-based DR
- 9.4 Manual recovery of DR entities
- 9.5 Special cases: vGPU-enabled VMs and SR-IOV VMs
10 Executing a Recovery Plan for an Outage Obj 3.3
- 10.1 PD "Migrate" task: when to use; tasks generated
- 10.2 PD "Activate" task: when to use; tasks generated
- 10.3 Choosing the recovery plan option: planned vs unplanned
- 10.4 Network failure handling during failover
- 10.5 Recovering Prism Central from continuous backup; pausing Synchronous Replication
11 Post-Failover Cleanup Obj 3.4
- 11.1 Determining when a cleanup is required
- 11.2 Cleaning up test entities
- 11.3 Post-failover configuration changes
- 11.4 Multipathing limitations in the DRaaS context
12 Migrating Legacy PDs to Protection Policies Obj 3.5
- 12.1 When to migrate from PD-based to PC-based DR
- 12.2 Migration process: Protection Domains to protection policies
- 12.3 Moving VMs from a Protection Domain to a Category
- 12.4 Caveats, limitations and planning for PD to PC migration
Part IV - Troubleshoot BCDR Failures
13 Troubleshooting Network Issues Causing DR Failure Obj 4.1
- 13.1 Troubleshooting replication bandwidth issues
- 13.2 VM connectivity post-failover: network mapping, IP not retained, NGT
- 13.3 Recovery Plan network validation errors
- 13.4 DR network port mappings and network segmentation
- 13.5 IP-reservation failure on managed network; Skipped Replication (A1113) alert
14 Diagnosing Failed Replications Obj 4.2
- 14.1 Replication failures caused by networking issues
- 14.2 Replication failures caused by storage issues (container space, RF2 to RF3)
- 14.3 Replication failures caused by permission issues
- 14.4 NearSync limitations; pausing Synchronous Replication
- 14.5 Asynchronous replication sizing; node usage and health statistics
15 Troubleshooting Third-Party Backup Failures Obj 4.3
- 15.1 Third-party user-permission issues
- 15.2 App-consistent snapshot failures: NGT, link false, networking
- 15.3 Storage bloat causes: deleted VM, distant expiration
- 15.4 Known issues: vTPM VM backup failures; iscsiadm timeout
16 Troubleshooting DR Setup Issues Obj 4.4
- 16.1 Troubleshooting misconfigured schedules (backup_schedule_check)
- 16.2 Troubleshooting network setup: firewall, connectivity, throughput
- 16.3 Diagnosing misconfigured users/roles
- 16.4 Recovery plan stages; Async/NearSync limits; CCLM limitations
- 16.5 Witness inside PC; Volume Group DR specs; vSphere Metro Storage Cluster
Training
Source corpus mapping
| Document | Primary objectives served |
|---|---|
| ds-ebg-ncp-bc (Exam Blueprint Guide) | Structure / weighting (all) |
| Disaster-Recovery-DRaaS-Guide vpc_7.5 | 1.1–1.5, 2.1, 3.1, 3.2, 3.4, 3.5, 4.1, 4.2 |
| Prism-Element-Data-Protection-Guide v7.5 | 1.1, 2.2, 3.2, 3.3, 4.2, 4.4 |
| Web-Console-Guide-Prism v7.5 | 1.1, 1.5, 2.2, 4.2 |
| Prism-Central-Guide vpc_7.5 | 1.2, 1.3, 3.1 |
| BP-2005-Data-Protection | 1.1, 1.5, 4.2 |
| BP-2009-Metro-Availability | 2.2, 4.4 (Metro) |
| Nutanix-Cloud-Clusters-Azure (NC2) | 1.4 (NC2 / L2 stretch) |
| Recovery-Plan-Validation-Errors-Guide vpc_7.5 | 2.1, 4.1 |
| KB - Recovery Plan fails to reserve an IP (managed network) | 4.1 |
| Document | Primary objectives served |
|---|---|
| KB - Alert A1113 Skipped Replication Of Snapshot | 4.1 |
| NCC - dr_service_reachability_check | 2.2 |
| NCC - backup_schedule_check | 4.4 |
| KB - DR: Pairing an Availability Zone (AZ) failure | 2.2, 4.1 |
| KB - Metro outage due to unstable VIP during a Cerebro leader change | 2.2 |
| KB - Space requirements for RF2 → RF3 container upgrade | 4.2 |
| KB - Unable to backup vTPM enabled VMs with third-party vendors | 4.3 |
| KB - 3rd party backups fail with iscsiadm sendtargets timeout | 4.3 |
| KB - Move VMs from Protection Domain to Category | 3.5 |
| Nutanix Guest Tools (NGT) reference | 1.1, 3.1, 4.1, 4.3 |