500-220 · Question #58
Drag and Drop Question Drag and drop the settings from the left into the boxes on the right to indicate if the setting will be cloned or not cloned using the Cisco Meraki MS switch cloning feature. An
The correct answer is Cloned; port name; interface type; STP bridge property; Not Cloned; switch name; switch management IP. Cisco Meraki MS Switch Cloning - Explanation What is Switch Cloning? The Meraki MS switch cloning feature copies configuration from one switch to another. The key principle: device-specific identity settings are NOT cloned; functional configuration settings ARE cloned. --- Cloned
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Cloned
- port name
- interface type
- STP bridge property
- Not Cloned
- switch name
- switch management IP
Explanation
Cisco Meraki MS Switch Cloning - Explanation
What is Switch Cloning?
The Meraki MS switch cloning feature copies configuration from one switch to another. The key principle: device-specific identity settings are NOT cloned; functional configuration settings ARE cloned.
Cloned Settings
These are configuration parameters that define how the switch operates - safe to duplicate across multiple switches.
| Setting | Why It's Cloned |
|---|---|
| Port name | Port labels are descriptive config (e.g., "Uplink-to-Core"). You want consistent naming conventions across similar switches. |
| Interface type | Access/trunk mode, allowed VLANs, speed/duplex - these define how ports function. Cloning ensures all switches in the same role behave identically. |
| STP bridge property | Spanning Tree Protocol bridge priority and related settings are network-design decisions. The same STP topology should apply to all switches in that role. |
Not Cloned Settings
These are device-unique identifiers - duplicating them would cause network conflicts.
| Setting | Why It's NOT Cloned |
|---|---|
| Switch name | Names uniquely identify devices in the dashboard. Two switches with the same name creates management confusion; Meraki preserves each switch's own name. |
| Switch management IP | IP addresses must be unique on a network. Cloning this would create an IP conflict, breaking connectivity for both switches. |
Common Misconceptions
- "Switch name sounds like a config setting, so it should be cloned." - Wrong. Name is an identity attribute, not a functional configuration. Think of it like a hostname: you don't clone hostnames.
- "STP feels advanced and might be excluded." - STP bridge priority is a switch-wide setting that's part of the network design, so it absolutely gets cloned to maintain consistent topology.
- Mental model shortcut: If removing the setting would make the switch unidentifiable or unreachable, it's NOT cloned. If removing it would make the switch misconfigured, it IS cloned.
Topics
Community Discussion
No community discussion yet for this question.