What is the purpose of configuring a repository in Prisma Cloud for scanning?

To create a backup of the repository

To store the repository's source code in Prisma Cloud

To specify which branches and files should be scanned

To set up a CI/CD pipeline in Prisma Cloud

A company wants to onboard its development systems to Prisma Cloud. The team uses GitHub for source control and Jenkins for CI/CD. The security team wants to scan code at both the repository level and the pipeline level. What should be configured to achieve both scanning points?

Connect only Jenkins, since it can scan the source code during the build.

Connect only GitHub, since it can scan code during pull requests.

Connect GitHub and use a webhook to trigger a Jenkins job that scans the repository.

Connect GitHub for repository scanning and integrate Jenkins for pipeline scanning.

An organization has a Jenkins server that builds projects for multiple teams. The security team wants to integrate Prisma Cloud, but each team should only be able to view scan results for their own projects. What is the correct way to configure access control for the Jenkins integration?

Use a single Prisma Cloud access key for all teams and rely on Jenkins folder permissions to control access.

Use a single access key and configure the Jenkins plugin to filter results by team.

Create a separate Prisma Cloud access key for each team and configure role-based access control in Prisma Cloud.

Create a separate Jenkins server for each team, each with its own Prisma Cloud integration.

What is the primary method to integrate Jenkins with Prisma Cloud for automated security checks?

Configuring a Jenkins job to run Prisma Cloud CLI commands

Setting up a Jenkins webhook to notify Prisma Cloud of builds

Creating a Jenkins user with admin permissions for Prisma Cloud

Installing a Prisma Cloud plugin in Jenkins

How does Prisma Cloud enforce security policies during the onboarding process?

By blocking the build if critical vulnerabilities are found

By sending an email to the developer

By automatically fixing vulnerabilities in the code

By deleting the repository if violations are found

Palo Alto NetworksCertified Cloud Security Engineer

Domain 2Objective 3

2.3 Explain the Process of Onboarding Application Development and Deployment Systems (e.g., GitHub, Jenkins) CLOUD-SECURITY-ENGINEER Practice Questions (Page 1)

Part of the Integration domain, which accounts for 16% of the CLOUD-SECURITY-ENGINEER exam.

29questions here

6free pages

7concepts

16%of the exam

Questions 1–5

1foundation · easy
What is the purpose of configuring a repository in Prisma Cloud for scanning?
Select an answer first
2application · medium
A company wants to onboard its development systems to Prisma Cloud. The team uses GitHub for source control and Jenkins for CI/CD. The security team wants to scan code at both the repository level and the pipeline level. What should be configured to achieve both scanning points?
Select an answer first
3expert · medium
An organization has a Jenkins server that builds projects for multiple teams. The security team wants to integrate Prisma Cloud, but each team should only be able to view scan results for their own projects. What is the correct way to configure access control for the Jenkins integration?
Select an answer first
4foundation · easy
What is the primary method to integrate Jenkins with Prisma Cloud for automated security checks?
Select an answer first
5foundation · easy
How does Prisma Cloud enforce security policies during the onboarding process?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CLOUD-SECURITY-ENGINEER

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-ENGINEER” is a trademark of its owner, used for identification only.