Free HCIA-Datacom V2.0 Practice Questions

Duplicate Address Detection ( DAD ) is an IPv6 mechanism used to verify that a unicast address is not already in use before the address is assigned to an interface. DAD is implemented using Neighbor Solicitation (NS) and Neighbor Advertisement (NA) messages, which are part of the ICMPv6 Neighbor Discovery protocol. Therefore, options A and D are correct.

When a host wants to verify a tentative IPv6 address, it sends an NS message for that address. If another node on the link is already using that address, that node responds with an NA message, indicating the address is duplicated and cannot be assigned. If no NA is received within the required period, the host assumes the address is unique and can use it. Options B and C are incorrect because Router Solicitation (RS) and Router Advertisement (RA) are used for router discovery, prefix advertisement, and stateless address autoconfiguration, not for DAD itself. HCIA-Datacom emphasizes the distinction between Neighbor Discovery functions, including address resolution, next-hop reachability, router discovery, and duplicate address detection in IPv6 networks.

According to the original topology and service-planning question, the required VLANs are VLAN 100 , VLAN 101 , and VLAN 102 , so options A , B , and C are correct. In HCIA-Datacom campus design questions, VLAN planning is usually based on service separation, such as user services, voice services, wireless services, management services, or specific departmental segmentation. Each service type is assigned an appropriate VLAN so that broadcast domains are separated and policies can be applied more effectively.

The reason option D is not selected is that it does not match the service requirements shown in the original figure. VLAN planning must follow the actual service design rather than arbitrary numbering. HCIA-Datacom emphasizes that campus VLAN planning should align with traffic isolation, gateway design, security policy deployment, and future scalability. Proper VLAN assignment helps simplify troubleshooting, reduce unnecessary broadcasts, and support service-based policy enforcement. This question tests the ability to read a service topology and identify which VLANs are actually required by the depicted design rather than choosing extra VLANs that are not part of the planned campus solution.

RADIUS and HWTACACS are AAA protocols that support accounting functions in addition to authentication and authorization. Accounting records can be used to track login sessions, service usage, command activity, or other information required by the deployment. LDAP and Microsoft Active Directory, by contrast, are directory-based identity technologies. Huawei documentation describes LDAP/AD integration primarily for authentication and authorization by querying directory information and validating user credentials. They are not used as the native AAA accounting protocol between a Huawei AAA client and an AAA server in the same way as RADIUS or HWTACACS. Therefore, when the question asks which listed protocols cannot be used for accounting between the AAA client and AAA server, AD and LDAP are the appropriate selections. RADIUS explicitly carries accounting messages, and HWTACACS also separates and supports authentication, authorization, and accounting functions. The source file leaves the answer blank, but the Datacom AAA model supports a verified answer of B and

D.