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 #61
In the DHCPv4 failover NORMAL state, leases are only stored on the primary peer.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
In NORMAL state:
Lease Storage: Both primary and secondary peers store leases via sync (TCP 647). Each manages its pool share (e.g., 50/50), but all leases are replicated for redundancy.
Why False: “Only primary” contradicts failover’s design―both peers maintain a full lease database for failover readiness.
Practical Example: In an INE lab, check leases on both peers (Data Management > DHCP > Leases), simulate primary failure, and troubleshoot secondary takeover.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
In NORMAL state:
Lease Storage: Both primary and secondary peers store leases via sync (TCP 647). Each manages its pool share (e.g., 50/50), but all leases are replicated for redundancy.
Why False: “Only primary” contradicts failover’s design―both peers maintain a full lease database for failover readiness.
Practical Example: In an INE lab, check leases on both peers (Data Management > DHCP > Leases), simulate primary failure, and troubleshoot secondary takeover.
Reference: Infoblox NIOS Administrator Guide C DHCP Failover; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #62
When defining a custom DHCP option, what does the administrator need to specify? (Select all that apply.)
- A . Option Name
- B . Option Number
- C . Data Type
- D . Data Value
Correct Answer: A, B, C
A, B, C
Explanation:
Comprehensive and Detailed In-Depth
Custom DHCP options (Data Management > DHCP > Option Spaces):
A (Option Name): Mandatory label (e.g., “CustomOpt”). Correct.
B (Option Number): Mandatory code (1-254, e.g., 150). Correct.
C (Data Type): Mandatory format (e.g., string, integer). Correct.
D (Data Value): Set when applying the option to a scope/range, not during definition.
Optional here. Incorrect.
Practical Example: In an INE lab, define “VoiceVLAN” (Number: 150, Type: integer), apply value “10” later, and troubleshoot client config.
Reference: Infoblox NIOS Administrator Guide C DHCP Options; INE Course Content: NIOS DDI DHCP Troubleshooting.
A, B, C
Explanation:
Comprehensive and Detailed In-Depth
Custom DHCP options (Data Management > DHCP > Option Spaces):
A (Option Name): Mandatory label (e.g., “CustomOpt”). Correct.
B (Option Number): Mandatory code (1-254, e.g., 150). Correct.
C (Data Type): Mandatory format (e.g., string, integer). Correct.
D (Data Value): Set when applying the option to a scope/range, not during definition.
Optional here. Incorrect.
Practical Example: In an INE lab, define “VoiceVLAN” (Number: 150, Type: integer), apply value “10” later, and troubleshoot client config.
Reference: Infoblox NIOS Administrator Guide C DHCP Options; INE Course Content: NIOS DDI DHCP Troubleshooting.
Question #63
Which of the following statements about restarting Grid services are true? (Select all that apply.)
- A . You can poll members to see which services will be restarted
- B . You can force service restart on a member
- C . You can schedule service restarts
- D . By default, the Grid restarts services every day
Correct Answer: B, C
B, C
Explanation:
Comprehensive and Detailed In-Depth
Restarting services (e.g., DNS, DHCP) on NIOS Grid members is a common administrative task, often required after configuration changes. Let’s break down each option with detailed reasoning:
A: "Poll members to see which services will be restarted" suggests proactively querying members for restart eligibility. NIOS doesn’t offer a specific polling feature for this―administrators check service status (e.g., via Grid Manager > Members > Services) or logs, but there’s no pre-restart polling tool. Incorrect.
B: In Grid Manager (Grid > Grid Manager > Members), you can select a member and click "Restart Services" with a "Force Restart" option, overriding any checks for necessity. This is useful in troubleshooting (e.g., clearing a hung DNS service). Correct.
C: NIOS allows scheduling service restarts via the "Schedule Restart" option in Grid Manager, letting you specify a time to minimize disruption (e.g., off-hours). This aligns with Grid management best practices taught in INE. Correct.
D: There’s no default daily restart policy in NIOS. Restarts occur only when triggered by an admin or system event (e.g., upgrade). This would disrupt service unnecessarily if true. Incorrect.
Practical Example: During an INE lab, you might force a restart on a member to resolve a DHCP failover issue or schedule a restart after updating a DNS zone to ensure propagation, reflecting real-world Grid troubleshooting.
Reference: Infoblox NIOS Administrator Guide C Managing Grid Services; INE Course Content: NIOS DDI Grid Troubleshooting.
B, C
Explanation:
Comprehensive and Detailed In-Depth
Restarting services (e.g., DNS, DHCP) on NIOS Grid members is a common administrative task, often required after configuration changes. Let’s break down each option with detailed reasoning:
A: "Poll members to see which services will be restarted" suggests proactively querying members for restart eligibility. NIOS doesn’t offer a specific polling feature for this―administrators check service status (e.g., via Grid Manager > Members > Services) or logs, but there’s no pre-restart polling tool. Incorrect.
B: In Grid Manager (Grid > Grid Manager > Members), you can select a member and click "Restart Services" with a "Force Restart" option, overriding any checks for necessity. This is useful in troubleshooting (e.g., clearing a hung DNS service). Correct.
C: NIOS allows scheduling service restarts via the "Schedule Restart" option in Grid Manager, letting you specify a time to minimize disruption (e.g., off-hours). This aligns with Grid management best practices taught in INE. Correct.
D: There’s no default daily restart policy in NIOS. Restarts occur only when triggered by an admin or system event (e.g., upgrade). This would disrupt service unnecessarily if true. Incorrect.
Practical Example: During an INE lab, you might force a restart on a member to resolve a DHCP failover issue or schedule a restart after updating a DNS zone to ensure propagation, reflecting real-world Grid troubleshooting.
Reference: Infoblox NIOS Administrator Guide C Managing Grid Services; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #64
When controlling Grid Members under Grid > Grid Manager > Members, what control options are available from the Toolbar? Choose 3 answers
- A . Reboot
- B . Restart
- C . Suspend
- D . Restart GUI
Correct Answer: A, B, C
A, B, C
Explanation:
Comprehensive and Detailed In-Depth
Grid Manager Toolbar (Grid > Members) offers member controls:
A (Reboot): Reboots the appliance―full restart. Correct.
B (Restart): Restarts services (e.g., DNS, DHCP) without reboot. Correct.
C (Suspend): Pauses services―useful for maintenance. Correct.
D: “Restart GUI” isn’t a member-level option―GUI runs on GM, not per member. Incorrect.
Practical Example: In an INE lab, reboot a member, restart services, suspend another, and troubleshoot impacts.
Reference: Infoblox NIOS Administrator Guide C Member Controls; INE Course Content: NIOS DDI Grid Troubleshooting.
A, B, C
Explanation:
Comprehensive and Detailed In-Depth
Grid Manager Toolbar (Grid > Members) offers member controls:
A (Reboot): Reboots the appliance―full restart. Correct.
B (Restart): Restarts services (e.g., DNS, DHCP) without reboot. Correct.
C (Suspend): Pauses services―useful for maintenance. Correct.
D: “Restart GUI” isn’t a member-level option―GUI runs on GM, not per member. Incorrect.
Practical Example: In an INE lab, reboot a member, restart services, suspend another, and troubleshoot impacts.
Reference: Infoblox NIOS Administrator Guide C Member Controls; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #65
The standard or recommended architecture for NIOS DNS views is "one member, one view".
- A . True
- B . False
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
DNS Views in NIOS allow multiple DNS perspectives (e.g., internal vs. external):
Architecture: NIOS supports multiple views per member―common for consolidating services (e.g., one appliance handles “Internal” and “External” views). “One member, one view” isn’t a standard or
recommended limit.
Why False: Best practice is flexible―views depend on use case, not a strict 1:1 ratio. Multiple views per member is typical and efficient.
Practical Example: In an INE lab, configure two views on one member, test split DNS, and troubleshoot view conflicts.
Reference: Infoblox NIOS Administrator Guide C DNS Views; INE Course Content: NIOS DDI DNS Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
DNS Views in NIOS allow multiple DNS perspectives (e.g., internal vs. external):
Architecture: NIOS supports multiple views per member―common for consolidating services (e.g., one appliance handles “Internal” and “External” views). “One member, one view” isn’t a standard or
recommended limit.
Why False: Best practice is flexible―views depend on use case, not a strict 1:1 ratio. Multiple views per member is typical and efficient.
Practical Example: In an INE lab, configure two views on one member, test split DNS, and troubleshoot view conflicts.
Reference: Infoblox NIOS Administrator Guide C DNS Views; INE Course Content: NIOS DDI DNS Troubleshooting.
Question #66
Which CSV export format is recommended for tasks that involve data manipulation and reimporting to the NIOS Grid?
- A . Infoblox CSV Import Format
- B . Standard CSV (Visible) Format
- C . Both formats are equally suitable
- D . Neither format is suitable for data manipulation
Correct Answer: A
A
Explanation:
Comprehensive and Detailed In-Depth
NIOS supports two CSV export formats in Grid Manager (Data Management > Export):
Infoblox CSV Import Format: Structured specifically for NIOS, with headers matching import fields (e.g., "fqdn,ip_address,mac_address"). Includes all necessary metadata for reimporting, making it ideal for editing (e.g., in Excel) and reuploading via the Data Import Wizard (DIW).
Standard CSV (Visible) Format: A human-readable format showing only visible Grid Manager data, lacking the full structure for reimport. It’s better for reporting or external analysis, not manipulation/reimport.
Why A: The Infoblox format ensures compatibility with NIOS’s import process, preserving object relationships and mandatory fields (e.g., marked with *). Editing and reimporting in this format maintains data integrity.
Option Analysis:
B: Standard format isn’t designed for reimport―missing fields cause import failures. Incorrect.
C: They serve different purposes; only Infoblox format suits reimporting. Incorrect.
D: Infoblox format is suitable, so this is false. Incorrect.
Practical Example: In an INE lab, you’d export DNS records in Infoblox CSV format, update IPs, and reimport to test bulk management, a Grid deployment skill.
Reference: Infoblox NIOS Administrator Guide C CSV Export/Import; INE Course Objective: NIOS DDI Grid Deployment.
A
Explanation:
Comprehensive and Detailed In-Depth
NIOS supports two CSV export formats in Grid Manager (Data Management > Export):
Infoblox CSV Import Format: Structured specifically for NIOS, with headers matching import fields (e.g., "fqdn,ip_address,mac_address"). Includes all necessary metadata for reimporting, making it ideal for editing (e.g., in Excel) and reuploading via the Data Import Wizard (DIW).
Standard CSV (Visible) Format: A human-readable format showing only visible Grid Manager data, lacking the full structure for reimport. It’s better for reporting or external analysis, not manipulation/reimport.
Why A: The Infoblox format ensures compatibility with NIOS’s import process, preserving object relationships and mandatory fields (e.g., marked with *). Editing and reimporting in this format maintains data integrity.
Option Analysis:
B: Standard format isn’t designed for reimport―missing fields cause import failures. Incorrect.
C: They serve different purposes; only Infoblox format suits reimporting. Incorrect.
D: Infoblox format is suitable, so this is false. Incorrect.
Practical Example: In an INE lab, you’d export DNS records in Infoblox CSV format, update IPs, and reimport to test bulk management, a Grid deployment skill.
Reference: Infoblox NIOS Administrator Guide C CSV Export/Import; INE Course Objective: NIOS DDI Grid Deployment.
Question #67
If a Grid Master Fails, what can be promoted to take the place of the Grid Master? (Choose one.)
- A . The Grid Manager
- B . A Grid Master Candidate
- C . Any active Grid Member
- D . A standby Grid Master
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Grid Master (GM) failure recovery:
B: A Grid Master Candidate (GMC), pre-designated in Grid Manager (Grid > Members), can be promoted (Grid > Promote GMC) to replace a failed GM, assuming its role. Correct.
A: Grid Manager is the UI, not a device. Incorrect.
C: Not all members are GMCs―only designated ones qualify. Incorrect.
D: No “standby GM” role―GMC is the term. Incorrect.
Practical Example: In an INE lab, promote a GMC after GM failure, test sync, and troubleshoot promotion issues.
Reference: Infoblox NIOS Administrator Guide C Grid Master Promotion; INE Course Content: NIOS DDI Grid Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
Grid Master (GM) failure recovery:
B: A Grid Master Candidate (GMC), pre-designated in Grid Manager (Grid > Members), can be promoted (Grid > Promote GMC) to replace a failed GM, assuming its role. Correct.
A: Grid Manager is the UI, not a device. Incorrect.
C: Not all members are GMCs―only designated ones qualify. Incorrect.
D: No “standby GM” role―GMC is the term. Incorrect.
Practical Example: In an INE lab, promote a GMC after GM failure, test sync, and troubleshoot promotion issues.
Reference: Infoblox NIOS Administrator Guide C Grid Master Promotion; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #68
An administrator is adding A records to an existing zone. Where is the Add Record function in Grid Manager?
- A . Grid > DNS > Members > (member) > (zone)
- B . Data Management > DNS > Zones > (zone)
- C . Data Management > Members > Services > DNS > (zone)
- D . Grid > Services > DNS > (zone)
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
In the Infoblox Grid Manager (the NIOS GUI), DNS management is centralized under the Data Management tab, which provides a logical structure for handling DNS zones and records. To add an A record (Address record) to an existing zone, the administrator navigates to Data Management > DNS
> Zones, selects the specific zone, and then uses the "Add Record" option (typically a "+" icon or button).
Option A focuses on member-specific settings, not zone record management.
Option C drills into member services, which is more about service status than record editing.
Option D is incorrect as "Grid > Services" doesn’t exist in this context―it’s a misnomer. The INE course covers practical DNS troubleshooting, reinforcing this workflow.
Reference: Infoblox NIOS Administrator Guide C Managing DNS Zones; INE Course Content: NIOS DDI DNS Troubleshooting.
B
Explanation:
Comprehensive and Detailed In-Depth
In the Infoblox Grid Manager (the NIOS GUI), DNS management is centralized under the Data Management tab, which provides a logical structure for handling DNS zones and records. To add an A record (Address record) to an existing zone, the administrator navigates to Data Management > DNS
> Zones, selects the specific zone, and then uses the "Add Record" option (typically a "+" icon or button).
Option A focuses on member-specific settings, not zone record management.
Option C drills into member services, which is more about service status than record editing.
Option D is incorrect as "Grid > Services" doesn’t exist in this context―it’s a misnomer. The INE course covers practical DNS troubleshooting, reinforcing this workflow.
Reference: Infoblox NIOS Administrator Guide C Managing DNS Zones; INE Course Content: NIOS DDI DNS Troubleshooting.
Question #69
A customer reports difficulty joining a standalone High Availability (HA) pair.
How should the customer diagnose the issue? Choose 2 answers
- A . Use error messages recorded in syslog and debug log on both nodes
- B . Use traffic capture on the first node (the active node)
- C . Use traffic capture on both nodes
- D . Reset everything before trying to re-join
Correct Answer: A, C
A, C
Explanation:
Comprehensive and Detailed In-Depth
Joining a standalone HA pair to a Grid involves network, authentication, and sync issues. Best diagnostics:
A: Syslog (show log syslog) and debug logs (e.g., infoblox.log in support bundle) on both nodes reveal errors (e.g., “Join failed: invalid secret”). Essential for root cause. Correct.
C: Traffic capture (tcpdump via CLI) on both nodes checks VRRP, bloxSync, and network issues (e.g., blocked ports). Comprehensive view of communication. Correct.
B: Capturing only the active node misses passive node issues (e.g., firewall blocking sync). Incomplete. Incorrect.
D: Resetting erases logs and configs, hindering diagnosis―last resort, not initial step. Incorrect.
Practical Example: In an INE lab, you’d check syslog for “sync failed,” run tcpdump -i eth0 port 443 on both, and troubleshoot a blocked SSL port.
Reference: Infoblox NIOS Administrator Guide C HA Troubleshooting; INE Course Content: NIOS DDI Grid Troubleshooting.
A, C
Explanation:
Comprehensive and Detailed In-Depth
Joining a standalone HA pair to a Grid involves network, authentication, and sync issues. Best diagnostics:
A: Syslog (show log syslog) and debug logs (e.g., infoblox.log in support bundle) on both nodes reveal errors (e.g., “Join failed: invalid secret”). Essential for root cause. Correct.
C: Traffic capture (tcpdump via CLI) on both nodes checks VRRP, bloxSync, and network issues (e.g., blocked ports). Comprehensive view of communication. Correct.
B: Capturing only the active node misses passive node issues (e.g., firewall blocking sync). Incomplete. Incorrect.
D: Resetting erases logs and configs, hindering diagnosis―last resort, not initial step. Incorrect.
Practical Example: In an INE lab, you’d check syslog for “sync failed,” run tcpdump -i eth0 port 443 on both, and troubleshoot a blocked SSL port.
Reference: Infoblox NIOS Administrator Guide C HA Troubleshooting; INE Course Content: NIOS DDI Grid Troubleshooting.
Question #70
What types of restrictions can be applied to a super user admin account?
- A . Database object type
- B . Network
- C . Read only or read/write
- D . No restrictions can be applied to super-user accounts
Correct Answer: D
D
Explanation:
Comprehensive and Detailed In-Depth
Superuser accounts in NIOS have unrestricted access:
Definition: Superusers (Administration > Administrators > Edit > Superuser) have full read/write permissions across all Grid objects and functions (DNS, DHCP, Grid settings).
Restrictions: Unlike regular admins, superusers can’t be limited by object type, network scope, or read-only status―their role overrides all constraints.
Options:
A/B/C: These apply to non-superuser accounts (e.g., limit to DNS zones or read-only). Incorrect for superusers.
D: Matches NIOS design―superusers are unrestricted by definition. Correct.
Practical Example: In an INE lab, a superuser overrides a restricted admin’s permissions to fix a Grid issue, testing ultimate control scenarios.
Reference: Infoblox NIOS Administrator Guide C Admin Permissions; INE Course Objective: NIOS DDI Grid Deployment.
D
Explanation:
Comprehensive and Detailed In-Depth
Superuser accounts in NIOS have unrestricted access:
Definition: Superusers (Administration > Administrators > Edit > Superuser) have full read/write permissions across all Grid objects and functions (DNS, DHCP, Grid settings).
Restrictions: Unlike regular admins, superusers can’t be limited by object type, network scope, or read-only status―their role overrides all constraints.
Options:
A/B/C: These apply to non-superuser accounts (e.g., limit to DNS zones or read-only). Incorrect for superusers.
D: Matches NIOS design―superusers are unrestricted by definition. Correct.
Practical Example: In an INE lab, a superuser overrides a restricted admin’s permissions to fix a Grid issue, testing ultimate control scenarios.
Reference: Infoblox NIOS Administrator Guide C Admin Permissions; INE Course Objective: NIOS DDI Grid Deployment.