1.3 Determine Network Communication and Connectivity Requirements for Cortex Cloud Components (e.g., Egress Rules, URLs, Ports, Regional Endpoints) CLOUD-SECURITY-ENGINEER Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A multinational organization is deploying Cortex Cloud connectors in both the US East and EU West regions. The network team is configuring egress rules in each region's VPC. What should they consider to ensure optimal connectivity and compliance?

   • ARoute all traffic through a central egress point in the US East region to simplify management.
   • BConfigure egress rules in each region to allow traffic to the respective regional Cortex Cloud endpoint, ensuring low-latency paths and data residency.
   • CAllow outbound traffic to any Cortex Cloud endpoint, as regional endpoints are interchangeable.
   • DUse the same egress rules in both regions, pointing to the global Cortex Cloud endpoint.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which Cortex Cloud component is responsible for collecting and processing security telemetry from connected data sources?

   • AManagement plane
   • BData plane
   • CControl plane
   • DConnector
   Reveal Solution Discussion Select an answer first
4. 13application · easy

   A network administrator is creating a firewall rule to allow Cortex Cloud connector traffic. The rule should be as restrictive as possible while still allowing the connector to function. Which protocol and port combination should be used?

   • AUDP port 53 (DNS)
   • BTCP port 8080 (HTTP proxy)
   • CTCP port 443 (HTTPS)
   • DTCP port 22 (SSH)
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A company is deploying Cortex Cloud connectors in an AWS environment. The security team wants to restrict outbound traffic to only the necessary Cortex Cloud endpoints. Which action should the team take to ensure the connectors can communicate while minimizing the egress footprint?

   • AAllow outbound traffic on port 22 to the Cortex Cloud management plane for secure shell access.
   • BAllow outbound HTTPS traffic only to the specific Cortex Cloud URLs and IP addresses documented for the connector type and region.
   • CAllow all outbound HTTPS traffic to the Cortex Cloud regional endpoint for the deployment region.
   • DAllow outbound traffic on port 443 to any destination, as Cortex Cloud uses standard HTTPS.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   An organization is deploying Cortex Cloud connectors in multiple AWS regions to support a global infrastructure. They want to minimize latency for connector-to-cloud communication. What is the best practice?

   • ADeploy all connectors in a single region and route traffic through a central egress point.
   • BDeploy connectors in each region and configure them to use the regional Cortex Cloud endpoint for that region.
   • CConfigure connectors to use the commercial cloud endpoint regardless of region.
   • DUse a global load balancer to route connector traffic to the nearest Cortex Cloud endpoint.
   Reveal Solution Discussion Select an answer first