You use Azure CDN Standard from Verizon in front of an App Service. You want the CDN to compress text-based assets and dynamic JSON API responses to reduce bandwidth. Clients already send Accept-Encoding headers. Which two actions should you take?

To compress text-based assets and dynamic JSON API responses, you must enable compression on the CDN endpoint and specify the relevant MIME types, such as application/json, text/css, and application/javascript. This tells the CDN to compress these content types before delivery. Additionally, Azure CDN Standard from Verizon has a minimum file size threshold for compression, typically 1 KB. Responses smaller than this will not be compressed, so ensuring responses are larger than 1 KB is crucial for compression to occur. Incorrect options: "Add a rule so that only cached responses are compressed; dynamic responses cannot be compressed by the CDN" is incorrect because CDNs can compress dynamic content if configured properly. "Add image/jpeg to the compressed MIME types to ensure images are compressed as well" is incorrect because images are typically already compressed using their native formats (e.g., JPEG, PNG) and re-compressing them with Gzip offers little to no benefit and can sometimes increase file size. "Set Content-Encoding: gzip on the origin for all responses so the CDN always delivers compressed content without additional configuration" is incorrect because while the origin can compress, the CDN can also perform compression, and relying solely on the origin might not optimize CDN caching and delivery as effectively. The CDN needs to be aware of and handle the compression.