Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
Which service is commonly used to store time-series metrics for database performance monitoring in Google Cloud?
Evaluate monitoring options for database performance
0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Terraform modules and infrastructure blueprints for advanced exploration of Google Cloud design. This is supporting engineering material, not an exam course.
Try it: Read one small VPC or service-account module. Draw the resources and permission boundaries it creates, and explain a least-privilege change without deploying an entire landing zone.
Reading the code is free. Deployment requires suitable permissions and can create billable infrastructure.
Official certification paths with exam-specific guides and preparation links for cloud roles.
Try it: Open the guide for your chosen role. For each weak domain, write one service-selection decision you cannot yet explain and find its product documentation.
Public certification information is free; training, labs, and exam registration may be paid.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
Which service is commonly used to store time-series metrics for database performance monitoring in Google Cloud?
Cloud Monitoring
Cloud Logging
Cloud Trace
Cloud Profiler
Correct answer
Cloud Monitoring
Cloud Monitoring collects and graphs time-series metrics such as CPU, memory, and query performance. It provides dashboards and alerting for database health.
What is a primary benefit of using read replicas for a Cloud SQL instance?
Improved read scalability
Automatic backups
Stronger consistency
Reduced storage costs
Correct answer
Improved read scalability
Read replicas allow read traffic to be distributed across copies of the primary instance, improving read throughput. They do not affect backup or consistency guarantees.
Which feature helps ensure high availability for a Cloud Spanner database?
Multi-region configuration
Single-zone deployment
Manual failover
Local SSD storage
Correct answer
Local SSD storage
Multi-region configuration provides redundancy across zones and regions, enabling automatic failover and high availability.
When performing a point-in-time recovery in Cloud SQL, what is the key requirement?
Binary logging enabled
Read replica present
Public IP access
Manual snapshot taken
Correct answer
Binary logging enabled
Point-in-time recovery relies on binary logs (or transaction logs) to restore data to a specific moment. It requires continuous backup settings.
Which practice helps reduce latency for globally distributed applications using Cloud Spanner?
Choosing an optimal multi-region configuration
Using the smallest instance type
Disabling automatic backups
Limiting database schema changes
Correct answer
Choosing an optimal multi-region configuration
Selecting a multi-region configuration close to users minimizes network latency. Instance size and backup settings do not directly affect geographic latency.
What is a common use case for Cloud Memorystore for Redis?
Caching query results
Long-term archival storage
Relational transaction logging
Schema version control
Correct answer
Caching query results
Memorystore for Redis is an in-memory store ideal for caching frequently accessed data such as query results or session information.
Which action should you take before scaling up a Cloud SQL instance?
Review current CPU and memory utilization
Disable all user connections
Export all data to Cloud Storage
Switch to a different database engine
Correct answer
Review current CPU and memory utilization
Analyzing utilization metrics ensures the new instance size matches workload demands. Scaling decisions should be data-driven.
What is a key advantage of using partitioned tables in Cloud Spanner?
Improved query performance for large datasets
Reduced need for indexes
Automatic encryption at rest
Simplified schema design
Correct answer
Improved query performance for large datasets
Partitioning helps manage and query large tables efficiently by dividing data into segments, enhancing performance for specific access patterns.
Which backup strategy applies to both Cloud SQL and Cloud Spanner?
Automated daily backups
Manual snapshot only
On-demand logical backups
File-system level backups
Correct answer
Manual snapshot only
Both services support automated scheduled backups and manual snapshots. Logical backups and file-system backups are not universally supported.
What is a best practice for managing database credentials in Google Cloud?
Use Secret Manager
Store in source code
Share via email
Hardcode in application config
Correct answer
Use Secret Manager
Secret Manager securely stores and manages sensitive data such as database passwords, with controlled access and audit logging.
Which scenario is most suitable for Cloud SQL over Cloud Spanner?
Strong consistency across multiple regions
High transactional throughput at global scale
Simple relational schema with moderate scale
Automatic multi-region failover
Correct answer
Simple relational schema with moderate scale
Cloud SQL is well-suited for relational workloads with moderate scale and simpler operational needs, whereas Spanner targets global scale and strong consistency.
What does enabling automatic backups primarily protect against?
Data loss due to accidental deletion
Network latency issues
Schema migration errors
Application-level bugs
Correct answer
Data loss due to accidental deletion
Automatic backups allow point-in-time recovery, protecting against data loss from mistakes or corruption. They do not address network or application logic issues.
Which tool can help analyze slow queries in a Cloud SQL PostgreSQL instance?
pg_stat_statements
Cloud Trace
Cloud Scheduler
Cloud Build
Correct answer
pg_stat_statements
The pg_stat_statements extension tracks execution statistics of SQL statements, helping identify slow or frequent queries for optimization.
What is a recommended approach for database schema changes in production?
Apply changes during peak traffic
Use migration tools and test in staging
Modify tables directly via console
Disable backups before changes
Correct answer
Use migration tools and test in staging
Schema changes should be tested in non-production environments and applied using migration tools to minimize risk and ensure consistency.
Which feature in Cloud Spanner helps maintain consistency across regions while optimizing for read performance?
Strong reads
Read-only transactions
Leaderless replication
Multi-region configuration
Correct answer
Multi-region configuration
Multi-region configuration in Cloud Spanner allows data to be replicated across multiple regions, ensuring high availability and consistency while optimizing read performance by serving reads from the nearest region.
Recall the answer before opening each card.
Cloud Monitoring collects and graphs time-series metrics like CPU, memory, and query performance for database health dashboards and alerting.
Read replicas improve read scalability by distributing read traffic across multiple copies of the primary instance, enhancing read throughput.
Multi-region configuration provides redundancy across zones and regions, enabling automatic failover and high availability for Cloud Spanner.
Point-in-time recovery requires binary logging (transaction logs) to be enabled, allowing restoration to any specific point in time.
Choosing an optimal multi-region configuration places replicas close to users, minimizing network latency for reads and writes.
Cloud Memorystore for Redis is commonly used as an in-memory cache for frequently accessed data such as query results or session information.
Review current CPU and memory utilization to ensure the new instance size matches workload demands, scaling based on data-driven metrics.
Partitioning improves query performance for large datasets by dividing data into segments, enhancing query efficiency for specific access patterns.
Both services support automated scheduled backups and manual snapshots, protecting against data loss from accidental deletion or corruption.
Use Secret Manager to securely store and manage database passwords with controlled access and audit logging instead of hardcoding credentials.
Cloud SQL is best for simple relational schemas with moderate scale and less demanding consistency or geographic requirements, whereas Spanner targets global scale.
Automatic backups protect against data loss due to accidental deletion, corruption, or other mistakes by enabling point-in-time recovery.
The pg_stat_statements extension tracks execution statistics of SQL statements, helping identify slow or frequent queries for optimization.
Use migration tools and test schema changes in a staging environment before applying to production to minimize risk and ensure consistency.
Multi-region configuration replicates data across regions, serving reads from the nearest region while ensuring strong consistency through synchronized replication.
Current CPU and memory utilization are key metrics to review before scaling, ensuring the new size matches actual workload demand.
Binary logging (transaction logs) must be enabled to support point-in-time recovery, allowing restoration to any specific moment.
Cloud Memorystore for Redis is an in-memory store ideal for caching frequently accessed data such as query results to reduce database load.
Automatic backups enable point-in-time recovery to protect against data loss from accidental deletions, corruption, or other mistakes.
Use Secret Manager to store database passwords with encryption, access control, and audit logging, avoiding hardcoded credentials.
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Choosing the right database service is foundational. Cloud SQL is ideal for moderate-scale relational workloads with simple schemas, while Cloud Spanner is designed for global scale, strong consistency, and high availability across regions. The practice set highlights that multi-region configuration in Spanner reduces latency for distributed applications, whereas read replicas in Cloud SQL improve read scalability. Partitioning in Spanner enhances query performance for large datasets. When evaluating services, consider factors like geographic distribution, consistency requirements, and operational complexity.
Monitoring database performance is critical. Cloud Monitoring collects and graphs time-series metrics like CPU, memory, and query performance, enabling alerts and dashboards. For Cloud SQL PostgreSQL, the pg_stat_statements extension helps analyze slow queries by tracking execution statistics. Scaling decisions should be based on reviewing current CPU and memory utilization rather than guesswork. Caching with Cloud Memorystore for Redis can reduce database load by storing frequently accessed data such as query results.
Backup and recovery strategies safeguard data. Point-in-time recovery in Cloud SQL requires binary logging (or transaction logs) enabled. Both Cloud SQL and Cloud Spanner support automated scheduled backups and manual snapshots, protecting against data loss from accidental deletion. High availability in Cloud Spanner is achieved through multi-region configuration, which provides redundancy across zones and regions. Automatic backups do not prevent application logic errors or network failures but are essential for disaster recovery.
Securing database credentials and managing schema changes are crucial operational practices. Use Secret Manager to store and control access to sensitive information like passwords, with audit logging. For schema changes in production, always use migration tools and test changes in a staging environment to minimize risk. This prevents unintended disruptions and ensures consistency across environments.
Study workflow
Determine the scale, consistency, and geographic distribution needs. For moderate relational workloads with simple schemas, prefer Cloud SQL. For global low-latency reads and strong consistency, use Cloud Spanner. Document required read/write patterns and latency targets.
Enable Cloud Monitoring to collect database metrics like CPU, memory, and query performance. Set up dashboards and alerts for thresholds. For PostgreSQL, install pg_stat_statements to track query execution statistics. Regularly review metrics to identify bottlenecks.
Enable automated scheduled backups for both Cloud SQL and Cloud Spanner. For Cloud SQL, ensure binary logging is enabled to support point-in-time recovery. Perform manual snapshots before major changes. Test recovery procedures periodically.
For Cloud SQL, add read replicas to distribute read traffic. For Cloud Spanner, choose a multi-region configuration to enable automatic failover and low-latency reads. Before scaling up a Cloud SQL instance, review current CPU and memory utilization to select the appropriate size.
Use Secret Manager to store database passwords and other secrets, granting access only to authorized services. For schema changes, use migration tools like Cloud SQL's database migration service or custom scripts, and always test changes in a staging environment before applying to production.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
Cloud SQL is ideal for moderate-scale relational workloads with a simple schema and less demanding consistency or geographic distribution requirements. Cloud Spanner is suited for global scale, strong consistency across regions, and high availability needs.
Point-in-time recovery in Cloud SQL requires binary logging (or transaction logs) to be enabled. This allows restoring data to any specific moment within the backup retention period, protecting against accidental changes or deletions.
Use the pg_stat_statements extension, which tracks execution statistics for SQL statements, including total time, calls, and rows processed. This helps identify slow or frequently executed queries for optimization.
Multi-region configuration replicates data across multiple geographic regions, ensuring high availability with automatic failover and low-latency reads by serving requests from the nearest region. It provides strong consistency globally.
Store database passwords and other secrets in Secret Manager, which provides encryption, access control, and audit logging. Avoid hardcoding credentials in code or configuration files. Grant minimal necessary access to services.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
