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 organization hosts media assets on an external HTTPS origin (media.partner.example.com:443) in a third-party cloud and wants to accelerate global delivery using Cloud CDN behind an external Application Load Balancer. Your architecture must meet the following requirements:
media.partner.example.com in the HTTP Host header.Which configuration should you implement?
INTERNET_IP_PORT pointing to the origin's public IP address, enable Cloud CDN, allowlist _cloud-eoips.googleusercontent.com on the origin firewall, and attach a Cloud Armor backend security policy containing both geo-blocking and WAF rules.This configuration uses an INTERNET_IP_PORT endpoint to connect directly to a third-party origin's public IP address and relies exclusively on a Cloud Armor backend security policy for both access control and WAF filtering.
INTERNET_IP_PORT, the load balancer does not validate the origin's SSL server certificate and does not send the SNI extension in the TLS ClientHello (because IP address literals are invalid in the SNI HostName field). This violates the TLS security requirement and can break TLS handshakes with multi-tenant origins.Host request header on the backend service, the load balancer preserves the client's original Host header, which the external origin may reject if it expects media.partner.example.com.INTERNET_IP_PORT couples your backend configuration to a static IP address; changing between INTERNET_IP_PORT and INTERNET_FQDN_PORT requires creating a new NEG.The origin did not support SNI or public CA-signed certificates, Cloud CDN caching was disabled (making every request hit the backend service), and the origin accepted the client's original Host header.
INTERNET_FQDN_PORT, configure a proxy-only subnet with Cloud NAT for egress IP allowlisting, attach an HTTPS health check, enable Cloud CDN, set a custom Host header, and attach a Cloud Armor edge security policy.This configuration uses a Regional External Application Load Balancer powered by managed Envoy proxies, a regional internet NEG, a proxy-only subnet with Cloud NAT for deterministic egress IPs, and distributed Envoy health checks.
INTERNET_FQDN_PORT, regional internet NEGs do not validate the origin's SSL server certificate by default unless you explicitly configure backend authenticated TLS.The workload required regional data residency without Cloud CDN caching, needed static Cloud NAT egress IPs or active Envoy health checks against multiple external endpoints, and used a regional Cloud Armor backend security policy with backend authenticated TLS.
INTERNET_FQDN_PORT endpoints for origin redundancy, attach an HTTPS health check and retry policy to the backend service, enable Cloud CDN, set a custom Host header, and attach a Cloud Armor edge security policy.This option attempts to add multi-endpoint load balancing, active HTTPS health checks, and retry policies to a global internet NEG behind a Global External Application Load Balancer, while relying solely on a Cloud Armor edge security policy.
_cloud-eoips.googleusercontent.com, the external origin firewall cannot restrict ingress strictly to Google's GFE egress ranges.502 (Bad Gateway) when the external endpoint is unreachable rather than using active health probes.Active health checks and multiple endpoints were used with a regional internet NEG on a regional Envoy-based load balancer—though that topology would not support Cloud CDN or Cloud Armor edge security policies.
INTERNET_FQDN_PORT (media.partner.example.com:443), Cloud CDN enabled, a custom Host request header set to media.partner.example.com, and no health check. Allowlist the IP ranges from the _cloud-eoips.googleusercontent.com DNS TXT record on the origin firewall, and attach both a Cloud Armor edge security policy and a Cloud Armor backend security policy to the backend service.A Global External Application Load Balancer paired with a global internet network endpoint group (NEG) uses Google Front Ends (GFEs) to terminate client connections at the edge, cache responses with Cloud CDN, and proxy cache misses over Google's backbone to an external origin.
INTERNET_FQDN_PORT endpoint on a global internet NEG instructs GFEs to send the configured FQDN in the SNI extension during the TLS handshake and validate the origin's public CA certificate, expiration, signature, and Subject Alternative Names (SANs). Setting a custom request header (Host: media.partner.example.com) overrides the client's incoming Host header so the external origin routes requests properly._cloud-eoips.googleusercontent.com DNS TXT record, allowing the origin firewall to permit only legitimate GFE traffic.502 if the origin becomes unreachable.This is the only configuration that combines Cloud CDN, SNI and public CA validation, pre-cache Cloud Armor enforcement, and origin WAF protection in a fully supported global topology.
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