Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A security engineer is configuring end-to-end encryption in transit between application microservices and a Google Cloud SQL for PostgreSQL database instance. The database instance is provisioned using a shared Certificate Authority (shared CA) mode and is accessed over Private Service Connect (PSC).
To satisfy strict compliance and zero-trust policies, client connections must enforce complete cryptographic server identity verification to prevent spoofing and Man-in-the-Middle (MitM) attacks.
Which configuration should the security engineer implement?
Cloud Key Management Service (KMS) CMEK is used for cryptographic control of data at rest (such as storage volume encryption), while sslmode=require ensures that the client only initiates an encrypted TLS session without validating the server certificate or hostname.
sslmode=require parameter enforces encryption in transit but performs zero validation of the CA certificate or server identity, leaving the session open to man-in-the-middle attacks.sslmode=require does not guard against server spoofing or MitM attacks.The requirement were to enforce customer ownership over database storage volume encryption keys at rest rather than securing transport layer identity verification.
The sslmode=verify-ca setting instructs PostgreSQL clients to verify that the server certificate is signed by a trusted Certificate Authority (CA), but it skips verification of the server's hostname against the certificate's Subject Alternative Name (SAN).
The database instance were using a dedicated per-instance CA (where the CA is unique to a single instance) and DNS hostname verification was not required.
Configuring sslmode=verify-full instructs the client to perform strict verification of both the CA signature and the server certificate's Subject Alternative Name (SAN) using the host specified in the connection string.
*.sql.goog.) in its SAN field, rather than private IP addresses.sslmode=verify-full, the hostname validation routine fails because the IP does not match the SAN DNS entry.The server certificate explicitly included the Private Service Connect IP address within the SAN extension attributes.
Server identity verification with TLS ensures that the client not only validates that the database server's certificate was signed by a trusted Certificate Authority (CA), but also validates that the certificate's Subject Alternative Name (SAN) matches the exact hostname to which the client is connecting.
INSTANCE_UID.PROJECT_DNS_LABEL.REGION_NAME.sql.goog.) in the server certificate's SAN field. Registering this name in a VPC private Cloud DNS zone ensures that private clients correctly resolve the DNS name to the PSC endpoint IP.sslmode=verify-full in PostgreSQL client drivers enforces both trusted CA validation and strict SAN hostname matching.This solution properly aligns DNS resolution, certificate SAN metadata, and client TLS enforcement (sslmode=verify-full), providing end-to-end cryptographic trust.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated