Don't think it's A. Remote Desktop (E) and Screenshot (D) are the ones missing from iOS/Android, so I'd pick those. OS updates can work on mobiles too, so that's a trap.
I'm thinking D makes sense if you round the APs per band individually first, then sum them up. So for 2.4 GHz (30 users / 15 per AP = 2), and for 5 GHz (70 users / 30 per AP = ~2.33, rounded to 2), so that gives you 4 total, but if both bands need their own APs, some guides say you need to count overlap or APs physically. Pretty sure it's D, unless I'm missing something obvious. Anyone else see it this way?
During a Meraki AP deployment, the default SSID that the exhibit shows is broadcast. What causes
this behavior?B/C tbh. On Cisco Meraki, "Out of License" actually happens if you have more devices than licenses or if a device license expires. The serial/model mismatches like D and E usually just trigger compliance warnings, not full Out of License states. Saw similar in exam reports, pretty sure these are the two main causes.
Yeah, it's B and C for Meraki. You go "Out of License" if you have more devices added than device licenses, or if a license has expired. Other options like mismatch in serials or models just cause compliance warnings, not full "Out of License" status. Pretty sure that's how Cisco enforces it but open to corrections.
I always thought you needed a DSCP value tagged for Apple.com, so I'd say D. It seems like QoS settings matter more here. But I get why A is popular, just not fully convinced since prioritizing traffic usually means tagging it.
Distributed Layer 3 roaming lets APs handle client traffic locally without pushing everything through an MX Security Appliance. I remember in centralized mode the concentrator is needed, so that's where B comes in. Not totally sure because of Meraki's weird naming sometimes, but A looks right here.
I remember seeing a similar question, and I thought it was plaintext since some older OSPF setups use simple passwords. Not fully sure though, as Meraki might support something else. If anyone knows for sure, let me know!
Yep, always seen A for Meraki MX OSPF configs. MX doesn't let you pick SHA-1 or certs, just MD5. C is supported by classic Cisco IOS but not on MX. Pretty confident it's A, but open to correction if firmware changed recently!
A or C? Saw similar on practice, but for Meraki MX it looks like only MD5 (A) is supported for OSPF auth. Plaintext is common on some older Cisco stuff, not here though I think. Pretty sure it's A, but correct me if I'm off!
With the Meraki Co-Term licensing model, couldn't licensing a network (B) also count depending on how you deploy? Some practice tests list B as a valid operation if you're applying licenses to a new network. The Meraki docs are sometimes unclear, especially if you've only used the dashboard in labs.
Has anyone seen the official guide say otherwise?