Soru

Zorluk: OrtaDeploying and Configuring Managed Database Instances

A database administrator needs to update an existing Cloud SQL for MySQL instance named `prod-mysql-db` to enable automated daily backups with a start time of 03:00 UTC and to enable point-in-time recovery (PITR). Which TWO `gcloud sql instances patch` command flags must be specified to meet these operational requirements?

  1. --backup-start-time=03:00Cevap
  2. --enable-bin-logCevap
  3. C
    --enable-point-in-time-recovery
  4. D
    --no-assign-ip

Cevap

To configure automated backups and point-in-time recovery on a Cloud SQL for MySQL database, specify `--backup-start-time=03:00` to establish the daily backup start time window and `--enable-bin-log` to turn on binary logging.
For Cloud SQL for MySQL instances, automated daily backups are configured using the `--backup-start-time` flag in `HH:MM` format. Point-in-time recovery for MySQL requires binary logging to be enabled using the `--enable-bin-log` flag.

Adım Adım Çözüm

1
Identify the database engine type
The target instance uses MySQL (`prod-mysql-db`).
Different database engines in Cloud SQL utilize distinct mechanisms and flags for point-in-time recovery.
2
Select the flag for automated backup scheduling
Use `--backup-start-time=03:00`.
This configures the start of the 4-hour window during which automated daily backups occur.
3
Select the flag required for point-in-time recovery on MySQL
Use `--enable-bin-log`.
Point-in-time recovery for Cloud SQL for MySQL relies on binary logs to replay transactions after restoring from a base backup.

Anahtar Kavram

Cloud SQL for MySQL backup and binary logging configuration via gcloud CLI
Bu soruyu puanla