Which configuration should be used to tag each NAS as a distinct log source to avoid IP aliasing in multi-region NAS log ingestion?

• 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: (C)

Differentiating log sources across regions relies on giving each NAS its own identifiable source at the edge, not just tagging data after it’s ingested. Deploying a BindPlane agent at each location to collect Syslog from the NAS devices ensures the logs carry location-specific provenance. By configuring a namespace for each log source, you create distinct, non-overlapping identities in the ingestion backend, so even if two NAS devices share the same IP in different regions, their logs are kept separate and correctly attributed.

Other approaches rely on labels or pulling data centrally, which can blur provenance or depend on the network address, leading to potential aliasing across regions. The edge-based Syslog collection with per-source namespaces provides robust, region-aware separation and preserves the true origin of each log stream.