Question 530At fictional Harborview ISP 133, a regional service-provider network, during a two-site transit migration, operations observes: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Why is this particular correction the best fit for the stated defect? Integrated routing and bridging links a bridge domain to an IP routing gateway. Layer 2 switching forwards traffic within the configured VLAN bridge domain. Customer VLAN IDs are not globally unique and require deliberate provider separation. The OSPF router ID uniquely identifies a router in link-state advertisements. ExplanationCorrect Answer A:Integrated routing and bridging links a bridge domain to an IP routing gateway. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Local hosts reach the IRB gateway and authorized routed subnets beyond it. Incorrect Answers B:Layer 2 switching forwards traffic within the configured VLAN bridge domain. This addresses a situation in which hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; however, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. C:Customer VLAN IDs are not globally unique and require deliberate provider separation. The choice would be appropriate if two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. D:The OSPF router ID uniquely identifies a router in link-state advertisements. That option concerns two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. The problem here is different: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 531At fictional Harborview ISP 133, a regional service-provider network, during a two-site transit migration, operations observes: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. What direct observation would prove the corrective action worked? The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Two identical inner customer tags remain isolated by separate outer tags or service instances. Local hosts reach the IRB gateway and authorized routed subnets beyond it. A controlled packet trace follows the intended segment program under the chosen IGP topology. ExplanationCorrect Answer C:Local hosts reach the IRB gateway and authorized routed subnets beyond it. Integrated routing and bridging links a bridge domain to an IP routing gateway. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Incorrect Answers A:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. It is useful for situations where an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the reported fault, though, is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:Two identical inner customer tags remain isolated by separate outer tags or service instances. That relates to circumstances in which two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Here the problem is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. D:A controlled packet trace follows the intended segment program under the chosen IGP topology. The choice would be appropriate if a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path. Here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 532At fictional Harborview ISP 133, a regional service-provider network, during a two-site transit migration, operations observes: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Which failure consequence follows most closely from ignoring this issue? Traffic leaks or becomes blackholed at the L2/L3 boundary. Unnecessary filtering interrupts normal bridged service. Hosts remain confined to a local broadcast domain. Traffic unexpectedly overloads a low-capacity link. ExplanationCorrect Answer C:Hosts remain confined to a local broadcast domain. Integrated routing and bridging links a bridge domain to an IP routing gateway. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Incorrect Answers A:Traffic leaks or becomes blackholed at the L2/L3 boundary. This relates to a case where an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the current situation is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:Unnecessary filtering interrupts normal bridged service. It is useful for situations where a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; the reported fault, though, is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. D:Traffic unexpectedly overloads a low-capacity link. This addresses a situation in which an intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected; however, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 533In a separate fictional JNCIS-SP lab review for Greenbridge ISP 134, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. What intervention most directly restores the intended routing or switching behavior? Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Check transit MPLS forwarding state and repair the missing label operation. ExplanationCorrect Answer C:Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Local hosts reach the IRB gateway and authorized routed subnets beyond it. Integrated routing and bridging links a bridge domain to an IP routing gateway. Incorrect Answers A:Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. This could help if an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port, but not when customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. This relates to a case where a provider access port drops customer tagged frames because it was configured for untagged access mode; the current situation is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. D:Check transit MPLS forwarding state and repair the missing label operation. That relates to circumstances in which an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Here the problem is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 534In a separate fictional JNCIS-SP lab review for Greenbridge ISP 134, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Which networking principle explains why the proposed correction is appropriate? Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Integrated routing and bridging links a bridge domain to an IP routing gateway. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. ExplanationCorrect Answer C:Integrated routing and bridging links a bridge domain to an IP routing gateway. Local hosts reach the IRB gateway and authorized routed subnets beyond it. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Incorrect Answers A:Virtual switching can provide separate Layer 2 forwarding contexts for tenants. It is relevant if two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services, but the reported issue is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. This could help if provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag, but not when customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. D:IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. It is useful for situations where an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface; the reported fault, though, is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 535In a separate fictional JNCIS-SP lab review for Greenbridge ISP 134, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Which validation result would confirm the design is now functioning? A correctly sized customer frame traverses the entire provider handoff without drops. The customer MAC is relearned on the authorized new handoff interface. An MPLS-aware trace and service probe pass before and after the selected cutover. Local hosts reach the IRB gateway and authorized routed subnets beyond it. ExplanationCorrect Answer D:Local hosts reach the IRB gateway and authorized routed subnets beyond it. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Integrated routing and bridging links a bridge domain to an IP routing gateway. Incorrect Answers A:A correctly sized customer frame traverses the entire provider handoff without drops. This is applicable when a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU; the present condition is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:The customer MAC is relearned on the authorized new handoff interface. It is relevant if a MAC is learned on an unexpected aggregation interface following a customer circuit move, but the reported issue is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. C:An MPLS-aware trace and service probe pass before and after the selected cutover. This could help if a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested, but not when customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 536In a separate fictional JNCIS-SP lab review for Greenbridge ISP 134, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. What likely service impact does this condition create? Repeated flooding and customer frame loss continue despite healthy routes. Subscriber VLANs collide or customer traffic arrives in the wrong service. Unauthorized OSPF adjacency could expose route-control information to customer equipment. Hosts remain confined to a local broadcast domain. ExplanationCorrect Answer D:Hosts remain confined to a local broadcast domain. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. Integrated routing and bridging links a bridge domain to an IP routing gateway. Incorrect Answers A:Repeated flooding and customer frame loss continue despite healthy routes. That could help when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; here, customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. B:Subscriber VLANs collide or customer traffic arrives in the wrong service. This is applicable when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; the present condition is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. C:Unauthorized OSPF adjacency could expose route-control information to customer equipment. It is relevant if a provider PE inadvertently attempts to form an OSPF adjacency on a customer LAN that should advertise reachability only, but the reported issue is that customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent.
Question 537At fictional Fairhaven Broadband 135, a regional service-provider network, during a preproduction design validation, operations observes: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Which configuration or operational correction most directly addresses this failure? Associate the gateway with the intended routing and bridging contexts and inspect both tables. Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. Investigate Ethernet MAC learning and bridge-table forwarding before changing IP routing. Check LDP transport address reachability and session parameters through the IGP. ExplanationCorrect Answer A:Associate the gateway with the intended routing and bridging contexts and inspect both tables. IRB traffic must bridge and route within an intentionally consistent service context. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Incorrect Answers B:Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. That could help when an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port; here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Investigate Ethernet MAC learning and bridge-table forwarding before changing IP routing. This is applicable when an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown; the present condition is that an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:Check LDP transport address reachability and session parameters through the IGP. It is relevant if two core routers cannot form an LDP session even though they discover one another on the connected link, but the reported issue is that an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 538At fictional Fairhaven Broadband 135, a regional service-provider network, during a preproduction design validation, operations observes: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Which Junos forwarding or control-plane rule applies to this case? Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. Dynamic MAC entries may age out and be relearned on subsequent traffic. BGP import policy governs which learned prefixes enter local route selection. IRB traffic must bridge and route within an intentionally consistent service context. ExplanationCorrect Answer D:IRB traffic must bridge and route within an intentionally consistent service context. Associate the gateway with the intended routing and bridging contexts and inspect both tables. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Incorrect Answers A:Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. It addresses a different problem: An operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. B:Dynamic MAC entries may age out and be relearned on subsequent traffic. This could matter when a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. In this case, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:BGP import policy governs which learned prefixes enter local route selection. That could help when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 539At fictional Fairhaven Broadband 135, a regional service-provider network, during a preproduction design validation, operations observes: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. What operational evidence best establishes successful remediation? The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. The bridge table resolves the destination MAC to the correct egress port. Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. The expected customer prefix appears in the advertised-route output and unintended prefixes do not. ExplanationCorrect Answer A:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. IRB traffic must bridge and route within an intentionally consistent service context. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Incorrect Answers B:The bridge table resolves the destination MAC to the correct egress port. It addresses a different problem: An operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Frame capture shows the intended outer S-tag and unchanged inner customer tag at handoff. This could matter when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. In this case, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:The expected customer prefix appears in the advertised-route output and unintended prefixes do not. That could help when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 540At fictional Fairhaven Broadband 135, a regional service-provider network, during a preproduction design validation, operations observes: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Which operational harm would persist without the intended correction? Customers can inject unapproved Layer 2 traffic into the provider bridge. A repeated VLAN number causes cross-customer broadcast leakage. Routers compute incompatible paths and traffic loops or blackholes can result. Traffic leaks or becomes blackholed at the L2/L3 boundary. ExplanationCorrect Answer D:Traffic leaks or becomes blackholed at the L2/L3 boundary. IRB traffic must bridge and route within an intentionally consistent service context. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Incorrect Answers A:Customers can inject unapproved Layer 2 traffic into the provider bridge. The choice would be appropriate if an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. B:A repeated VLAN number causes cross-customer broadcast leakage. That option concerns two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. The problem here is different: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Routers compute incompatible paths and traffic loops or blackholes can result. It addresses a different problem: Two supposed adjacent routers have different views of a backbone link because database synchronization never completes. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.