I talk about points that are not dependent on requirements. In principle, it is preferable to follow Meraki's best practices for implementation. This is because Meraki is simple and not multifunctional. Meraki's product design concept is "Work Simple". In special environments, solutions are limited when problems arise. Because of its low functionality (Simple). And because it is easy to deploy on a large scale, the problem can easily spread too. If you are trying to do something complicated, you should rethink whether you should implement Meraki. Therefore, If you can share your grand design image (ideas for network topology), someone may be able to point out problems. General MX Best Practices - Cisco Meraki https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/General_MX_Best_Practices General MS Best Practices - Cisco Meraki https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MS_Switching/General_MS_Best_Practices WiFi Basics and Best Practices - Cisco Meraki https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices
... View more
