Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud Security Engineer · Google Cloud
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
B. Create access levels in Access Context Manager to prevent data exfiltration, and use a shared VPC for communication between projects. Explanation: Access Context Manager allows you to define access levels based on various attributes, such as the user's identity and the context of their request, which can help limit actions that could be used for data exfiltration. This setup allows you to enforce security policies around sensitive data while still allowing communication through a Shared VPC. Shared VPC enables networking between different projects, ensuring that resources can communicate securely without exposing them to the public internet or compromising security policies.
Explanation: To prevent data exfiltration while allowing communication between projects, a single service perimeter is the best approach. This creates a secure boundary around all projects under the "implementation" folder, ensuring that resources within the perimeter can communicate while preventing unauthorized access or data transfer outside the perimeter. Automating the addition of new projects to the service perimeter ensures scalability and compliance with organizational security requirements.
Similitudes con la opción C: Uso de IaC y Cloud Function: La opción D también utiliza una herramienta de IaC (Terraform) y una Cloud Function para automatizar la creación y gestión de los service perimeters. Monitoreo con Stackdriver y Cloud Pub/Sub: Se utiliza Stackdriver y Cloud Pub/Sub para detectar la creación de nuevos proyectos. Diferencias con la opción C: Cantidad de service perimeters: La opción D crea tres service perimeters diferentes (dev, staging, prod), mientras que la opción C solo crea uno. Asignación automática de proyectos: La función Cloud de la opción D asigna automáticamente los nuevos proyectos al perímetro de servicio correspondiente. En la opción C, la asignación de proyectos a los service perimeters se debe realizar manualmente.