nutanix‐database‐automation‐ncp‐db‐ncp‐db‐65‐exam‐questions_7 - itnett/FTD02H-N GitHub Wiki
Creating a table with 100 “Do Not Answer This” (i.e., distractor or incorrect choices to avoid) and 100 “Choosing This is the Safest Choice” (i.e., the correct or most reliable choices) is a great way to help you identify pitfalls and recognize safer answers during the Nutanix Certified Professional - Database Automation (NCP-DB) exam.
NCP-DB Exam Cheat Sheet: "Do Not Answer" and "Safest Choice" Table
| Question Area | Do Not Answer This (Incorrect Choice) | Choosing This is the Safest Choice (Correct Answer) |
|---|---|---|
| NDB Concepts | "NDB manages databases without any user input." | "NDB automates database provisioning and management." |
| Supported Databases | "NDB supports NoSQL databases only." | "NDB supports MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, MongoDB." |
| Service Level Agreements (SLAs) | "SLAs are optional for NDB-managed databases." | "SLAs define data retention policies, snapshot frequency, and RPO/RTO." |
| Compute Profile | "Compute Profile specifies only storage size." | "Compute Profile defines vCPUs, RAM, and storage configuration." |
| Network Profile | "Network Profile only specifies IP range." | "Network Profile specifies VLAN, IP range, and DNS settings." |
| Software Profile | "Software Profile does not manage patch versions." | "Software Profile manages database engine versions and patches." |
| PITR (Point-in-Time Recovery) | "PITR is always enabled by default." | "PITR requires Continuous Log Retention in SLAs." |
| HA Configurations | "NDB does not support high availability." | "Patroni for PostgreSQL, Replica Sets for MongoDB, Oracle RAC." |
| Time Machine Status | "Time Machine can be ignored if frozen." | "Frozen status means the database was de-registered without removal." |
| Patch Rollback | "Rollback can be done anytime, even without NDB tools." | "Rollback requires patches applied using NDB." |
| Alert Status | "Alerts are only informational." | "Alerts can be Acknowledged or Resolved in the dashboard." |
| Log Catch-Up Interval | "Log catch-up can be set to 5 minutes." | "Minimum log catch-up interval is 15 minutes." |
| Database Engine Compatibility | "NDB supports any database version." | "Use only NDB-supported versions for each database engine." |
| NDB Installation | "NDB installs itself automatically." | "Download the QCOW2/OVA image and configure in Prism Central." |
| Network Configuration | "Dynamic VLANs are best for NDB." | "Use static VLANs managed by NDB for stretched VLANs." |
| Alerts Retention | "Alerts are retained indefinitely." | "Alerts are retained for 180 days by default." |
| Repository Profile | "Repository Profiles are not necessary for patching." | "Configure a Repository Profile to define where OS patches are fetched." |
| PostgreSQL HA Management | "HA is managed manually." | "Use Patroni to manage PostgreSQL HA and failover." |
| Maintenance Window | "No need to schedule patching; apply anytime." | "Create and use a Maintenance Window for automated patching." |
| Data Availability Across Clusters | "Use Data Protection policy." | "Use Recovery Plans to manage Time Machine data availability." |
| Database Restoration | "Replace the entire source volume with a snapshot." | "Copy specific database files to the source volume." |
| Email Notifications for Alerts | "NDB uses SNMP for alert notifications." | "NDB sends alert notifications via email." |
| Snapshot Frequency | "Snapshots can be done only weekly." | "Configure snapshots in the SLA for daily, weekly, or continuous logs." |
| Log Storage During Catch-Up | "Logs are stored on the Database Agent." | "Logs are temporarily stored in the Time Machine." |
| VM Registration Requirements | "No special account privileges needed." | "Login account must be a member of the sysadmin role for SQL Server." |
| Profile Availability | "All profiles are visible by default." | "Set profile status to 'Published' to make it available to all users." |
| Patch Management for Oracle | "Simply install patches without checks." | "Download PSU from Oracle and validate compatibility first." |
| Data Replication Across Clusters | "Manual replication is the only way." | "Use SLAs with cross-cluster replication enabled." |
| MongoDB Patching | "Patch the primary member last." | "Patch the primary member first, triggering a failover." |
| NDB Server Connectivity | "Only port 443 is needed." | "Ensure ports 443 and 9440 are open for NDB communication." |
| Patch Workflow Initialization | "Start by applying patches immediately." | "Validate the patch repository configuration first." |
| Access Control Roles | "Use only the Super Admin for all tasks." | "Create custom roles with specific permissions as needed." |
| Patching Oracle Grid Home | "Only 5GB of space is needed." | "Ensure at least 15GB is available for Oracle Grid home." |
| Log Catch-Up Operation Frequency | "Set the frequency to 10 minutes." | "The shortest log catch-up interval is 15 minutes." |
| Alert Policy Configuration | "All policies are disabled by default." | "All alert policies are enabled by default." |
| Database Recovery Choices | "Always use the latest snapshot." | "Use PITR to minimize data loss to the last possible point." |
| NDB Management Components Deployment | "API Server and Repository VMs can be on different networks." | "API Server must be on the same L2 network as other components." |
| Alert Policy Management | "Alerts are managed per policy basis." | "Alert retention is a global setting, not per policy." |
| Cloning Databases | "Clone databases without a Time Machine." | "Use Time Machine to manage cloning and refresh operations." |
| Patch File Source for NDB Software Profile | "Patch file alone is sufficient." | "Installer package for database software is required." |
| NDB Compute Profile Definition | "Specifies only memory." | "Specifies vCPUs, cores, memory, and storage." |
| Network Profile Scope | "Can only use IPAM-managed VLANs." | "Only static VLANs managed by NDB can be added." |
| SLA Management Scope | "SLAs cover only log retention." | "SLAs define both log and snapshot retention policies." |
| User Roles for NDB API Access | "Use any admin account." | "Use an NDB-specific user account with appropriate permissions." |
| Snapshot Retention in SLAs | "Snapshots are retained for 30 days by default." | "Retention settings in SLAs define snapshot durations." |
| Database Provisioning Order | "Patching happens last." | "Validate profiles, then apply patches before provisioning." |
| Database Cloning Prerequisites | "No specific profiles are needed." | "Compute, Network, and Software profiles must be configured." |
| PITR Configuration Needs | "Snapshots alone are enough." | "Continuous log retention is required for PITR." |
| Alert Notifications Configuration | "Only email notifications are possible." | "Email is the default notification method, but SNMP or API can be used." |
| Alert Policy Retention Settings | "Configured per alert." | "Alert retention is a global setting." |
| NDB Roles and Responsibilities | "Use one role for all tasks." | "Define roles such as Super Admin, DBA, Infrastructure Admin, etc." |
| Maintenance Window Usage | "Used only for database backups." | "Used to automate tasks like OS patching and database patching." |
| HA Patching Process for MongoDB | "Patch all nodes simultaneously." | "Patch the primary node first, then failover and patch secondaries." |
| Time Machine SLAs Exclusion | "Include network configuration." | "Do not include non-recovery related settings in SLAs." |
| Oracle Patching Requirements | "Grid home doesn't need separate space." | "Ensure sufficient space for Grid home before patching." |
| Repository Configuration | "Configure repositories manually each time." | "Use a Repository Profile to manage repository configurations." |
| Database Restore Methods | "Always restore the whole volume." | "Use specific file copy methods to minimize impact." |
Continuing the table for “Do Not Answer This” (incorrect choices) and “Choosing This is the Safest Choice” (correct choices):
| Question Area | Do Not Answer This (Incorrect Choice) | Choosing This is the Safest Choice (Correct Answer) |
|---|---|---|
| Data Availability Across Clusters | "Replicate snapshots manually every day." | "Use SLAs with cross-cluster replication enabled." |
| Database Patch Rollback Prerequisite | "Rollback can be done without any NDB involvement." | "Patches must have been applied using NDB for rollback." |
| Compute Resource Allocation | "Assign random vCPU and RAM values to the Compute Profile." | "Compute Profile defines consistent vCPU, memory, and storage configurations." |
| Alert Configuration Options | "Alerts are static and cannot be configured." | "Alerts can be configured and managed in the NDB dashboard." |
| Multi-Cluster Management | "Only one cluster can be managed by NDB." | "Multiple clusters can be managed by enabling NDB Multi-Cluster." |
| Repository Profile Necessity | "Repository Profile is optional for OS patching." | "Repository Profile must be configured for OS patching." |
| PITR Capability | "PITR can be used without continuous log retention." | "PITR requires SLAs with Continuous Log Retention enabled." |
| Snapshot Scheduling | "Snapshots can only be scheduled monthly." | "Snapshots can be configured for daily, weekly, or continuous logs." |
| Patching Priority for HA Configurations | "Patch the secondary nodes first." | "Patch the primary node first, then perform a failover and patch secondary nodes." |
| Database Clone Refresh Requirements | "No profiles are required for refreshing clones." | "NDB uses snapshots and transaction logs to refresh clones." |
| Alert Status Management | "Alerts are resolved automatically without user intervention." | "Set alerts to Acknowledged or Resolved manually based on their status." |
| Patching NDB Components | "Patching is handled solely through OS tools." | "Use NDB tools and interfaces for patch management to ensure consistency." |
| Failover Configuration for HA | "Failover should be manual to reduce risks." | "Use automated tools like Patroni for PostgreSQL and Replica Sets for MongoDB." |
| NDB Server Deployment Options | "The API Server can be deployed anywhere on the network." | "Deploy the API Server on the same L2 network as other NDB components." |
| Log Retention Configuration | "Logs are retained indefinitely without configuration." | "Configure log retention periods through Service Level Agreements (SLAs)." |
| Network Profile Updates | "Network profiles do not need to be updated after initial setup." | "Regularly update Network Profiles to reflect any changes in VLAN or IP ranges." |
| Alert Policy Defaults | "All alert policies are disabled by default." | "All alert policies are enabled by default; review and adjust as needed." |
| Database Access Management | "Any user can access databases without restrictions." | "Use Access Control to assign appropriate roles and restrict access." |
| Repository Configuration for Updates | "Use random repositories for updates." | "Configure a trusted Repository Profile for reliable patch downloads." |
| Cloning Databases Without Time Machine | "Clone databases directly from production without a Time Machine." | "Use Time Machine to manage cloning and refresh operations." |
| Patch Management and Planning | "Apply patches without testing." | "Test patches in a non-production environment before deploying." |
| Snapshots and Continuous Logs | "Only snapshots are necessary for backups." | "Use both snapshots and continuous log retention for comprehensive backups." |
| Oracle Patching Requirements | "Ignore Oracle's Grid home space requirements." | "Ensure sufficient space (15GB) for Oracle Grid home." |
| Database Registration for PostgreSQL | "No specific steps required for PostgreSQL registration." | "Create a Software Profile, Network Profile, and Compute Profile before registering." |
| Alert Management Dashboard | "Alerts automatically adjust retention settings." | "Manually configure alert retention settings globally in the dashboard." |
| Database Availability During Upgrades | "Shutdown databases before applying upgrades." | "Use rolling upgrades to keep databases available during patching." |
| NDB Agent and Server Configuration | "NDB Agent and Server can be configured independently." | "Ensure NDB Agent and Server are configured to communicate effectively across clusters." |
| Database Restoration Methods | "Restore the entire database volume whenever possible." | "Restore specific database files to avoid affecting other databases on the volume." |
| Database Migration Between Clusters | "Migrate databases manually between clusters." | "Use NDB tools and policies for seamless database migration." |
| High Availability Best Practices | "Always use manual failover methods." | "Leverage NDB’s HA tools like Patroni and Replica Sets for automated failover." |
| Data Replication and Retention | "Replicate data randomly between clusters." | "Use SLAs to define specific replication policies and retention periods." |
| PostgreSQL Cluster State Management | "Manage PostgreSQL cluster state manually." | "Use etcd and Patroni to automatically manage PostgreSQL cluster state." |
| Patching Policies for Multi-Cluster Setup | "Apply patches simultaneously across all clusters." | "Schedule and apply patches based on cluster priorities and dependencies." |
| User Account Management | "Use default user accounts for all operations." | "Create specific user accounts with defined roles for security and management." |
| Continuous Log Retention Policy | "Set continuous log retention for all databases." | "Apply continuous log retention selectively based on recovery needs." |
| Database Engine Versions | "Update to the latest database engine versions immediately." | "Verify compatibility and test new versions before updating in production." |
| Log Catch-Up Intervals | "Set log catch-up intervals to any value under 10 minutes." | "Minimum configurable log catch-up interval is 15 minutes." |
| Snapshot Frequency in SLAs | "Snapshots can be set to random frequencies." | "Define snapshot frequencies based on business requirements in SLAs." |
| Database Backup Configuration | "Rely solely on manual backups." | "Use automated backups with Time Machine for reliable recovery." |
| Access Control Setup | "Assign all users to the Super Admin role." | "Create custom roles with specific privileges to control access." |
| Data Availability Planning | "Keep default settings for all availability configurations." | "Customize availability settings to meet specific RPO/RTO objectives." |
| Patch Validation Steps | "Skip validation if patches are from trusted sources." | "Always validate patches in a non-production environment first." |
| Database Configuration for New Deployments | "Deploy databases without setting up profiles." | "Configure Compute, Network, and Software Profiles before deployment." |
| Database Restoration Best Practices | "Restore databases immediately without planning." | "Plan restoration based on snapshots and PITR to minimize data loss." |
| Alert Severity Configuration | "Set all alerts to the same severity level." | "Customize alert severities based on the impact and criticality." |
| Network Security Configuration | "Use default security settings for all networks." | "Review and update network security settings regularly for each cluster." |
| Database Patching Sequence | "Patch databases in random order." | "Follow a structured patching order based on database roles and dependencies." |
| Cloning Process Management | "Use the same clone for all purposes." | "Customize clones for different environments and purposes." |
| Log Storage Management | "Store logs indefinitely without a plan." | "Define log storage duration in SLAs to optimize storage usage." |
| Role Assignments for Maintenance | "Only the DBA role should manage maintenance tasks." | "Assign roles based on the specific tasks and responsibilities needed." |
| Patching Oracle Instances | "Patch Oracle instances without stopping services." | "Follow Oracle best practices for patching, including stopping services as needed." |
| Database Registration Requirements | "Register databases without checking connectivity." | "Ensure connectivity through required ports (e.g., 9440, 5985) before registration." |
| Database Operations Strategy | "Operate databases manually without automation tools." | "Use NDB automation tools to streamline database operations." |
| Database Refresh Requirements | "Refresh databases only once." | "Regularly refresh databases to ensure data consistency and performance." |
| Cluster Configuration Management | "Configure clusters without considering interdependencies." | "Analyze and configure clusters based on their dependencies and roles." |
| Log Backup Retention Settings | "Retain logs indefinitely by default." | "Set specific retention periods for log backups in SLAs." |
| Access Configuration for New Users | "Grant all new users admin-level access." | "Assign minimal necessary privileges to new users for security." |