An urgent security fix requires removing three specific paths from Cloud CDN edge caches immediately while leaving other cached objects intact. What is the appropriate action?

Submitting a cache invalidation request for specific paths is the correct action because it immediately removes the outdated content from Cloud CDN edge caches without affecting other cached objects. This ensures the security fix is applied promptly across all CDN locations. Waiting for objects to expire by TTL is too slow for an urgent fix. Disabling Cloud CDN for the backend service would remove all cached content, not just the specific paths, and would also negate the performance benefits of the CDN. Updating the origin to return 404s would make the content unavailable but wouldn't clear the cached, potentially vulnerable, content from the CDN.