Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is establishing a centralized Shared VPC architecture to host workloads across multiple departments. The central network security team manages the Shared VPC host project, which contains subnet-frontend (in us-central1), subnet-backend (in us-central1), and subnet-analytics (in us-east1).
The organization must meet the following access and administrative requirements:
service-project-app and must only be able to provision VM instances into subnet-frontend.service-project-data and must only be able to provision VM instances into subnet-analytics.How should IAM roles and resource bindings be configured to meet these requirements following the principle of least privilege?
roles/compute.networkAdmin) in their respective service projects. Use VPC Network Peering to connect each service project's local VPC back to the host project's Shared VPC.This configuration sets up independent VPC networks inside each service project and attempts to link them back to a host VPC using VPC Network Peering, rather than implementing a unified Shared VPC topology.
roles/compute.networkAdmin in service projects decentralizes network administration and gives application teams autonomy over firewall rules and local subnets.subnet-frontend and subnet-analytics in the host project.Application teams required autonomous control over their own local VPC routing and firewall policies while needing non-transitive private connectivity to common services.
roles/compute.networkUser) at the host project level, while restricting subnet selection via IAM conditions on Compute Instance Admin in each service project. Assign the central network team Compute Admin (roles/compute.admin) on both the host and service projects.Granting roles/compute.networkUser at the host project level gives designated principals permission to use all current and future subnets in all VPC networks contained within that host project.
subnet-backend.roles/compute.admin) to the central network team on all service projects grants them unnecessary administrative control over compute instances and workloads in those service projects.roles/compute.networkUser grants blanket access to all VPC networks in the host project.compute.subnetworks.use permissions without needing condition expressions.All service projects required unrestricted access to deploy instances into every subnet throughout the Shared VPC host project.
roles/compute.xpnAdmin) role to the AppDev and Analytics teams on the host project. Assign the central network team Security Admin (roles/compute.securityAdmin) on the host project.The Shared VPC Admin (roles/compute.xpnAdmin) role grants organization-level or folder-level authority to enable host projects, attach or detach service projects, and manage Shared VPC associations.
roles/compute.xpnAdmin to developer and analytics teams gives them administrative control to attach projects and modify host project configuration across the organization.roles/compute.xpnAdmin does not grant developer teams standard instance deployment permissions (compute.instances.create) within service projects.roles/compute.securityAdmin to the network team restricts them to managing firewall rules and security policies, leaving them unable to create or modify subnets, routes, and core VPC infrastructure.roles/compute.xpnAdmin must be granted at the organization or folder level, not to project-level development teams.roles/compute.securityAdmin manages firewalls and SSL certificates but cannot administer subnets or Cloud Routers.The development leads were responsible for administering organization-wide Shared VPC enablement and associating projects under the organization hierarchy.
service-project-app and Compute Network User (roles/compute.networkUser) specifically on the subnet-frontend resource in the host project. Assign the Analytics team Compute Instance Admin on service-project-data and Compute Network User specifically on the subnet-analytics resource in the host project. Assign the central network team Compute Network Admin (roles/compute.networkAdmin) at the host project level.Shared VPC enables centralized management of networking infrastructure by separating host projects from service projects. Subnet-level access control allows administrators to grant the Compute Network User (roles/compute.networkUser) role on individual subnet resources rather than across the entire host project.
roles/compute.networkUser at the individual subnet resource level (e.g., subnet-frontend or subnet-analytics) grants Service Project Admins permission to attach network interfaces and instantiate VMs in that specific subnet only, preventing unauthorized provisioning into other subnets like subnet-backend.roles/compute.instanceAdmin.v1 or similar) in their respective service projects allows developers to manage virtual machines and application workloads autonomously.roles/compute.networkAdmin) to the network team at the host project level provides complete control over routing, peering, subnets, and firewall rules without granting service project workload permissions.Applying the roles/compute.networkUser role directly to target subnets adheres to least privilege by restricting service teams from discovering and deploying into unauthorized subnets, satisfying all architectural and security constraints.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated