Infoblox NIOS-DDI-Expert Practice Exams
Last updated on Oct 22,2026- Exam Code: NIOS-DDI-Expert
- Exam Name: Infoblox Qualified NIOS DDI Expert - INE
- Certification Provider: Infoblox
- Latest update: Oct 22,2026
Question #71
To revert to an older version of code, the user must be able to upgrade from that older version of code to the code the Infoblox device is currently running.
- A . True
- B . False
Correct Answer: A
A
Explanation:
Comprehensive and Detailed In-Depth
Reverting in NIOS (Grid > Upgrade > Revert) rolls back to the previous version:
Requirement: The older version must be compatible with an upgrade path to the current version. NIOS stores the prior image and database, ensuring revertibility if the upgrade was valid (e.g., 8.6.1 to 8.6.2).
Why True: If the older version couldn’t upgrade to the current one (e.g., due to major schema changes or skipped versions), revert wouldn’t be offered―NIOS enforces this compatibility.
Practical Example: In an INE lab, you’d upgrade from 8.6.1 to 8.6.2, revert to 8.6.1, and troubleshoot DNS continuity, verifying this rule.
Reference: Infoblox NIOS Administrator Guide C Software Revert; INE Course Content: NIOS DDI Grid Troubleshooting.
A
Explanation:
Comprehensive and Detailed In-Depth
Reverting in NIOS (Grid > Upgrade > Revert) rolls back to the previous version:
Requirement: The older version must be compatible with an upgrade path to the current version. NIOS stores the prior image and database, ensuring revertibility if the upgrade was valid (e.g., 8.6.1 to 8.6.2).
Why True: If the older version couldn’t upgrade to the current one (e.g., due to major schema changes or skipped versions), revert wouldn’t be offered―NIOS enforces this compatibility.
Practical Example: In an INE lab, you’d upgrade from 8.6.1 to 8.6.2, revert to 8.6.1, and troubleshoot DNS continuity, verifying this rule.
Reference: Infoblox NIOS Administrator Guide C Software Revert; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #72
The Infoblox appliance has an LCD panel. To join a node to a Grid, the administrator should use the LCD panel at the front of the Infoblox appliance.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Infoblox physical appliances (e.g., IB-1400 series) feature an LCD panel for basic configuration, but its role in Grid joining is limited:
LCD Capabilities: The panel allows setting IP addresses, hostnames, and basic network parameters (e.g., via arrow keys and menu options). It’s useful for initial setup or recovery.
Grid Joining Process: Joining a node to a Grid requires:
Configuring the node’s IP and Grid Master IP.
Authenticating with Grid credentials (e.g., shared secret).
Initiating the join via Grid Manager (Grid > Members > Add) or CLI (set membership).
Why False: The LCD can set preliminary network settings, but full Grid joining―specifying the Grid Master, VPN details, and completing sync―requires CLI or GUI access. The panel lacks the interface for these steps.
Practical Example: In an INE lab, you’d use the LCD to set an IP on a new node, then SSH to run set membership and join the Grid, troubleshooting connectivity via logs.
Reference: Infoblox NIOS Administrator Guide C LCD Panel; INE Course Content: NIOS DDI Grid Deployment.
B
Explanation:
Comprehensive and Detailed In-Depth
Infoblox physical appliances (e.g., IB-1400 series) feature an LCD panel for basic configuration, but its role in Grid joining is limited:
LCD Capabilities: The panel allows setting IP addresses, hostnames, and basic network parameters (e.g., via arrow keys and menu options). It’s useful for initial setup or recovery.
Grid Joining Process: Joining a node to a Grid requires:
Configuring the node’s IP and Grid Master IP.
Authenticating with Grid credentials (e.g., shared secret).
Initiating the join via Grid Manager (Grid > Members > Add) or CLI (set membership).
Why False: The LCD can set preliminary network settings, but full Grid joining―specifying the Grid Master, VPN details, and completing sync―requires CLI or GUI access. The panel lacks the interface for these steps.
Practical Example: In an INE lab, you’d use the LCD to set an IP on a new node, then SSH to run set membership and join the Grid, troubleshooting connectivity via logs.
Reference: Infoblox NIOS Administrator Guide C LCD Panel; INE Course Content: NIOS DDI Grid Deployment.
Question #73
A Grid member in a DHCP Failover pair is in the PARTNER-DOWN state.
What does this mean?
- A . The member has lost contact with its peer
- B . An administrator put the member in this state to indicate the member’s peer is down
- C . An administrator put the member in this state to indicate the member is down and the member’s peer will take over
- D . This member is malfunctioning and the member’s peer must take over assignments
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
PARTNER-DOWN in DHCP Failover:
B: Admin manually sets this state (Grid > DHCP > Failover > Edit) to signal the peer is down (e.g., powered off), giving the member full pool control. Correct.
A: Loss of contact is COMMUNICATIONS-INTERRUPTED―PARTNER-DOWN is deliberate. Incorrect.
C: Indicates the member is down―opposite of intent. Incorrect.
D: Malfunction implies automatic state―PARTNER-DOWN is manual. Incorrect.
Practical Example: In an INE lab, set PARTNER-DOWN, verify full lease control, and troubleshoot sync resumption.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover States; INE Course Content: NIOS DDI DHCP Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
PARTNER-DOWN in DHCP Failover:
B: Admin manually sets this state (Grid > DHCP > Failover > Edit) to signal the peer is down (e.g., powered off), giving the member full pool control. Correct.
A: Loss of contact is COMMUNICATIONS-INTERRUPTED―PARTNER-DOWN is deliberate. Incorrect.
C: Indicates the member is down―opposite of intent. Incorrect.
D: Malfunction implies automatic state―PARTNER-DOWN is manual. Incorrect.
Practical Example: In an INE lab, set PARTNER-DOWN, verify full lease control, and troubleshoot sync resumption.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover States; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #74
How are Workflow Approval notifications delivered in NIOS?
- A . Via SMS
- B . Via push notifications
- C . Via email
- D . Via in-app notifications
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
Workflow Approval in NIOS enforces change control with notifications:
Mechanism: When a requester submits a change (e.g., new DNS record), approvers are notified via email, configured in Grid Properties (Grid > Grid Manager > Grid Properties > Email).
Details: SMTP server settings (e.g., IP, port, credentials) must be defined for delivery. No other methods are natively supported.
Options:
A: SMS isn’t supported―requires external integration. Incorrect.
B: Push notifications aren’t part of NIOS GUI or mobile app (none exists). Incorrect.
C: Email is the documented, sole method. Correct.
D: In-app notifications don’t exist―Grid Manager relies on email. Incorrect.
Practical Example: In an INE lab, you’d configure an SMTP server, request a zone change, and troubleshoot email delivery failures for approval, testing Grid management.
Reference: Infoblox NIOS Administrator Guide C Workflow Approval Notifications; INE Course
Objective: NIOS DDI Grid Deployment.
C
Explanation:
Comprehensive and Detailed In-Depth
Workflow Approval in NIOS enforces change control with notifications:
Mechanism: When a requester submits a change (e.g., new DNS record), approvers are notified via email, configured in Grid Properties (Grid > Grid Manager > Grid Properties > Email).
Details: SMTP server settings (e.g., IP, port, credentials) must be defined for delivery. No other methods are natively supported.
Options:
A: SMS isn’t supported―requires external integration. Incorrect.
B: Push notifications aren’t part of NIOS GUI or mobile app (none exists). Incorrect.
C: Email is the documented, sole method. Correct.
D: In-app notifications don’t exist―Grid Manager relies on email. Incorrect.
Practical Example: In an INE lab, you’d configure an SMTP server, request a zone change, and troubleshoot email delivery failures for approval, testing Grid management.
Reference: Infoblox NIOS Administrator Guide C Workflow Approval Notifications; INE Course
Objective: NIOS DDI Grid Deployment.
Question #75
You need to reset the database on a Grid member and disconnect it from the Grid, but you would like it to preserve its current network settings.
What command can you use to do this?
- A . reset all
- B . reset database
- C . reset member
- D . It is possible to reset without losing network settings
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Resetting a Grid member’s database while retaining network settings requires a targeted CLI command:
Requirements: Clear DNS/DHCP/Grid data, disconnect from the Grid, keep IP/hostname for reconnection or standalone use.
Commands:
reset database: Wipes the NIOS database (zones, leases, Grid membership), leaving network settings (IP, gateway, etc.) intact. The member becomes standalone, requiring rejoining if needed.
set factory: Full reset to factory defaults, erasing everything (database, network, licenses).
Options:
A (reset all): Not a valid command (see Q28). Incorrect.
B (reset database): Meets all criteria―clears database, disconnects, preserves network. Correct.
C (reset member): Not a specific CLI command; vague term. Incorrect.
D: Misinterprets the question as a statement―it’s possible with B, but this isn’t a command. Incorrect.
Practical Example: In an INE lab, you’d run reset database on a test member, verify its IP persists via show network, and troubleshoot rejoining the Grid.
Reference: Infoblox NIOS CLI Reference Guide C Reset Commands; INE Course Content: NIOS DDI Grid Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
Resetting a Grid member’s database while retaining network settings requires a targeted CLI command:
Requirements: Clear DNS/DHCP/Grid data, disconnect from the Grid, keep IP/hostname for reconnection or standalone use.
Commands:
reset database: Wipes the NIOS database (zones, leases, Grid membership), leaving network settings (IP, gateway, etc.) intact. The member becomes standalone, requiring rejoining if needed.
set factory: Full reset to factory defaults, erasing everything (database, network, licenses).
Options:
A (reset all): Not a valid command (see Q28). Incorrect.
B (reset database): Meets all criteria―clears database, disconnects, preserves network. Correct.
C (reset member): Not a specific CLI command; vague term. Incorrect.
D: Misinterprets the question as a statement―it’s possible with B, but this isn’t a command. Incorrect.
Practical Example: In an INE lab, you’d run reset database on a test member, verify its IP persists via show network, and troubleshoot rejoining the Grid.
Reference: Infoblox NIOS CLI Reference Guide C Reset Commands; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #76
You have DHCPv4 failover, and one of the peers lost power, triggering the COMMUNICATIONS-INTERRUPTED state. Power will be restored in 1 hour. In the meantime, there are several new devices coming online.
What must you do to ensure DHCP service runs smoothly for everyone?
- A . Contact Infoblox Support and be ready to place the remaining peer or member into PARTNER-DOWN
- B . Immediately increase lease time on affected networks to 4 hours or more
- C . Change DHCP relay or router configuration to only relay to the remaining peer or member
- D . Nothing. All existing clients can renew with the remaining peer. The remaining peer can likely service a few new clients even with the reduced new client capacity
Correct Answer: D
D
Explanation:
Comprehensive and Detailed In-Depth
DHCP Failover in NIOS ensures redundancy between two peers (primary and secondary). When one peer loses power, the state shifts to COMMUNICATIONS-INTERRUPTED, meaning the remaining peer continues serving DHCP but with limited capacity for new leases. Let’s analyze:
Failover Mechanics: In NORMAL state, peers split the lease pool (e.g., 50/50 or custom split). In COMMUNICATIONS-INTERRUPTED, the surviving peer:
Renews leases for existing clients (using its synced database).
Assigns new leases from its portion of the pool, with reduced capacity (e.g., MCLT―Maximum Client Lead Time―limits new lease duration).
Scenario: Power is out for 1 hour, and new devices are joining. The remaining peer can handle renewals and has some new lease capacity (depending on pool size and MCLT, typically 1 hour by default).
Options:
A: Contacting support and forcing PARTNER-DOWN gives the surviving peer full pool access, but it’s unnecessary for a 1-hour outage with "a few" new clients. Overkill.
B: Increasing lease time (e.g., to 4 hours) prevents lease expiration but doesn’t address new client capacity and requires manual reversion. Unneeded complexity.
C: Reconfiguring relays to point only to the surviving peer is redundant―it’s already receiving requests―and risks misconfiguration. Incorrect.
D: Doing nothing leverages the failover design: existing clients renew seamlessly, and the remaining peer services new clients within its capacity. Correct for this short-term, low-impact scenario.
Practical Example: In an INE lab, you’d monitor the surviving peer’s lease usage (via Grid Manager > DHCP > Leases) and confirm it handles the load, a key troubleshooting skill.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
D
Explanation:
Comprehensive and Detailed In-Depth
DHCP Failover in NIOS ensures redundancy between two peers (primary and secondary). When one peer loses power, the state shifts to COMMUNICATIONS-INTERRUPTED, meaning the remaining peer continues serving DHCP but with limited capacity for new leases. Let’s analyze:
Failover Mechanics: In NORMAL state, peers split the lease pool (e.g., 50/50 or custom split). In COMMUNICATIONS-INTERRUPTED, the surviving peer:
Renews leases for existing clients (using its synced database).
Assigns new leases from its portion of the pool, with reduced capacity (e.g., MCLT―Maximum Client Lead Time―limits new lease duration).
Scenario: Power is out for 1 hour, and new devices are joining. The remaining peer can handle renewals and has some new lease capacity (depending on pool size and MCLT, typically 1 hour by default).
Options:
A: Contacting support and forcing PARTNER-DOWN gives the surviving peer full pool access, but it’s unnecessary for a 1-hour outage with "a few" new clients. Overkill.
B: Increasing lease time (e.g., to 4 hours) prevents lease expiration but doesn’t address new client capacity and requires manual reversion. Unneeded complexity.
C: Reconfiguring relays to point only to the surviving peer is redundant―it’s already receiving requests―and risks misconfiguration. Incorrect.
D: Doing nothing leverages the failover design: existing clients renew seamlessly, and the remaining peer services new clients within its capacity. Correct for this short-term, low-impact scenario.
Practical Example: In an INE lab, you’d monitor the surviving peer’s lease usage (via Grid Manager > DHCP > Leases) and confirm it handles the load, a key troubleshooting skill.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #77
Which of the following transport protocols are supported by scheduled NIOS Grid Backup? (Select all that apply.)
- A . SFTP
- B . SCP
- C . FTP
- D . HTTPS
Correct Answer: A, B, C, D
A, B, C, D
Explanation:
Comprehensive and Detailed In-Depth
NIOS Grid Backup allows scheduled exports of the configuration database (DNS, DHCP, Grid settings)
to an external server.
Supported protocols ensure flexibility and security:
A (SFTP): Secure File Transfer Protocol (SSH-based) is supported for encrypted backups to remote servers (port 22). Widely used for secure transfers. Correct.
B (SCP): Secure Copy Protocol (also SSH-based) is supported, offering a simple, secure file transfer option (port 22). Correct.
C (FTP): File Transfer Protocol (unencrypted, port 21) is supported for legacy systems, though less secure. Correct.
D (HTTPS): Web-based secure transfer (port 443) is supported, allowing backups to HTTP servers with SSL/TLS encryption. Correct.
Setup: In Grid Manager (Grid > Grid Manager > Backup), you configure the protocol, server IP, and credentials.
Practical Example: In an INE lab, you’d schedule a backup using SFTP to a remote server, test restoration, and troubleshoot connectivity issues, reinforcing Grid deployment skills.
Note: All four are explicitly supported per NIOS documentation, making this a comprehensive list.
Reference: Infoblox NIOS Administrator Guide C Grid Backup; INE Course Objective: NIOS DDI Grid Deployment.
A, B, C, D
Explanation:
Comprehensive and Detailed In-Depth
NIOS Grid Backup allows scheduled exports of the configuration database (DNS, DHCP, Grid settings)
to an external server.
Supported protocols ensure flexibility and security:
A (SFTP): Secure File Transfer Protocol (SSH-based) is supported for encrypted backups to remote servers (port 22). Widely used for secure transfers. Correct.
B (SCP): Secure Copy Protocol (also SSH-based) is supported, offering a simple, secure file transfer option (port 22). Correct.
C (FTP): File Transfer Protocol (unencrypted, port 21) is supported for legacy systems, though less secure. Correct.
D (HTTPS): Web-based secure transfer (port 443) is supported, allowing backups to HTTP servers with SSL/TLS encryption. Correct.
Setup: In Grid Manager (Grid > Grid Manager > Backup), you configure the protocol, server IP, and credentials.
Practical Example: In an INE lab, you’d schedule a backup using SFTP to a remote server, test restoration, and troubleshoot connectivity issues, reinforcing Grid deployment skills.
Note: All four are explicitly supported per NIOS documentation, making this a comprehensive list.
Reference: Infoblox NIOS Administrator Guide C Grid Backup; INE Course Objective: NIOS DDI Grid Deployment.
Question #78
The only way to get access to all of the possible diagnostic CLI commands is to connect a serial cable to the serial port of the Infoblox appliance.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Infoblox NIOS provides a Command Line Interface (CLI) for diagnostics, accessible via multiple methods, not solely the serial port:
Serial Console: Connecting a serial cable (9600 baud) to the appliance’s serial port grants CLI access, useful for physical troubleshooting or when network access is down. It provides full diagnostic commands (e.g., "show process," "set debug").
SSH: Remote access via SSH (default port 22) to the appliance’s management IP offers the same CLI, assuming network connectivity and credentials are available. This is equally comprehensive.
Key Point: Both methods provide access to all diagnostic commands (e.g., "show log," "reset database"), debunking the "only way" claim. The serial port is just one option, often used in failure scenarios (e.g., network outage), but SSH is more common day-to-day.
INE Context: The course covers CLI troubleshooting, emphasizing both serial and SSH access for Grid diagnostics, making this a practical distinction.
Why False: The statement’s exclusivity is incorrect―multiple access methods exist.
Reference: Infoblox NIOS Administrator Guide C CLI Access; INE Course Content: NIOS DDI Grid Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
Infoblox NIOS provides a Command Line Interface (CLI) for diagnostics, accessible via multiple methods, not solely the serial port:
Serial Console: Connecting a serial cable (9600 baud) to the appliance’s serial port grants CLI access, useful for physical troubleshooting or when network access is down. It provides full diagnostic commands (e.g., "show process," "set debug").
SSH: Remote access via SSH (default port 22) to the appliance’s management IP offers the same CLI, assuming network connectivity and credentials are available. This is equally comprehensive.
Key Point: Both methods provide access to all diagnostic commands (e.g., "show log," "reset database"), debunking the "only way" claim. The serial port is just one option, often used in failure scenarios (e.g., network outage), but SSH is more common day-to-day.
INE Context: The course covers CLI troubleshooting, emphasizing both serial and SSH access for Grid diagnostics, making this a practical distinction.
Why False: The statement’s exclusivity is incorrect―multiple access methods exist.
Reference: Infoblox NIOS Administrator Guide C CLI Access; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #79
What command clears the NIOS database but preserves system logs and other licensed features such as reporting?
- A . reset all
- B . reset database
- C . reset config
- D . reset all licenses
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Clearing the NIOS database requires a precise CLI command:
B (reset database): Wipes DNS zones, DHCP leases, and Grid membership, but retains:
System logs (e.g., syslog, infoblox.log).
Licenses (e.g., reporting, DNSSEC).
Network settings (IP, hostname). Correct.
A: “reset all” isn’t valid (see Q28). Incorrect.
C: “reset config” isn’t a command―closest is set factory, which wipes everything. Incorrect.
D: reset all licenses clears licenses only, not the database. Incorrect.
Practical Example: In an INE lab, you’d run reset database, verify logs persist via show log, and reconfigure, testing Grid recovery.
Reference: Infoblox NIOS CLI Reference Guide C Reset Commands; INE Course Content: NIOS DDI Grid Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
Clearing the NIOS database requires a precise CLI command:
B (reset database): Wipes DNS zones, DHCP leases, and Grid membership, but retains:
System logs (e.g., syslog, infoblox.log).
Licenses (e.g., reporting, DNSSEC).
Network settings (IP, hostname). Correct.
A: “reset all” isn’t valid (see Q28). Incorrect.
C: “reset config” isn’t a command―closest is set factory, which wipes everything. Incorrect.
D: reset all licenses clears licenses only, not the database. Incorrect.
Practical Example: In an INE lab, you’d run reset database, verify logs persist via show log, and reconfigure, testing Grid recovery.
Reference: Infoblox NIOS CLI Reference Guide C Reset Commands; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #80
VRRP is used for Infoblox High Availability. VRRP requires a virtual IP address, a virtual router ID, a virtual MAC address, and a VRRP priority.
The administrator configures which values? (Select all that apply.)
- A . Virtual MAC address
- B . Virtual IP address
- C . Virtual router ID
- D . VRRP priority
Correct Answer: B, C, D
B, C, D
Explanation:
Comprehensive and Detailed In-Depth
Virtual Router Redundancy Protocol (VRRP) is the mechanism Infoblox uses for HA pairs, ensuring seamless failover between active and passive nodes by sharing a virtual IP (VIP). Let’s analyze what the administrator configures:
A (Virtual MAC Address): VRRP automatically generates the virtual MAC address based on the Virtual Router ID (VRID) using the format 00:00:5E:00:01:XX, where XX is the VRID in hexadecimal. The admin doesn’t manually set this―it’s derived. Incorrect.
B (Virtual IP Address): The VIP is the shared IP that clients use to reach the HA pair. The administrator must configure this in the HA setup (e.g., 192.168.1.100) to define the service endpoint. Correct.
C (Virtual Router ID): The VRID (1-255) uniquely identifies the VRRP group on the network. The admin sets this to avoid conflicts with other VRRP instances. Correct.
D (VRRP Priority): The priority (0-255) determines which node is active (higher priority wins). The
admin configures this (e.g., 100 for active, 90 for passive) to control failover behavior. Correct.
Practical Example: In an INE lab, you’d configure a VIP (e.g., 10.0.0.10), VRID (e.g., 25), and priorities (e.g., 100/90) to set up an HA pair, then troubleshoot failover using VRRP logs.
Reference: Infoblox NIOS Administrator Guide C HA Configuration with VRRP; INE Course Content:
NIOS DDI Grid Deployment.
B, C, D
Explanation:
Comprehensive and Detailed In-Depth
Virtual Router Redundancy Protocol (VRRP) is the mechanism Infoblox uses for HA pairs, ensuring seamless failover between active and passive nodes by sharing a virtual IP (VIP). Let’s analyze what the administrator configures:
A (Virtual MAC Address): VRRP automatically generates the virtual MAC address based on the Virtual Router ID (VRID) using the format 00:00:5E:00:01:XX, where XX is the VRID in hexadecimal. The admin doesn’t manually set this―it’s derived. Incorrect.
B (Virtual IP Address): The VIP is the shared IP that clients use to reach the HA pair. The administrator must configure this in the HA setup (e.g., 192.168.1.100) to define the service endpoint. Correct.
C (Virtual Router ID): The VRID (1-255) uniquely identifies the VRRP group on the network. The admin sets this to avoid conflicts with other VRRP instances. Correct.
D (VRRP Priority): The priority (0-255) determines which node is active (higher priority wins). The
admin configures this (e.g., 100 for active, 90 for passive) to control failover behavior. Correct.
Practical Example: In an INE lab, you’d configure a VIP (e.g., 10.0.0.10), VRID (e.g., 25), and priorities (e.g., 100/90) to set up an HA pair, then troubleshoot failover using VRRP logs.
Reference: Infoblox NIOS Administrator Guide C HA Configuration with VRRP; INE Course Content:
NIOS DDI Grid Deployment.