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.
You manage a Shared VPC hosting PCI-DSS workloads and are assessing its network exposure using Security Command Center (SCC), Firewall Insights, and Cloud Logging. Firewall Rules Logging is enabled across all VPC rules and Cloud NGFW Layer 7 inspection policies (apply_security_profile_group) with a 6-week observation period.
After 14 days, you observe the following:
OPEN_FIREWALL finding (PCI-DSS v3.2.1 control 1.2.1) on ingress rule allow-partner-api (0.0.0.0/0, tcp:8080-8090, icmp), while Firewall Insights flags the rule's port range as overly permissive but does not flag its IP range.35.191.0.0/16, 130.211.0.0/22) shows zero hits.HIGH severity CVE threat log in networksecurity.googleapis.com/firewall_threat reports malicious traffic from 198.51.100.45.How should you interpret these findings and correlate the logs to remediate exposure?
This option recommends waiting the full 6-week observation period before acting on overly permissive insights, adding a lower-priority rule to shadow allow-partner-api, and filtering compute.googleapis.com/firewall logs for apply_security_profile_fallback_action = ALLOW to trace the threat.
It unnecessarily delays cleanup of inactive rules, applies invalid firewall priority logic that fails to eliminate exposure, and misinterprets a Cloud NGFW fallback error indicator as normal Layer 7 inspection.
medium severity misconfigurations while SCC continues flagging allow-partner-api as OPEN_FIREWALL.apply_security_profile_fallback_action = ALLOW in firewall logs indicates a misconfigured intrusion prevention rule (such as a missing or unassociated firewall endpoint), meaning traffic bypassed Layer 7 inspection instead of generating threat logs.You were diagnosing why Layer 7 threat logs failed to appear due to a missing firewall endpoint association (apply_security_profile_fallback_action = ALLOW) and modifying or replacing the higher-priority rule directly.
When Cloud NGFW properly redirects traffic to a Layer 7 firewall endpoint, the firewall rule log records disposition: INTERCEPTED and apply_security_profile_fallback_action: UNSPECIFIED.
This option suggests deleting unhit Google Cloud load balancer health check IP ranges, enabling VPC Flow Logs on subnets to track packets dropped by ingress deny rules, and correlating Cloud NGFW threat logs using clientIp and serverPort.
Although removing unused ports is beneficial, the remaining actions introduce service outages, leave blind spots in dropped-ingress monitoring, and query incorrect log field names that fail to match threat logs.
deny rules), but they only log ingress traffic that is permitted by an ingress allow rule; packets blocked by ingress deny rules are never logged in VPC Flow Logs.clientIp and serverPort belong to URL filtering logs (firewall_url_filter) and Advanced malware sandbox logs (firewall_wildfire), whereas threat logs (firewall_threat) use source_ip_address and destination_port.The investigation involved URL filtering or WildFire logs rather than threat logs, you were diagnosing dropped egress traffic with VPC Flow Logs, and the unhit IP addresses were obsolete customer ranges rather than Google Cloud load balancer health check ranges.
To audit dropped ingress packets and detect attack spikes, you must enable Firewall Rules Logging on deny rules and analyze Firewall Insights (Deny rules with hits) rather than relying on VPC Flow Logs.
This approach integrates Firewall Insights, Security Command Center (SCC), Cloud Monitoring, and Cloud NGFW threat logs to evaluate network exposure, maintain PCI-DSS compliance, and trace active security events. Firewall Insights analyzes Firewall Rules Logging data for TCP and UDP traffic to pinpoint overly permissive attributes, while SCC checks firewall metadata for public 0.0.0.0/0 exposure on non-exempt ports.
allow-partner-api permits both TCP and ICMP, Firewall Insights does not flag the 0.0.0.0/0 IP range as overly broad since it may be used for ICMP traffic. However, it flags the partially used tcp:8080-8090 range. Narrowing both the TCP port range and the 0.0.0.0/0 source range remediates the PCI-DSS v3.2.1 control 1.2.1 OPEN_FIREWALL finding.35.191.0.0/16 and 130.211.0.0/22) and other Google Cloud service blocks may show zero hits during an observation window, but must be retained to prevent breaking load balancer health probes.deny rule hit counts provides early warning of potential attacks. Correlating source_ip_address and destination_port in networksecurity.googleapis.com/firewall_threat with src_ip and dest_port in compute.googleapis.com/firewall (where disposition is INTERCEPTED) links the CVE alert directly to the intercepting Cloud NGFW rule.deny hit-count telemetry to detect sudden probing spikes.Unlike relying on VPC Flow Logs or blindly deleting unhit ranges, this strategy respects protocol-specific analysis boundaries, preserves essential platform connectivity, and accurately joins Layer 7 threat telemetry with firewall rule hits.
This option suggests dismissing the SCC OPEN_FIREWALL finding based on Firewall Insights' IP output, deleting any zero-hit rule after 14 days without checking machine learning (ML) predictions, and expecting a separate INTERCEPTED firewall log entry per threat packet.
It misreads how Firewall Insights and SCC evaluate protocols, risks deleting critical low-frequency rules, and misunderstands session-based logging in Cloud NGFW.
OPEN_FIREWALL detector still flags 0.0.0.0/0 under PCI-DSS 1.2.1 whenever allowed includes ports outside exempt values (icmp, tcp:22, tcp:443, tcp:3389, udp:3389, sctp:22).apply_security_profile_group rules, compute.googleapis.com/firewall logs INTERCEPTED only once at the start of a session, whereas networksecurity.googleapis.com/firewall_threat logs individual threats detected throughout the session.The rule only permitted exempt protocols like icmp or tcp:443, ML predictions confirmed a low future hit probability backed by similar rules, and you were reviewing standard DENY rule repeat logs rather than INTERCEPTED session logs.
Unlike apply_security_profile_group rules that log once per session, standard DENY firewall policy rules repeat log entries every 5 seconds while matching packets continue arriving.
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