Meraki Solutions Specialist flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Meraki dashboard management plane

Cloud-hosted Cisco Meraki interface where administrators configure and monitor organizations, networks, and devices; devices poll the dashboard and keep running cached configuration if the cloud is unreachable.

Organization-network-device hierarchy

Meraki's three-tier structure: an organization owns licenses, administrators, and inventory; networks group devices by site or purpose; each device belongs to exactly one network.

Meraki device outbound connectivity

Meraki devices open outbound TCP 443 sessions to the Meraki cloud; no inbound firewall ports, public IP addresses, or management tunnels are required for dashboard control.

Co-termination licensing model

A per-organization model in which all license expirations align to one shared date, calculated from the value and duration of every license claimed into the organization.

Per-device licensing model

A model where each device holds its own license with an independent expiration date, allowing mixed terms and devices to be added or removed without shifting other expirations.

Meraki license grace period

After a license expires, the device enters roughly a 30-day grace period during which it still passes traffic; afterward it stops forwarding until a valid license is applied.

Organization administrator roles

Role-based dashboard permissions covering full organization admin, read-only organization admin, network admin limited to chosen networks, and monitor-only, with SAML SSO and MFA support.

Zero-touch provisioning

Deployment process in which a serial or order number is claimed into organization inventory and assigned to a network; on boot with internet access the device downloads its configuration automatically.

Configuration templates

Organization-level setting collections bound to multiple networks so shared SSIDs, VLANs, and firewall rules are inherited and updated centrally rather than per network.

Device replacement workflow

Dashboard function that swaps a failed device's serial for a replacement unit in the same network slot, preserving the original configuration, VLANs, and policy settings.

Trunk port configuration

A switch port that carries multiple VLANs, using an explicit allowed-VLAN list plus one untagged native VLAN; required for interswitch links and access point uplinks.

SSID NAT mode

Wireless mode where the access point serves DHCP in a private subnet and translates client traffic to its own IP address, isolating wireless clients from the local LAN.

SSID bridged mode

Wireless mode that places clients onto a tagged LAN VLAN, so they obtain addresses from the network DHCP server and behave like wired hosts.

Layer 3 firewall rules

MX rules evaluated top-down for each VLAN that allow or deny traffic by protocol, source, destination address, and port, ending in a configurable default policy.

Layer 7 firewall rules

MX rules that identify and block applications or content categories by traffic signature rather than port number, requiring an Advanced Security license.

Intrusion prevention signatures

Snort-based IDS and IPS rule sets on MX that detect or block known malicious traffic patterns; prevention mode requires an Advanced Security license.

Site-to-site VPN firewall

Rules that decide which local subnets remote Auto VPN peers may reach; the default is allow, so deny rules are added to restrict lateral traffic between sites.

Splash page guest access

Captive portal for guest SSIDs supporting click-through, dashboard sign-on, RADIUS, or social login, with a walled garden listing domains reachable before authentication.

Group policy overrides

Policy assigned to matched clients, identities, or devices that overrides network-level firewall, VLAN, traffic shaping, and content-filtering settings for that group.

802.1X RADIUS authentication

WPA2-Enterprise authentication where the access point relays client credentials to an external RADIUS server, whose returned attributes can assign VLANs and group policies.

Dashboard alert profile

Per-network notification rules that send email, SMS, or webhook messages when conditions such as device offline, uplink down, or usage thresholds are met.

Packet capture tool

Built-in dashboard live tool that records traffic on an MX, MS, or MR interface with configurable filters and export a downloadable pcap file for analysis.

Meraki Insight

Add-on monitoring that measures web application response time from the MX and attributes delay to the client, LAN, WAN, or server.

Uplink performance test

MX live tool that measures latency, jitter, and packet loss to a selected target across WAN uplinks to confirm ISP quality.

Event log retention

Dashboard record of configuration changes and device events, filterable by time and keyword, retained for roughly 30 days and exported by API or syslog for longer history.

Syslog export

Network setting that streams MX or MS flows, URL logs, security events, and appliance or switch event logs to an external syslog server for retention and SIEM ingestion.

Dashboard API base URL

The REST endpoint https://api.meraki.com/api/v1, where organization and network identifiers form the resource path for every call.

API key authentication

Every request carries an X-Cisco-Meraki-API-Key header; keys are generated per dashboard administrator and inherit that administrator's role and network permissions.

API rate limit

Each organization allows about ten API requests per second; exceeding the limit returns HTTP 429 with a Retry-After header indicating when to retry.

Link header pagination

List endpoints return capped result sets; clients must follow the rel="next" URL in the response Link header, raising perPage to minimize total calls.

Action batches

Asynchronous API construct that submits many configuration actions in a single call, executes them in order, and is monitored through a batch status endpoint.

Webhook receiver

An HTTPS endpoint configured under dashboard alerts that receives JSON POST payloads containing alert type, level, device serial, network ID, and timestamp.