Cisco 500-220 Practice Test 28
Question 270
A Cisco Meraki deployment engineer must choose a safe configuration decision and one validating observation. An enterprise needs cloud and campus routers to learn dozens of Auto VPN prefixes through a datacenter headend. Which TWO steps together provide a targeted response with objective verification? Select TWO answers.
- Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
- Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing.
- Check SSID security, RADIUS events, successful EAP exchange and the associated client VLAN.
- Inspect device enrollment, installed configuration profiles, OS support and compliance or security status.
- Use a corporate SSID with an appropriate identity method and VLAN assignment, separate from guest access.
Explanation
Correct Answers
A:The discriminating evidence is: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
B:The targeted next step is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing. The technical reason is: BGP route propagation requires a supported device and configuration and explicit policies; a working VPN tunnel alone does not prove BGP exchange. A successful verification would use: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
Incorrect Answers
C:That evidence is relevant to the distinct Meraki subject of MR corporate SSID with WPA enterprise authentication, not the specific BGP route exchange at VPN hub and datacenter requirement.
D:That evidence is relevant to the distinct Meraki subject of Systems Manager MDM enrollment and compliance profiles, not the specific BGP route exchange at VPN hub and datacenter requirement.
E:That action is relevant to the distinct Meraki subject of Enterprise SSID design for authentication and segmentation, not the specific BGP route exchange at VPN hub and datacenter requirement.
Question 271
A Cisco Meraki deployment engineer investigates this operational case: A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable. What is the most appropriate FIRST action to address the stated requirement? Select ONE best answer.
- Validate the device's management network DNS, gateway and permitted outbound cloud connectivity before changing user firewall rules.
- Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing.
- Design Systems Manager app deployment by device tags or target groups, verifying licensing and platform compatibility.
- Design separate guest, employee and IoT VLANs with deliberate inter-VLAN routing and firewall rules.
Explanation
Correct Answer
B:The targeted next step is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing.
Incorrect Answers
A:That action is relevant to the distinct Meraki subject of Meraki device check-in requirements and upstream firewall rules, not the specific BGP route exchange at VPN hub and datacenter requirement.
C:That action is relevant to the distinct Meraki subject of Managed app rollout and assignment scoping, not the specific BGP route exchange at VPN hub and datacenter requirement.
D:That action is relevant to the distinct Meraki subject of Network segmentation with VLANs and routed boundaries, not the specific BGP route exchange at VPN hub and datacenter requirement. For this scenario, the proper response is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing. Verify it through: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
Question 272
A peer reviewer evaluates the following Meraki case. A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable. The proposed action is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing. Which technical principle BEST supports this decision? Select ONE best answer.
- Dynamic routing relies on consistent interfaces, adjacency and advertisement policy; the presence of an MX does not imply automatic OSPF peering everywhere.
- Subscription, co-term and legacy per-device models have distinct compliance behavior, and one Dashboard organization does not mix these models.
- BGP route propagation requires a supported device and configuration and explicit policies; a working VPN tunnel alone does not prove BGP exchange.
- Meraki Dashboard distributes management configuration and telemetry while supported devices forward local user traffic using their running configuration.
Explanation
Correct Answer
C:BGP route propagation requires a supported device and configuration and explicit policies; a working VPN tunnel alone does not prove BGP exchange. In this situation (A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable.), it justifies the action: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing.
Incorrect Answers
A:Verify it through: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
B:That principle is relevant to the distinct Meraki subject of Meraki subscription licensing versus historical per-device licensing, not the specific BGP route exchange at VPN hub and datacenter requirement.
D:That principle is relevant to the distinct Meraki subject of Dashboard cloud control plane versus local packet forwarding, not the specific BGP route exchange at VPN hub and datacenter requirement.
Question 273
A Meraki support engineer must distinguish facts from assumptions. A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable. Which diagnostic observation MOST DIRECTLY verifies the problem or requirement? Select ONE best answer.
- Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
- Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
- Compare MR RF profile, supported client bands, per-channel utilization and a targeted roaming test.
- Check the MX route list, downstream interface addressing and forward/return reachability to a test endpoint.
Explanation
Correct Answer
B:Applied to the described situation (A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable.), it should establish: Only authorized branch prefixes appear in the upstream routing table and return traffic follows a valid path.
Incorrect Answers
A:That evidence is relevant to the distinct Meraki subject of Static route next hop and VPN route preference, not the specific BGP route exchange at VPN hub and datacenter requirement.
C:That evidence is relevant to the distinct Meraki subject of MR RF profile and band planning across device generations, not the specific BGP route exchange at VPN hub and datacenter requirement.
D:That evidence is relevant to the distinct Meraki subject of MX static routes to downstream layer three network, not the specific BGP route exchange at VPN hub and datacenter requirement.
Question 274
An implementation lead needs a measurable acceptance criterion for a Meraki change. A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable. The proposed validation is: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge. Which result BEST demonstrates that the intended requirement is satisfied? Select ONE best answer.
- Guest endpoints stay isolated while authorized staff reach only specified internal resources.
- Only authorized branch prefixes appear in the upstream routing table and return traffic follows a valid path.
- Real-time audio meets target quality while bulk file transfers are correctly deprioritized when links saturate.
- The team receives useful flow-level telemetry without mistaking it for a full forensic packet trace.
Explanation
Correct Answer
B:The acceptance criterion is: Only authorized branch prefixes appear in the upstream routing table and return traffic follows a valid path. Verify it using: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge. The associated corrective action is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing.
Incorrect Answers
A:That outcome is relevant to the distinct Meraki subject of Network segmentation with VLANs and routed boundaries, not the specific BGP route exchange at VPN hub and datacenter requirement. For this scenario, the proper response is: Evaluate supported BGP topology and path filters when a concentrator must exchange VPN routes with upstream routing. Verify it through: Check peer state, accepted and advertised prefixes and next-hop reachability at the intended datacenter edge.
C:That outcome is relevant to the distinct Meraki subject of End-to-end QoS trust and voice policy, not the specific BGP route exchange at VPN hub and datacenter requirement.
D:That outcome is relevant to the distinct Meraki subject of NetFlow export and traffic visibility limits, not the specific BGP route exchange at VPN hub and datacenter requirement.
Question 275
A Meraki operations reviewer examines this case. A datacenter changes a route filter and suddenly only a subset of branch networks remains reachable. Which assumption is the MOST DIRECTLY relevant unsafe or technically wrong shortcut to reject here? Select ONE best answer.
- Conclude that missing Wireless controls prove an MX firmware defect when the network contains only a security appliance.
- Place both MX units behind the same unplugged power strip and claim hardware redundancy guarantees site uptime.
- Assume BGP automatically advertises all private networks from any device plugged into the VPN hub.
- Add a broad default route toward an inactive interface to fix one missing warehouse subnet.
Explanation
Correct Answer
C:It conflicts with the relevant behavior: BGP route propagation requires a supported device and configuration and explicit policies; a working VPN tunnel alone does not prove BGP exchange.
Incorrect Answers
A:That proposal is unsafe in its own context (the separate topic of Combined networks and device role visibility), but it is not the shortcut tied most directly to this incident. The case-specific fault to reject concerns BGP route exchange at VPN hub and datacenter: Assume BGP automatically advertises all private networks from any device plugged into the VPN hub.
B:That proposal is unsafe in its own context (the separate topic of MX high availability warm spare and uplink failover), but it is not the shortcut tied most directly to this incident. The case-specific fault to reject concerns BGP route exchange at VPN hub and datacenter: Assume BGP automatically advertises all private networks from any device plugged into the VPN hub.
D:That proposal is unsafe in its own context (the separate topic of Static route next hop and VPN route preference), but it is not the shortcut tied most directly to this incident. The case-specific fault to reject concerns BGP route exchange at VPN hub and datacenter: Assume BGP automatically advertises all private networks from any device plugged into the VPN hub.
Question 276
A Cisco Meraki deployment engineer investigates this operational case: An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN. What is the most appropriate FIRST action to address the stated requirement? Select ONE best answer.
- Claim the verified device serials into the correct organization and pre-stage the network settings before field installation.
- Choose an appropriate supported route exchange and validate OSPF neighbor topology rather than inventing static routes for every subnet.
- Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing.
- Follow Dashboard API pagination links until all authorized result pages are retrieved before declaring an inventory complete.
Explanation
Correct Answer
C:The targeted next step is: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing. The technical reason is: A static route pointing to an unreachable next hop cannot repair a missing layer-2 or layer-3 path; prefix selection determines eligible matches.
Incorrect Answers
A:That action is relevant to the distinct Meraki subject of Bulk device claim and zero-touch staging, not the specific Static route next hop and VPN route preference requirement.
B:That action is relevant to the distinct Meraki subject of OSPF LAN exchange and MX routing design, not the specific Static route next hop and VPN route preference requirement.
D:That action is relevant to the distinct Meraki subject of API pagination and complete inventory reconciliation, not the specific Static route next hop and VPN route preference requirement.
Question 277
A peer reviewer evaluates the following Meraki case. An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN. The proposed action is: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing. Which technical principle BEST supports this decision? Select ONE best answer.
- Hub-to-hub participation can enable meshing while spoke designs reduce unnecessary peer relationships in large deployments.
- A static route pointing to an unreachable next hop cannot repair a missing layer-2 or layer-3 path; prefix selection determines eligible matches.
- Dynamic routing relies on consistent interfaces, adjacency and advertisement policy; the presence of an MX does not imply automatic OSPF peering everywhere.
- Add a broad default route toward an inactive interface to fix one missing warehouse subnet.
Explanation
Correct Answer
B:A static route pointing to an unreachable next hop cannot repair a missing layer-2 or layer-3 path; prefix selection determines eligible matches. In this situation (An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN.), it justifies the action: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing.
Incorrect Answers
A:That principle is relevant to the distinct Meraki subject of Mesh Auto VPN scaling and required lateral paths, not the specific Static route next hop and VPN route preference requirement.
C:That principle is relevant to the distinct Meraki subject of OSPF LAN exchange and MX routing design, not the specific Static route next hop and VPN route preference requirement.
D:This is an unsafe shortcut: Add a broad default route toward an inactive interface to fix one missing warehouse subnet. It does not establish the needed behavior: A static route pointing to an unreachable next hop cannot repair a missing layer-2 or layer-3 path; prefix selection determines eligible matches. The controlled response is: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing.
Question 278
A Meraki support engineer must distinguish facts from assumptions. An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN. Which diagnostic observation MOST DIRECTLY verifies the problem or requirement? Select ONE best answer.
- Compare client event history, AP channel/utilization, RSSI trends and authentication records during the failure.
- Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
- Inspect VLAN IDs, L3 gateway placement, DHCP scopes and the rule path for a representative cross-VLAN flow.
- Check SVI addressing, routing state, next hops and representative inter-VLAN traffic.
Explanation
Correct Answer
B:The discriminating evidence is: Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP. Expected result: The intended private subnet is forwarded through a reachable next hop without stealing unrelated routes.
Incorrect Answers
A:That evidence is relevant to the distinct Meraki subject of MR wireless RF interference and roaming diagnosis, not the specific Static route next hop and VPN route preference requirement.
C:That evidence is relevant to the distinct Meraki subject of Network segmentation with VLANs and routed boundaries, not the specific Static route next hop and VPN route preference requirement. For this scenario, the proper response is: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing.
D:That evidence is relevant to the distinct Meraki subject of MS switch routing interface and L3 reachability, not the specific Static route next hop and VPN route preference requirement.
Question 279
An implementation lead needs a measurable acceptance criterion for a Meraki change. An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN. The proposed validation is: Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP. Which result BEST demonstrates that the intended requirement is satisfied? Select ONE best answer.
- Branch and datacenter routers exchange only expected internal routes with controlled convergence.
- The intended private subnet is forwarded through a reachable next hop without stealing unrelated routes.
- Voice stays intelligible while bulk traffic shares the link according to the approved policy.
- The branch reaches approved hub-hosted applications while unnecessary inter-spoke tunnels are absent.
Explanation
Correct Answer
B:The acceptance criterion is: The intended private subnet is forwarded through a reachable next hop without stealing unrelated routes. Verify it using: Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
Incorrect Answers
A:That outcome is relevant to the distinct Meraki subject of OSPF LAN exchange and MX routing design, not the specific Static route next hop and VPN route preference requirement.
C:That outcome is relevant to the distinct Meraki subject of MS QoS trust and voice traffic classification, not the specific Static route next hop and VPN route preference requirement.
D:That outcome is relevant to the distinct Meraki subject of Auto VPN hub-and-spoke site reachability, not the specific Static route next hop and VPN route preference requirement.
Question 280
A Cisco Meraki deployment engineer must choose a safe configuration decision and one validating observation. An MX must reach a downstream printer network behind an L3 switch but the static next hop is configured in the wrong VLAN. Which TWO steps together provide a targeted response with objective verification? Select TWO answers.
- Compare configured VLAN ID, interface address, DHCP scope and one client's lease and gateway reachability.
- Choose hubs for branches that must reach shared datacenter subnets and verify every spoke has the intended hub association.
- Plan managed switch access-port protections against rogue DHCP, spoofing and accidental loops according to platform support.
- Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
- Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing.
Explanation
Correct Answers
D:The discriminating evidence is: Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
E:The targeted next step is: Verify static-route next hops and subnet specificity before selecting them as a substitute for dynamic routing. The technical reason is: A static route pointing to an unreachable next hop cannot repair a missing layer-2 or layer-3 path; prefix selection determines eligible matches. A successful verification would use: Compare destination prefix, next-hop connectivity, route table and return path for a chosen test IP.
Incorrect Answers
A:That evidence is relevant to the distinct Meraki subject of MX VLAN interfaces and DHCP configuration, not the specific Static route next hop and VPN route preference requirement.
B:That action is relevant to the distinct Meraki subject of Auto VPN hub-and-spoke site reachability, not the specific Static route next hop and VPN route preference requirement.
C:That action is relevant to the distinct Meraki subject of Layer two protections and unauthorized DHCP sources, not the specific Static route next hop and VPN route preference requirement.