What Links a Secure Cloud Analytics Private Network Monitor Sensor to the Portal?

350-701 By islever Editorial Last updated

Describe security monitoring and telemetry technologies

Short answer

BD Link the private network monitor sensor to the Secure Cloud Analytics portal using the sensor's unique service key and public IP address.

Question

A Cisco Secure Cloud Analytics administrator is setting up a private network monitor sensor to monitor an on-premises environment. Which two pieces of information from the sensor are used to link to the Secure Cloud Analytics portal? (Choose two.)
  1. private IP address
  2. unique service key Correct Answer
  3. SSL certificate
  4. public IP address Correct Answer
  5. NAT ID

Key Takeaways

The exam tests which identifiers enroll an on-premises Secure Cloud Analytics sensor with the cloud portal; the trap is choosing the private IP address or NAT ID instead of the public IP address and unique service key.

Linking a Cisco Secure Cloud Analytics private network monitor sensor to the portal requires the sensor's public IP address and unique service key. This page confirms those two identifiers and explains why private IP, SSL certificate, and NAT ID are not used for enrollment.

Common mistake: A common mistake is selecting the private IP address (A), assuming internal reachability identifies the sensor; the portal links through the sensor's public IP address or its unique service key, not its private address.

Expert Analysis

Why the Answer Is Correct

Cisco Secure Cloud Analytics links a private network monitor sensor to the portal by identifying it with its public IP address or, when that address cannot be determined, by manually entering the sensor's unique service key. These two values give the portal a way to map the on-premises sensor to the correct tenant and establish the cloud connection. The public IP is the externally visible address the portal can use, while the service key is the unique enrollment identifier for that sensor. Because the question asks for two pieces of information, both B and D are required.

Why the Other Options Are Wrong

A private IP address (A) is only meaningful inside the local network and cannot identify the sensor to the cloud portal. An SSL certificate (C) supports encrypted transport and trust, but it is not the enrollment or linking value requested here. A NAT ID (E) is not a Secure Cloud Analytics sensor-linking field; NAT may affect addressing, but it is not the portal identifier.

Community Comment Notes

ITVI points readers to Cisco's Sensor Advanced Configuration Guide, and Pierre_Bouvier summarizes the required values as "Unique Service Key / Public IP Address." XBfoundX explains that linking is normally done by identifying the sensor's public IP address and that the unique service key is used when the public IP cannot be determined. The comment consensus aligns with B and D, and the same conclusion follows from Cisco's documented sensor-linking procedure.

Official Reference

https://www.cisco.com/c/dam/en/us/td/docs/security/stealthwatch/cloud/configuration/Sensor_Advanced_Configuration_Guide_DV_5_1.pdf

This link opens the official vendor documentation in a new tab.

Exam Strategy

For this multi-select question, focus on what the cloud portal needs to identify an on-premises sensor: an externally visible address or a unique enrollment key. Do not overcomplicate the decision with certificates or NAT identifiers, and select exactly two answers.

Frequently Asked Questions

Why is the sensor's private IP address not used to link it to Secure Cloud Analytics?

The portal needs an externally identifiable sensor; the private IP is not routable from the cloud portal, so the public IP address or unique service key is used instead.

What should be used if the sensor's public IP address cannot be determined?

Use the sensor's unique service key to manually link it to the Secure Cloud Analytics portal.

More 350-701 FAQ →

Discussion 5 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 5

  1. Pierre_Bouvier 👍 2
    two critical pieces of information are required to link the ONA sensor to the Secure Cloud Analytics portal to add Unique Service Key / Public IP Address
  2. ITVI 👍 2
    Read it up here: https://www.cisco.com/c/dam/en/us/td/docs/security/stealthwatch/cloud/configuration/Sensor_Advanced_Configuration_Guide_DV_5_1.pdf
  3. XBfoundX 👍 1
    Onceasensoris installed, it will need to be linked with your portal. This is done by identifying the sensor's public IP address and entering it into the web portal. If you cannot determine the sensor's public IP address, you can manually link the sensor to your portal using its unique service key. The sensor can connect to the following portals: l https://sensor.ext.obsrvbl.com (US) l https://sensor.eu-prod.obsrvbl.com (EU) l https://sensor.anz-prod.obsrvbl.com (Australia)
  4. XBfoundX 👍 1
    https://www.cisco.com/c/dam/en/us/td/docs/security/stealthwatch/cloud/configuration/Sensor_Advanced_Configuration_Guide_DV_5_1.pdf
  5. dfb0b7d 👍 1
    bd

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

What Is a Feature of an Endpoint Detection and Response Solution?

S-grade

Which Two Methods Belong in an AAA Authentication Method List?

S-grade

Preventing Unauthorized DHCP Servers on Cisco Switches

S-grade

What Is Considered a Cloud Data Breach in Cisco 350-701?

S-grade

← Back to 350-701 Study Guide