In a Frame Relay WAN, you must configure a static map to the remote S-AMER site at IP address 172.16.1.3 over DLCI 704. Which frame-relay map command correctly creates this mapping and forwards broadcasts?

Introduction / Context:
Frame Relay is a legacy wide area network technology that uses virtual circuits identified by Data Link Connection Identifiers, commonly called DLCIs. When dynamic Inverse ARP is not available or not desired, administrators can configure static frame-relay map statements to associate remote IP addresses with local DLCIs. Understanding the correct syntax of the frame-relay map command is essential for ensuring that traffic reaches remote sites and that broadcasts and multicast packets are forwarded when needed.

Given Data / Assumptions:

• Remote site S-AMER has IP address 172.16.1.3.
• The local Frame Relay interface uses DLCI 704 to reach S-AMER.
• Broadcast and multicast traffic should be forwarded over this virtual circuit.
• We are configuring a static mapping on a Cisco router interface.

Concept / Approach:
The frame-relay map command associates a Layer 3 protocol address with a Layer 2 DLCI. The basic syntax for IPv4 is frame-relay map ip remote-ip dlci broadcast. The broadcast keyword tells the router to forward broadcast and multicast frames, which is important for protocols like routing updates or DHCP that rely on broadcast traffic. Therefore, the correct command must use the given remote IP address, the correct DLCI, and the broadcast keyword in the proper order.

Step-by-Step Solution:
1. Identify the remote IP address of the S-AMER site: 172.16.1.3.2. Identify the correct DLCI for reaching S-AMER: 704.3. Apply the Cisco syntax: frame-relay map ip remote-ip dlci broadcast.4. Substituting values gives: frame-relay map ip 172.16.1.3 704 broadcast.5. Compare this to the options and select the one that exactly matches.

Verification / Alternative check:
You can verify this choice by checking the interface configuration in Cisco documentation. The remote IP address must match the far end router interface, and the DLCI must match the value assigned by the Frame Relay provider. Verifying these details against a network diagram or service provider information confirms that DLCI 704 is correct for S-AMER and that the broadcast keyword is required for dynamic routing protocols.

Why Other Options Are Wrong:
Option B uses DLCI 196, option C uses 702, and option D uses 344. These DLCIs represent different virtual circuits and would send traffic to the wrong remote endpoint. Even though the syntax and broadcast keyword look correct, using an incorrect DLCI prevents packets from reaching the S-AMER site. Therefore, only the mapping with DLCI 704 is valid for this scenario.

Common Pitfalls:
A common mistake is to forget the broadcast keyword, which can cause routing protocols to fail across the Frame Relay cloud. Another pitfall is assuming that the DLCI is globally significant; in reality, it is often locally significant to each router, which means you must always check the provider documentation or network diagram. Confusing DLCI values between different remote sites can break connectivity in complex hub-and-spoke topologies.

Final Answer:
frame-relay map ip 172.16.1.3 704 broadcast