CDN CDN Origin Shield & Pull/Push Zones

Question 1

What is the primary purpose of an origin shield in a CDN architecture?

Accepted Answer

To act as a mid-tier cache that reduces the number of requests reaching the origin server

Answer

To encrypt traffic between edge nodes

Answer

To load-balance between multiple CDN providers

Answer

To generate dynamic content at the edge

Question 2

Which scenario benefits most from enabling origin shield?

Accepted Answer

A high-traffic media site with large cacheable assets and a single origin data center

Answer

A site with 100% dynamic, personalized content

Answer

A real-time WebSocket application

Answer

A site already using a multi-region origin setup

Question 3

What is a 'pull zone' in CDN terminology?

Accepted Answer

A CDN configuration where edge nodes fetch content from the origin on demand when a cache miss occurs

Answer

A zone where CDN pushes files to edge nodes proactively

Answer

A geographic region restricted from accessing content

Answer

A billing zone for egress traffic

Question 4

What is a 'push zone' in CDN terminology?

Accepted Answer

A storage zone where operators proactively upload files directly to CDN edge storage for immediate availability

Answer

A zone that pushes cached content invalidations to users

Answer

An automated origin health-push mechanism

Answer

A DNS push notification system

Question 5

When using origin shield, which cache TTL setting has the most impact on reducing origin requests?

Accepted Answer

Origin cache-control max-age

Answer

Browser cache TTL

Answer

Shield-to-edge TTL

Answer

DNS TTL

Question 6

What is 'cache coalescing' (also called request collapsing) at an origin shield node?

Accepted Answer

Queuing concurrent cache-miss requests for the same object and sending only one upstream request to the origin

Answer

Merging multiple CDN providers into one

Answer

Combining small files into a single larger cached object

Answer

Merging TTL values from multiple Cache-Control headers