500-560 · Question #116
Which statement correctly describes how Cisco Meraki devices behave should they be unable to contact the Meraki Cloud server?
The correct answer is D. The network devices continue to function normally (traffic lows at full rate) but management and. Cisco Meraki devices operate on a "cloud-managed but locally switched/routed" architecture, meaning the data plane (actual traffic forwarding) runs independently on the device hardware regardless of cloud connectivity - so option D is correct: traffic continues flowing at full…
Question
Which statement correctly describes how Cisco Meraki devices behave should they be unable to contact the Meraki Cloud server?
Options
- AThe network devices will attempt to establish a connection to a locally hosted database server
- BThe devices may be re-initiated into a backup mode if an administrator manually intervenes using
- CThe network stops passing traffic across all devices and the interfaces including any connected
- DThe network devices continue to function normally (traffic lows at full rate) but management and
How the community answered
(41 responses)- A5% (2)
- B2% (1)
- D93% (38)
Explanation
Cisco Meraki devices operate on a "cloud-managed but locally switched/routed" architecture, meaning the data plane (actual traffic forwarding) runs independently on the device hardware regardless of cloud connectivity - so option D is correct: traffic continues flowing at full rate, but you lose the ability to make configuration changes, view dashboards, or receive alerts through the Meraki Dashboard.
Why the distractors are wrong:
- A is wrong because Meraki has no fallback to a local database server; there is no on-premises management controller in the Meraki architecture.
- B is wrong because Meraki devices do not require manual admin intervention to stay operational - they continue running autonomously without any "backup mode" initiation.
- C is wrong because traffic does not stop; interfaces stay up and the network keeps passing traffic normally. Meraki explicitly separates the management plane from the data plane to prevent this scenario.
Memory tip: Think of it as a "set it and forget it" appliance - once configured, the device's forwarding rules are cached locally, so losing the cloud connection is like losing your TV remote but the TV stays on. You can't change the channel, but the picture keeps playing.
Topics
Community Discussion
No community discussion yet for this question.