When defining a Custom Option, what attributes must an administrator provide?

Comprehensive and Detailed In-Depth Explanation:Defining a custom DHCP option in NIOS (Data Management > DHCP > Option Spaces):

Required Attributes:

A (Option Name):User-defined label (e.g., “VoIPConfig”). Mandatory for identification. Correct.

B (Code):Option number (1-254), matching vendor spec (e.g., 66 for TFTP). Mandatory. Correct.

C (Type):Data type (e.g., string, IP), defining format. Mandatory. Correct.

D (Allowed Value(s)):Optional—constrains values (e.g., “server1”), but not required for definition. Incorrect here.

Practical Example:In an INE lab, you’d define Option 66 (Name: “TFTP,” Code: 66, Type: string), apply it, and troubleshoot client uptake.References:Infoblox NIOS Administrator Guide – Custom DHCP Options; INE Course Content: NIOS DDI DHCP Troubleshooting.