Professional-Cloud-Security-Engineer Exam Dumps - Google Cloud Certified Questions and Answers

Setting up a Shared VPC allows you to create a centrally managed network that spans multiple projects. Here's how you can achieve this while ensuring separation of duties:

Create a Host Project:

Create a project that will act as the host project for your Shared VPC.

Configure Shared VPC:

In the host project, enable the Shared VPC feature.

Create Service Projects:

Create separate service projects for different teams, such as developers and other stakeholders.

Assign Roles:

Security Team: Grant the Compute Network Admin role. This allows the security team to manage network resources, such as firewall rules, subnets, and routes.

Developers: Share the host project’s network with the service projects. Assign roles like Compute Instance Admin to developers in the service projects, enabling them to create and manage VM instances without altering network configurations.

Firewall Management:

The security team will define and manage firewall rules within the host project, ensuring consistent and secure network policies.

Benefits:

Separation of Duties: Security teams handle networking, and developers focus on application deployment and management.

Centralized Control: Network policies are centrally managed, ensuring compliance and security.

Scalability: Easy to add new projects and teams without compromising the overall network security.

References

Google Cloud VPC Documentation

Managing Resources with Shared VPC

https://cloud.google.com/logging/docs/export/troubleshoot#errors_exporting_to_cloud_storage

https://cloud.google.com/logging/docs/export/troubleshoot

Unable to grant correct permissions to the destination: Even if the sink was successfully created with the correct service account permissions, this error message displays if the access control model for the Cloud Storage bucket was set to uniform access when the bucket was created. For existing Cloud Storage buckets, you can change the access control model for the first 90 days after bucket creation by using the Permissions tab. For new buckets, select the Fine-grained access control model during bucket creation. For details, see Creating Cloud Storage buckets.

Objective: Ensure that a Cloud Storage bucket in Project A can only be readable from Project B and prevent data access or copying to Cloud Storage buckets outside the network, even with correct credentials.

Solution: Use VPC Service Controls to create a security perimeter.

Steps:

Step 1: Open the Google Cloud Console.

Step 2: Navigate to the VPC Service Controls page.

Step 3: Create a new service perimeter.

Step 4: Add Project A and Project B to the service perimeter.

Step 5: Include Cloud Storage service in the perimeter configuration.

Step 6: Define access levels to ensure that only resources within the perimeter can access the Cloud Storage bucket.

By setting up a VPC Service Controls perimeter, you can enforce security boundaries that restrict data access and movement to within defined projects, providing an extra layer of protection beyond IAM permissions.

References:

VPC Service Controls Overview

Configuring VPC Service Controls

VPC Peering is between organizations not between Projects in an organization. That is Shared VPC. In this case, both projects are in same organization so having VPC Service Controls around both projects with necessary rules should be fine.

https://cloud.google.com/vpc-service-controls/docs/overview

Configure Cloud Interconnect:

Cloud Interconnect provides high-bandwidth, low-latency connectivity between your on-premises network and Google Cloud. You can choose between Dedicated Interconnect or Partner Interconnect depending on your requirements.

Set up the physical connection and establish the interconnect through the Google Cloud Console or by working with a partner.

Set Up HA VPN:

High Availability (HA) VPN provides a robust, reliable VPN connection to Google Cloud with SLA guarantees. This is crucial for ensuring secure and high-bandwidth connectivity.

Configure two VPN tunnels to ensure redundancy and failover capabilities.

Update Default Route:

Replace the default 0.0.0.0/0 route in your Google Cloud VPC to direct traffic to your on-premises network via the Cloud Interconnect and HA VPN setup.

This ensures all internet-facing traffic is securely routed through your on-premises internet connection.

Ensure Proper Security and Routing Policies:

Implement appropriate firewall rules and security policies on both Google Cloud and on-premises environments to control traffic and ensure secure communication.

Monitor the traffic and connectivity status to maintain optimal performance and security.

References:

Cloud Interconnect Documentation

HA VPN Documentation

Routing Traffic

To monitor and get notified in case the script causing the Compute Engine instance to crash is executed again, you should create an Alerting Policy in Stackdriver (now known as Google Cloud Monitoring). The Process Health condition can be set to monitor the number of executions of the script and ensure it remains below the desired threshold. By enabling notifications, you will be alerted if this threshold is exceeded.

Step-by-Step:

Log Script Executions: Ensure that the script execution is logged.

Create a User-Defined Metric: Go to Google Cloud Console > Logging > Logs-based Metrics, and create a new user-defined metric that counts the number of times the script executes.

Set Up Alerting Policy:

Navigate to Google Cloud Console > Monitoring > Alerting.

Click on “Create Policy”.

Add a condition and select “Logs-based Metric”.

Configure the condition to trigger when the number of script executions exceeds the threshold.

Configure Notifications: Add notification channels (email, SMS, etc.) to the alerting policy.

Save and Test: Save the policy and test to ensure notifications are received when the script is executed beyond the threshold.

References:

Google Cloud Logging User-defined Metrics

Google Cloud Monitoring Alerting Policies

nodeSelector is the simplest recommended form of node selection constraint. You can add the nodeSelector field to your Pod specification and specify the node labels you want the target node to have. Kubernetes only schedules the Pod onto nodes that have each of the labels you specify. => https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector Tolerations are applied to pods. Tolerations allow the scheduler to schedule pods with matching taints. Tolerations allow scheduling but don 't guarantee scheduling: the scheduler also evaluates other parameters as part of its function. => https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

"Date shifting techniques randomly shift a set of dates but preserve the sequence and duration of a period of time. Shifting dates is usually done in context to an individual or an entity. That is, each individual's dates are shifted by an amount of time that is unique to that individual."

To grant an IAM user access to HTTPS resources protected by Identity-Aware Proxy (IAP), you should assign the IAP-Secured Web App User role.

IAP-Secured Web App User (C):

This role grants the necessary permissions for a user to access web applications secured by IAP. It includes permissions to access the IAP-secured resources, ensuring that users can authenticate and gain the appropriate access based on the policies defined in IAP.

Assigning this role ensures that users have the right level of access to protected web resources, aligned with the security controls enforced by IAP.

References

Identity-Aware Proxy Documentation

IAP Roles and Permissions