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 web application uses a global external Application Load Balancer with Cloud CDN across a Managed Instance Group (MIG) and a Cloud Storage bucket. In Cloud Monitoring, you observe the following:
frontend_tcp_rtt_bucket latency is elevated, and logs show mismatched ETag values with Cache-Control: public, max-age=5./assets/q4-pricing.pdf was deleted from the bucket but is still served from edge caches.Which actions should you take?
This approach resolves origin-level cache-sharding caused by inconsistent entity tags (ETag), separates edge cache TTL from browser cache TTL using CDN-Cache-Control, and immediately purges accidentally cached content through a targeted cache invalidation.
ETag headers to validate object freshness across backend instances. When MIG instances generate different ETag values for the same file, Cloud CDN treats each mismatch as a cache miss and performs an unnecessary cache fill. Deploying a consistent VM image or disabling ETag headers eliminates these forced re-fetches, lowering Total cache fill volume and 95th-percentile client latency (frontend_tcp_rtt_bucket).Cache-Control: public, max-age=5 with CDN-Cache-Control: public, max-age=86400 ensures downstream user browsers revalidate every 5 seconds while Google Front End (GFE) edge caches retain and serve the asset for 24 hours (86,400 seconds)./assets/q4-pricing.pdf has already been removed from the Cloud Storage origin, issuing a specific invalidation path (/assets/q4-pricing.pdf) stops Cloud CDN from serving the stale copy before its TTL expires./assets/q4-pricing.pdf avoids flushing healthy cached objects across the rest of the bucket.Unlike blanket invalidations or long browser max-age settings, this combination fixes the underlying ETag root cause, aligns with HTTP caching semantics for tiered TTLs, and uses invalidation sparingly for an accidental upload.
This option strips Host and Protocol components from custom cache keys, marks MIG origin responses with Cache-Control: private, and purges the entire Cloud Storage backend bucket cache using a /* wildcard invalidation.
Cache-Control: private directive instructs shared caches—including Cloud CDN—not to store the response, permitting caching only in the end user's local browser. This drops the MIG cache hit ratio to 0% and sends 100% of traffic to the origin.Host and Protocol merges cache entries when identical assets are served across multiple domains or over both HTTP and HTTPS, but it does not fix ETag mismatches across MIG instances./* invalidation removes every cached object in the Cloud Storage backend bucket rather than just /assets/q4-pricing.pdf, triggering massive Total cache fill traffic, higher origin operations costs, and increased latency as edge caches repopulate.private directive behavior: Shared proxy caches ignore max-age when private is specified and never serve those responses to other clients.No part of this configuration would work for shared CDN caching; public caching with CDN-Cache-Control and a single-object invalidation path are required instead.
This option enables dynamic compression at the Cloud CDN layer, adds no-cache alongside max-age=86400 on MIG responses, and revokes public allUsers Identity and Access Management (IAM) permissions on the Cloud Storage bucket.
Cache-Control: no-cache allows Cloud CDN to store the response, but forces it to revalidate every single client request with the origin server before serving from cache. Combined with mismatched ETag headers across MIG instances, revalidation requests continue failing and triggering full cache fills.allUsers read access from the Cloud Storage bucket prevents future unauthenticated cache fills, but it does not delete copies of /assets/q4-pricing.pdf already residing in Cloud CDN edge caches—and it breaks delivery for all other public assets in that bucket.no-cache semantics: Requires origin validation on every lookup rather than serving directly from edge memory.Via header) reduces both cache fill and egress transfer.Every client request strictly required origin validation, dynamic compression was unavailable on the origin, and the entire bucket needed to become private alongside an explicit cache invalidation.
This option standardizes ETag values across MIG instances, increases the global Cache-Control max-age directive to 24 hours for all caches, and relies on URL versioning and least-recently-used (LRU) eviction rather than explicit cache invalidation.
Cache-Control: public, max-age=86400 applies to both shared edge caches and end-user browsers when no overriding directive like CDN-Cache-Control or s-maxage is present. Browsers will cache responses locally for 24 hours instead of revalidating every 5 seconds./assets/q4-pricing.pdf from receiving the accidentally cached non-public file.file_v2.pdf) forces Cloud CDN to fetch a new cache key, leaving the old URL still accessible until expiry.Browsers were permitted to cache MIG responses for 24 hours without 5-second revalidation, and /assets/q4-pricing.pdf were a routine public update rather than an accidental upload of sensitive data.
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