A global content site runs on Azure App Service with Azure Database for PostgreSQL Flexible Server. Users report slow downloads for images and CSS from distant regions, and the database CPU is high due to read-heavy queries. The web tier averages 40% CPU. You must reduce end-user latency worldwide and offload the database without changing the application code significantly. Which two actions should you take first?

Serving static assets via Azure CDN directly addresses slow downloads for images and CSS from distant regions by caching content closer to users at edge Points of Presence (POPs), reducing latency. Provisioning read replicas for Azure Database for PostgreSQL and routing read-only queries to them offloads the primary database, reducing its CPU utilization caused by read-heavy queries without significant application code changes. Increasing the App Service plan or disabling autoscale doesn't address static asset delivery or database read offloading. Replacing PostgreSQL with Azure Table Storage would require significant application code changes and might not support complex queries. Autoscaling App Service based only on CPU doesn't solve the static asset or database read issues.