Pass with Professional-Cloud-Security-Engineer Practice Materials 100% for sure

Your organization develops software involved in many open source projects and is concerned about software supply chain threats You need to deliver provenance for the build to demonstrate the software is untampered.
What should you do?

• A. * 1- Generate Supply Chain Levels for Software Artifacts (SLSA) level 3 assurance by using Cloud Build.* 2. View the build provenance in the Security insights side panel within the Google Cloud console.
• B. * 1, Publish the software code on GitHub as open source.* 2. Establish a bug bounty program, and encourage the open source community to review, report, and fix the vulnerabilities.
• C. * 1. Hire an external auditor to review and provide provenance* 2. Define the scope and conditions.* 3.Get support from the Security department or representative.* 4. Publish the attestation to your public web page.
• D. * 1. Review the software process.* 2. Generate private and public key pairs and use Pretty Good Privacy (PGP) protocols to sign the output software artifacts together with a file containing the address of your enterprise and point of contact.* 3. Publish the PGP signed attestation to your public web page.

Your organization has established a highly sensitive project within a VPC Service Controls perimeter. You need to ensure that only users meeting specific contextual requirements such as having a company-managed device, a specific location, and a valid user identity can access resources within this perimeter. You want to evaluate the impact of this change without blocking legitimate access. What should you do?

• A. Configure a VPC Service Controls perimeter in dry run mode, and enforce strict network segmentation using firewall rules. Use multi-factor authentication (MFA) for user verification.
• B. Use the VPC Service Control Violation dashboard to identify the impact of details about access denials by service perimeters.
• C. Use Cloud Audit Logs to monitor user access to the project resources. Use post-incident analysis to identify unauthorized access attempts.
• D. Establish a Context-Aware Access policy that specifies the required contextual attributes, and associate the policy with the VPC Service Controls perimeter in dry run mode.

Your organization develops software involved in many open source projects and is concerned about software supply chain threats You need to deliver provenance for the build to demonstrate the software is untampered.
What should you do?

• A. * 1, Publish the software code on GitHub as open source.* 2. Establish a bug bounty program, and encourage the open source community to review, report, and fix the vulnerabilities.
• B. * 1. Hire an external auditor to review and provide provenance* 2. Define the scope and conditions.* 3.Get support from the Security department or representative.* 4. Publish the attestation to your public web page.
• C. * 1. Review the software process.* 2. Generate private and public key pairs and use Pretty Good Privacy (PGP) protocols to sign the output software artifacts together with a file containing the address of your enterprise and point of contact.* 3. Publish the PGP signed attestation to your public web page.
• D. * 1. Generate Supply Chain Levels for Software Artifacts (SLSA) level 3 assurance by using Cloud Build.* 2. View the build provenance in the Security insights side panel within the Google Cloud console.

Your organization wants to publish yearly reports of your website usage analytics. You must ensure that no data with personally identifiable information (PII) is published by using the Cloud Data Loss Prevention (Cloud DLP) API. Data integrity must be preserved. What should you do?

• A. Discover and transform PII data in your reports by using the Cloud DLP API.
• B. Encrypt the PII from the report by using the Cloud DLP API.
• C. Detect all PII in storage by using the Cloud DLP API. Create a cloud function to delete the PII.
• D. Discover and quarantine your PII data in your storage by using the Cloud DLP API.

Your company has been creating users manually in Cloud Identity to provide access to Google Cloud resources. Due to continued growth of the environment, you want to authorize the Google Cloud Directory Sync (GCDS) instance and integrate it with your on-premises LDAP server to onboard hundreds of users.
You are required to:
Replicate user and group lifecycle changes from the on-premises LDAP server in Cloud Identity.
Disable any manually created users in Cloud Identity.
You have already configured the LDAP search attributes to include the users and security groups in scope for Google Cloud. What should you do next to complete this solution?

• A. 1. Configure the option to delete domain users not found in LDAP.2. Run GCDS after user and group lifecycle changes.
• B. 1. Configure the option to suspend domain users not found in LDAP.2. Set up a recurring GCDS task.
• C. 1. Configure the LDAP search attributes to exclude manually created Cloud Identity users not found in LDAP.2. Set up a recurring GCDS task.
• D. 1. Configure the LDAP search attributes to exclude manually created Cloud identity users not found in LDAP.2. Run GCDS after user and group lifecycle changes.