NIOS-DDI-EXPERT Practice Questions

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 – Software Revert; INE Course Content: NIOS DDI Grid

Troubleshooting.

Comprehensive and Detailed In-Depth

The Authentication Policy in NIOS (Administration > Authentication) governs remote authentication

(e.g., LDAP, RADIUS). The "Assign users to this group if remote admin group cannot be found" option

is a fallback mechanism:

Purpose: If a user’s remote group (e.g., from AD) isn’t mapped to an NIOS group, this setting assigns

them to a default group with predefined permissions.

Requirement: It’s optional—not mandatory. Leaving it unset means unmatched users are denied

access unless individually mapped, enhancing security in some cases.

Why False: "Always" implies it’s required, but NIOS allows flexibility. For strict environments, admins

might skip this to prevent unauthorized access, relying on explicit mappings.

Options Analysis:

A: Suggests a mandatory setting, but documentation and UI show it’s a choice. Incorrect.

B: Correctly reflects that it’s not always necessary—optional based on policy. Correct.

Practical Example: In an INE lab, you’d configure LDAP without a fallback group, test an unmapped

user’s denial, and troubleshoot authentication logs, reinforcing Grid security concepts.

Reference: Infoblox NIOS Administrator Guide – Authentication Policy; INE Course Objective: NIOS

DDI Grid Deployment.

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 – HA Troubleshooting; INE Course Content: NIOS DDI

Grid Troubleshooting.

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 – DHCP Leases; INE Course Content: NIOS DDI DHCP

Troubleshooting.

Comprehensive and Detailed In-Depth

Workflow Approval notifications:

A: The Grid Master (GM) sends emails via its configured SMTP settings (Grid > Grid Properties >

Email), as it manages Grid-wide tasks. Correct.

B: GMC is a standby, not active unless promoted—doesn’t send emails. Incorrect.

C: Only GM sends, not both—GMC is passive. Incorrect.

D: SuperAdmin is a role, not a process—no sending capability. Incorrect.

Practical Example: In an INE lab, configure SMTP on the GM, test approval emails, and troubleshoot

delivery from GM logs.

Reference: Infoblox NIOS Administrator Guide – Workflow Notifications; INE Course Objective: NIOS

DDI Grid Deployment.

Comprehensive and Detailed In-Depth

Restarting services post-change (e.g., DNS zone update) requires minimizing downtime:

B: “Restart if needed” checks if a restart is required per member, and “sequentially” staggers restarts

(e.g., passive HA nodes first), ensuring continuous service. Least disruptive. Correct.

A: Simultaneous force restart stops all services at once—maximum disruption. Incorrect.

C: GM-only restart ignores other members needing updates, incomplete. Incorrect.

D: HA members only misses single nodes or GM, partial solution. Incorrect.

Practical Example: In an INE lab, you’d select sequential restart after a DHCP range change, monitor

client connectivity, and troubleshoot minimal impact.

Reference: Infoblox NIOS Administrator Guide – Service Restarts; INE Course Content: NIOS DDI Grid

Troubleshooting.

Comprehensive and Detailed In-Depth

Copying DNS records in NIOS (Data Management > DNS > Zones):

Process: Select source zone, choose records, copy to target zone.

B: Copy all of one type (e.g., A records) via filter. Correct.

C: Select multiple types (e.g., A and PTR) using multi-select. Correct.

D: Individually pick records (e.g., “host1 A”) via checkboxes. Correct.

A: “All records” isn’t an option—copying requires specificity (type or selection). Incorrect.

Practical Example: In an INE lab, copy A and PTR records from “lab.com” to “test.com,” test

resolution, and troubleshoot mismatches.

Reference: Infoblox NIOS Administrator Guide – DNS Record Management; INE Course Content: NIOS

DDI DNS Troubleshooting.

Comprehensive and Detailed In-Depth

NIOS Online Documentation is accessible via Grid Manager:

D: Help > Documentation > NIOS Online Documentation opens a browser to the latest NIOS docs

(e.g., Admin Guide) hosted online or locally. Correct.

A: Logs > Download is for syslog/support bundles, not docs. Incorrect.

B: Tools > Support Bundle is diagnostics, not documentation. Incorrect.

C: No “Download Admin guide” option exists under Tools. Incorrect.

Practical Example: In an INE lab, you’d access docs via Help to troubleshoot a Grid join issue, testing

resource navigation.

Reference: Infoblox NIOS Administrator Guide – UI Navigation; INE Course Content: NIOS DDI Grid

Troubleshooting.

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 – DNS Views; INE Course Content: NIOS DDI DNS

Troubleshooting.

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 – Grid Master Promotion; INE Course Content: NIOS

DDI Grid Troubleshooting.