050-SEPROSIEM-01 · Question #21
In a Remote collector site, RCs
The correct answer is D. Must be connected to the D-SRV1 of the master site. In a Remote Collector site, RCs must connect to the D-SRV1 of the master site because it serves as the central data management point for the entire RSA enVision deployment.
Question
In a Remote collector site, RCs
Options
- AConnot be deployed in a virtual environment
- BCan process up to 30000 events per second
- CMust be connected to the D-SRV1 of the each site
- DMust be connected to the D-SRV1 of the master site
How the community answered
(42 responses)- A17% (7)
- B5% (2)
- C7% (3)
- D71% (30)
Why each option
In a Remote Collector site, RCs must connect to the D-SRV1 of the master site because it serves as the central data management point for the entire RSA enVision deployment.
RSA enVision Remote Collectors can be deployed in virtual environments; there is no architectural restriction preventing virtualized RC deployments.
30,000 events per second is not the documented processing capacity for RCs in RSA enVision; this figure is inaccurate and not a defined specification for the Remote Collector component.
RCs must connect to the D-SRV1 of the master site specifically, not to a D-SRV1 of each individual site, as the master site's server is the designated central collection and management point.
RSA enVision architecture requires Remote Collectors to forward all collected event data to the D-SRV1 of the master site, which acts as the authoritative data repository and management hub for the deployment. This design centralizes data aggregation and ensures the master site maintains oversight of all remote collection activity. Connecting to a local or non-master D-SRV would violate the required data flow hierarchy and prevent proper centralized management.
Concept tested: RSA enVision Remote Collector connectivity to master site D-SRV1
Topics
Community Discussion
No community discussion yet for this question.