Examkin

Question

Difficulty: Very hardDeploying and Configuring Managed Database Instances

A enterprise architecture team is deploying a critical enterprise accounting database to Google Cloud using Cloud SQL for PostgreSQL. Security and compliance policies require the following specifications:
1. The instance must be accessible exclusively via Private IP within the custom Virtual Private Cloud (VPC) named `corp-vpc` and must NOT have a public IP address assigned.
2. The deployment must guarantee high availability across availability zones with automatic failover.
3. Automated backups must execute daily at 03:00 UTC, and Point-in-Time Recovery (PITR) must be explicitly enabled.

Which `gcloud` command correctly provisions this Cloud SQL instance while fully satisfying all security and operational constraints?

  1. gcloud sql instances create acct-db-prod --database-version=POSTGRES_15 --tier=db-custom-4-16384 --region=us-central1 --network=projects/corp-finance-proj/global/networks/corp-vpc --no-assign-ip --availability-type=REGIONAL --backup-start-time=03:00 --enable-point-in-time-recoveryAnswer
  2. B
    gcloud sql instances create acct-db-prod --database-version=POSTGRES_15 --tier=db-custom-4-16384 --region=us-central1 --network=projects/corp-finance-proj/global/networks/corp-vpc --availability-type=REGIONAL --backup-start-time=03:00 --enable-point-in-time-recovery
  3. C
    gcloud sql instances create acct-db-prod --database-version=POSTGRES_15 --tier=db-custom-4-16384 --zone=us-central1-a --network=corp-vpc --no-assign-ip --availability-type=ZONAL --backup-start-time=03:00 --enable-bin-log
  4. D
    gcloud sql instances create acct-db-prod --database-version=POSTGRES_15 --tier=db-custom-4-16384 --region=us-central1 --network=corp-vpc --no-assign-ip --availability-type=REGIONAL --spot --backup-start-time=03:00

Answer

The command specifying `gcloud sql instances create acct-db-prod` with `--no-assign-ip`, `--network=projects/corp-finance-proj/global/networks/corp-vpc`, `--availability-type=REGIONAL`, `--backup-start-time=03:00`, and `--enable-point-in-time-recovery` correctly provisions the instance.
The correct command explicitly satisfies all three security and operational requirements: disabling public IP using `--no-assign-ip` while binding to the private VPC network, providing cross-zone automatic failover with `--availability-type=REGIONAL`, and enabling point-in-time recovery for PostgreSQL via `--enable-point-in-time-recovery`.

Step-by-Step Solution

1
Evaluate IP Connectivity Flags
By default, `gcloud sql instances create` assigns a public IP address unless `--no-assign-ip` is passed alongside `--network`.
Security requirements mandate private IP connectivity only with zero public IP exposure.
2
Evaluate High Availability Configuration
`--availability-type=REGIONAL` provisions a primary instance and a standby replica in a secondary zone within the region.
`--availability-type=ZONAL` creates a single-zone deployment without automatic failover capabilities.
3
Evaluate Backup and PITR Engine-Specific Syntax
For PostgreSQL instances in Cloud SQL, `--enable-point-in-time-recovery` enables Write-Ahead Log (WAL) archiving for recovery to specific timestamps.
`--enable-bin-log` applies exclusively to MySQL instances; using it on PostgreSQL represents a flag error.

Key Concept

Cloud SQL Private IP, High Availability, and Point-in-Time Recovery Deployment Flags
Estimated Time:3m 0s
Rate this question

Topics

Deploying and Configuring Managed Database Instances