CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Enable CloudFront Geo-targeting for the China region

  Why it's wrong here

  CloudFront geo-targeting, more accurately geo-restriction, lets you allow or block requests based on the country of the viewer, but it does not add any infrastructure to mainland China. Enabling it for China would merely tell CloudFront to accept or deny requests from Chinese IP addresses; the requests that are allowed still travel to CloudFront's nearest edge location outside mainland China, so they remain subject to the same latency, packet loss, and potential blocking that affect all cross-border traffic. Geo-targeting is a policy feature, not a way to extend CloudFront's reach into a legally restricted region.

• ✓

  Use AWS China Regions (cn-north-1, cn-northwest-1) which require a separate AWS account

  Why this is correct

  The correct approach is to use the AWS China Regions (cn-north-1 in Beijing, operated by Sinnet, and cn-northwest-1 in Ningxia, operated by NWCD), which require a separate AWS account from the standard global account. These regions are physically located in mainland China and operate under different compliance frameworks, including ICP licensing. To serve content to Chinese users efficiently and legally, you must deploy resources in these regions—there is no way to use the global CloudFront service to directly serve mainland China, because the global edge network does not extend there and Chinese law mandates local hosting for end-user content.

• ✗

  Enable CloudFront Accelerated Transfer for China

  Why it's wrong here

  This option is invalid because AWS CloudFront does not expose any feature called 'Accelerated Transfer.' Even if such a feature existed, it would not help users in mainland China: standard CloudFront distributions serve content from a global network of edge locations that excludes mainland China, so any request from China would still cross the Great Firewall and incur high latency. Moreover, providing content to mainland China without an ICP license and without using the AWS China partition violates Chinese regulations, regardless of any CloudFront setting.

• ✗

  Use Route 53 latency routing to direct Chinese users to the nearest CloudFront PoP

  Why it's wrong here

  Route 53 latency routing is a DNS-based traffic management feature that routes users to the endpoint with the lowest measured latency, but it is not a content delivery solution. Since CloudFront has no Points of Presence (PoPs) inside mainland China, Chinese users would simply be directed to the nearest available edge—likely in Hong Kong, Singapore, or Japan—which still requires traversing China's internet filtering and suffers from cross-border bottlenecking. Latency routing also cannot satisfy China's regulatory requirement for ICP filing, and it does not create any localized infrastructure within mainland China.

Go deeper

Related to this question