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 static web assets in a private Amazon S3 bucket (assets.s3.us-east-2.amazonaws.com) without custom Cache-Control metadata on the objects. You want to deliver these assets through Cloud CDN with a global external Application Load Balancer under both cdn.example.com and static.example.com, while meeting the following requirements:
Which configuration should you implement?
assets.s3.us-east-2.amazonaws.com and attach it to a Cloud CDN-enabled backend service with awsV4Authentication configured in securitySettings. Add a custom request header on the backend service to set Host to assets.s3.us-east-2.amazonaws.com, set the cache mode to FORCE_CACHE_ALL with a default TTL, exclude Host from the custom cache key, and configure CORS rules on the S3 bucket (relying on Cloud CDN's Vary: Origin support).This architecture integrates a third-party object storage bucket as an external backend (custom origin) for Cloud CDN using an internet network endpoint group (NEG) attached to a backend service on a global external Application Load Balancer. By combining AWS Signature Version 4 (awsV4Authentication), a custom Host request header, the FORCE_CACHE_ALL cache mode, and a custom cache key, Cloud CDN securely retrieves, caches, and shares private S3 objects across multiple frontend domains.
awsV4Authentication under securitySettings on the backend service instructs Cloud CDN to sign origin requests using an HMAC access key ID and secret key (GET, HEAD, OPTIONS, and TRACE methods). Clients cannot access the S3 bucket directly without valid credentials.Host header (cdn.example.com or static.example.com). Adding a custom request header that rewrites Host to assets.s3.us-east-2.amazonaws.com ensures S3 virtual-hosted routing and SigV4 signature verification succeed.Authorization header on cache-fill requests, CACHE_ALL_STATIC and USE_ORIGIN_HEADERS refuse to cache responses lacking public, must-revalidate, or s-maxage directives. Setting FORCE_CACHE_ALL with a default TTL overrides this restriction so objects are cached immediately.corsPolicy, so CORS headers must originate from the S3 bucket's CORS rules. Cloud CDN natively permits caching responses with Vary: Origin, Access-Control-Request-Headers, and Access-Control-Request-Method. Excluding Host from the custom cache key prevents sharding identical objects between cdn.example.com and static.example.com.FORCE_CACHE_ALL removes the need to update Cache-Control metadata across existing S3 objects.Host from the backend service cache key consolidates cache entries across multiple domains.awsV4Authentication protects data in transit and blocks unauthorized direct bucket access.OPTIONS preflight methods in private origin authentication and Vary: Origin caching.Alternative approaches either fail to cache Authorization-bearing origin responses (CACHE_ALL_STATIC or USE_ORIGIN_HEADERS without Cache-Control metadata), break S3 virtual-hosted requests by forwarding the client Host header, or rely on unsupported features such as SigV4A or Media CDN-only corsPolicy settings.
Host header, set the cache mode to FORCE_CACHE_ALL, retain the default cache key configuration, and configure CORS rules on the S3 bucket.This option attempts to connect a Cloud CDN backend service to an Amazon S3 Multi-Region Access Point using AWS Signature Version 4A (SigV4A) while keeping the default cache key settings, applying a custom Host request header, enabling FORCE_CACHE_ALL, and configuring CORS on S3.
awsV4Authentication only supports standard AWS Signature Version 4, which signs requests scoped to a specific single origin region (such as us-east-2).https://cdn.example.com/logo.png and https://static.example.com/logo.png as two distinct cache keys, duplicating cached objects and lowering the overall cache hit ratio.awsV4Authentication requires a single originRegion parameter and automatically sets the service name to s3, making it incompatible with multi-region SigV4A signing.Host—as the cache key.awsV4Authentication) instead of a Multi-Region Access Point with SigV4A, and customized the cache key to omit Host.When migrating or designing multi-domain static delivery on Cloud CDN backend services, always review the default cache key settings (includeHost, includeProtocol, includeQueryString), as all three default to true.
assets.s3.us-east-2.amazonaws.com and attach it to a Cloud CDN-enabled backend service with awsV4Authentication configured in securitySettings. Keep the default CACHE_ALL_STATIC cache mode, exclude Host from the custom cache key, preserve the client's Host header on origin requests, and configure CORS rules on the S3 bucket.This option correctly sets up an internet NEG with AWS Signature Version 4 (awsV4Authentication), excludes Host from the custom cache key, and delegates CORS handling to the S3 bucket. However, it leaves the cache mode at the default CACHE_ALL_STATIC setting and preserves the incoming client Host header when forwarding cache-fill requests to Amazon S3.
Authorization header to every origin request. Under CACHE_ALL_STATIC (and USE_ORIGIN_HEADERS), Cloud CDN strictly refuses to cache responses to requests containing an Authorization header unless the origin response includes Cache-Control: public, must-revalidate, or s-maxage. Because the S3 objects have no custom Cache-Control metadata, every request results in a cache miss.Host, the backend service forwards cdn.example.com or static.example.com to Amazon S3. Virtual-hosted-style S3 endpoints expect the bucket's FQDN (assets.s3.us-east-2.amazonaws.com) in the Host header to identify the bucket and validate the SigV4 signature.Authorization header safeguard: Cloud CDN enforces strict caching rules on authenticated origin requests under CACHE_ALL_STATIC to prevent accidentally caching per-user content.Host preservation: External Application Load Balancer backend services pass through the client-supplied Host header unless explicitly overwritten via custom request headers.CACHE_ALL_STATIC will not cache responses if an Authorization header was sent and required Cache-Control directives are absent.Cache-Control: public, max-age=3600 (or s-maxage/must-revalidate) and added a custom request header on the backend service to rewrite Host to assets.s3.us-east-2.amazonaws.com.A common misconception is that CACHE_ALL_STATIC caches all static file types regardless of authentication headers. In practice, using awsV4Authentication without modifying origin metadata requires FORCE_CACHE_ALL.
assets.s3.us-east-2.amazonaws.com, attach it to a Cloud CDN-enabled backend service configured with USE_ORIGIN_HEADERS, enable Cloud CDN signed URLs on the backend service to authenticate origin requests to S3, and configure a corsPolicy on the backend service URL map.This configuration mixes Cloud CDN client-side access controls with Media CDN routing features. Signed URLs cryptographically authorize end-user requests sent to Cloud CDN, USE_ORIGIN_HEADERS enforces explicit origin caching headers, and corsPolicy is a route-level configuration specific to Media CDN's EdgeCacheService resource.
awsV4Authentication).corsPolicy resource on URL maps or backend services; built-in corsPolicy enforcement is exclusively a Media CDN capability.USE_ORIGIN_HEADERS requires valid Cache-Control (max-age, s-maxage, or public) or Expires headers from the origin. Without custom Cache-Control metadata on the S3 objects, Cloud CDN will not cache them.Host headers: Leaving the default Host header forwarding and default cache key configuration causes origin rejections and duplicate cache entries across cdn.example.com and static.example.com.EdgeCacheService and corsPolicy belong to Media CDN, not Cloud CDN.USE_ORIGIN_HEADERS never infers cacheability from MIME types.EdgeCacheService and EdgeCacheOrigin with corsPolicy and awsV4Authentication) to serve high-throughput media workloads rather than Cloud CDN with an external Application Load Balancer, and you wanted signed requests solely for client authorization.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