When you attach an SSL certificate to a Google Cloud HTTPS Load Balancer, what happens when the certificate expires?
Think about what happens when a browser checks a certificate that is no longer valid.
When an SSL certificate expires, the load balancer still serves HTTPS traffic, but browsers detect the expired certificate and warn users. The load balancer does not automatically renew certificates or switch protocols.
You want to create a managed SSL certificate resource in Google Cloud using JSON. Which JSON snippet correctly defines the domains for the certificate?
Remember that domains should be a list of strings, not a single string.
The correct format uses a JSON array for the domains field. Options A, B, and D use incorrect types or formats for the domains.
You want to design a system that automatically provisions and renews SSL certificates for multiple domains on Google Cloud. Which architecture best supports this?
Consider which option minimizes manual work and leverages Google Cloud's automation.
Google-managed SSL certificates automatically renew and integrate with Cloud Load Balancers, making option B the best architecture for automatic renewal.
What is a key security risk when using self-managed SSL certificates on Google Cloud compared to Google-managed certificates?
Think about who is responsible for tracking certificate expiration.
Self-managed certificates require manual renewal. If forgotten, they expire causing warnings and downtime. Google-managed certificates handle renewal automatically.
You manage multiple Google Cloud projects for different teams, each with their own domains. What is the best practice for managing SSL certificates efficiently and securely across these projects?
Consider security, automation, and ease of management across projects.
Centralizing certificate management with Google-managed certificates reduces manual work, improves security, and allows sharing via load balancers, making option A best practice.