Meraki Dashboard Navigation Guide for the 500-220 Exam
The Cisco Meraki Solutions Specialist (500-220) exam assumes you already know where things live in the Dashboard. This guide maps the information architecture so you can find any feature by its click path, not by guesswork.
Contents
Quick summary
| Takeaway | What it means |
|---|---|
| Scope comes first | Almost every navigation decision starts with whether you are working at the organisation level or inside a single network. |
| The left rail is the map | The rail changes contents based on scope and on which product types a network contains. |
| Features cluster by product | Wireless, Switch, Security & SD-WAN, and Systems Manager each own a section of the rail with their own menus. |
| Blueprint maps to menus | Each 500-220 domain corresponds to identifiable areas of the Dashboard you should be able to reach without hunting. |
| Practise the click paths | Knowing a setting exists is not enough; the exam expects you to know the route to it. |
The two scopes: organisation and network
The single most important thing to understand about the Meraki Dashboard is scope. Everything you configure or monitor happens at one of two levels: the organisation or an individual network. Confusing the two is the fastest way to lose points on a navigation-heavy question.
The organisation is the top-level container. It holds your licensing, your inventory of unclaimed and claimed devices, administrators, and the list of networks. Settings applied here are broad and administrative. A network is a working set of devices in one place, such as a branch office, and it is where day-to-day configuration lives.
The Dashboard shows your current scope near the top of the interface. When a question asks where a task is performed, first decide whether it is an org-wide concern like adding a licence or an admin, or a network concern like configuring an SSID. That decision alone eliminates half the wrong answers.
What lives at the organisation level
Organisation-wide items include the licensing model and license expiry, the device inventory, administrators and their permissions, the network list, and cross-network settings such as change logs and configuration templates. If a task touches more than one network at once, expect it to live under Organisation.
What lives at the network level
Network-level items include the actual configuration of wireless, switching, and security appliances, plus clients, event logs, and per-network alerts. When you select a network, the left rail rebuilds itself to show only the product types that network contains.
Reading the left rail
The left rail is the primary navigation. At the organisation scope it shows Organisation-level menus. When you enter a network, the rail groups items by product type, and each group expands into its own set of pages.
A network that contains access points shows a Wireless section. A network with switches shows a Switch section. A network with an MX appliance shows Security & SD-WAN. Systems Manager appears for endpoint management. If a product section is missing from the rail, that network does not contain that device type, and that is itself a diagnostic clue.
- Wireless: SSIDs, access control, firewall and traffic shaping, radio settings, and wireless monitoring.
- Switch: switch ports, port profiles, switch settings, and switch stacks.
- Security & SD-WAN: appliance status, addressing and VLANs, firewall rules, and site-to-site VPN.
- Systems Manager: enrolled devices, profiles, and Sentry policies.
- Network-wide: general settings, administration, group policies, alerts, and event log.
Where the exam topics actually live
The 500-220 blueprint is organised into four domains. Each maps onto areas of the Dashboard you should be able to reach on reflex. Learning the click path for each domain is more durable than memorising isolated screens.
Cloud Management concerns the organisation scope: licensing, inventory, admin roles, and how the cloud architecture is administered. Design and Implementation live mostly at the network level, in the per-product sections where you build SSIDs, VLANs, firewall rules, and switch configuration. Monitoring and Troubleshooting spans both scopes, drawing on the event log, clients pages, and per-product status views.
SSIDs and group policies
Wireless configuration begins under Wireless > SSIDs, where you name and enable an SSID and set its association and splash settings. Group policies, which apply bandwidth, firewall, and traffic rules to sets of clients, are found under the network-wide menus and can then be applied to SSIDs or individual clients. Knowing that group policies are network-wide rather than buried inside the Wireless section is a common point of confusion the exam can test.
Monitoring and troubleshooting paths
The event log, network-wide clients list, and each product's status page are your troubleshooting starting points. When a question describes a symptom, the intended answer usually names a specific page you would open. Practise associating symptoms with the page that surfaces the evidence, such as a client's connection history versus an appliance's uplink status.
Studying navigation without a licensed organisation
Most candidates preparing for the 500-220 do not have access to a licensed, populated Meraki organisation to click around in. That is a genuine problem, because the exam assumes hands-on familiarity with the interface and its click paths.
You can still build a useful mental model. Work domain by domain, and for each objective write down the scope, the rail section, and the page name where the task is performed. Turn that into routes you can rehearse. A training simulator can support recall, but current Meraki documentation or a real organization remains the authority.
500-220 domains mapped to Dashboard scope and location
| Domain (weight) | Primary scope | Where it lives in the rail |
|---|---|---|
| Cloud Management (15%) | Organisation | Organisation menus: licensing, inventory, administrators |
| Design (30%) | Network | Per-product sections: Wireless, Switch, Security & SD-WAN |
| Implementation (25%) | Network | SSIDs, VLANs, firewall rules, switch ports, group policies |
| Monitoring & Troubleshooting (30%) | Both | Event log, clients, and per-product status pages |
Try CMSS Professor
CMSS Professor uses an original Dashboard-style simulator to rehearse selected organization, network, SSID, and group-policy paths without a licensed organization. It does not reproduce the live product, and its practice estimate is not an exam prediction. Inspect the free public preview before choosing one-time access.
Frequently asked questions
What is the difference between organisation and network scope?
The organisation is the top-level container for licensing, inventory, admins, and the network list. A network is a working set of devices where you configure wireless, switching, and security. Most configuration happens at the network level.
Where do I find SSIDs in the Meraki Dashboard?
SSIDs live at the network level under Wireless > SSIDs, but only if the network contains access points. Group policies that you apply to SSIDs are found under the network-wide menus, not inside the Wireless section.
Why does the left rail look different between networks?
The rail rebuilds based on the product types a network contains. A network with only switches will not show a Wireless section, so a missing section tells you which device types are present.
How can I practise navigation without a real Meraki organisation?
Map each objective to its scope, rail section, and page name, then rehearse selected paths. A training simulator can support recall without hardware, but it does not reproduce the live Dashboard.