Infoblox NIOS-DDI-Expert Practice Exams
Last updated on Oct 21,2026- Exam Code: NIOS-DDI-Expert
- Exam Name: Infoblox Qualified NIOS DDI Expert - INE
- Certification Provider: Infoblox
- Latest update: Oct 21,2026
Question #30
What protocol and port does DHCP Failover use to keep lease information synchronized between two peers?
- A . Default is TCP 1194, can be user configured
- B . Default is UDP 1194, can be user configured
- C . Default is TCP 647, can be user configured
- D . Default is UDP 647, can be user configured
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
Infoblox NIOS implements DHCP Failover based on the IETF DHCP Failover protocol (draft standard), using TCP port 647 by default for lease synchronization between peers. This port facilitates the exchange of lease data to ensure both the primary and secondary servers maintain consistent states (e.g., NORMAL, COMMUNICATIONS-INTERRUPTED). TCP is used for reliability, as lease sync requires guaranteed delivery. The port can be changed by the administrator if needed (e.g., for firewall rules), making "user configured" accurate.
Options A and B (port 1194) are incorrect―1194 is commonly associated with OpenVPN, not DHCP Failover.
Option D is wrong because it’s TCP, not UDP. This is a key DHCP troubleshooting topic in the INE course.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
C
Explanation:
Comprehensive and Detailed In-Depth
Infoblox NIOS implements DHCP Failover based on the IETF DHCP Failover protocol (draft standard), using TCP port 647 by default for lease synchronization between peers. This port facilitates the exchange of lease data to ensure both the primary and secondary servers maintain consistent states (e.g., NORMAL, COMMUNICATIONS-INTERRUPTED). TCP is used for reliability, as lease sync requires guaranteed delivery. The port can be changed by the administrator if needed (e.g., for firewall rules), making "user configured" accurate.
Options A and B (port 1194) are incorrect―1194 is commonly associated with OpenVPN, not DHCP Failover.
Option D is wrong because it’s TCP, not UDP. This is a key DHCP troubleshooting topic in the INE course.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #32
Any serial cable will work to connect to the serial port of an Infoblox appliance.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Connecting to an Infoblox appliance’s serial port for CLI access requires specific hardware compatibility, not just any serial cable. Here’s why:
Serial Port Specs: Infoblox appliances use a standard DB9 serial port with a default baud rate of 9600 bps, 8 data bits, no parity, 1 stop bit (8N1). The cable must match this configuration and the appliance’s pinout (typically RS-232 standard).
Cable Types:
A straight-through serial cable won’t work―it’s for connecting dissimilar devices (e.g., DTE to DCE).
A null modem cable (with crossed transmit/receive pins) is required to connect a computer (DTE) to the appliance (DTE), ensuring proper signal flow.
Practical Issue: Using an incompatible cable (e.g., lacking null modem crossover or incorrect connectors like RJ45) results in no communication, a common troubleshooting pitfall.
INE Context: The course’s troubleshooting labs emphasize correct serial access for diagnosing network-down scenarios, highlighting this specificity.
Why False: Not all serial cables are null modem cables, and connector compatibility (e.g., DB9 vs.
USB adapters) matters. Thus, "any serial cable" is incorrect.
Example: In an INE lab, you’d use a DB9 null modem cable with a terminal emulator (e.g., PuTTY) set
to 9600 bps to access CLI logs after a Grid member failure.
Reference: Infoblox NIOS Administrator Guide C Serial Console Access; INE Course Content: NIOS DDI Grid Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
Connecting to an Infoblox appliance’s serial port for CLI access requires specific hardware compatibility, not just any serial cable. Here’s why:
Serial Port Specs: Infoblox appliances use a standard DB9 serial port with a default baud rate of 9600 bps, 8 data bits, no parity, 1 stop bit (8N1). The cable must match this configuration and the appliance’s pinout (typically RS-232 standard).
Cable Types:
A straight-through serial cable won’t work―it’s for connecting dissimilar devices (e.g., DTE to DCE).
A null modem cable (with crossed transmit/receive pins) is required to connect a computer (DTE) to the appliance (DTE), ensuring proper signal flow.
Practical Issue: Using an incompatible cable (e.g., lacking null modem crossover or incorrect connectors like RJ45) results in no communication, a common troubleshooting pitfall.
INE Context: The course’s troubleshooting labs emphasize correct serial access for diagnosing network-down scenarios, highlighting this specificity.
Why False: Not all serial cables are null modem cables, and connector compatibility (e.g., DB9 vs.
USB adapters) matters. Thus, "any serial cable" is incorrect.
Example: In an INE lab, you’d use a DB9 null modem cable with a terminal emulator (e.g., PuTTY) set
to 9600 bps to access CLI logs after a Grid member failure.
Reference: Infoblox NIOS Administrator Guide C Serial Console Access; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #33
What is the destination IP address of a DHCPDISCOVER packet from a client?
- A . 0.0.0.0
- B . 224.0.0.52
- C . 255.255.255.255
- D . Broadcast address of client subnet
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
DHCPDISCOVER is the initial broadcast a client sends to find a DHCP server:
Packet Details:
Source IP: 0.0.0.0 (client has no IP yet).
Destination IP: 255.255.255.255 (limited broadcast, all devices on the local network).
Sent via UDP (port 67 server, 68 client).
Why 255.255.255.255: The client doesn’t know the server’s IP and broadcasts to all local devices.
Relays may forward it, but the initial packet targets the universal broadcast address.
Options:
A: 0.0.0.0 is the source, not destination. Incorrect.
B: 224.0.0.52 is a multicast address, not used in DHCPDISCOVER. Incorrect.
C: Matches DHCP broadcast standard (RFC 2131). Correct.
D: Subnet-specific broadcast (e.g., 192.168.1.255) applies post-relay, not the initial packet. Incorrect.
Practical Example: In an INE lab, you’d capture a DHCPDISCOVER with Wireshark, confirm 255.255.255.255, and troubleshoot relay issues.
Reference: RFC 2131 C DHCP; Infoblox NIOS Administrator Guide C DHCP Basics; INE Course Content:
NIOS DDI DHCP Troubleshooting.
C
Explanation:
Comprehensive and Detailed In-Depth
DHCPDISCOVER is the initial broadcast a client sends to find a DHCP server:
Packet Details:
Source IP: 0.0.0.0 (client has no IP yet).
Destination IP: 255.255.255.255 (limited broadcast, all devices on the local network).
Sent via UDP (port 67 server, 68 client).
Why 255.255.255.255: The client doesn’t know the server’s IP and broadcasts to all local devices.
Relays may forward it, but the initial packet targets the universal broadcast address.
Options:
A: 0.0.0.0 is the source, not destination. Incorrect.
B: 224.0.0.52 is a multicast address, not used in DHCPDISCOVER. Incorrect.
C: Matches DHCP broadcast standard (RFC 2131). Correct.
D: Subnet-specific broadcast (e.g., 192.168.1.255) applies post-relay, not the initial packet. Incorrect.
Practical Example: In an INE lab, you’d capture a DHCPDISCOVER with Wireshark, confirm 255.255.255.255, and troubleshoot relay issues.
Reference: RFC 2131 C DHCP; Infoblox NIOS Administrator Guide C DHCP Basics; INE Course Content:
NIOS DDI DHCP Troubleshooting.
Question #34
An Infoblox Grid is using remote authentication for a group named Infoblox-Admins. Where are the permissions for the accounts in Infoblox-Admins defined?
- A . Individual user accounts on the external server
- B . Group definitions on the external server
- C . Group permissions on the Grid
- D . Individual user accounts on the Grid
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
When NIOS uses remote authentication (e.g., RADIUS, LDAP, or Active Directory), user authentication is handled by the external server, but permissions are defined within the NIOS Grid. For a group like "Infoblox-Admins," the external server verifies user credentials and group membership, but the Grid Manager assigns permissions (e.g., read/write access to DNS zones) to the group itself. This centralizes access control within NIOS, ensuring consistency across the Grid.
Options A and B are incorrect because the external server manages authentication, not NIOS-specific permissions.
Option D is wrong as permissions are group-based, not individually assigned on the Grid. The INE course covers Grid administration, including authentication setup.
Reference: Infoblox NIOS Administrator Guide C Authentication; INE Course Objective: NIOS DDI Grid Deployment.
C
Explanation:
Comprehensive and Detailed In-Depth
When NIOS uses remote authentication (e.g., RADIUS, LDAP, or Active Directory), user authentication is handled by the external server, but permissions are defined within the NIOS Grid. For a group like "Infoblox-Admins," the external server verifies user credentials and group membership, but the Grid Manager assigns permissions (e.g., read/write access to DNS zones) to the group itself. This centralizes access control within NIOS, ensuring consistency across the Grid.
Options A and B are incorrect because the external server manages authentication, not NIOS-specific permissions.
Option D is wrong as permissions are group-based, not individually assigned on the Grid. The INE course covers Grid administration, including authentication setup.
Reference: Infoblox NIOS Administrator Guide C Authentication; INE Course Objective: NIOS DDI Grid Deployment.
Question #35
You are asked to configure DHCPv4 failover on the Grid.
Which of the following do you need for it to function correctly? (Select all that apply.)
- A . DHCP members are directly connected via crossover network cables
- B . DHCP members are located in the same subnet
- C . TCP port 647 is open between DHCP members
- D . DHCP relays are configured to relay to DHCP members simultaneously
Correct Answer: C, D
C, D
Explanation:
Comprehensive and Detailed In-Depth
DHCPv4 Failover requirements:
C: TCP 647 is the failover sync port―must be open for lease coordination. Correct.
D: Relays must send requests to both peers (e.g., via IP helper addresses) for load balancing/redundancy. Correct.
A: Crossover cables aren’t required―standard network connectivity suffices. Incorrect.
B: Same subnet isn’t mandatory―peers can be remote if routable. Incorrect.
Practical Example: In an INE lab, ensure port 647 is open, configure relays, test failover, and troubleshoot sync issues.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover Setup; INE Course Content: NIOS DDI DHCP Troubleshooting.
C, D
Explanation:
Comprehensive and Detailed In-Depth
DHCPv4 Failover requirements:
C: TCP 647 is the failover sync port―must be open for lease coordination. Correct.
D: Relays must send requests to both peers (e.g., via IP helper addresses) for load balancing/redundancy. Correct.
A: Crossover cables aren’t required―standard network connectivity suffices. Incorrect.
B: Same subnet isn’t mandatory―peers can be remote if routable. Incorrect.
Practical Example: In an INE lab, ensure port 647 is open, configure relays, test failover, and troubleshoot sync issues.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover Setup; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #36
When defining a custom DHCP option, how does the administrator select the option name?
- A . The name must exactly match what the vendor has defined
- B . The name must match the vendor definition, but it is not case-sensitive
- C . The name must contain the vendor name
- D . The administrator may define any name
Correct Answer: D
D
Explanation:
Comprehensive and Detailed In-Depth
Custom DHCP options in NIOS allow tailoring DHCP responses for specific devices or applications:
Configuration: In Grid Manager (Data Management > DHCP > Option Spaces > Add), admins define custom options with:
Option Number: Must match the DHCP standard or vendor spec (1-254).
Name: A user-defined label for clarity (e.g., "TFTP-Server").
Data Type: (e.g., string, IP).
Naming Freedom: The "name" is an internal NIOS identifier, not tied to DHCP packets or vendor standards―it’s for admin convenience. The option number and value align with vendor needs (e.g., Option 66 for TFTP), but the name can be arbitrary (e.g., "MyTFTP" vs. "VendorTFTP").
Options:
A/B: Vendor definitions apply to option numbers/values, not names. Case sensitivity is irrelevant.
Incorrect.
C: No requirement to include the vendor name―it’s optional. Incorrect.
D: Admins can choose any descriptive name, making management intuitive. Correct.
Practical Example: In an INE lab, you’d define a custom option "VoIPConfig" (Option 66, string), assign it to a range, and troubleshoot client reception, testing DHCP flexibility.
Reference: Infoblox NIOS Administrator Guide C Custom DHCP Options; INE Course Content: NIOS DDI DHCP Troubleshooting.
D
Explanation:
Comprehensive and Detailed In-Depth
Custom DHCP options in NIOS allow tailoring DHCP responses for specific devices or applications:
Configuration: In Grid Manager (Data Management > DHCP > Option Spaces > Add), admins define custom options with:
Option Number: Must match the DHCP standard or vendor spec (1-254).
Name: A user-defined label for clarity (e.g., "TFTP-Server").
Data Type: (e.g., string, IP).
Naming Freedom: The "name" is an internal NIOS identifier, not tied to DHCP packets or vendor standards―it’s for admin convenience. The option number and value align with vendor needs (e.g., Option 66 for TFTP), but the name can be arbitrary (e.g., "MyTFTP" vs. "VendorTFTP").
Options:
A/B: Vendor definitions apply to option numbers/values, not names. Case sensitivity is irrelevant.
Incorrect.
C: No requirement to include the vendor name―it’s optional. Incorrect.
D: Admins can choose any descriptive name, making management intuitive. Correct.
Practical Example: In an INE lab, you’d define a custom option "VoIPConfig" (Option 66, string), assign it to a range, and troubleshoot client reception, testing DHCP flexibility.
Reference: Infoblox NIOS Administrator Guide C Custom DHCP Options; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #37
The Infoblox WAPI/RESTful API requires the administrator to use the Perl programming language.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
The Infoblox Web API (WAPI) is a RESTful API that allows administrators to interact with the NIOS system programmatically for tasks like managing DNS records, DHCP leases, and Grid configurations. Contrary to requiring Perl, WAPI is language-agnostic―it uses HTTP-based requests (GET, POST, PUT, DELETE) and returns data in JSON format. While Infoblox provides sample scripts in Perl (and historically supported a Perl API), administrators can use any programming language (e.g., Python, Java, or even tools like cURL) that supports HTTP requests. The misconception might stem from older documentation emphasizing Perl examples, but the INE course, focusing on advanced NIOS management, clarifies that WAPI is not tied to Perl.
Reference: Infoblox NIOS Documentation C WAPI Guide; INE Course Objective: NIOS Grid Troubleshooting (covers API usage).
B
Explanation:
Comprehensive and Detailed In-Depth
The Infoblox Web API (WAPI) is a RESTful API that allows administrators to interact with the NIOS system programmatically for tasks like managing DNS records, DHCP leases, and Grid configurations. Contrary to requiring Perl, WAPI is language-agnostic―it uses HTTP-based requests (GET, POST, PUT, DELETE) and returns data in JSON format. While Infoblox provides sample scripts in Perl (and historically supported a Perl API), administrators can use any programming language (e.g., Python, Java, or even tools like cURL) that supports HTTP requests. The misconception might stem from older documentation emphasizing Perl examples, but the INE course, focusing on advanced NIOS management, clarifies that WAPI is not tied to Perl.
Reference: Infoblox NIOS Documentation C WAPI Guide; INE Course Objective: NIOS Grid Troubleshooting (covers API usage).
Question #38
How does the passive member of a High Availability (HA) pair receive its database updates?
- A . SSL VPN from the Active node
- B . SSL VPN from the Grid Master
- C . bloxSync from the Active node
- D . bloxSync from the Grid Master
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
In an HA pair, the passive node stays synchronized with the active node to ensure seamless failover. This synchronization uses bloxSync, a proprietary Infoblox protocol that securely transfers database updates (e.g., DNS records, DHCP leases) between the HA pair members over an SSL-encrypted connection. The active node, being the operational member, directly provides these updates to the passive node. The Grid Master handles Grid-wide sync, but within an HA pair, the active node is the source.
Options A and B misrepresent the mechanism (it’s not a traditional VPN), and Option D incorrectly attributes the sync to the Grid Master. This is a critical HA troubleshooting topic in the INE course.
Reference: Infoblox NIOS Documentation C HA Pair Configuration; INE Course Content: NIOS DDI Grid Troubleshooting.
C
Explanation:
Comprehensive and Detailed In-Depth
In an HA pair, the passive node stays synchronized with the active node to ensure seamless failover. This synchronization uses bloxSync, a proprietary Infoblox protocol that securely transfers database updates (e.g., DNS records, DHCP leases) between the HA pair members over an SSL-encrypted connection. The active node, being the operational member, directly provides these updates to the passive node. The Grid Master handles Grid-wide sync, but within an HA pair, the active node is the source.
Options A and B misrepresent the mechanism (it’s not a traditional VPN), and Option D incorrectly attributes the sync to the Grid Master. This is a critical HA troubleshooting topic in the INE course.
Reference: Infoblox NIOS Documentation C HA Pair Configuration; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #39
The DHCP server has assigned an address, but the client did not renew before the lease timer ended.
What status will be listed for this address?
- A . Active
- B . Released
- C . Expired
- D . Abandoned
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
DHCP lease states in NIOS:
Scenario: Client gets IP (e.g., 192.168.1.10, 1-hour lease), doesn’t renew, and timer expires.
C (Expired): Lease times out, marked “Expired” in NIOS (Data Management > DHCP > Leases), available for reassignment. Correct.
A: Active is for current, unexpired leases. Incorrect.
B: Released requires client action (DHCPRELEASE). Incorrect.
D: Abandoned is for declined or conflicting leases, not timeouts. Incorrect.
Practical Example: In an INE lab, set a 5-minute lease, wait for expiry, check “Expired” status, and troubleshoot lease reuse.
Reference: Infoblox NIOS Administrator Guide C DHCP Leases; INE Course Content: NIOS DDI DHCP
Troubleshooting.
C
Explanation:
Comprehensive and Detailed In-Depth
DHCP lease states in NIOS:
Scenario: Client gets IP (e.g., 192.168.1.10, 1-hour lease), doesn’t renew, and timer expires.
C (Expired): Lease times out, marked “Expired” in NIOS (Data Management > DHCP > Leases), available for reassignment. Correct.
A: Active is for current, unexpired leases. Incorrect.
B: Released requires client action (DHCPRELEASE). Incorrect.
D: Abandoned is for declined or conflicting leases, not timeouts. Incorrect.
Practical Example: In an INE lab, set a 5-minute lease, wait for expiry, check “Expired” status, and troubleshoot lease reuse.
Reference: Infoblox NIOS Administrator Guide C DHCP Leases; INE Course Content: NIOS DDI DHCP
Troubleshooting.
Question #40
An administrator defined several Upgrade Groups before updating the software on a Grid.
What members must be put in the same Upgrade Group?
- A . Members of the same type (Hardware vs. vNIOS)
- B . Members that run the same set of services (DNS, DHCP, etc.)
- C . Members that running the same software version before upgrade
- D . Members that will be upgraded at the same time
Correct Answer: D
D
Explanation:
Comprehensive and Detailed In-Depth
Upgrade Groups in NIOS allow administrators to control the sequence and timing of software upgrades across Grid members, minimizing disruption. Here’s the detailed reasoning:
Upgrade Groups Purpose: They define which members upgrade together in a single phase, based on operational needs (e.g., location, role, or downtime tolerance), not inherent traits like type or services.
Options Analysis:
A: Hardware vs. virtual NIOS (vNIOS) distinction isn’t mandatory―different types can upgrade together if operationally feasible. Incorrect.
B: Service roles (DNS, DHCP) don’t dictate grouping; a DNS-only member and a DHCP-only member could upgrade simultaneously if desired. Incorrect.
C: Pre-upgrade software versions don’t force grouping―NIOS manages version compatibility during the upgrade process. Incorrect.
D: The defining trait of an Upgrade Group is that its members upgrade at the same time, as set by the admin in the upgrade schedule (Grid > Upgrade). Correct.
Process: In Grid Manager, you create groups (e.g., "Group 1: East Coast Members") and assign members to upgrade concurrently, followed by "Group 2," etc.
Practical Example: In an INE lab, you might group two HA pair passive nodes in "Group 1" to upgrade at 1 AM, ensuring the active nodes (Group 2) upgrade later, testing Grid deployment resilience.
Reference: Infoblox NIOS Administrator Guide C Software Upgrades; INE Course Objective: NIOS DDI Grid Deployment.
D
Explanation:
Comprehensive and Detailed In-Depth
Upgrade Groups in NIOS allow administrators to control the sequence and timing of software upgrades across Grid members, minimizing disruption. Here’s the detailed reasoning:
Upgrade Groups Purpose: They define which members upgrade together in a single phase, based on operational needs (e.g., location, role, or downtime tolerance), not inherent traits like type or services.
Options Analysis:
A: Hardware vs. virtual NIOS (vNIOS) distinction isn’t mandatory―different types can upgrade together if operationally feasible. Incorrect.
B: Service roles (DNS, DHCP) don’t dictate grouping; a DNS-only member and a DHCP-only member could upgrade simultaneously if desired. Incorrect.
C: Pre-upgrade software versions don’t force grouping―NIOS manages version compatibility during the upgrade process. Incorrect.
D: The defining trait of an Upgrade Group is that its members upgrade at the same time, as set by the admin in the upgrade schedule (Grid > Upgrade). Correct.
Process: In Grid Manager, you create groups (e.g., "Group 1: East Coast Members") and assign members to upgrade concurrently, followed by "Group 2," etc.
Practical Example: In an INE lab, you might group two HA pair passive nodes in "Group 1" to upgrade at 1 AM, ensuring the active nodes (Group 2) upgrade later, testing Grid deployment resilience.
Reference: Infoblox NIOS Administrator Guide C Software Upgrades; INE Course Objective: NIOS DDI Grid Deployment.