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 company runs internet-facing APIs behind a global external Application Load Balancer protected by Google Cloud Armor Enterprise. To reduce mean time to remediation (MTTR) during active incidents, you must design an automated response workflow that meets these requirements:
Which configuration should you implement?
evaluateAdaptiveProtectionAutoDeploy() and JSON Key Authentication DoThe evaluateAdaptiveProtectionAutoDeploy() expression enables Adaptive Protection to automatically deploy machine-learning-generated mitigation rules against Layer 7 distributed denial-of-service (DDoS) anomalies, while the User Service Account parameter in Google SecOps uses a static JSON private key file for API authentication.
roles/compute.networkAdmin) role grants compute.backendServices.setSecurityPolicy to attach policies, but lacks compute.securityPolicies.update, which is required for securityPolicies.addRule.0.8, confidence above 0.5, and impacted baseline below 0.01.The goal were exclusively mitigating high-volume L7 HTTP floods via ML-generated signatures on an external Application Load Balancer where Workload Identity was unavailable and roles/compute.securityAdmin was assigned.
Preconfigured rules for named IP address lists allow Cloud Armor to reference external third-party IP lists, while VPC firewall rules control traffic entering or leaving Compute Engine VM network interfaces inside a Virtual Private Cloud.
evaluateThreatIntelligence().You needed to integrate a daily-synced third-party IP allowlist into Cloud Armor while separately restricting direct external access to VMs that do not sit behind a proxy load balancer.
CLOUD_ARMOR_NETWORK Policies DoA CLOUD_ARMOR_NETWORK policy is a regional network edge security policy used with Advanced Network DDoS protection for regional external passthrough Network Load Balancers, protocol forwarding, and VMs with public IP addresses.
CLOUD_ARMOR_NETWORK policies.evaluateThreatIntelligence()) is supported only on external Application Load Balancers and external proxy Network Load Balancers, not on network edge security policies.CLOUD_ARMOR_NETWORK security policy is configured with --network-ddos-protection ADVANCED, Cloud Armor prohibits adding custom rules to that policy. Attempting to invoke securityPolicies.addRule from Google SecOps against it will fail.Region in the Google SecOps Add a Rule to a Security Policy action targets regional security policies, whereas global external Application Load Balancer policies require omitting Region.MITIGATION_STARTED, MITIGATION_ONGOING, MITIGATION_ENDED logs) rather than Layer 7 WAF or threat-feed rules.You were solely enabling always-on L3/L4 volumetric DDoS protection for a regional passthrough Network Load Balancer or public VM IP without adding custom rules or using evaluateThreatIntelligence().
This architecture combines Google Cloud Armor Threat Intelligence for continuous edge filtering with the Google Security Operations (SecOps) Cloud Armor integration for automated SOAR playbook remediation authenticated through Workload Identity.
evaluateThreatIntelligence() match expression inspects incoming requests against continuously updated Google Threat Intelligence feeds—such as Tor exit nodes or VPN providers—and blocks, redirects, or rate-limits matching traffic at the Google Cloud edge.securityPolicies.addRule with Policy Name and Rule JSON (containing deny or throttle rate-limiting definitions). Leaving the optional Region parameter empty ensures the rule targets the global security policy attached to the global external Application Load Balancer.roles/iam.serviceAccountTokenCreator to the SecOps instance identity (gke-init-python@... or soar-python@...) on a target service account—uses service account impersonation to issue short-lived tokens rather than static JSON keys. Assigning a custom role with compute.securityPolicies.update enforces least-privilege access.Unlike Adaptive Protection auto-deploy (which relies on volumetric L7 baseline deviations) or VPC firewall rules (which cannot filter proxied client IPs from GFEs), pairing evaluateThreatIntelligence() with Workload-Identity-authenticated SecOps playbooks provides both proactive feed-based filtering and real-time programmatic incident response at the network edge.
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