500-220 Practice Questions

https://documentation.meraki.com/SM/Monitoring_and_Reporting/MDM_Commands_in_Systems

_Manager - Under Live Tools Selective Wiping is only for MacOS. Here we have Windows Laptop as

well

Reference: https://documentation.meraki.com/SM/Other_Topics/Systems_Manager_FAQ

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_

Design/Best_Practice_Design_-_MX_Security_and_SD-

WAN/MX_Templates_Best_Practices#:~:text=policy%2C%20choose%20Save-

,Local%20Overrides,will%20override%20the%20template%20configuration.

Ports used to contact the VPN registry:

- Source UDP port range 32768-61000

- Destination UDP port 9350 or UDP port 9351

Ports used for IPsec tunneling:

- Source UDP port range 32768-61000

- Destination UDP port range 32768-61000

https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN__Configuration_and_Troubleshooting

Reference: https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN__Configuration_and_Troubleshooting

Verbs in the API follow the usual REST conventions:

GET returns the value of a resource or a list of resources, depending on whether an identifier is

specified.

POST adds a new resource

PUT updates a resource

DELETE removes a resource

https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboar

d_API

https://documentation.meraki.com/MS/Layer_3_Switching/MS_Warm_Spare_(VRRP)_Overview

This is because the SD-WAN policy for “All Databases & cloud services” has the following settings:

Uplink selection policy: Prefer WAN1, Fail over if down

Traffic filters: Custom performance classes

Custom performance classes: Database

Database performance criteria: Maximum latency 200 ms, Maximum jitter 20 ms, Maximum loss 1%

This means that the SD-WAN traffic will be routed via WAN1 by default, unless WAN1 is down or fails

to meet the database performance criteria. In that case, the traffic will be routed via WAN2, if WAN2

meets the database performance criteria. Therefore, the condition that will cause the traffic to be

routed via WAN2 is when WAN1 tunnel latency is 20 ms or more (which exceeds the maximum jitter

of 20 ms), and WAN2 tunnel meets the configured performance criteria (maximum latency 200 ms,

maximum jitter 20 ms, maximum loss 1%).

See Behavior - Firmware MX 15.11 or Lower section For MXs running firmware MX15.11 or below,

the source IP that MX uses while pinging a destination is the MX IP of highest VLAN ID. If the

destination is across a VPN, the MX uses the MX IP of highest VLAN ID participating in VPN. For MXs

running firmware MX 15.12+, additional ping options have been added to the live tool. The ping tool

now has a drop down to select the source IP address for pinging destinations from the MX.

https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the

_Ping_Live_Tool

If you only need traffic statistics from your spoke site clients then you only need to enable insight on

the spoke network as the hub site will not gather data for remote sites.

https://community.meraki.com/t5/Wireless-LAN/Meraki-Insight-Licensing/m-p/152684

A license is only required for those networks where Meraki Insight functionality is desired. One

license is required per network, regardless of whether that network has a single MX or HA pair.

Licenses can be moved between networks, but historical data for the old network will be lost.

https://meraki.cisco.com/lib/pdf/meraki_datasheet_mi.pdf

https://documentation.meraki.com/MI/MI_Web_App_Health/Overview#:~:text=On%20this%20pag

e%2C%20you%20can,that%20ports%20cannot%20be%20specified.

https://documentation.meraki.com/MR/Deployment_Guides/Mesh_Deployment_Guide

There will be a throughput reduction (~50% reduction) with each “hop” in a mesh. It is

recommended that a mesh network be designed for no more than one mesh hop from the gateway

to client device.