H12-821_V1.0 Practice Questions

In the provided configuration, IS-IS is enabled on Loopback0 but not on Loopback3 of R2. As a result, R2 will advertise the route 10.0.2.2/32 (from Loopback0 ) to R1 through IS-IS. However, the route 10.0.2.3/32 will not be advertised because IS-IS is not enabled on that loopback interface. The import-route direct command does not override this behavior ​.

A is correct – Removing unused accounts helps minimize the risk surface .

B is false – Email is not a secure method for transferring sensitive information like passwords, even if encrypted.

C is correct – Unique administrator accounts help with accountability and tracking.

D is false – Long-term password validity reduces security. Passwords should be rotated regularly.

Reference from Huawei HCIP-Datacom-Core Technology Study Guide:

“To secure admin access, avoid account sharing, delete inactive users, and periodically update credentials through secure channels.”

(Chapter: Device Security – Section: Account Management)

The asbr-summary command is executed in the global OSPF view to summarize external routes. The abr-summary command is executed in the OSPF area view to summarize routes between areas. By default, the advertise parameter is enabled unless explicitly overridden by the not-advertise option ​.

The Originator ID in a BGP route represents the Router ID of the device that originally advertised the route into the BGP domain. Since RTA originates the route 10.1.1.0/24 into the BGP process, the Originator ID in the route received by RTD will be set to 1.1.1.1 ​.

Explanation of IS-IS Packet Types and Synchronization Process:

In the given scenario, R2 requests LSPs from R1 to synchronize its Link State Database (LSDB). The following IS-IS packet types are involved in this synchronization process:

1. P2P IIH (Point-to-Point IS-IS Hello):

Purpose: Establishes and maintains IS-IS neighbor relationships.

Step: This packet is exchanged initially to detect and maintain the adjacency between R1 and R2.

2. PSNP (Partial Sequence Number PDU):

Purpose: Requests missing or outdated LSPs (Link State PDUs) from a neighbor to synchronize the LSD

B.  

Step: In this case, R2 sends a PSNP to R1 to request the missing or outdated LSP.

3. LSP (Link State PDU):

Purpose: Contains routing information and is used to update the LSD

B.  

Step: R1 sends the requested LSPs to R2 for synchronization.

4. CSNP (Complete Sequence Number PDU):

Purpose: Lists all LSPs in the sender ' s LSDB to help neighbors verify and request missing LSPs.

Step: R1 sends a CSNP during retransmission timeout to notify R2 of its LSPs.