500-220 Exam Dumps - Engineering Cisco Meraki Solutions v1.0

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.

These are the two features and functions that are supported when using an MX appliance in Passthrough mode. According to the [MX Addressing and VLANs] article, Passthrough mode allows the MX appliance to act as a layer 2 bridge, passing traffic between its LAN and WAN ports without performing any routing or address translation. However, some features such as intrusion prevention and site-to-site VPN are still available in this mode.

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

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

The correct answer is B and D. These are the two methods of targeting and applying management profiles to System Manager clients, according to the [System Manager: Getting Started] article. The article explains that:

• Defining the scope: This method allows you to target devices based on their network, tag, or owner. You can define the scope of a profile from the Systems Manager > Manage > Settings page or from the Systems Manager > Monitor > Overview page.
• Using device tags: This method allows you to target devices based on their attributes, such as OS, model, location, or user. You can use device tags to create dynamic groups of devices that share common characteristics. You can apply device tags from the Systems Manager > Monitor > Devices page or from the Systems Manager > Manage > Tags page.

"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

What happens if a network loses connectivity to the Meraki cloud?

Because of Meraki’s out of band architecture, most end users are not affected if Meraki wireless APs, switches, or security appliances cannot

communicate with Meraki’s cloud services (e.g., because of a temporary WAN failure):

• Users can access the local network (printers, file shares, etc.)

• If WAN connectivity is available, users can access the Internet

• Network policies (firewall rules, QoS, etc.) continue to be enforced

• Users can authenticate via 802.1X/RADIUS and can roam wirelessly between access points

• Users can initiate and renew DHCP leases

• Established VPN tunnels continue to operate

• Local configuration tools are available (e.g., device IP configuration

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

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.

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.

https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Configuring_SAML_Single_Sign-on_for_Dashboard

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.

By default, iOS apps provisioned through Systems Manager that are found in the App Store will self-update if automatic updates has been turned on in the Settings. For custom iOS apps, or to manually push down updates, check the following steps. https://documentation.meraki.com/SM/Apps_and_Software/Updating_Managed_iOS_Apps

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/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/High_Density_Wi-Fi_Deployments

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