Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your enterprise operates a Shared VPC architecture with a host project inside a Shared-Network folder and workload service projects inside Production and Development folders. You need to implement micro-segmentation and compliance auditing at scale to meet the following requirements:
Which configuration strategy should you implement?
This approach combines organization policy constraints, hierarchical firewall policies, VPC Flow Logs, and Security Command Center to establish defense-in-depth micro-segmentation and continuous compliance auditing across a multi-project Google Cloud resource hierarchy.
Deny All by default) blocks Compute Engine VMs from obtaining public IPv4 addresses unless explicitly overridden.Shared-Network folder and the organization), rather than the service project folders. Using secure tags and target service accounts provides IAM-governed, identity-based micro-segmentation, while goto_next rules delegate granular workload decisions down to VPC-level firewall rules.allow and deny rules records permit/drop verdicts in Cloud Logging, while VPC Flow Logs and Security Command Center provide continuous traffic telemetry, anomaly detection, and compliance framework auditing.allow or deny rules defined at the organization or Shared-Network folder levels.Attaching policies to the organization and Shared-Network folder ensures Shared VPC VM interfaces actually inherit the segmentation rules, uses supported identity-based targets (secure tags and service accounts), and respects the logging constraint that only allow and deny actions support firewall rules logging.
This option substitutes Restrict Protocol Forwarding Based on type of IP Address for the VM external IP constraint and uses a Google Cloud Armor hierarchical security policy instead of a hierarchical VPC firewall policy for internal micro-segmentation.
The requirement was solely to enforce consistent Layer 7 WAF and DDoS protections across external Application Load Balancers in multiple projects and block external protocol forwarding rules, rather than enforcing VM-level VPC micro-segmentation.
This option applies the correct organization policy constraints and monitoring tools, but it attempts to enforce hierarchical firewall policies at the service project folders (Production and Development) and uses network tags as rule targets.
Shared-Network folder and organization), not the folders containing the service projects (Production and Development).The workloads were deployed into standalone VPC networks directly inside the Production and Development service projects (rather than a Shared VPC host network) and the rules used secure tags or target service accounts instead of legacy network tags.
This option selects the appropriate organization policies, secure tags, and traffic monitoring services, but it attempts to associate a hierarchical firewall policy directly with a project and enable firewall logging on goto_next rules.
allow and deny rules, and is not supported for goto_next rules. Relying on goto_next logging will fail to capture explicit enforcement decisions in Cloud Logging.goto_next: The goto_next action simply delegates packet evaluation to lower-level folder policies or VPC network rules without making a terminal permit or deny decision, which is why logging is reserved for allow and deny actions.The hierarchical firewall policy were attached to the Shared-Network folder (or the organization node) rather than the host project itself, and firewall rules logging were enabled on the explicit allow and deny rules instead of goto_next rules.
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