A company is setting up ingestion of AWS CloudTrail logs into Cortex XSIAM. They have configured the API-based ingestion connector and verified that the AWS account credentials are valid. However, no logs are appearing in Cortex. Which step in the ingestion pipeline is most likely to be the cause of this issue?

The storage tier is full and rejecting new data

The logs are being quarantined due to format errors

The data is being normalized incorrectly

The logs are not being collected from the AWS S3 bucket

A company wants to ingest data from their cloud infrastructure, including virtual machine metrics and audit logs. They also want to ingest alerts from their endpoint protection platform. Which data source types should they use?

Logs for VM metrics, telemetry for audit logs, and alerts for endpoint alerts

Alerts for VM metrics, logs for audit logs, and telemetry for endpoint alerts

Telemetry for all three data types

Telemetry for VM metrics, logs for audit logs, and alerts for endpoint alerts

An administrator is troubleshooting why logs from a network device are not appearing in Cortex XSIAM. The device is configured to send syslog to the Cortex collector, and the collector is receiving the logs. However, the logs are not appearing in the Cortex data store. What should the administrator check next?

Whether the network device is powered on

Whether the syslog format is supported by Cortex

Whether the storage quota is exceeded

A security team is ingesting logs from a network appliance into Cortex XSIAM via syslog. The logs are arriving but some are missing timestamps. The team wants to ensure all logs have consistent timestamps for correlation. What should they do?

Ignore the missing timestamps because they are not important

Ask the vendor to modify the appliance firmware

Configure the ingestion pipeline to add a timestamp during normalization

Use a different ingestion method, such as direct upload

A security team is ingesting logs from a custom application via API into Cortex XSIAM. The logs are arriving but some are being dropped during the parsing stage. The team has verified that the API is sending well-formed JSON. What is the most likely cause of the parsing failures?

The network connection is unstable

The JSON schema does not match the expected Cortex schema

The API is sending data too quickly

Palo Alto NetworksCertified Cloud Security Professional

Domain 2Objective 3

2.3 Demonstrate Understanding of Data Source Ingestion CLOUD-SECURITY-PROFESSIONAL Practice Questions (Page 3)

Part of the Cortex Fundamentals domain, which accounts for 15% of the CLOUD-SECURITY-PROFESSIONAL exam.

26questions here

6free pages

5concepts

15%of the exam

Questions 11–15

11application · medium
A company is setting up ingestion of AWS CloudTrail logs into Cortex XSIAM. They have configured the API-based ingestion connector and verified that the AWS account credentials are valid. However, no logs are appearing in Cortex. Which step in the ingestion pipeline is most likely to be the cause of this issue?
Select an answer first
12application · medium
A company wants to ingest data from their cloud infrastructure, including virtual machine metrics and audit logs. They also want to ingest alerts from their endpoint protection platform. Which data source types should they use?
Select an answer first
13application · medium
An administrator is troubleshooting why logs from a network device are not appearing in Cortex XSIAM. The device is configured to send syslog to the Cortex collector, and the collector is receiving the logs. However, the logs are not appearing in the Cortex data store. What should the administrator check next?
Select an answer first
14application · medium
A security team is ingesting logs from a network appliance into Cortex XSIAM via syslog. The logs are arriving but some are missing timestamps. The team wants to ensure all logs have consistent timestamps for correlation. What should they do?
Select an answer first
15expert · hard
A security team is ingesting logs from a custom application via API into Cortex XSIAM. The logs are arriving but some are being dropped during the parsing stage. The team has verified that the API is sending well-formed JSON. What is the most likely cause of the parsing failures?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CLOUD-SECURITY-PROFESSIONAL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Palo Alto Networks. “CLOUD-SECURITY-PROFESSIONAL” is a trademark of its owner, used for identification only.

2.3 Demonstrate Understanding of Data Source Ingestion CLOUD-SECURITY-PROFESSIONAL Practice Questions (Page 3)

Questions 11–15

A company wants to ingest data from their cloud infrastructure, including virtual machine metrics and audit logs. They also want to ingest alerts from their endpoint protection platform. Which data source types should they use?

A security team is ingesting logs from a network appliance into Cortex XSIAM via syslog. The logs are arriving but some are missing timestamps. The team wants to ensure all logs have consistent timestamps for correlation. What should they do?

A security team is ingesting logs from a custom application via API into Cortex XSIAM. The logs are arriving but some are being dropped during the parsing stage. The team has verified that the API is sending well-formed JSON. What is the most likely cause of the parsing failures?

Keep studying — Cortex Fundamentals