ECMS Network Design, Deployment, and SD-WAN 2 — Questions and Answers
Question 1: What Meraki organization-level feature allows a network engineer to push a firmware upgrade to hundreds of sites during a scheduled maintenance window?
- Individual device reboot scheduling only
- Organization-wide firmware upgrade scheduling via Organization > Firmware upgrades (Correct answer)
- CLI push via SSH to each device
- Automatic upgrades cannot be scheduled in Meraki
Correct answer: Organization-wide firmware upgrade scheduling via Organization > Firmware upgrades
Meraki's firmware upgrade management at the Organization level allows administrators to schedule upgrades across all devices in specified networks during off-peak maintenance windows.
Question 2: What is the purpose of Meraki 'Network Tags' when applied to networks in an organization?
- They control which VLANs are allowed on trunk ports
- They group networks for bulk operations, reporting, and configuration template binding (Correct answer)
- They define routing policies between tagged networks
- They assign Meraki cloud region for data residency purposes
Correct answer: They group networks for bulk operations, reporting, and configuration template binding
Network tags in Meraki allow administrators to logically group networks, enabling bulk firmware upgrades, alert configuration, API filtering, and template assignment for networks sharing common attributes.
Question 3: When sizing a Meraki MX for a branch deployment, what throughput specification should be the primary consideration?
- Number of VLANs supported
- Stateful firewall throughput matching expected WAN bandwidth plus headroom for growth (Correct answer)
- Number of SSIDs the MX can broadcast
- Maximum number of Meraki cloud API calls per second
Correct answer: Stateful firewall throughput matching expected WAN bandwidth plus headroom for growth
The MX stateful firewall throughput rating should match or exceed the site's WAN link capacity, with additional headroom to account for traffic growth and inspection overhead.
Question 4: What is the recommended Meraki architecture for providing high-availability at a data center hub site with no single point of failure?
- Single high-powered MX with RAID storage
- Warm Spare (VRRP) with two MX appliances sharing a virtual IP (Correct answer)
- Active-active clustering of four MX appliances
- Dual ISP connections to a single MX
Correct answer: Warm Spare (VRRP) with two MX appliances sharing a virtual IP
Meraki Warm Spare uses VRRP to deploy two MX appliances where one is active and one is standby; if the active unit fails, the standby takes over the virtual IP within seconds.
Question 5: In a Meraki deployment, what is the significance of placing the Meraki dashboard in 'Monitor Only' mode for a network?
- The network devices lose connectivity to the cloud
- Administrators can view the network but cannot make configuration changes until the mode is changed (Correct answer)
- Device traffic is limited to monitoring protocols like SNMP
- The network stops generating Event Log entries
Correct answer: Administrators can view the network but cannot make configuration changes until the mode is changed
Monitor Only mode is a role-based access restriction that allows read-only dashboard access, preventing configuration changes while still enabling visibility and troubleshooting.
Question 6: When deploying Meraki devices at a site without a local IT administrator, what feature ensures the devices automatically connect and receive configuration without manual setup?
- Manual staging by Meraki TAC
- Zero-Touch Provisioning (ZTP) via Meraki cloud (Correct answer)
- USB configuration file import
- TFTP-based configuration bootstrap
Correct answer: Zero-Touch Provisioning (ZTP) via Meraki cloud
Meraki's Zero-Touch Provisioning allows devices to be shipped directly to a site where they automatically connect to the cloud using pre-claimed licensing and receive their full configuration.
ECMS Network Design, Deployment, and SD-WAN 2
What Meraki organization-level feature allows a network engineer to push a firmware upgrade to hundreds of sites during a scheduled maintenance window?