500-220 Sample Questions Answers

Assuming this MX has established a full tunnel with its VPN peer, the MX will route the WebEx traffic based on the SD-WAN policy configured in the exhibit. The SD-WAN policy has two performance classes: Conf and Default. The Conf performance class matches the traffic with destination port 9000, which is used by WebEx for VoIP and video RTP3. The Conf performance class has a preferred uplink of WAN 2 and a failover uplink of WAN 1. It also has thresholds for latency, jitter, and loss that determine when to switch from the preferred uplink to the failover uplink. Therefore, the WebEx traffic will prefer WAN 2 as long as it meets the thresholds in the Conf performance class. If WAN 2 exceeds the thresholds or goes down, the WebEx traffic will switch to WAN 1 as the failover uplink.

To clarify, to optimize load balancing asymmetrically with a 4:1 ratio between links, two actions that are required are:

• Enable load balancing: This option allows the MX to use both of its uplinks for load balancing. When load balancing is enabled under Security & SD-WAN > Configure > SD-WAN & Traffic shaping, traffic flows will be distributed between the two uplinks proportional to the WAN 1 and WAN 2 bandwidths specified under Uplink configuration1.
• Change the assigned speeds of WAN 1 and WAN 2 so that the ratio is 4:1: The assigned speed of a WAN link is a value that indicates the bandwidth available on that link. By changing the assigned speeds of WAN 1 and WAN 2 so that they reflect the desired load-balancing ratio, the administrator can ensure that the MX uses both links efficiently and proportionally1. For example, if WAN 1 has a bandwidth of 100 Mbps and WAN 2 has a bandwidth of 25 Mbps, then setting their assigned speeds to 100 Mbps and 25 Mbps respectively will achieve a 4:1 load-balancing ratio.

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

IOS:

• Kiosk mode
• Single App mode
• Wallpaper
• Cisco Security Connector
• Active Sync

Android:

• Kiosk mode
• Backpack
• Wallpaper
• Active Sync

This question is related to the topic of System Manager: Getting Started in the Cisco Meraki documentation. You can find more information about this topic in the [System Manager: Getting Started] article or the [System Manager Overview] page.

https://documentation.meraki.com/SM/Profiles_and_Settings/Configuration_Settings_Payloads

When band steering is enabled on an SSID, APs will stop advertising that SSID in 2.4GHz beacons. Since 2.4GHz-only clients that rely on a passive scan will not “see” that SSID in beacons, they might not be able to join this SSID unless they do an active scan or have been pre-configured with the SSID name and security settings (for example, a pre-shared key). https://documentation.meraki.com/MR/Radio_Settings/Band_Steering

A screenshot of a computer screen Description automatically generated

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies

"Inbound and outbound flows will generate a syslog message showing the source and destination along with port numbers and the firewall rule that they matched. For inbound rules, 1=deny and 0=allow." https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Syslog_Server_Overview_and_Configuration

This is the approximate number of APs that are needed based on client count, assuming that each AP can support up to 25 concurrent video streaming users. This can be calculated by using the formula:

Number of APs = (Number of Users x Percentage of Users on a Band) / Number of Users per AP on that Band

Where Number of Users is 100, Percentage of Users on 2.4 Ghz is 30%, Percentage of Users on 5 Ghz is 70%, Number of Users per AP on 2.4 Ghz is 15, and Number of Users per AP on 5 Ghz is 30. Therefore,

Number of APs = (100 x 0.3 / 15) + (100 x 0.7 / 30) Number of APs = (3.33) + (2.33) Number of APs = 5.66

Rounding to the nearest whole number, the number of APs is 4.

This question is related to the topic of Wireless Capacity Planning in the Cisco Meraki documentation. You can find more information about this topic in the [Wireless Capacity Planning] article or the [Best Practice Design - MR Wireless] page.

See Monitoring Mesh section Mesh monitoring tools are located at the bottom of every AP detail page, which can be accessed by navigating to Wireless > Monitor > Access Points, then clicking on an Access Point. https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Wireless_Mesh_Networking

The settings that will be cloned using the Cisco Meraki MS switch cloning feature are:

• port name
• interface type
• STP bridge property

The settings that will not be cloned using the Cisco Meraki MS switch cloning feature are:

• switch management IP
• switch name

Routed Mode:

• This mode is the default mode of operation
• This mode is generally also the default gateway for devices on the LAN
• Client traffic to the internet has the source IP rewritten to match the WAN IP of the appliance
• DHCP services can be configured on the MX appliance

Passthrough Mode:

• The MX appliance acts as a layer 2 bridge
• VLANs cannot be configured
• No address translation is provided
• This mode is not recommended at the network perimeter

This question is related to the topic of MX Addressing and VLANs in the Cisco Meraki documentation. You can find more information about this topic in the MX Addressing and VLANs article or the General MX Best Practices page.

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%).

The error message “NotNow” is seen in the Event Log on an iOS device's details page when an action cannot be performed because the device is locked with a passcode. These actions include pushing managed apps, installing profiles, and other actions. When this occurs the device will attempt to re-connect with the MDM server as soon as the device is unlocked in order to retry the action. https://documentation.meraki.com/SM/Monitoring_and_Reporting/Status_of_%22NotNow%22_in_Systems_Manager_Event_Log

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.

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

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.

https://www.ciscolive.com/c/dam/r/ciscolive/latam/docs/2019/pdf/BRKCRS-1579.pdf

Implementing syslog versus SNMP can meet the design requirement of gathering information such as flows and client connectivity. Syslog can collect and report various types of events, such as VPN connectivity, uplink connectivity, DHCP leases, firewall rules, IDS alerts, and security events. Syslog can also provide detailed information about the flows and client connectivity on the network devices, such as source and destination IP addresses, ports, protocols, bytes transferred, etc. SNMP, on the other hand, can collect and report various statistics and information about the network devices, such as CPU utilization, interface status, memory usage, etc. However, SNMP does not provide as much information about the flows and client connectivity as syslog does.