Your Compute Engine-hosted monitoring dashboard serves real-time reports to external stakeholders without authentication. You must secure the channel (encrypt in transit) while allowing public access. How should you configure this?

The correct solution is to add an HTTP(S) load balancer with a Google-managed SSL certificate. An HTTP(S) load balancer provides a public IP address and handles SSL termination, encrypting traffic in transit between the client and the load balancer. Google-managed SSL certificates simplify certificate management, ensuring the channel is secured without manual intervention, and it allows public access. Incorrect options: Adding a public IP and using a service account key for encryption is incorrect because service account keys are for authentication/authorization within Google Cloud, not for encrypting public-facing HTTP traffic. Using Cloud Scheduler and Cloud Build to export reports to Cloud Storage is for data distribution, not for securing a real-time dashboard channel. Adding an HTTP(S) load balancer and configuring Identity-Aware Proxy (IAP) is incorrect because IAP provides authentication and access control, which contradicts the requirement for public access.