Professional-Cloud-Database-Engineer Dumps with Practice Exam Questions Answers

https://cloud.google.com/sql/docs/mysql/backup-recovery/backing-up#locationbackups You can use a custom location for on-demand and automatic backups. For a complete list of valid location values, see the Instance locations.

From Google's documentation, "For stateful resources, such as databases, ensure that deletion protection is enabled. The syntax is: lifecycle { prevent_destroy = true } https://cloud.google.com/docs/terraform/best-practices-for-terraform#stateful-resources

This answer is correct because it meets the requirements of having an optimal and highly available environment with automatic failover. According to the Google Cloud documentation1, a regional Cloud SQL instance is an instance that has a primary server in one zone and a standby server in another zone within the same region. The primary and standby servers are kept in sync using synchronous replication, which ensures zero data loss and minimal downtime in case of a zonal outage or an instance failure. If the primary server becomes unavailable, Cloud SQL automatically fails over to the standby server, which becomes the new primary server1.

It is always more secure to use an internal IP, so removing them doesn’t make sense. Eliminate A. You can use Private Google Access when VM instances only have internal IP addresses, so disabling the internal IPs and use Private Google Access doesn’t make sense. Eliminate B. Specifying an authorized network when they’re on the same subnet doesn’t make sense. Eliminate C. A way to improve network security would be to disable external IPs since they’re not needed.

Start with the lowest tier and smallest size and then grow your instance as needed. Memorystore provides automated scaling using APIs, and optimized node placement across zones for redundancy. Memorystore for Memcached can support clusters as large as 5 TB, enabling millions of QPS at very low latency