I don't think it's C. The main trap is ignoring how APs handle high density with that many streams. I remember best practices point closer to B, but open to other maths if I missed something.
Meraki dashboard has retention limits, so for full history, you'd need option C with a syslog server. That's the best practice from what I know. If anyone's used another reliable method let me know!
Does "best practice" here mean most secure or most cost-effective? If the question is just about maximizing the number of logs stored but not necessarily needing external backup, wouldn't A work? More context about compliance requirements could change things too.
A packet arrives on the VPN concentrator with source IP 10.168.70.3 and destined for IP 10.116.32.4.
What is the next hop for the packet, based on this concentrator routing table?B for me since I can't actually see the full routing table in the exhibit. If there's no visible match or default shown, I don't think we have enough detail to confidently say where 10.116.32.4 would go. Maybe I'm missing something obvious though.
I was looking at similar questions in some labs and I thought A since the default gateway could be used if there's no direct VPN route. Maybe I'm missing something, but unless that VPN entry is more specific, the packet should go out via 10.128.124.62, right? Pretty sure about A but open to corrections.
The VPN concentrator is experiencing issues. Which action should be taken to ensure a stable
environment?Don't think it's D, because configuring routed mode isn't what's needed for this scenario. The key with Meraki one-arm VPN concentrators is to keep all LAN ports physically disconnected, so C is the accurate step to ensure the VPN operates smoothly and you don't end up with routing loops. Pretty sure about this based on exam guides and Meraki docs, but if anyone interprets it differently let me know.