500-220 Sample Questions Answers

On the device, navigate to Settings > General > Device Management

Select Meraki Management, and select Remove to delete the management profile and any managed configuration profiles installed via SM

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

This can be determined by looking at the concentrator routing table and finding the entry for the destination IP 10.116.32.4. The next hop for this entry is the Auto VPN peer “Store 1532 – appliance”.

This question is related to the topic of Implementing Dynamic Routing Protocols in the Engineering Cisco Meraki Solutions (ECMS) official training documentation. You can find more information about this topic in the ECMS v2.2 Course Overview or the ECMS1 v2.1 Course Overview.

https://documentation.meraki.com/SM/Device_Enrollment/Containerization_with_Systems_Manager

There are two operations in which a license can be applied, License more devices or Renew my dashboard license. This article will compare both operations and describe their behaviors. https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_-_License_More_Devices_vs_Renewal

These are the two operations that enable licenses to be applied in an organization that uses the Co-Termination licensing model. According to the Meraki Co-Termination Licensing Overview, there are two ways to add licenses to an organization:

• Renewing the Dashboard license: This option allows you to extend the co-termination date of your organization by purchasing new licenses for the same or longer term as your existing licenses. You can renew your Dashboard license from the Organization > Configure > License Info page or from the Meraki Dashboard homepage.
• Licensing more devices: This option allows you to add new devices to your organization by purchasing new licenses for them. You can license more devices from the Organization > Inventory page or from the Meraki Dashboard homepage.

Table Description automatically generated with medium confidence

Configuring a syslog server for the network is the Cisco Meraki best practice method to preserve complete historical network event logs. A syslog server can be configured to store messages for reporting purposes from MX Security Appliances, MR Access Points, and MS switches1. The syslog server can collect various types of events, such as VPN connectivity, uplink connectivity, DHCP leases, firewall rules, IDS alerts, and security events2. The syslog server can also help with troubleshooting and monitoring the network performance and security.

If a Meraki Access Point does not have a configuration from the Meraki Cloud Controller it will instead broadcast a default SSID of "Meraki-Scanning."

vs

-scanning

Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway.

https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

This is because the AP is broadcasting the default SSID “meraki-scanning” which is only broadcast when the AP has never connected to the Meraki Cloud Controller1.

This question is related to the topic of Wireless Access Points Quick Start in the Cisco Meraki documentation. You can find more information about this topic in the Wireless Access Points Quick Start article or the Using the Cisco Meraki Device Local Status Page page.

When a rogue access point is contained, clients will be unable to connect to the rogue AP. Additionally, any currently associated clients will lose their connection to the rogue AP. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal

https://documentation.meraki.com/MV/Advanced_Configuration/Scheduled_Recording

By default, the Meraki security camera's will record continuously 24/7. In some situations, certain times of day are not allowed to be recorded. Scheduled recording covers this requirement as well as improve the video retention capabilities of the camera.

https://developer.cisco.com/meraki/api-v1/#!clone-organization

Route Priority

Each type of route configured on the MX has a specific priority in comparison with other types of routes. The priority is as follows:

Directly Connected

Client VPN

Static Routes

AutoVPN Routes

Non-Meraki VPN Peers

BGP learned Routes

NAT*

https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior

The performance probe is a small payload (approximately 100 bytes) of UDP data sent over all established VPN tunnels every 1 second. MX appliances track the rate of successful responses and the time that elapses before receiving a response. This data allows the MX to determine the packet loss, latency, and jitter over each VPN tunnel in order to make the necessary performance-based decisions.

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/Meraki_SD-WAN#Performance_Probes