Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
What is a primary benefit of using a managed Kubernetes service on Google Cloud?
Evaluate managed services trade-offs
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.
What is a primary benefit of using a managed Kubernetes service on Google Cloud?
Reduced operational overhead for cluster management
Elimination of the need for containerized applications
Automatic scaling of virtual machines without limits
Guaranteed lower costs compared to self-managed Kubernetes
Correct answer
Reduced operational overhead for cluster management
Managed Kubernetes services handle control plane upgrades and maintenance, reducing operational tasks. Users still manage nodes and applications, and costs depend on usage.
Which practice helps ensure that infrastructure changes are repeatable and traceable?
Infrastructure as Code
Manual configuration via the console
Ad-hoc command-line operations
Periodic documentation updates
Correct answer
Infrastructure as Code
Infrastructure as Code uses code to define and manage infrastructure, enabling version control and consistent deployments. Manual and ad-hoc methods are error-prone and hard to audit.
When designing a multi-region deployment, what should you consider for data residency?
Storing data in regions that comply with local laws
Using the cheapest available region regardless of location
Placing all data in a single region for simplicity
Ignoring latency for global applications
Correct answer
Storing data in regions that comply with local laws
Data residency requirements dictate where data can be stored based on legal and regulatory constraints. Designing regions around these needs ensures compliance and user trust.
What is a common use case for Cloud Pub/Sub in event-driven architectures?
Decoupling event producers from consumers
Storing large binary files permanently
Replacing relational databases for transactions
Providing low-latency interactive queries
Correct answer
Decoupling event producers from consumers
Cloud Pub/Sub enables asynchronous messaging, allowing producers and consumers to operate independently and scale separately. It is not a storage or transactional database system.
Which factor most influences the choice between regional and multi-regional storage classes?
Data access patterns and latency requirements
The color of the storage bucket name
The number of objects stored
The default region of the project
Correct answer
Data access patterns and latency requirements
Regional storage offers lower latency within a single region, while multi-regional storage provides broader geographic access. Choose based on where and how often data is accessed.
What is a key security practice for managing service accounts?
Granting the minimum required permissions
Using service accounts for all interactive users
Sharing service account keys across teams
Assigning broad roles to simplify management
Correct answer
Granting the minimum required permissions
Principle of least privilege reduces risk by granting only necessary permissions. Service accounts should not be shared, and broad roles increase security exposure.
Which tool is best suited for tracking configuration changes to Google Cloud resources over time?
Cloud Audit Logs
Cloud Monitoring dashboards
Cloud Storage lifecycle rules
Cloud CDN cache settings
Correct answer
Cloud Audit Logs
Cloud Audit Logs records administrative and data access activities, providing a history of configuration changes. Monitoring dashboards visualize metrics but do not track configuration history.
What is a benefit of using Cloud Functions for application logic?
Automatic scaling in response to events
Running long-lived persistent connections
Hosting static websites without any configuration
Replacing all virtual machines in an architecture
Correct answer
Automatic scaling in response to events
Cloud Functions automatically scales to handle event-driven workloads and charges based on execution time. It is not ideal for persistent connections or replacing all VMs.
Which network component helps restrict inbound traffic to specific ports and sources?
Firewall rules
Cloud VPN tunnels
Cloud Interconnect settings
Route tables in VPC
Correct answer
Firewall rules
Firewall rules define allowed and denied traffic based on protocols, ports, and source IP ranges. They are essential for network security and segmentation.
What is a recommended approach for handling application secrets in Google Cloud?
Using Secret Manager to store and access sensitive data
Hardcoding secrets in application source code
Storing secrets in publicly accessible Cloud Storage buckets
Sending secrets via email to team members
Correct answer
Using Secret Manager to store and access sensitive data
Secret Manager provides secure storage and fine-grained access control for sensitive data such as API keys and passwords. Hardcoding or exposing secrets increases risk.
Which scenario is most suitable for using a managed instance group?
Running identical application instances that require scaling
Hosting a single database with strict consistency needs
Performing one-time data processing jobs
Storing archival backups with infrequent access
Correct answer
Running identical application instances that require scaling
Managed instance groups automate scaling and health checks for identical virtual machines. They are ideal for stateless, scalable workloads, not for unique or archival tasks.
What is a primary advantage of using a load balancer in front of backend services?
Distributing traffic across multiple backends for availability
Reducing the number of required backend instances to zero
Eliminating the need for secure backend communication
Ensuring all requests are served from the nearest region
Correct answer
Distributing traffic across multiple backends for availability
Load balancers improve availability and responsiveness by spreading traffic and performing health checks. They do not remove the need for backend instances or secure communication.
Which practice helps prevent cost overruns in Google Cloud projects?
Setting budgets and alerts for resource usage
Using the largest instance types by default
Disabling all monitoring to reduce log costs
Deploying all resources in the most expensive region
Correct answer
Setting budgets and alerts for resource usage
Budgets and alerts notify you of unexpected usage and help control spending. Oversized instances and expensive regions increase costs unnecessarily.
What is a key consideration when planning a disaster recovery strategy?
Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
Choosing the most expensive storage class for backups
Using a single region for all backup copies
Ignoring testing of recovery procedures
Correct answer
Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
RTO and RPO define acceptable downtime and data loss thresholds, guiding the design of effective disaster recovery. Testing and diversified backups are essential for reliability.
Which Google Cloud service provides a fully managed solution for running stateful workloads with strong consistency and high availability?
Cloud Run
Cloud Spanner
Cloud Functions
Cloud Pub/Sub
Correct answer
Cloud Spanner
Cloud Spanner is a fully managed, horizontally scalable, and strongly consistent database service designed for stateful workloads requiring high availability and global distribution.
Recall the answer before opening each card.
Reduced operational overhead because the control plane upgrades and maintenance are handled by the service, freeing users from cluster management tasks.
Infrastructure as Code, which uses version-controlled code to define and manage infrastructure, enabling consistent deployments and auditing.
Store data in regions that comply with local legal and regulatory requirements to ensure user trust and legal compliance.
Decoupling event producers from consumers through asynchronous messaging, allowing independent scaling and operation.
Data access patterns and latency requirements—regional for low latency within a region, multi-regional for broader geographic access.
Grant the minimum required permissions (least privilege) to reduce risk from compromised or misused accounts.
Cloud Audit Logs, which record administrative and data access activities, providing a historical record of changes.
Automatic scaling in response to events, with billing based on execution time, suitable for event-driven workloads.
Firewall rules that define allowed/dented traffic based on protocol, port, and source IP ranges.
Use Secret Manager for secure storage, access control, and avoiding hardcoding secrets in code or configuration.
For running identical application instances that require automated scaling and health checks, typical for stateless workloads.
Distributing traffic across multiple backends and performing health checks to improve availability and responsiveness.
Set budgets and alerts for resource usage to notify of unexpected spending and control costs proactively.
Recovery Time Objective (RTO) and Recovery Point Objective (RPO) that define acceptable downtime and data loss.
Cloud Spanner, designed for high availability and horizontal scalability with strong consistency.
Users remain responsible for managing nodes and applications, including patching and scaling nodes.
Manual changes are error-prone and hard to audit, lacking repeatability and traceability compared to Infrastructure as Code.
Producers and consumers can operate independently and scale separately, improving decoupling and resilience.
Regional storage offers lower latency for users within the same region, while multi-regional may have higher latency but broader geographic redundancy.
Following the principle of least privilege and using centralized secret management minimizes security exposure and reduces risk.
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.
This section covers decisions around managed Kubernetes, Cloud Functions, and managed instance groups. Key considerations include whether to use a fully managed Kubernetes service (reducing operational overhead) versus self-managed, and when to use serverless functions versus managed VMs. The practice bank reinforces that managed Kubernetes still requires user node management, Cloud Functions automatically scales for event-driven workloads, and managed instance groups are ideal for stateless, identical application instances.
This section focuses on service account security, network traffic control, and secret management. The practice bank emphasizes granting minimum permissions (least privilege), using firewall rules to restrict inbound traffic, and storing sensitive data like API keys in Secret Manager. These practices enforce access boundaries and protect against unauthorized exposure. Key decisions involve choosing appropriate roles and avoiding hardcoded or overly permissive configurations.
This section covers load balancing, Cloud Pub/Sub, and Cloud Audit Logs. Load balancers distribute traffic to improve availability and responsiveness, while Cloud Pub/Sub decouples event producers and consumers for resilient architectures. Cloud Audit Logs provides a history of configuration changes, supporting auditing and troubleshooting. The practice bank illustrates that these services work together to create scalable, observable, and highly available systems.
This section addresses data residency compliance, storage class selection, disaster recovery planning, and fully managed stateful databases. The practice bank shows how to align storage choices with access patterns and latency needs, and how to define RTO/RPO for disaster recovery. It also highlights Cloud Spanner as a service for strongly consistent, globally distributed stateful workloads. These decisions directly affect cost, performance, and business continuity.
Study workflow
Evaluate workload requirements: if you want to reduce control plane management tasks, choose managed Kubernetes; for event-driven, short-lived logic, use Cloud Functions; for identical stateless VMs that auto-scale, use managed instance groups. Avoid managed services for workloads needing custom configurations or persistent connections.
Identify the minimum permissions required for each service account to perform its tasks. Use predefined roles that align with job functions. Avoid granting broad roles like Owner or Editor. Regularly review and audit permissions using IAM Recommender to remove unused privileges.
Analyze data access frequency and geographic distribution. For low-latency access within a single region, use regional storage. For data accessed globally or requiring geo-redundancy, use multi-regional storage. Consider lifecycle policies to transition data to colder classes for cost savings.
Define Recovery Time Objective (maximum acceptable downtime) and Recovery Point Objective (maximum acceptable data loss). Choose a strategy (e.g., backup, standby, multi-region) that meets these targets. Regularly test failover procedures and document recovery steps.
Create budgets at the project or billing account level to monitor spending. Set alert thresholds (e.g., 50%, 90%, 100%) to notify via email or Pub/Sub when usage exceeds predictions. Review budget reports regularly and adjust resource sizes or use committed use discounts to optimize costs.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
Regional storage replicates data within a single region, offering lower latency for users in that region. Multi-regional storage replicates across multiple regions, providing broader geographic access and higher durability. Choose based on where your users are and latency requirements.
Use Cloud Pub/Sub when you need to decouple event producers from consumers for resilience and independent scaling. It is ideal for asynchronous workloads, such as order processing or log streaming, where immediate response is not required. Direct HTTP calls suit synchronous request-reply patterns.
Avoid creating long-lived keys when possible; use workload identity federation or attach service accounts to resources. If keys are necessary, rotate them regularly, restrict usage with conditions, and store them in Secret Manager. Monitor key usage with Cloud Audit Logs.
Recovery Time Objective (RTO) defines the maximum acceptable downtime after a disaster. Recovery Point Objective (RPO) defines the maximum acceptable data loss measured in time. Together they guide the selection and configuration of backup, replication, and failover strategies.
Consider data residency constraints and choose regions that comply with laws. Use Cloud Spanner or Cloud Bigtable for globally distributed data. Implement load balancing across regions and use Cloud CDN for static content. Plan for failover and test disaster recovery procedures regularly.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
