PCCSE 無料問題集「Palo Alto Networks Prisma Certified Cloud Security Engineer」

（A）Kubernetes-audit

（B）Waas-request

（C）Filesystem

（D）Network-outgoing

（E）Processes

（A）Prisma Cloud Enterprise Administrator's Guide

（B）Prisma Cloud Compute API Reference

（C）Prisma Cloud API Reference

（D）Prisma Cloud Administrator's Guide (Compute)

（A）Ignore

（B）Block

（C）Allow

（D）Snooze

（E）Alert

（A）8888

（B）80

（C）8080

（D）443

（A）It restricts access only to certain types of resources within the cloud account.

（B）It restricts access only to the resources and data that pertains to the cloud account(s) within an account group.

（C）It restricts access to all resources and data within the cloud account.

（D）It does not restrict access to any resources within the cloud account.

（A）Open the Compliance Standards section of the policy, and then save.

（B）Edit the policy, go to step 3 (Compliance Standards), click + at the bottom, select the compliance standard, fill in the other boxes, and then click Confirm.

（C）Create the Compliance Standard from Compliance tab, and then select Add to Policy.

（D）Custom policies cannot be added to existing standards.

（A）Images

（B）Journal

（C）Text

（D）Audio

（E）Documents

（A）3

（B）1

（C）4

（D）2

（A）Deploy defenders to scan complete container compliance.

（B）Change the rule options to list only failed checks in the compliance rule edit window.

（C）Wait until Prisma Cloud finishes the compliance scan and recheck.

（D）Change the rule options to list both failed and passed checks in the compliance rule edit window.

（A）Defenders will fail open until the web-socket can be re-established.

（B）Defenders continue to alert and enforce using the policies and settings most recently cached before upgrading the Console.

（C）Defenders continue to alert, but not enforce, using the policies and settings most recently cached before upgrading the Console.

（D）Defenders will fail closed until the web-socket can be re-established.

（A）config from iam where dest.cloud.type = 'AWS' AND source.cloud.service.name = 'ec2' AND source.cloud.resource.type = 'instance' AND dest.cloud.service.name = 'lambda' AND action.name =
'ec2:TerminateInstances'

（B）config from iam where dest.cloud.type = 'AWS' AND source.cloud.service.name = 'lambda' AND source.cloud.resource.type = 'function' AND dest.cloud.service.name = 'ec2' AND action.name =
'ec2:TerminateInstances'

（C）iam from cloud.resource where dest.cloud.type = 'AWS' AND source.cloud.service.name = 'lambda' AND source.cloud.resource.type = 'function' AND dest.cloud.service.name = 'ec2' AND action.name =
'ec2:TerminateInstances'

（D）iam from cloud.resource where cloud.type equals 'AWS' AND cloud.resource.type equals 'lambda function' AND cloud.service.name = 'ec2' AND action.name equals 'ec2:TerminateInstances'

（A）Defender scans will automatically be disabled, so agentless scans are the only scans occurring.

（B）Agentless scan will automatically be disabled, so Defender scans are the only scans occurring.

（C）Both agentless and Defender scans will be disabled and an error message will be received.

（D）Agentless scans do not conflict with Defender scans, so both will run.

（A）Remove Defenders DaemonSet, and then use Cloud Discovery to automatically redeploy the Defenders.

（B）Run the provided curl | bash script from Console to remove Defenders, and then use Cloud Discovery to automatically redeploy Defenders.

（C）Remove Defenders, and then deploy the new DaemonSet so Defenders do not have to automatically update on each deployment.

（D）Let Defenders automatically upgrade.