500-220 Exam Preparation Material | Engineering Cisco Meraki Solutions v1.0

Explanation:
https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/High_Density_Wi-Fi_Deployments

Explanation:
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.

Explanation:
When configuring an SSID with a Sign-On Splash page, to ensure that unauthenticated clients do not have full network access and are not added to the allow list (also known as a whitelist), you would need to adjust settings that relate to client access and network security post-authentication. The two settings that are relevant in this context are:
Controller disconnection behavior
This setting determines what happens if the connection between the access point and the controller (in this case, the Meraki cloud) is lost. If set to restrict access, unauthenticated clients would not be able to access the network if the AP cannot verify their status with the controller.
Firewall & traffic shaping
By configuring firewall and traffic shaping rules, you can restrict network access for unauthenticated clients. Even if they bypass the splash page, they wouldn't be able to access the network fully without proper authentication if the rules are set to block or limit traffic.

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

Explanation:
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