Exam 500-220 topic 4 question 55 discussion

See the Configuring a Survey SSID section. Note: If the AP does not have a wired connection to the network, it will broadcast an SSID similar to "meraki-scanning" for access to the local status page: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Conducting_Site_Surveys_with_MR_Access_Points This should not be C because the doc below shows the SSID as the following: <SSID_name>-scanning. This question clearly shows the SSID: meraki-scanning. https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

If a Meraki Access Point does not have a configuration from the Meraki Cloud Controller it will instead broadcast a default SSID of "Meraki-Scanning." The AP takes an address of 10.128.128.128, the SSID runs DHCP, and it will try to assign any clients that associate with it an address. This is merely to provide a connection between a client and the AP to allow for local configuration. https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

Correct answer is B: <SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. ----- Wrong answer C: "Meraki Setup" ----> It's not "SETUP" Cause: An AP has never connected to a Meraki network.

<SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway. Source: https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

Default SSIDs <SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway.

I also go with C, after looking this post: "If the MR has never connected to the cloud it will broadcast a Meraki Setup SSID that can be joined to get to the LSP." https://community.meraki.com/t5/Wireless-LAN/Meraki-MR46-local-status-page-access/m-p/222217#M30768

Correct: A

<SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway.

We cannot confirm that the AP has in fact NEVER connected to the Meraki controller. We also cannot confirm that is has never received a configuration from what we are shown. The only thing we know for sure is that this SSID will be displayed if it cannot reach it's default gw according to Meraki documentation. This means the IP, mask or default gw could be configured incorrectly.

Correct answer is C.

C is correct. It is safe to assume the SSID isn't "meraki" so in this case the answer is C. If a Meraki Access Point does not have a configuration from the Meraki Cloud Controller it will instead broadcast a default SSID of "Meraki-Scanning." vs <SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

Correct answer is B

<SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway.

B is the correct answer. See below. <SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway. Meraki Setup Cause: An AP has never connected to the Meraki Cloud Controller (MCC) or has been factory reset. Solution: Establish MCC connectivity for the AP by ensuring appropriate Internet access.

I guess the word deployment is the key ..if its being deployed it has never reached the meraki cloud. I asked my meraki se for this answer.

B is the correct answer per the documentation <SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway. https://documentation.meraki.com/MR/Other_Topics/Troubleshooting_local_connection_issues_using_default_SSID_on_MR_Access_Points

<SSID_name>-scanning Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway. Solution: Check the AP's IP address configuration and reachability to its default gateway.