A. DNS cache poisoning
B. Token theft and replay during long sessions
C. Log bloat in SIEM
D. Connector overload from idle sockets
A. Disabling SIEM alerts for external downtime
B. Hard-coding provider IP ranges in Connectors
C. Forcing agentless mode for all applications
D. Multi-cloud Connector deployment with DNS-based failover
A. Reduces Connector CPU utilization
B. Enables granular data handling per application context
C. Ensures RBAC inheritance across Collections
D. Avoids duplicate log entries in SIEM
A. No action-DLP updates propagate automatically to connected Sites
B. Re-publish all access policies
C. Clear policy staging cache
D. Restart all Connectors to reload fingerprints
A. Enable log truncation on failure
B. Configure multiple syslog destinations with priority order
C. Store logs only on the Connector until manual export
D. Switch to UDP transport to permit lossy delivery
A. Tap (SPAN) mode behind load balancer
B. Policy-enforced inline proxy mode
C. Reverse proxy (transparent) mode
D. Discovery-only mode
A. Internal IP assigned by the Connector
B. User's email address in lower case
C. Device UUID captured by the Symantec Agent
D. TLS session ticket value
A. Enable ESMTP email relay
B. Permit outbound TCP 443 and UDP 123 to Symantec PoPs
C. Establish GRE tunnels to SASE core
D. Block inbound ICMP to reduce noise
A. Bulk CSV importer for all Policy objects
B. Global kill-switch that blocks traffic instantly
C. Plan -> Onboard wizard that stages Sites, Apps, Policies sequentially
D. Log replay simulator for historical policies
A. Enables batch editing of global policies
B. Limits blast radius of misconfiguration or credential compromise
C. Reduces SIEM license consumption
D. Ensures faster log downloads for analysts
