Limits of Neo4j Bolt Connector advertised_address on preventing accidental public exposure

Determine whether configuring the Bolt connector's advertised_address can limit network exposure when the listen_address is set to 0.0.0.0 and authentication is disabled.

According to the documentation, advertised_address is used for cluster communication and does not change the actual bind address, but it is unclear if setting it to a specific interface influences accessibility when the listener is bound to all interfaces. This raises questions about the effectiveness of advertised_address as a safeguard and the required complementary settings.

1. Does setting dbms.connector.bolt.advertised_address to a specific IP address restrict exposure when dbms.connector.bolt.listen_address is 0.0.0.0?
2. If authentication is disabled, does advertising an address affect who can connect via Bolt?
3. Should administrators rely on advertised_address as a security control, or must they explicitly restrict listen_address and enable authentication?