Which configuration should be used when you want to avoid IP aliasing across four NAS regions and tag each as a log source?

Which configuration should be used when you want to avoid IP aliasing across four NAS regions and tag each as a log source?

• A. Configure feed management to pull data and configure an ingestion label per log source.
• B. Configure feed management to pull data from each location and configure a namespace per log source.
• C. Configure a Bindplane agent collecting Syslog from each location and configure a namespace per log source.
• D. Configure a Bindplane agent and an ingestion label per log source.

Answer: (A)

Centralize ingestion from all NAS regions and give each log source its own tag at ingestion. Using feed management to pull data from all locations and applying a dedicated ingestion label for each NAS region ensures every log carries a clear origin identity, so logs from different regions aren’t confused by overlapping or changing IPs. The label travels with the data, making it easy to filter, route, and analyze by source without relying on IP addresses alone. Namespaces can isolate sources, but they don’t provide the same explicit, actionable identity for downstream tooling and querying. An agent-based approach adds deployment overhead at every site and can complicate consistency and routing. The combination of centralized data pull plus per-source ingestion labels gives precise provenance and scalable, straightforward log source tagging.

Centralize ingestion from all NAS regions and give each log source its own tag at ingestion. Using feed management to pull data from all locations and applying a dedicated ingestion label for each NAS region ensures every log carries a clear origin identity, so logs from different regions aren’t confused by overlapping or changing IPs. The label travels with the data, making it easy to filter, route, and analyze by source without relying on IP addresses alone.

Namespaces can isolate sources, but they don’t provide the same explicit, actionable identity for downstream tooling and querying. An agent-based approach adds deployment overhead at every site and can complicate consistency and routing. The combination of centralized data pull plus per-source ingestion labels gives precise provenance and scalable, straightforward log source tagging.