Page Rule Cache TTL precedence over DNS‑level TTL when multiple rules match

When a request matches both a DNS‑level Cache TTL setting and one or more Page Rules that also define a Cache TTL, the documentation states that the Page Rule value “takes precedence” for matched requests. However, it does not clarify the resolution order when several Page Rules match the same URL, nor whether the most specific rule, the first rule in the list, or the rule with the highest priority wins.

Understanding this behavior is essential for avoiding stale content delivery after origin updates, especially when surrogate‑key purges or Cache‑Control: private headers are also in play.

• Which Page Rule is applied when multiple rules match the same request?
• Does the DNS‑level TTL ever re‑apply after a Page Rule match is evaluated?
• How can an operator verify the effective TTL without relying on trial‑and‑error cache purges?