Courseiva

CCNA Fundamental Cloud Concepts Questions

75 of 98 questions · Page 1/2 · Fundamental Cloud Concepts topic · Answers revealed

Practice these questionsExam hubAll questions
1
MCQmedium

What is horizontal scaling, and how does it differ from vertical scaling?

A.Horizontal scaling adds CPU/memory to existing servers; vertical scaling adds more servers.
B.Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances.
C.Horizontal scaling is for databases only; vertical scaling is for web servers.
D.Horizontal scaling requires application downtime; vertical scaling is always online.
AnswerB

Horizontal: add more VMs/containers (scale out). Vertical: upgrade to a larger VM with more CPU/RAM (scale up). Cloud autoscaling is primarily horizontal.

Why this answer

Horizontal scaling (scale-out) adds more instances (e.g., additional virtual machines or containers) to distribute the workload across multiple nodes, improving fault tolerance and capacity. Vertical scaling (scale-up) increases the resources (CPU, RAM, storage) of an existing instance, often hitting hardware limits and requiring downtime. Option B correctly captures this distinction.

Exam trap

Cisco often tests the common misconception that horizontal scaling means adding resources to a single server (like upgrading RAM), when in fact it means adding more servers to share the load.

How to eliminate wrong answers

Option A is wrong because it reverses the definitions: horizontal scaling adds more servers, not CPU/memory to existing servers, while vertical scaling adds resources to a single server. Option C is wrong because horizontal and vertical scaling apply to all types of workloads (databases, web servers, etc.), not exclusively to one or the other. Option D is wrong because horizontal scaling typically requires no downtime (instances can be added or removed live), while vertical scaling often requires a reboot or downtime to resize the instance.

Practice this question →
2
MCQeasy

A startup needs to run a web application with unpredictable traffic. They want to avoid over-provisioning and only pay for resources used. Which cloud benefit best addresses this need?

A.Built-in security
B.Pay-as-you-go pricing
C.Global reach and low latency
D.Managed services
AnswerB

Pay-as-you-go allows paying only for what you use, ideal for unpredictable traffic.

Why this answer

Pay-as-you-go pricing (Option B) directly matches the startup's need to avoid over-provisioning and pay only for resources consumed. This cloud pricing model allows resources to scale up and down automatically based on traffic, with billing tied to actual usage (e.g., compute hours, data transfer). It eliminates the capital expense of idle capacity, which is critical for unpredictable workloads.

Exam trap

Google Cloud often tests the misconception that 'managed services' automatically include pay-as-you-go pricing, but managed services (e.g., Amazon RDS) still require selecting a pricing model (on-demand vs. reserved) and do not guarantee avoidance of over-provisioning.

How to eliminate wrong answers

Option A is wrong because built-in security addresses data protection and compliance, not cost optimization or resource scaling based on demand. Option C is wrong because global reach and low latency improve user experience via edge locations (e.g., CDN), but do not affect how the startup pays for or provisions compute resources. Option D is wrong because managed services reduce operational overhead (e.g., patching, backups) but still require selecting a pricing model; they do not inherently prevent over-provisioning or ensure pay-per-use billing.

Practice this question →
3
MCQmedium

A company plans to run a batch processing job every night for 2 hours. They want to minimize costs while ensuring the job completes within a 4-hour window. Which pricing model should they choose?

A.On-demand pricing
B.Preemptible VM instances
C.Committed use discounts
D.Sustained use discounts
AnswerB

Preemptible VMs cost significantly less and are suitable for fault-tolerant batch jobs.

Why this answer

Preemptible VM instances (B) are ideal for fault-tolerant, short-lived batch jobs that can handle interruptions. They offer significantly lower cost than on-demand instances, and because the job runs for only 2 hours within a 4-hour window, it can be restarted if preempted, ensuring completion at minimal expense.

Exam trap

Google Cloud often tests the misconception that sustained use discounts are the best for any long-running workload, but the trap here is that the 2-hour nightly job does not accumulate enough monthly usage to trigger significant sustained use discounts, making preemptible VMs the correct cost-minimizing choice for interruptible batch jobs.

How to eliminate wrong answers

Option A is wrong because on-demand pricing is the most expensive option and does not offer cost optimization for a batch job that can tolerate interruptions. Option C is wrong because committed use discounts require a 1- or 3-year commitment, which is excessive for a nightly 2-hour job and does not align with the flexible, short-duration nature of the workload. Option D is wrong because sustained use discounts apply automatically to on-demand instances running for a significant portion of a month (e.g., over 25%), but a 2-hour nightly job totals only about 60 hours per month, which is well below the threshold for meaningful discounts.

Practice this question →
4
MCQeasy

A company's application is called 'stateless' because it doesn't store any user session data in the application server's memory. Each request contains all necessary information. Why is statelessness important for cloud scalability?

A.Stateless applications use less storage because they don't store any data.
B.Stateless applications can be scaled horizontally without session loss because any instance can handle any request — enabling easy addition/removal of instances.
C.Stateless applications are more secure because they don't remember who the user is.
D.Stateless applications eliminate the need for databases since no data is stored.
AnswerB

No local session state means any server can handle any user's request. Add an instance and it's immediately useful; remove one and no user loses their session. This is the foundation of horizontal cloud scalability.

Why this answer

Statelessness is critical for cloud scalability because it enables horizontal scaling: any instance can process any request without needing to recall previous interactions. Since no session data is stored locally, new instances can be added or removed dynamically without risk of session loss, allowing the application to handle fluctuating loads efficiently. This aligns with the cloud's elasticity model, where resources are provisioned on demand.

Exam trap

Cisco often tests the misconception that statelessness means 'no data is stored anywhere,' leading candidates to pick Option D, but the correct understanding is that data is stored externally, not on the application server itself.

How to eliminate wrong answers

Option A is wrong because stateless applications don't necessarily use less storage; they still store data externally (e.g., in databases or caches), and the claim conflates memory usage with storage. Option C is wrong because statelessness does not inherently improve security; it simply means no session state is kept on the server, but authentication tokens (e.g., JWT) are still sent with each request and can be compromised. Option D is wrong because stateless applications still require databases or external storage for persistent data; eliminating databases would break data durability and consistency.

Practice this question →
5
MCQeasy

Google Cloud bills Compute Engine VMs per second (after a 1-minute minimum). A batch job runs for exactly 3 minutes and 47 seconds. How many minutes does Google Cloud charge for?

A.4 minutes (rounded up to the nearest minute).
B.Exactly 3 minutes and 47 seconds of compute time.
C.1 hour (traditional cloud billing minimum).
D.5 minutes (rounded up to the nearest 5-minute interval).
AnswerB

Per-second billing means the charge is for exactly 227 seconds (3 min 47 sec). No per-hour or per-minute rounding inflates the cost.

Why this answer

Google Cloud Compute Engine bills per second after a 1-minute minimum. Since the job runs for 3 minutes and 47 seconds, the total billable time is exactly 3 minutes and 47 seconds — no rounding up to the nearest minute or any other interval. Option B correctly reflects this per-second billing model.

Exam trap

Google Cloud often tests the misconception that cloud providers always round up to the nearest minute or hour, but Google Cloud's per-second billing after a 1-minute minimum is a specific exception that candidates must recall precisely.

How to eliminate wrong answers

Option A is wrong because it assumes rounding up to the nearest minute, but Google Cloud bills per second after the first minute, so 3 minutes and 47 seconds is not rounded to 4 minutes. Option C is wrong because it references a traditional 1-hour minimum billing model, which Google Cloud does not use for Compute Engine VMs — they use a 1-minute minimum with per-second billing thereafter. Option D is wrong because it suggests rounding to the nearest 5-minute interval, which is not part of Google Cloud's billing policy for Compute Engine.

Practice this question →
6
MCQeasy

A small business wants to host a low-traffic website with a single-page application. They have limited budget and no IT staff. Which Google Cloud solution is most cost-effective and easy to manage?

A.Use App Engine Standard Environment
B.Deploy a virtual machine on Compute Engine with a web server
C.Host the static files on Cloud Storage and use Cloud CDN
D.Set up Google Kubernetes Engine cluster
AnswerC

Cloud Storage can host static websites with built-in CDN and no server management.

Why this answer

Option C is correct because hosting static files (HTML, CSS, JS) on Cloud Storage with Cloud CDN provides a serverless, highly scalable, and low-cost solution for a low-traffic single-page application. Cloud Storage serves static content directly without provisioning any virtual machines, and Cloud CDN caches content at edge locations to reduce latency and egress costs. This eliminates the need for any server management, making it ideal for a business with no IT staff.

Exam trap

The trap here is that candidates often assume a web server (Compute Engine) or a platform like App Engine is necessary for any website, overlooking that static hosting on Cloud Storage with CDN is the simplest and cheapest option for single-page applications.

How to eliminate wrong answers

Option A is wrong because App Engine Standard Environment, while serverless, is designed for dynamic applications and incurs costs for always-on instances or scaling, even for low-traffic static sites, making it less cost-effective than pure static hosting. Option B is wrong because deploying a virtual machine on Compute Engine requires manual OS patching, web server configuration, and ongoing maintenance, which contradicts the 'no IT staff' requirement and introduces unnecessary complexity and cost for a static site. Option D is wrong because Google Kubernetes Engine is an orchestration platform for containerized applications, which is overkill and expensive for a simple static website, requiring cluster management and expertise that the business lacks.

Practice this question →
7
MCQmedium

A company wants to ensure that no employee can accidentally delete critical data stored in Cloud Storage. They need a solution that protects against accidental deletion even by users with full permissions. Which approach should they use?

A.Enable Object Versioning and set a retention policy
B.Use customer-managed encryption keys
C.Set up Cloud Audit Logs for data access
D.Restrict IAM roles to Viewer only
AnswerA

Versioning keeps deleted objects, and retention policies prevent deletion within a set period.

Why this answer

Object Versioning in Cloud Storage preserves non-current object versions, allowing recovery from accidental overwrites or deletions. A retention policy prevents object deletion (including version deletion) until the retention period expires, even for users with full permissions like `storage.objects.delete`. Together, they provide a defense-in-depth against accidental data loss.

Exam trap

Google Cloud often tests the misconception that IAM roles alone can prevent deletion, but the trap here is that users with full permissions (e.g., `roles/storage.admin`) can delete objects unless a retention policy is applied, which overrides IAM at the bucket level.

How to eliminate wrong answers

Option B is wrong because customer-managed encryption keys (CMEK) protect data at rest but do not prevent deletion; they only control who can decrypt the data. Option C is wrong because Cloud Audit Logs record who performed a deletion but do not prevent it from happening. Option D is wrong because restricting IAM roles to Viewer only would block legitimate users from performing their jobs and does not address the requirement to protect against accidental deletion by users with full permissions.

Practice this question →
8
MCQeasy

An organization is planning to adopt cloud services but needs to understand which party is responsible for physical security of the data center. Under the shared responsibility model, who is responsible for physical data center security in a public cloud deployment?

A.The customer, because they own the data stored in the data center
B.A shared responsibility: the cloud provider secures the building exterior while the customer secures the server racks
C.The cloud provider, who is entirely responsible for all physical security of data center facilities and hardware
D.A third-party security company contracted by both the customer and the cloud provider
AnswerC

Physical security is always the cloud provider's responsibility. This includes facility perimeter security, building access controls, environmental controls, and hardware security. It is one of the most clear-cut divisions in the shared responsibility model.

Why this answer

In the cloud shared responsibility model, physical security of data centers — including building access controls, perimeter security, surveillance, and hardware security — is always the sole responsibility of the cloud provider. Customers never have physical access to cloud provider data centers and bear no responsibility for physical security. This is one of the fundamental security benefits of using a public cloud.

Practice this question →
9
MCQhard

A company wants to reduce latency for IoT devices located in remote areas with poor connectivity. They need to preprocess data locally before sending it to the cloud. Which architecture should they use?

A.Deploy Cloud CDN to cache responses.
B.Use edge computing devices that run Cloud IoT Edge and preprocess data.
C.Use Cloud IoT Core with MQTT and process data on the server side.
D.Use a VPN to connect devices directly to the cloud.
AnswerB

Edge computing processes data locally and sends only necessary data to the cloud.

Why this answer

Option B is correct because edge computing devices running Cloud IoT Edge allow local preprocessing of data, reducing the volume of data transmitted over poor connectivity links. This architecture minimizes latency by processing data closer to the source, which is critical for IoT devices in remote areas. Cloud IoT Edge extends Google Cloud's data processing capabilities to the edge, enabling real-time insights without constant cloud connectivity.

Exam trap

The trap here is that candidates often confuse edge computing with CDN caching, thinking both reduce latency similarly, but CDN caches responses for repeated requests while edge computing processes data locally to reduce transmission volume.

How to eliminate wrong answers

Option A is wrong because Cloud CDN caches static content at edge locations to reduce latency for web content delivery, but it does not preprocess IoT device data or address local data reduction before cloud transmission. Option C is wrong because Cloud IoT Core with MQTT handles device connectivity and server-side processing, but it still requires sending raw data over the network, which does not reduce latency or bandwidth usage in poor connectivity scenarios. Option D is wrong because a VPN secures the connection but does not preprocess data locally; it still requires all data to traverse the network to the cloud, which is inefficient with poor connectivity.

Practice this question →
10
MCQhard

A cloud architect is explaining to executives why they should use managed services (like Cloud SQL, Memorystore, Pub/Sub) instead of running self-managed equivalents on VMs (PostgreSQL on VM, Redis on VM, RabbitMQ on VM). Which argument best captures the strategic rationale for preferring managed services?

A.Managed services are always less expensive than self-managed alternatives on VMs
B.Managed services transfer undifferentiated operational complexity (patching, backups, HA, scaling) to Google, freeing engineering teams to focus on differentiated business logic rather than infrastructure management
C.Managed services guarantee better performance than self-managed deployments in all scenarios
D.Using managed services eliminates the need for any cloud expertise within the engineering team
AnswerB

This is the strategic argument. 'Undifferentiated heavy lifting' — the operational work common to every company running that software — is what managed services absorb. No company's competitive advantage comes from being better at PostgreSQL patch management; it comes from the applications and insights built on top of databases. Managed services free teams for that differentiated work.

Why this answer

Option B correctly captures the strategic rationale because managed services like Cloud SQL, Memorystore, and Pub/Sub offload undifferentiated heavy lifting—such as automated patching, backup management, high-availability failover, and horizontal scaling—to Google Cloud. This allows engineering teams to focus on building and improving application-specific features rather than spending time on infrastructure tasks that do not provide competitive advantage.

Exam trap

Google Cloud often tests the misconception that managed services are universally cheaper or better performing, when in reality the strategic value lies in reducing operational overhead and allowing teams to focus on business-differentiating work, not in cost or raw performance guarantees.

How to eliminate wrong answers

Option A is wrong because managed services are not always less expensive; they often have higher per-unit costs than self-managed VMs, especially at high sustained usage, due to the premium for operational convenience and built-in features. Option C is wrong because managed services do not guarantee better performance in all scenarios; for example, a self-managed PostgreSQL on a dedicated VM with tuned kernel parameters can outperform a shared Cloud SQL instance under certain workloads. Option D is wrong because using managed services does not eliminate the need for cloud expertise; engineers still need to understand networking, IAM, cost optimization, and service-specific configurations to use them effectively.

Practice this question →
11
Matchingmedium

Match each Google Cloud pricing concept to its definition.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Automatic discounts for running instances most of the month

Discounts for committing to 1 or 3 years of usage

Short-lived, low-cost instances for batch jobs

Limited free usage of selected GCP services

Committed Use Discounts (abbreviation)

Why these pairings

These are key pricing models in Google Cloud.

Practice this question →
12
MCQmedium

A startup is building a web application and wants to avoid managing servers or operating systems. They need to deploy code quickly and scale automatically. Which cloud service model best meets these requirements?

A.Function as a Service (FaaS)
B.Software as a Service (SaaS)
C.Platform as a Service (PaaS)
D.Infrastructure as a Service (IaaS)
AnswerC

PaaS provides a managed platform for deploying code without server management.

Why this answer

Platform as a Service (PaaS) is the correct choice because it abstracts the underlying infrastructure (servers, OS, storage) while providing a managed platform for deploying and scaling web applications. The startup can focus on writing code and pushing updates without managing operating systems or servers, and PaaS platforms like Google App Engine or AWS Elastic Beanstalk offer automatic scaling based on demand.

Exam trap

Google Cloud often tests the distinction between PaaS and FaaS by making candidates think that FaaS (serverless) is the only way to avoid managing servers, but PaaS also abstracts servers while supporting full web applications with persistent state and longer execution times.

How to eliminate wrong answers

Option A is wrong because Function as a Service (FaaS) is designed for event-driven, stateless functions that run in short bursts, not for deploying a full web application that requires persistent state or long-running processes. Option B is wrong because Software as a Service (SaaS) delivers ready-to-use applications to end users, not a platform for the startup to deploy and manage their own code. Option D is wrong because Infrastructure as a Service (IaaS) provides virtualized servers, storage, and networking, which still requires the startup to manage operating systems, patches, and scaling manually, contradicting the requirement to avoid managing servers or OS.

Practice this question →
13
MCQmedium

An organization wants to modernize its on-premises applications. The IT team identifies three types of applications: legacy apps that can only move with significant refactoring, custom-built apps that can be containerized and moved as-is, and applications that can be replaced entirely by SaaS solutions. This categorization approach is called what?

A.Disaster recovery planning
B.Application portfolio assessment using migration strategies (the 6 Rs framework)
C.Capacity planning for on-premises servers
D.Software development lifecycle (SDLC) planning
AnswerB

The 6 Rs framework (Rehost, Replatform, Refactor, Repurchase, Retire, Retain) categorizes each application by its appropriate migration approach — the standard framework for cloud migration planning.

Why this answer

The scenario describes categorizing applications based on their migration path: legacy apps requiring refactoring, custom apps suitable for containerization, and apps replaceable by SaaS. This directly aligns with the '6 Rs' framework (Rehost, Replatform, Refactor, Repurchase, Retire, Retain) used in application portfolio assessment for cloud migration. Option B is correct because the 6 Rs provide a structured way to evaluate and classify each application's optimal migration strategy.

Exam trap

Cisco often tests the 6 Rs framework by describing a specific migration scenario and asking for the correct 'R' term; the trap here is confusing 'application portfolio assessment' with generic IT planning terms like capacity planning or SDLC, which are unrelated to migration strategy categorization.

How to eliminate wrong answers

Option A is wrong because disaster recovery planning focuses on backup, failover, and business continuity after migration, not on categorizing applications by their migration approach. Option C is wrong because capacity planning deals with sizing compute, storage, and network resources for on-premises servers, not with classifying applications into migration strategies like refactoring or SaaS replacement. Option D is wrong because SDLC planning covers the phases of software development (requirements, design, coding, testing, deployment), not the categorization of existing applications for cloud migration.

Practice this question →
14
MCQeasy

A software team is using Google Cloud and wants to understand the difference between 'scaling up' (vertical scaling) and 'scaling out' (horizontal scaling) for their web application. Which description correctly distinguishes these two approaches?

A.Scaling up adds more servers to handle increased load; scaling out makes each server more powerful by adding CPU and RAM
B.Vertical scaling (scaling up) increases the resources of an individual server (more CPU, RAM), while horizontal scaling (scaling out) adds more servers to distribute load — horizontal scaling is generally preferred in cloud environments for its flexibility and lack of a ceiling
C.Both scaling up and scaling out describe the same approach — adding more cloud resources to handle increased demand
D.Scaling up is only possible in cloud environments; on-premises systems can only scale out
AnswerB

This correctly defines both approaches and notes the cloud preference for horizontal scaling. Cloud autoscaling is built on horizontal scale — adding identical instances behind a load balancer. Vertical scaling is limited by maximum available machine sizes and often requires downtime for resize.

Why this answer

Option B correctly distinguishes vertical scaling (scaling up) as increasing the resources (CPU, RAM) of an existing server, and horizontal scaling (scaling out) as adding more servers to distribute the load. In cloud environments like Google Cloud, horizontal scaling is generally preferred because it offers near-infinite scalability, better fault tolerance, and no single point of failure, unlike vertical scaling which has a hardware ceiling and can cause downtime during upgrades.

Exam trap

Google Cloud often tests the reversal of definitions—candidates mistakenly think 'scaling up' means adding more servers because 'up' sounds like 'more,' but the correct distinction is that 'up' refers to increasing the power of a single server, while 'out' refers to adding more servers.

How to eliminate wrong answers

Option A is wrong because it reverses the definitions: scaling up increases server resources, not adds more servers, and scaling out adds more servers, not makes a single server more powerful. Option C is wrong because scaling up and scaling out are fundamentally different approaches—vertical scaling increases capacity of a single node, while horizontal scaling distributes load across multiple nodes. Option D is wrong because scaling up is possible in both cloud and on-premises environments (e.g., adding RAM to a physical server), and on-premises systems can also scale out by adding more physical servers; the statement is factually incorrect.

Practice this question →
15
MCQeasy

A company wants to use computing resources over the internet without managing physical servers. The cloud provider manages the underlying hardware and virtualization, while the company manages the operating system, middleware, and applications. Which cloud service model does this describe?

A.Software as a Service (SaaS)
B.Infrastructure as a Service (IaaS)
C.Platform as a Service (PaaS)
D.Function as a Service (FaaS)
AnswerB

IaaS provides virtualized compute, storage, and networking. The provider manages physical infrastructure; the customer manages OS, middleware, and applications. Compute Engine is Google's IaaS offering.

Why this answer

This scenario describes Infrastructure as a Service (IaaS) because the cloud provider manages the physical hardware and virtualization layer, while the customer retains control over the operating system, middleware, and applications. In IaaS, the provider offers virtualized computing resources (e.g., virtual machines, storage, networks) via APIs or dashboards, and the customer is responsible for OS patches, application configuration, and middleware management. This matches the given split of responsibilities exactly.

Exam trap

Cisco often tests the distinction between IaaS and PaaS by describing a scenario where the customer manages the OS — many candidates mistakenly choose PaaS because they associate 'platform' with application deployment, but PaaS removes OS management from the customer entirely.

How to eliminate wrong answers

Option A is wrong because Software as a Service (SaaS) delivers fully managed applications to end users, where the provider handles everything including the OS, middleware, and application code — the customer only configures usage settings, not the underlying stack. Option C is wrong because Platform as a Service (PaaS) provides a managed runtime environment where the provider handles the OS and middleware, and the customer only deploys and manages their own application code — the customer does not manage the OS or middleware. Option D is wrong because Function as a Service (FaaS) is a serverless compute model where the provider manages all infrastructure, including the OS and runtime, and the customer only uploads individual functions that execute in stateless containers — the customer has no control over the OS or middleware.

Practice this question →
16
MCQeasy

A retail company experiences heavy traffic during holiday sales and low traffic at other times. Which cloud computing characteristic is most beneficial for handling this variable workload?

A.Broad network access
B.High availability
C.Elasticity
D.Pay-as-you-go pricing
AnswerC

Elasticity automatically adjusts resources to match workload changes.

Why this answer

Option A is correct because elasticity allows resources to scale up and down automatically based on demand. Option B is wrong because pay-as-you-go is a pricing model, not a scaling characteristic. Option C is wrong because high availability focuses on uptime, not scaling.

Option D is wrong because broad network access is about accessibility via the internet.

Practice this question →
17
MCQhard

An architect is evaluating trade-offs between using Google Cloud's global network backbone for application traffic versus routing traffic over the public internet. She notes that Google's global network is one of the largest private networks in the world. What is the primary performance advantage of routing application traffic over Google's private backbone?

A.Google's private backbone uses faster optical fiber than public internet service providers
B.Traffic on Google's private backbone avoids public internet congestion and variable routing, providing consistently lower latency and higher throughput for traffic between regions and to users near Google PoPs
C.Google's private backbone is free for customers while public internet egress incurs data transfer charges
D.Using Google's backbone eliminates the need for application-level TLS encryption because the network is inherently secure
AnswerB

This correctly identifies the advantage. Public internet traffic traverses multiple autonomous systems with variable congestion. Google's backbone provides a direct, high-quality path between regions. Applications using Cloud CDN or global load balancers benefit from traffic entering Google's network early and staying on the backbone.

Why this answer

Option B is correct because Google's private backbone is a dedicated, software-defined network that uses Google's own fiber infrastructure and BGP routing policies to keep traffic entirely within Google's controlled environment. This avoids the unpredictable congestion, packet loss, and variable routing paths of the public internet, resulting in consistently lower latency and higher throughput for traffic between Google Cloud regions and to users near Google Points of Presence (PoPs).

Exam trap

Google Cloud often tests the misconception that 'private network' means 'free' or 'inherently secure,' leading candidates to pick cost or security options, when the real advantage is performance through congestion avoidance and deterministic routing.

How to eliminate wrong answers

Option A is wrong because while Google's backbone uses high-quality fiber, the primary performance advantage is not simply faster optical fiber—public ISPs also use modern fiber; the key difference is the private, controlled routing that avoids internet congestion. Option C is wrong because Google's private backbone is not free; customers still pay for egress traffic, though routing over the backbone may reduce costs compared to internet routing in some scenarios, but cost is not the primary performance advantage. Option D is wrong because using Google's backbone does not eliminate the need for TLS encryption; the network is physically and logically isolated but does not provide application-layer security, and data in transit should still be encrypted to protect against internal threats and meet compliance requirements.

Practice this question →
18
MCQeasy

A small business runs a single Linux server on-premises for file storage and a simple static website. They experience frequent power outages causing server downtime, and they want to improve availability with minimal cost and management overhead. They have limited IT staff. What should they do?

A.Implement a load balancer across two on-premises servers
B.Use Cloud Storage for the static website and Cloud Filestore for file storage
C.Migrate to a single Compute Engine VM in Google Cloud
D.Use a third-party colocation facility
AnswerB

Cloud Storage offers automatic replication and high availability for static content; Cloud Filestore provides managed NFS storage with redundancy, reducing downtime risk.

Why this answer

Option B is correct because Cloud Storage provides highly available static website hosting with automatic replication, and Cloud Filestore offers managed file storage, both requiring minimal management. Option A still has a single point of failure. Option C requires additional hardware and doesn't eliminate power issues.

Option D adds cost without reducing management overhead.

Practice this question →
19
MCQeasy

What does 'serverless computing' mean, and what does a developer NOT have to manage when using serverless services?

A.Serverless means no code is needed — the cloud provider writes the application logic automatically.
B.Serverless means developers don't provision or manage servers, OS, or scaling — they only write and deploy code.
C.Serverless computing only works for batch jobs that run overnight.
D.Serverless is a type of on-premises architecture where servers are hidden from developers.
AnswerB

In serverless, the cloud provider handles all infrastructure: servers, OS, scaling, patching, and capacity. Developers focus purely on application logic.

Why this answer

Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation and provisioning of servers. The developer writes and deploys code (functions) without needing to provision, configure, or scale underlying servers, operating systems, or runtime environments. Option B correctly captures this: developers only write and deploy code, while the provider handles infrastructure management.

Exam trap

Cisco often tests the misconception that 'serverless' means 'no servers at all' or 'no code needed,' leading candidates to pick Option A, when in fact servers exist but are abstracted from the developer.

How to eliminate wrong answers

Option A is wrong because serverless does not mean 'no code is needed'; developers still write application logic, and the cloud provider does not automatically generate it. Option C is wrong because serverless computing is not limited to batch jobs; it supports event-driven, real-time, and synchronous workloads (e.g., API backends, data processing). Option D is wrong because serverless is a cloud-native architecture, not an on-premises one; servers are abstracted from developers but still exist in the provider's data centers.

Practice this question →
20
MCQhard

A media streaming company runs its video transcoding pipeline on Google Cloud. The pipeline uses Compute Engine instances with GPU accelerators to process videos. The instances are started and stopped by a custom scheduler based on a Cloud Pub/Sub queue of new video uploads. Recently, the team noticed that transcoding jobs are failing intermittently with 'Out of memory' errors on some instances, and the overall cost has increased by 30% over the past month. The operations team reports that the same job configurations used to succeed before. The pipeline does not use any managed instance groups or autoscaling; each job provisions its own instance manually via a script. The company wants to reduce failures and costs. Which course of action should they take?

A.Move the transcoding pipeline to Cloud Functions to automatically scale without VM management
B.Increase the memory of all instances to 64 GB and manually select GPU types with more memory
C.Switch all instances to preemptible VMs to reduce cost, and increase the number of retry attempts for failed jobs
D.Use a managed instance group with custom autoscaling based on CPU/memory utilization and implement a queue-based scaling metric
AnswerD

Autoscaling ensures right-sized instances are used, reducing failures and costs.

Why this answer

Option D is correct because using a managed instance group (MIG) with custom autoscaling based on CPU/memory utilization and a queue-based scaling metric (e.g., Cloud Pub/Sub queue depth) addresses both the intermittent 'Out of memory' errors and the cost increase. The MIG automatically provisions and terminates instances based on actual workload, preventing resource over-provisioning (which drives cost) and under-provisioning (which causes OOM failures). This eliminates the manual, static instance provisioning that cannot adapt to varying job resource requirements.

Exam trap

The trap here is that candidates assume increasing resources (Option B) or using cheaper VMs (Option C) will solve the problem, but Cisco tests the understanding that intermittent failures in a batch processing pipeline are often due to lack of dynamic scaling, not static resource sizing or cost alone.

How to eliminate wrong answers

Option A is wrong because Cloud Functions has a maximum timeout of 9 minutes (for HTTP functions) and 540 seconds (for background functions), which is insufficient for video transcoding jobs that often run for hours; also, Cloud Functions does not support GPU accelerators, which are required for the pipeline. Option B is wrong because blindly increasing memory to 64 GB and selecting GPU types with more memory does not address the root cause of intermittent failures (likely due to resource contention or mis-sized instances) and will significantly increase costs, not reduce them. Option C is wrong because switching to preemptible VMs reduces cost but increases failure rates due to preemption (VMs can be terminated at any time within 24 hours), and simply increasing retry attempts does not fix the underlying OOM errors caused by insufficient memory for the job.

Practice this question →
21
MCQmedium

A company is evaluating whether to use a public cloud (Google Cloud), a private cloud (on-premises VMware), or a managed private cloud (hosted single-tenant environment). Which scenario is the strongest argument for choosing a managed private cloud over a public cloud?

A.The company wants to pay less for cloud services.
B.The company has regulatory requirements that mandate physically dedicated (single-tenant) infrastructure or strict hardware-level isolation.
C.The company wants the fastest possible internet speeds for their applications.
D.The company has fewer than 10 employees and doesn't need multi-tenant scale.
AnswerB

Some highly regulated industries (defense, certain financial regulations, healthcare in some jurisdictions) require dedicated hardware. Managed private cloud provides this while still outsourcing operations.

Why this answer

Option B is correct because a managed private cloud (hosted single-tenant) provides physically dedicated infrastructure that ensures hardware-level isolation, which is often required by strict regulatory standards such as HIPAA, PCI-DSS, or FedRAMP. Public clouds like Google Cloud typically use multi-tenant architectures where multiple customers share the same physical hardware, which may not satisfy these compliance mandates. The key differentiator is the guarantee of dedicated physical resources, not just logical isolation.

Exam trap

Google Cloud often tests the misconception that 'private cloud' always means on-premises, but the trap here is that a managed private cloud is hosted off-premises yet still provides single-tenant hardware isolation, which is the key differentiator from public cloud multi-tenancy.

How to eliminate wrong answers

Option A is wrong because managed private clouds are generally more expensive than public clouds due to dedicated hardware and management overhead, so cost reduction is not a valid argument. Option C is wrong because internet speed is determined by the company's ISP and network connectivity, not by the cloud deployment model; public clouds often have faster global network backbones. Option D is wrong because a small company with fewer than 10 employees would typically benefit from the lower cost and scalability of a public cloud, not the higher cost and overhead of a managed private cloud.

Practice this question →
22
MCQmedium

A company's finance director asks: 'If we move to cloud, do we need to buy fewer servers?' An IT architect responds that the answer depends on whether the company is adopting IaaS, PaaS, or SaaS. How does the service model affect hardware ownership?

A.All three models (IaaS, PaaS, SaaS) require the same amount of customer-owned hardware since cloud supplements rather than replaces on-premises systems
B.In all three models, the cloud provider owns and manages the physical hardware, eliminating the need for customer-owned servers for those workloads — with IaaS requiring the most customer management (VMs) and SaaS requiring the least (just use the application)
C.Only SaaS eliminates the need for customer servers; IaaS and PaaS still require on-premises hardware for hybrid connectivity
D.The service model doesn't affect hardware ownership — hardware purchase decisions are independent of whether the company uses cloud services
AnswerB

This is correct. In all three models, the provider owns the physical hardware — the customer buys no servers. The difference is how much software infrastructure the customer manages on top: IaaS → manage VMs; PaaS → manage application code; SaaS → just use the product. All three eliminate customer hardware ownership for covered workloads.

Why this answer

Option B is correct because in IaaS, PaaS, and SaaS, the cloud provider owns and manages the physical hardware in their data centers. The customer's hardware ownership decreases as the service model abstracts more layers: IaaS provides virtual machines (VMs) that the customer manages, PaaS provides a managed platform (runtime, middleware) without customer control over the underlying OS or hardware, and SaaS delivers a fully managed application where the customer only uses the software. Thus, moving to any of these models reduces or eliminates the need for customer-owned servers for those specific workloads.

Exam trap

Cisco often tests the misconception that IaaS still requires on-premises servers for hybrid connectivity or that PaaS requires customer hardware, when in fact all three models shift physical hardware ownership to the cloud provider, and the difference lies in the level of customer management, not hardware ownership.

How to eliminate wrong answers

Option A is wrong because it incorrectly claims all three models require the same amount of customer-owned hardware; in reality, each model shifts hardware ownership to the provider to varying degrees, with SaaS eliminating it entirely for the workload. Option C is wrong because it falsely states that only SaaS eliminates the need for customer servers; both IaaS and PaaS also offload physical hardware ownership to the provider, though IaaS may still require customer-managed VMs and PaaS may require some configuration, but neither requires on-premises servers for the cloud-hosted workloads. Option D is wrong because the service model directly affects hardware ownership: IaaS, PaaS, and SaaS each define different levels of abstraction and responsibility, which determines whether the customer must own physical servers or can rely entirely on provider-managed infrastructure.

Practice this question →
23
MCQeasy

A company is comparing the total cost of keeping its data center versus moving to public cloud. An analyst argues that the comparison should include not just hardware costs but also facility costs. What facility costs should be included in the on-premises total cost of ownership calculation?

A.Only the cost of the servers themselves, since other costs are shared across the organization
B.Physical space/rent, electricity (for servers and cooling), cooling system maintenance, physical security, and fire suppression — all of which are real costs borne by the organization for operating its own data center
C.Internet connectivity costs only, since data centers require high-bandwidth connections
D.Data center facility costs do not need to be included since they are fixed costs that don't change whether servers are present or not
AnswerB

This is the complete set of facility costs. Power is often the largest ongoing cost after staff. Cooling typically adds 30-50% to the power cost of the IT equipment itself. Physical security and fire suppression add further costs. All must be included for an accurate TCO comparison against cloud.

Why this answer

Option B is correct because a comprehensive on-premises total cost of ownership (TCO) must include all facility-related costs that are directly incurred to operate a data center. These include physical space/rent, electricity for servers and cooling, cooling system maintenance, physical security, and fire suppression. Excluding these costs would understate the true cost of running an on-premises environment, which is a key consideration when comparing to public cloud models like IaaS.

Exam trap

Cisco often tests the misconception that facility costs are either negligible or shared overhead, when in fact they are direct, variable costs that must be included in a proper TCO analysis for on-premises versus cloud comparison.

How to eliminate wrong answers

Option A is wrong because it incorrectly limits facility costs to only the servers themselves; in reality, servers are hardware, not facility costs, and other costs like power and cooling are real, not shared arbitrarily. Option C is wrong because internet connectivity is a network cost, not a facility cost; while important, it is separate from the physical infrastructure costs of the data center itself. Option D is wrong because facility costs are not fixed regardless of server presence; they scale with the data center's operation and are directly attributable to the on-premises deployment, so they must be included for an accurate TCO comparison.

Practice this question →
24
MCQhard

A data analytics company uses BigQuery for large-scale queries. They notice that some queries are very expensive due to scanning large amounts of data. They want to reduce costs without changing query logic. Which feature should they use?

A.Query caching
B.Partitioning and clustering tables
C.Authorized views
D.Flat-rate pricing with reservations
AnswerB

Partitioning prunes partitions, clustering orders data; both reduce bytes processed.

Why this answer

Partitioning and clustering tables in BigQuery physically organize data into smaller, manageable segments based on specified columns (e.g., date or timestamp). This allows queries to use partition pruning and clustering-based block pruning to scan only the relevant data, drastically reducing the amount of data processed and thus lowering costs without altering the query logic.

Exam trap

Google Cloud often tests the misconception that cost reduction must come from changing pricing models (like flat-rate) rather than from data organization techniques that reduce the actual amount of data processed.

How to eliminate wrong answers

Option A is wrong because query caching only returns results from previously run queries if the underlying data hasn't changed, but it does not reduce the cost of new or uncached queries that scan large datasets. Option C is wrong because authorized views control access to underlying tables by allowing users to query through a view, but they do not reduce the amount of data scanned or the cost of the query itself. Option D is wrong because flat-rate pricing with reservations provides a fixed-cost capacity model that can make costs predictable, but it does not reduce the amount of data scanned per query; it only changes the billing method, and queries still process the same large volumes of data.

Practice this question →
25
MCQeasy

Refer to the exhibit. A user receives this error when trying to copy an object from one bucket to another. What is the most likely cause?

A.The service account used does not have the required IAM permissions to copy objects.
B.The buckets are located in different regions and cross-region copy is not allowed.
C.The destination bucket has exceeded its storage quota.
D.The source bucket name is misspelled in the request.
AnswerA

The 403 error indicates access denied due to missing permissions.

Why this answer

The error when copying an object between buckets is most likely due to insufficient IAM permissions. In Google Cloud, the service account initiating the copy must have both `storage.objects.get` (to read the source object) and `storage.objects.create` (to write to the destination bucket) permissions. Without these, the operation fails with an access denied error, even if the buckets exist and are accessible.

Exam trap

Google Cloud often tests the misconception that cross-region copy is blocked by default, but in Google Cloud Storage, cross-region copies are allowed as long as IAM permissions are correct, making permissions the primary gatekeeper.

How to eliminate wrong answers

Option B is wrong because cross-region copy is fully supported in Google Cloud Storage; objects can be copied between buckets in different regions without restriction. Option C is wrong because exceeding the storage quota would cause a quota exceeded error, not a permissions-related error, and the error message shown is typical of access issues. Option D is wrong because a misspelled bucket name would result in a 'bucket not found' error (HTTP 404), not a permissions error.

Practice this question →
26
Matchingmedium

Match each Google Cloud networking concept to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Virtual Private Cloud – isolated network

Content delivery network for low-latency delivery

Distributes traffic across instances

Outbound internet for private instances

Dedicated connection between on-prem and GCP

Why these pairings

These are key networking components in Google Cloud.

Practice this question →
27
MCQmedium

A developer is building a real-time collaborative document editing application (similar to Google Docs). Users must see each other's edits instantly. Which data consistency model is required for this use case, and what is the implication for the database choice?

A.Eventual consistency is acceptable because users will eventually see each other's edits after a short delay, and this enables higher performance
B.Strong consistency or real-time synchronization is required so all users see the same document state simultaneously; this rules out eventually consistent NoSQL stores and pushes toward strongly consistent databases or specialized collaboration protocols
C.Consistency doesn't matter for this use case because each user edits different parts of the document
D.This workload requires a relational database because only SQL can handle concurrent user edits correctly
AnswerB

Real-time collaboration requires that edits are applied in a consistent order visible to all users simultaneously. Eventually consistent databases (like Cassandra in default mode) would show different users different states of the document. This workload requires either strongly consistent storage or specialized real-time sync protocols (Operational Transformation, CRDTs) that handle concurrent edits correctly.

Why this answer

Option B is correct because real-time collaborative editing requires all users to see the same document state simultaneously, which demands strong consistency or real-time synchronization. This rules out eventually consistent NoSQL stores (e.g., Amazon DynamoDB in default mode) and pushes toward strongly consistent databases (e.g., Google Cloud Spanner, CockroachDB) or specialized collaboration protocols like Operational Transformation (OT) or Conflict-Free Replicated Data Types (CRDTs) that provide convergence guarantees.

Exam trap

Google Cloud often tests the misconception that eventual consistency is sufficient for real-time applications, but the trap here is that users expect instant, conflict-free updates, which only strong consistency or specialized synchronization protocols can guarantee.

How to eliminate wrong answers

Option A is wrong because eventual consistency introduces a delay that can cause users to see conflicting or stale document states, breaking the real-time collaboration experience required for a Google Docs-like application. Option C is wrong because users often edit overlapping sections (e.g., the same paragraph or sentence), and without a consistency model, concurrent edits would lead to lost updates or document corruption. Option D is wrong because relational databases are not the only solution; strongly consistent NoSQL databases (e.g., Google Cloud Firestore in strong consistency mode) or specialized CRDT-based systems can handle concurrent edits correctly without requiring SQL.

Practice this question →
28
MCQeasy

A business leader asks: 'What is the difference between a data center region and an availability zone in Google Cloud?' Which explanation is most accurate?

A.A region is a single data center building; an availability zone is a floor within that building
B.A region is a geographic area containing multiple independent zones; each zone is a distinct facility with independent power, cooling, and networking — failures in one zone don't affect other zones in the region
C.A region is equivalent to an availability zone; both terms refer to a single data center
D.An availability zone is larger than a region and spans multiple geographic areas for global redundancy
AnswerB

This is the correct definition. GCP regions (e.g., us-central1) contain multiple zones (a, b, c, d). Each zone is independent infrastructure. A zonal failure (power outage, cooling failure) doesn't propagate to other zones. Customers deploy across multiple zones within a region for high availability against zone-level failures.

Why this answer

Option B is correct because in Google Cloud, a region is a specific geographic location composed of multiple zones, where each zone is an independent data center with its own power, cooling, and networking infrastructure. This isolation ensures that failures within one zone do not impact other zones in the same region, providing high availability and fault tolerance for applications.

Exam trap

The trap here is confusing the hierarchical relationship between regions and zones, leading candidates to incorrectly think a region is a single data center or that zones are larger than regions, which Google Cloud often tests by presenting false equivalencies or reversed sizes.

How to eliminate wrong answers

Option A is wrong because a region is not a single data center building; it is a collection of multiple independent zones, each of which is a separate facility. Option C is wrong because a region and an availability zone are not equivalent; a region contains multiple zones, and each zone is a distinct data center within that region. Option D is wrong because an availability zone is smaller than a region and does not span multiple geographic areas; it is confined to a single region, while regions themselves are separate geographic areas.

Practice this question →
29
MCQmedium

What is the key difference between a virtual machine (VM) and a container in terms of how they package and run applications?

A.VMs run on physical hardware; containers run in the cloud.
B.VMs include a full guest OS; containers share the host OS kernel and contain only the application and its dependencies.
C.Containers are less secure than VMs because they share hardware.
D.VMs are only for Linux applications; containers support all operating systems.
AnswerB

This is the fundamental difference. VMs carry a full OS (gigabytes), making them slower to start and heavier. Containers share the host kernel (megabytes) and start in seconds.

Why this answer

The key difference is that a virtual machine (VM) includes a full guest operating system (OS) running on top of a hypervisor, which virtualizes the underlying hardware. In contrast, a container packages only the application and its dependencies (libraries, binaries, configuration files) and shares the host OS kernel via the container runtime (e.g., Docker, containerd). This makes containers lightweight and faster to start, as they avoid the overhead of a separate OS instance.

Exam trap

Google Cloud often tests the misconception that containers are simply 'lightweight VMs' or that the difference is about location (cloud vs. on-prem), when the actual distinction is the presence or absence of a guest OS and kernel sharing.

How to eliminate wrong answers

Option A is wrong because VMs do not inherently run on physical hardware; they run on a hypervisor that abstracts the physical hardware, and containers can run on physical hardware, in the cloud, or on-premises — location is not the defining difference. Option C is wrong because containers share the host OS kernel, not the hardware directly, and security depends on isolation mechanisms (e.g., cgroups, namespaces, seccomp); a misconfigured container can be less secure, but VMs provide stronger isolation via a separate kernel, so the blanket statement 'containers are less secure because they share hardware' is technically inaccurate. Option D is wrong because VMs support multiple operating systems (Windows, Linux, etc.) and containers primarily run on Linux or Windows with kernel support; containers do not support all operating systems — for example, a Linux container cannot run natively on a Windows host without a Linux VM.

Practice this question →
30
MCQeasy

A startup wants to deploy a web application globally and expects traffic to be unpredictable — sometimes very low, sometimes very high. Which cloud characteristic ensures the startup only pays for the compute resources it actually uses?

A.Resource pooling, which allows the startup to share physical hardware with other tenants
B.Measured service / pay-per-use pricing, where the startup is billed only for actual resource consumption with no payment for idle capacity
C.Broad network access, which allows the application to be reached from any device globally
D.On-demand self-service, which allows the startup to provision resources through a web interface without calling a sales team
AnswerB

Measured service is the NIST cloud characteristic that directly answers this. The startup is metered — billed for actual CPU, memory, network, and storage consumed. During low-traffic periods, bills are low. During spikes, costs scale up. No capacity is pre-purchased and wasted.

Why this answer

Option B is correct because the measured service / pay-per-use pricing model of cloud computing ensures that the startup is billed only for the compute resources it actually consumes, such as CPU hours, memory, or storage, with no charges for idle capacity. This directly addresses the need to handle unpredictable traffic spikes without incurring costs for unused resources during low-traffic periods. In Google Cloud, this is implemented through per-second billing for compute instances and autoscaling, which dynamically adjusts resources based on demand.

Exam trap

Google Cloud often tests the distinction between the 'what' (e.g., resource pooling, broad network access) and the 'why it matters for cost' (measured service), leading candidates to confuse a general cloud characteristic with the specific billing model that addresses pay-for-use.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the cloud provider's ability to serve multiple tenants from the same physical hardware using virtualization, but it does not directly determine billing based on actual usage; it is about multi-tenancy and efficiency, not cost proportionality. Option C is wrong because broad network access describes the ability to access cloud services over the network via standard protocols (e.g., HTTP/HTTPS) from any device, but it has no relation to billing models or paying only for resources used. Option D is wrong because on-demand self-service allows users to provision resources automatically without human interaction, but it does not define the pricing model; it enables rapid provisioning but does not guarantee pay-per-use billing.

Practice this question →
31
MCQeasy

A non-technical manager asks what a 'virtual machine' is and how it differs from the physical servers the company used to run in its own data center. Which explanation is most accurate and accessible?

A.A virtual machine is a web-based application that runs in a browser and replaces traditional desktop software
B.A virtual machine is a complete software-defined computer that runs on shared physical hardware, providing the same capabilities as a dedicated server but created and managed through software in minutes
C.A virtual machine is a physical server located in the cloud provider's data center that is reserved exclusively for one customer
D.A virtual machine is a type of database that stores data virtually rather than on physical disk
AnswerB

This accurately describes a VM: it behaves like a physical server (has CPU, memory, OS, storage) but exists as software running on shared hardware. The key management advantage is that it can be provisioned, modified, and terminated through software, unlike physical servers which require manual hardware work.

Why this answer

Option B is correct because a virtual machine (VM) is a software-based emulation of a physical computer that runs on shared physical hardware via a hypervisor. It provides the same capabilities as a dedicated server (CPU, memory, storage, networking) but can be provisioned, cloned, and managed in minutes through software, which is the core difference from traditional on-premises physical servers that require manual setup and are tied to specific hardware.

Exam trap

The trap here is that Cisco often tests the misconception that 'virtual' means 'web-based' or 'in the cloud as a service,' leading candidates to confuse VMs with SaaS applications or dedicated physical servers, when the key differentiator is the hypervisor-based abstraction of hardware.

How to eliminate wrong answers

Option A is wrong because a virtual machine is not a web-based application running in a browser; that describes a web app or SaaS, not a VM. Option C is wrong because a virtual machine is not a physical server reserved exclusively for one customer; that describes a dedicated physical host or bare-metal server, while VMs share underlying physical hardware with other tenants via a hypervisor. Option D is wrong because a virtual machine is not a type of database; databases store data, while VMs are complete computing environments that can host databases or any other software.

Practice this question →
32
MCQeasy

What is virtualization in the context of cloud computing, and why is it fundamental to how cloud providers deliver services?

A.Virtualization is the process of converting physical servers into digital images for backup purposes.
B.Virtualization abstracts physical hardware into multiple isolated virtual machines, enabling many customers to share physical infrastructure efficiently and securely.
C.Virtualization is a networking technique that routes internet traffic more efficiently.
D.Virtualization is a backup strategy where data is stored in multiple geographic locations.
AnswerB

A hypervisor divides physical hardware into isolated VMs. Cloud providers run thousands of customer VMs on shared physical servers — the foundation of cloud economics and multi-tenancy.

Why this answer

Virtualization is fundamental to cloud computing because it decouples the operating system and applications from the underlying physical hardware through a hypervisor (e.g., VMware ESXi, KVM, Hyper-V). This abstraction allows a single physical server to host multiple isolated virtual machines (VMs), each with its own guest OS, enabling cloud providers to achieve high resource utilization, multi-tenancy, and rapid provisioning. Without virtualization, providers would be limited to one OS per physical server, drastically reducing efficiency and scalability.

Exam trap

Cisco often tests the misconception that virtualization is only about backup or networking, so candidates mistakenly pick options that describe tangential technologies (disk imaging, traffic routing, or geo-replication) instead of the core abstraction of physical hardware into multiple isolated environments.

How to eliminate wrong answers

Option A is wrong because virtualization is not merely converting physical servers into digital images for backup; that describes disk imaging or backup processes, not the core abstraction of hardware into multiple VMs. Option C is wrong because virtualization is not a networking technique for routing traffic; that describes technologies like SDN or routing protocols (e.g., BGP, OSPF), not the hypervisor-based abstraction of compute resources. Option D is wrong because virtualization is not a backup strategy for geographic data replication; that describes disaster recovery or geo-redundancy, not the foundational multi-tenant resource sharing enabled by hypervisors.

Practice this question →
33
MCQmedium

A company's cloud spending suddenly spikes by 300% for one week before returning to normal. The cloud team investigates and finds a developer accidentally left a large cluster of VMs running over the weekend. Which cloud financial management practice most effectively prevents this type of unexpected cost spike?

A.Requiring all cloud resource creation to go through a central IT approval process to prevent accidental VM creation
B.Setting Cloud Billing budget alerts that notify stakeholders when spending approaches defined thresholds, enabling early detection and response to abnormal spending patterns
C.Reviewing cloud bills at the end of each month to identify cost anomalies and address them retroactively
D.Using Reserved Instances for all VM workloads to reduce per-hour costs, making accidental long-running VMs less expensive
AnswerB

Budget alerts are the direct preventive control. A budget alert at 150% of normal daily spending would have triggered early Saturday morning, prompting investigation. This gives the team time to act before a full weekend of over-spending accumulates. Budget alerts with escalating thresholds (50%, 80%, 100%, 150%) are a best practice.

Why this answer

Option B is correct because Cloud Billing budget alerts provide real-time notifications when spending exceeds defined thresholds, enabling the cloud team to detect and respond to the 300% spike immediately rather than after the fact. This proactive monitoring directly addresses the root cause—unexpected resource usage—by alerting stakeholders while the VMs are still running, allowing them to shut down the cluster and prevent further cost accumulation.

Exam trap

Google Cloud often tests the distinction between proactive prevention (alerts) and reactive cost optimization (Reserved Instances or monthly reviews), leading candidates to mistakenly choose D because they focus on reducing cost per unit rather than preventing the unexpected usage itself.

How to eliminate wrong answers

Option A is wrong because requiring central IT approval for resource creation introduces a bottleneck that slows down development agility and does not prevent a developer from leaving VMs running; it only controls creation, not runtime duration. Option C is wrong because reviewing bills at the end of each month is a retroactive practice that cannot prevent the cost spike—by the time the bill is reviewed, the 300% increase has already been incurred, making it a detection method rather than a prevention method. Option D is wrong because Reserved Instances reduce per-hour costs but do not prevent the unexpected spike; even at a lower rate, leaving a large cluster running for a full weekend would still result in a significant cost increase, and the practice does not address the behavioral or monitoring gap.

Practice this question →
34
MCQhard

An architect explains that her cloud application uses a 'loosely coupled architecture.' She contrasts it with a tightly coupled on-premises system where all components run in a single process. What is the primary operational benefit of loose coupling in a cloud environment?

A.Loosely coupled applications are always faster because messages are passed in memory rather than over the network
B.Loose coupling allows individual components to fail, scale, or be updated independently without cascading failures to the entire system
C.Loosely coupled architectures require less developer expertise and are easier to build than monolithic applications
D.Loose coupling reduces cloud costs because fewer network calls are made between services
AnswerB

This is the primary operational benefit. When components communicate through queues and APIs rather than direct coupling, a failure in one component doesn't automatically bring down others. Each component can also scale independently based on its own load, and teams can deploy updates without coordinating a system-wide release.

Why this answer

In a loosely coupled architecture, components communicate via well-defined interfaces (e.g., REST APIs, message queues) and are deployed as independent services. This means a failure in one component does not propagate to others, and each component can be scaled or updated without affecting the rest of the system. This isolation is the primary operational benefit in a cloud environment, enabling high availability and continuous delivery.

Exam trap

Cisco often tests the misconception that 'loose coupling' implies faster performance or lower cost, when in fact the primary benefit is operational independence and fault isolation, not raw speed or expense.

How to eliminate wrong answers

Option A is wrong because loose coupling typically involves network calls (e.g., HTTP, AMQP) between services, which are slower than in-memory calls; the statement incorrectly claims messages are passed in memory. Option C is wrong because loosely coupled architectures (e.g., microservices) require significant developer expertise in areas like service discovery, distributed tracing, and eventual consistency, making them harder to build than monolithic applications. Option D is wrong because loose coupling often increases the number of network calls between services, which can increase latency and data transfer costs, not reduce them.

Practice this question →
35
MCQmedium

An organization runs its entire infrastructure on a single public cloud provider (Google Cloud). All applications, data, and services live in Google Cloud's infrastructure. Which deployment model describes this?

A.Private cloud
B.Public cloud
C.Hybrid cloud
D.Community cloud
AnswerB

Public cloud means all infrastructure is provided by and located in a third-party provider's (Google's) facilities, shared with other customers but logically isolated. Using only Google Cloud is a public cloud deployment.

Why this answer

Option B is correct because the organization is using a single public cloud provider, Google Cloud, which delivers computing resources over the public internet on a pay-as-you-go basis. In a public cloud deployment, the infrastructure is owned and operated by the cloud provider and shared across multiple tenants, which matches the scenario where all applications, data, and services reside in Google Cloud's infrastructure.

Exam trap

Cisco often tests the misconception that using a single public cloud provider is a 'private cloud' because the organization has exclusive use of that provider's resources, but the key distinction is that the provider's infrastructure is still shared among multiple customers, making it a public cloud deployment.

How to eliminate wrong answers

Option A is wrong because a private cloud is dedicated to a single organization and is typically hosted on-premises or in a single-tenant environment, not on a shared public cloud provider like Google Cloud. Option C is wrong because a hybrid cloud requires a combination of at least two distinct deployment models (e.g., public and private) that are interconnected, whereas the scenario describes all infrastructure on a single public cloud. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., compliance or security requirements) and is not a single public cloud provider used exclusively by one organization.

Practice this question →
36
MCQhard

A company's monolithic application is difficult to update because any change requires testing and redeploying the entire application, causing multi-hour downtime during updates. The team is considering a microservices architecture. What is the primary benefit of microservices in this context?

A.Microservices always cost less than monolithic applications to run.
B.Each service can be updated and deployed independently, enabling teams to release changes faster with lower risk and without full-application downtime.
C.Microservices eliminate the need for testing because each service is small enough to be bug-free.
D.Microservices allow applications to run on any hardware without modification.
AnswerB

Independent deployability is the core microservices benefit for the described problem. Updating service A doesn't require redeploying services B, C, D — dramatically reducing deployment risk and duration.

Why this answer

Microservices architecture decomposes a monolithic application into small, independently deployable services. Each service can be updated, scaled, and deployed without affecting other services. This eliminates the 'entire-application-redeploy' problem — updating the payment service doesn't require redeploying the catalog or user management services.

Cloud platforms support microservices with containers (GKE), serverless functions (Cloud Run), and managed messaging (Pub/Sub) for service communication.

Practice this question →
37
MCQeasy

A company's security team wants to control which resources on the internet can communicate with their virtual machines in Google Cloud. Which fundamental cloud networking concept provides this control?

A.VPC firewall rules that control inbound and outbound network traffic to VMs based on IP ranges, protocols, and ports
B.Cloud IAM policies that grant or deny permissions for external systems to access VM resources
C.Cloud Storage bucket policies that restrict access to VM storage volumes
D.DNS records that determine which internet addresses can resolve the VM's hostname
AnswerA

VPC firewall rules are the correct answer. They are stateful, software-defined firewalls applied to VM network interfaces in Google Cloud VPCs. Rules specify what traffic is allowed or denied based on source/destination IPs, protocols, and ports — providing precise control over which internet resources can communicate with the VMs.

Why this answer

Option A is correct because VPC firewall rules are the fundamental cloud networking construct that controls network traffic to and from virtual machine instances in Google Cloud. These rules operate at the network layer, filtering traffic based on source/destination IP ranges, protocols (e.g., TCP, UDP, ICMP), and port numbers, thereby governing which internet resources can communicate with the VMs.

Exam trap

Cisco often tests the distinction between network-layer controls (firewall rules) and identity/access management (IAM), tempting candidates to choose IAM policies because they sound like 'control' over access, but IAM does not filter network traffic at the packet level.

How to eliminate wrong answers

Option B is wrong because Cloud IAM policies control identity-based permissions for who can perform actions on cloud resources (e.g., who can create VMs), not network-level traffic filtering between internet resources and VMs. Option C is wrong because Cloud Storage bucket policies govern access to objects in Cloud Storage, not to VM storage volumes; VM storage is handled by persistent disks or local SSDs, which are not controlled by bucket policies. Option D is wrong because DNS records resolve hostnames to IP addresses but do not enforce any access control or filtering of network traffic; they merely provide name resolution.

Practice this question →
38
MCQmedium

A startup is building a gaming application where players must see each other's moves in real time. The database storing game state must guarantee that all players see the same state simultaneously. Which consistency requirement does this impose and why does it matter for database selection?

A.Eventual consistency is sufficient; the game can show slightly stale state to some players without impact on gameplay
B.Strong consistency is required so all players simultaneously read the same current game state; eventual consistency would create conflicting game states visible to different players
C.Consistency doesn't matter for gaming databases because games update state so frequently that any inconsistency resolves within milliseconds
D.The game should avoid databases entirely and use local storage on each player's device to ensure fast, consistent state access
AnswerB

This is correct. Strong consistency guarantees that after a write (player moves), all subsequent reads from any client see that write. This ensures all players operate on the same view of game state. Cloud Spanner's external consistency or Firestore's strongly consistent reads serve this requirement.

Why this answer

B is correct because real-time multiplayer gaming requires strong consistency to ensure all players see the identical game state simultaneously. In a GCDL context, this means the database must support ACID transactions or linearizable reads (e.g., using Google Cloud Spanner or a strongly consistent NoSQL system like Cloud Firestore in strong consistency mode). Eventual consistency would allow different players to observe different board positions, breaking the game's core requirement of a shared, current state.

Exam trap

Cisco often tests the misconception that eventual consistency is 'good enough' for real-time applications, but the trap is that gaming state requires a single, globally agreed view—eventual consistency introduces windows of divergence that break the core gameplay contract.

How to eliminate wrong answers

Option A is wrong because eventual consistency allows stale reads, which would let players see different game states (e.g., one player sees a move that another hasn't yet), causing conflicts and breaking real-time gameplay. Option C is wrong because consistency is critical in gaming databases; high update frequency does not resolve inconsistency—it can actually exacerbate it, leading to race conditions and state divergence. Option D is wrong because using only local storage on each device eliminates a shared authoritative state, making it impossible to synchronize moves across players and violating the requirement for a single source of truth.

Practice this question →
39
MCQmedium

A company architect is explaining cloud network connectivity options to executives. She distinguishes between using the public internet to connect to cloud services versus using a dedicated private connection. What is the primary advantage of a dedicated private connection over the public internet for enterprise workloads?

A.Dedicated connections are always free, while public internet connections incur data transfer charges
B.Dedicated private connections provide consistent, predictable bandwidth and lower latency by bypassing public internet congestion and variable routing
C.Dedicated connections provide stronger encryption because the public internet uses no encryption
D.Public internet connections have higher bandwidth limits than dedicated connections
AnswerB

This is the primary advantage. By using a private circuit that doesn't traverse the public internet, enterprises get guaranteed bandwidth, predictable latency, and a more reliable connection — critical for applications like database replication, real-time analytics, or mission-critical transactional workloads.

Why this answer

A dedicated private connection, such as AWS Direct Connect or Azure ExpressRoute, provides consistent, predictable bandwidth and lower latency because it bypasses the public internet's variable routing and congestion. This is critical for enterprise workloads that require stable performance for real-time applications, large data transfers, or hybrid cloud architectures. The public internet introduces jitter, packet loss, and unpredictable latency due to shared infrastructure and best-effort routing.

Exam trap

Google Cloud often tests the misconception that dedicated connections are inherently more secure due to encryption, but the real advantage is network isolation and performance predictability, not encryption strength.

How to eliminate wrong answers

Option A is wrong because dedicated private connections are not free; they incur recurring costs for port hours, data transfer, and cross-connects, while public internet data transfer charges are typically lower or included in standard bandwidth plans. Option C is wrong because the public internet does use encryption (e.g., TLS/SSL, IPsec VPNs), and dedicated connections do not inherently provide stronger encryption—they rely on the same encryption protocols if needed, but their primary security benefit is isolation from the public internet, not encryption strength. Option D is wrong because public internet connections generally have higher bandwidth limits (e.g., multi-gigabit via broadband or fiber) compared to dedicated connections, which are provisioned at specific, often lower, committed rates (e.g., 1 Gbps, 10 Gbps) and require scaling via additional circuits.

Practice this question →
40
MCQhard

An architect proposes using a 'private cloud' deployment model for a company that wants cloud-like capabilities but is prohibited from using public cloud due to data residency regulations. What is a key advantage of private cloud compared to public cloud, and what is a significant trade-off?

A.Advantage: private cloud is always cheaper than public cloud. Trade-off: private cloud provides less storage capacity
B.Advantage: full control over data residency, security posture, and compliance configuration. Trade-off: organization bears full cost of infrastructure, loses public cloud's scale economics, and has limited elasticity compared to public cloud's vast resource pools
C.Advantage: private cloud provides automatic scaling to unlimited capacity. Trade-off: private cloud requires purchasing hardware every time capacity is needed
D.Advantage: private cloud services are managed by the cloud provider, reducing operational burden. Trade-off: customers cannot customize private cloud configurations
AnswerB

This captures both sides accurately. Private cloud satisfies regulatory requirements for data control and residency. But the organization must fund all infrastructure, skilled operations staff, and hardware refresh — at costs that rarely match public cloud's shared-scale economics. Elasticity is limited to what the organization has built, not global resource pools.

Why this answer

Option B is correct because a private cloud gives the organization exclusive control over data residency, security, and compliance, which is essential when regulations prohibit public cloud use. The trade-off is that the organization must bear the full capital and operational costs of the infrastructure, losing the scale economics and near-infinite elasticity of public cloud providers like AWS, Azure, or GCP.

Exam trap

Cisco often tests the misconception that private cloud is always cheaper or that it provides unlimited elasticity, when in fact the key differentiator is control over compliance and data residency, with the trade-off being higher cost and limited scalability.

How to eliminate wrong answers

Option A is wrong because private cloud is not always cheaper than public cloud; in fact, it often has higher upfront capital expenditure and ongoing operational costs, and storage capacity is not inherently less—private clouds can be scaled with additional hardware. Option C is wrong because private clouds do not provide automatic scaling to unlimited capacity; their elasticity is bounded by the organization's own hardware resources, and scaling requires procurement and deployment of additional physical infrastructure, not just purchasing hardware every time. Option D is wrong because private cloud services are typically managed by the organization's own IT team, not the cloud provider, and customers have full customization control over configurations, which is a key advantage, not a trade-off.

Practice this question →
41
Drag & Dropmedium

Drag and drop the steps to migrate an on-premises MySQL database to Cloud SQL using Database Migration Service into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

The migration process requires setting up the destination, connecting to the source, creating and starting the migration, then promoting.

Practice this question →
42
MCQmedium

A hospital runs a patient records system that must remain on-premises due to strict regulatory data residency requirements. However, they also want to use cloud-based AI for diagnostic imaging analysis. Which cloud deployment model best describes their architecture?

A.Public cloud — all workloads run in a provider's infrastructure.
B.Private cloud — all workloads run in the hospital's own infrastructure.
C.Hybrid cloud — combining on-premises infrastructure with public cloud services.
D.Multi-cloud — using multiple public cloud providers simultaneously.
AnswerC

Hybrid cloud connects on-premises (patient records, regulatory compliance) with public cloud (AI imaging analysis). This is the textbook hybrid cloud pattern for regulated industries.

Why this answer

The hospital must keep patient records on-premises to comply with data residency regulations, but wants to leverage cloud-based AI for diagnostic imaging. A hybrid cloud model combines on-premises infrastructure (for sensitive data) with public cloud services (for AI processing), allowing data to remain resident while compute-intensive tasks are offloaded. This matches the scenario exactly, as hybrid cloud enables workload distribution across private and public environments.

Exam trap

Cisco often tests the misconception that 'hybrid cloud' requires equal distribution of workloads, but the trap here is that candidates may confuse 'multi-cloud' (multiple public providers) with 'hybrid cloud' (private + public), failing to recognize that on-premises infrastructure is a key component of hybrid cloud.

How to eliminate wrong answers

Option A is wrong because a public cloud would require all workloads, including patient records, to run in the provider's infrastructure, violating the on-premises data residency requirement. Option B is wrong because a private cloud would keep everything on-premises, failing to utilize cloud-based AI services for diagnostic imaging. Option D is wrong because multi-cloud involves using multiple public cloud providers, but does not inherently include on-premises infrastructure, so it cannot satisfy the data residency constraint.

Practice this question →
43
MCQeasy

An organization wants to ensure business continuity by replicating critical data to a different region. Which Google Cloud feature should they use?

A.Cloud Storage dual-region or multi-region
B.Cloud Dataflow
C.Compute Engine instance groups
D.Cloud VPN
AnswerA

These storage classes automatically replicate data across geographic regions for disaster recovery.

Why this answer

Cloud Storage dual-region or multi-region configuration is the correct choice because it provides built-in, asynchronous replication of data across geographically separated locations, ensuring business continuity through high availability and durability. This feature automatically stores redundant copies of objects in multiple zones within a region or across regions, protecting against regional failures without requiring additional infrastructure or manual intervention.

Exam trap

Google Cloud often tests the misconception that Compute Engine instance groups or Cloud VPN provide data replication, when in fact they only manage compute or network connectivity, respectively, and candidates must recognize that native storage replication requires a storage service like Cloud Storage with dual-region or multi-region configuration.

How to eliminate wrong answers

Option B is wrong because Cloud Dataflow is a fully managed service for stream and batch data processing pipelines, not a data replication or storage solution; it does not inherently replicate data across regions for business continuity. Option C is wrong because Compute Engine instance groups provide auto-scaling and load balancing for virtual machines, but they do not replicate data; they only manage compute resources, and any data replication would require separate storage or database services. Option D is wrong because Cloud VPN establishes an encrypted tunnel between on-premises networks and Google Cloud, enabling secure connectivity but not replicating data; it is a networking tool, not a data replication or storage service.

Practice this question →
44
Multi-Selecthard

A large enterprise is evaluating moving its data analytics workloads to Google Cloud. Which TWO factors should they consider when comparing on-premises costs to cloud costs? (Choose two.)

Select 2 answers
A.Elimination of hardware maintenance labor costs
B.Increased latency due to network distance
C.Reduction in data center power and cooling expenses
D.Licensing costs for software that may not be compatible with cloud
E.Requirement to redesign applications for cloud-native services
AnswersA, C

Cloud reduces or eliminates the need for on-premises hardware maintenance staff.

Why this answer

Option A is correct because moving analytics workloads to Google Cloud eliminates the need for the enterprise to maintain its own hardware, including servers, storage, and networking equipment. This removes direct labor costs for tasks such as hardware troubleshooting, firmware updates, and physical repairs, which are instead handled by Google's infrastructure teams. This is a direct operational expenditure (OpEx) saving compared to the capital expenditure (CapEx) and ongoing maintenance of on-premises hardware.

Exam trap

Google Cloud often tests the distinction between direct cost factors (like hardware maintenance and power/cooling) and indirect considerations (like latency, licensing compatibility, and application redesign) to see if candidates can separate TCO line items from migration risks or performance trade-offs.

Practice this question →
45
MCQeasy

A business user asks what makes cloud storage different from simply buying a larger external hard drive for the office. Which characteristic most clearly differentiates cloud storage from local storage devices?

A.Cloud storage is faster than local storage for all types of data access
B.Cloud storage is accessible from anywhere via the internet, scales elastically without hardware purchases, and provides built-in redundancy across multiple physical locations
C.Cloud storage cannot be used for backup, while external hard drives are purpose-built for backup
D.Cloud storage requires specialized hardware on the customer's side to access data
AnswerB

These three characteristics — universal accessibility, elastic scalability, and built-in geographic redundancy — are what fundamentally differentiate cloud storage from a local external drive. A hard drive is physically local, has fixed capacity, and has no built-in redundancy.

Why this answer

Cloud storage is fundamentally different from local storage because it provides internet-based accessibility, elastic scalability without requiring hardware procurement, and built-in redundancy across geographically distributed data centers. These characteristics enable on-demand resource provisioning and high availability, which a single external hard drive cannot offer. The correct answer, B, captures these core differentiators that align with the NIST definition of cloud computing.

Exam trap

Google Cloud often tests the misconception that cloud storage is inherently faster than local storage, leading candidates to select Option A, but the real differentiator is ubiquitous access and elasticity, not raw speed.

How to eliminate wrong answers

Option A is wrong because cloud storage is not universally faster than local storage; local storage (e.g., USB 3.0 or SATA SSDs) often has lower latency and higher throughput for local access, while cloud storage performance depends on network bandwidth and latency. Option C is wrong because cloud storage is commonly used for backup (e.g., AWS S3 for backup, Azure Backup) and external hard drives are not exclusively purpose-built for backup—they are general-purpose storage devices. Option D is wrong because cloud storage does not require specialized hardware on the customer side; access is typically via standard internet protocols (HTTP/HTTPS, S3 API, NFS) using commodity devices like laptops or smartphones.

Practice this question →
46
MCQhard

A global enterprise must store customer data in specific geographic regions to comply with data residency laws. They also need to be able to analyze data across all regions without centralizing it. Which approach best balances compliance and analytics?

A.Deploy identical Compute Engine instances with databases in each region.
B.Use regional Cloud Storage buckets per region and BigQuery with federated queries.
C.Store all data in a single region and use Cloud CDN for fast access.
D.Use a single Cloud Storage multi-region bucket with granular access controls.
AnswerB

Federated queries allow analyzing data in place across regions, maintaining compliance.

Why this answer

Option C is correct because a multi-region deployment with BigQuery's federated queries allows querying data across regions without moving it. Option A is wrong because storing all data in a single region violates residency laws. Option B is wrong because using VMs in each region requires managing infrastructure and does not inherently provide cross-region analytics.

Option D is wrong because Cloud Storage's multi-region bucket stores data in multiple regions, which may violate data residency if data is replicated outside the required region.

Practice this question →
47
MCQhard

A company migrates its on-premises database to Cloud SQL. The security team is concerned about who is responsible for patching the underlying operating system and database engine. Under the shared responsibility model, which of the following is true?

A.The customer must patch the operating system of the Cloud SQL instances.
B.Google Cloud is responsible for patching the operating system and database engine.
C.The customer is responsible for physical security of the data centers.
D.The customer is responsible for applying database engine patches.
AnswerB

For managed services, the provider handles underlying infrastructure maintenance.

Why this answer

Under the Google Cloud shared responsibility model, Google Cloud manages the underlying infrastructure, including patching the operating system and database engine for managed services like Cloud SQL. This is because Cloud SQL is a fully managed service where Google Cloud handles OS and database engine updates, ensuring security and compliance without customer intervention. The customer remains responsible for data, access management, and application-level configurations.

Exam trap

The trap here is that candidates confuse Cloud SQL (a managed service) with Compute Engine (IaaS), where the customer is responsible for OS and database patching, leading them to incorrectly select options A or D.

How to eliminate wrong answers

Option A is wrong because the customer is not responsible for patching the operating system of Cloud SQL instances; Google Cloud automatically manages OS patches as part of the managed service. Option C is wrong because physical security of data centers is solely Google Cloud's responsibility under the shared responsibility model, not the customer's. Option D is wrong because database engine patches are applied by Google Cloud for Cloud SQL, not by the customer, as the service handles version upgrades and security patches automatically.

Practice this question →
48
MCQeasy

A company is migrating its on-premises data center to Google Cloud. They want to avoid large upfront hardware costs and only pay for the resources they consume. Which cloud benefit does this represent?

A.Security
B.Pay-as-you-go pricing
C.High availability
D.Scalability
AnswerB

Pay-as-you-go eliminates large upfront hardware purchases and bills based on consumption.

Why this answer

Option B is correct because the scenario describes a shift from capital expenditure (CapEx) to operational expenditure (OpEx), which is the core of pay-as-you-go pricing. This model allows the company to avoid large upfront hardware costs and only pay for the compute, storage, and network resources actually consumed, aligning with Google Cloud's consumption-based billing model.

Exam trap

The trap here is that candidates often confuse 'scalability' with 'pay-as-you-go' because both involve resource adjustment, but scalability is about dynamic capacity changes, not the financial model of avoiding upfront costs.

How to eliminate wrong answers

Option A is wrong because security is a shared responsibility model in Google Cloud, not a financial model that avoids upfront costs; it does not address the consumption-based pricing described. Option C is wrong because high availability refers to redundant infrastructure and uptime guarantees (e.g., via multi-zonal deployments), not to the elimination of upfront hardware expenses. Option D is wrong because scalability is the ability to automatically adjust resources based on demand (e.g., using managed instance groups), which is a separate benefit from the pay-as-you-go pricing model that avoids initial capital outlay.

Practice this question →
49
Multi-Selectmedium

Which TWO of the following are key benefits of using a cloud provider like Google Cloud? (Choose exactly 2.)

Select 2 answers
A.Access to a global network infrastructure
B.Complete removal of physical security responsibilities
C.Reduced internet latency
D.Elimination of hardware costs
E.Economies of scale leading to lower costs
AnswersA, E

Cloud providers have data centers worldwide.

Why this answer

Option A is correct because cloud providers like Google Cloud operate a vast, globally distributed network of data centers interconnected via high-capacity fiber optic cables and private peering agreements. This global infrastructure allows customers to deploy workloads close to their users, reducing latency and improving performance without building their own network. Access to this network is a fundamental benefit of cloud computing, enabling global reach and reliability.

Exam trap

Google Cloud often tests the shared responsibility model to trick candidates into thinking that physical security is completely offloaded, when in fact customers still secure their own virtual assets and data.

Practice this question →
50
MCQeasy

A product manager wants to understand what 'latency' means for her company's cloud-hosted e-commerce application. Her developer explains that latency is critical for user experience. Which definition of latency is most accurate in this context?

A.Latency is the total amount of data that can be transferred per second between the user and the application
B.Latency is the time elapsed between a user action (click, page load) and receiving the server's response — directly affecting how fast and responsive the application feels
C.Latency is the percentage of time the application is available versus unavailable
D.Latency is the number of requests the server can handle simultaneously before performance degrades
AnswerB

This correctly defines latency in the context of web applications. High latency makes applications feel slow and unresponsive. For e-commerce, high latency directly increases cart abandonment. Techniques like CDN, edge computing, and database query optimization reduce latency.

Why this answer

Option B is correct because latency in the context of a cloud-hosted e-commerce application specifically measures the round-trip time from a user action (such as a click or page load) to the receipt of the server's response. This directly impacts perceived responsiveness and user experience, as higher latency leads to noticeable delays in interactions like adding items to a cart or checking out.

Exam trap

Google Cloud often tests the distinction between latency and throughput, trapping candidates who confuse the total data transfer rate (bandwidth) with the time delay of a single transaction.

How to eliminate wrong answers

Option A is wrong because it describes throughput (bandwidth), not latency; throughput measures data transfer rate per second, while latency measures delay. Option C is wrong because it defines availability (uptime), often expressed as a percentage of time the service is operational, not latency. Option D is wrong because it describes concurrency or capacity (the number of simultaneous requests a server can handle), which is related to scalability and load handling, not the time delay of a single request-response cycle.

Practice this question →
51
MCQmedium

A company's on-premises applications occasionally need more compute capacity than their own infrastructure can provide (during seasonal peaks). They want to use cloud resources to handle the overflow traffic while keeping base workloads on-premises. Which cloud architectural pattern describes this?

A.Cloud migration — moving workloads from on-premises to cloud permanently.
B.Cloud bursting — using cloud capacity to handle overflow when on-premises resources are exhausted.
C.Multi-cloud — using multiple cloud providers for redundancy.
D.Disaster recovery — using cloud as a failover site when on-premises fails.
AnswerB

Cloud bursting dynamically extends on-premises capacity with cloud resources during peaks. It's an elastic hybrid pattern where cloud supplements (not replaces) on-premises infrastructure.

Why this answer

Option B is correct because cloud bursting is the architectural pattern specifically designed to handle overflow traffic by dynamically provisioning cloud resources when on-premises capacity is exhausted. This allows the company to maintain base workloads on their own infrastructure while seamlessly scaling into the cloud during seasonal peaks, typically using orchestration tools like AWS Auto Scaling or Azure VM Scale Sets to burst into a virtual private cloud (VPC) or virtual network (VNet).

Exam trap

Google Cloud often tests the distinction between cloud bursting and disaster recovery, where candidates mistakenly choose disaster recovery because both involve using cloud resources as a backup, but disaster recovery is for failover during outages, not for handling peak demand.

How to eliminate wrong answers

Option A is wrong because cloud migration involves permanently moving all workloads to the cloud, which contradicts the requirement to keep base workloads on-premises. Option C is wrong because multi-cloud refers to using multiple cloud providers for redundancy or avoiding vendor lock-in, not for handling overflow from on-premises infrastructure. Option D is wrong because disaster recovery is a failover mechanism for when on-premises systems completely fail, not for augmenting capacity during normal operations.

Practice this question →
52
MCQhard

A large financial institution has a hybrid cloud strategy with sensitive data stored on-premises and customer-facing applications in Google Cloud. They need low-latency access between on-premises databases and cloud applications, but also require encryption in transit and strong access controls. The on-premises network uses non-google-compatible routing protocols. Which solution should they implement?

A.Establish a Cloud VPN connection and use Identity-Aware Proxy for access
B.Directly peer with Google using Carrier Peering
C.Deploy Dedicated Interconnect, use Cloud VPN for encryption, and VPC Service Controls for access
D.Use a third-party VPN appliance on a Compute Engine instance and configure firewall rules
AnswerC

Dedicated Interconnect offers low latency, Cloud VPN adds encryption, and VPC Service Controls enforce access policies, meeting all requirements.

Why this answer

Option C is correct because Dedicated Interconnect provides the required low-latency, high-bandwidth connection between on-premises and Google Cloud, while Cloud VPN over the interconnect adds encryption in transit (IPsec) for sensitive data. VPC Service Controls enforce strong access controls by preventing data exfiltration from managed services, and the solution works with non-Google-compatible routing protocols since Dedicated Interconnect uses BGP, which is standard and supported.

Exam trap

Google Cloud often tests the misconception that Cloud VPN alone is sufficient for low-latency hybrid connections, but the trap here is that Cloud VPN uses the public internet, which cannot guarantee low latency, whereas Dedicated Interconnect provides a dedicated, low-latency link.

How to eliminate wrong answers

Option A is wrong because Cloud VPN alone cannot meet the low-latency requirement (it traverses the public internet and adds latency) and Identity-Aware Proxy controls access to applications, not network-level data exfiltration. Option B is wrong because Carrier Peering provides direct peering but does not include encryption in transit (no IPsec) and typically lacks the strong access controls needed for sensitive data. Option D is wrong because a third-party VPN appliance on Compute Engine still uses the public internet for the VPN tunnel, failing the low-latency requirement, and firewall rules alone do not provide the granular data exfiltration controls of VPC Service Controls.

Practice this question →
53
MCQmedium

When choosing a Google Cloud region for a new application, which factors should primarily drive the decision?

A.Always choose `us-central1` because it has the most services and lowest cost.
B.Proximity to users (for low latency), data residency requirements, available services in the region, and pricing.
C.The alphabetical order of region names — 'a' regions are newer and more stable.
D.Google assigns regions automatically based on the user's IP address at account creation.
AnswerB

These four factors drive region selection. Users in Tokyo should be served by an Asia-Pacific region. EU GDPR requires EU data residency. Some services (like specific GPU types) are only in certain regions.

Why this answer

Option B is correct because selecting a Google Cloud region requires balancing multiple factors: proximity to users minimizes latency for real-time applications; data residency ensures compliance with local regulations (e.g., GDPR); service availability varies by region (e.g., some regions lack GPUs or specific machine types); and pricing differs due to regional operational costs. Google Cloud's global infrastructure is designed to let customers choose regions based on these trade-offs, not on a single criterion.

Exam trap

Google Cloud often tests the misconception that a single 'best' region exists (like us-central1) or that region selection is automated, when in reality it requires a deliberate trade-off analysis of latency, compliance, service availability, and cost.

How to eliminate wrong answers

Option A is wrong because us-central1 does not always have the most services (e.g., some newer services launch first in other regions) and its pricing is not universally the lowest; costs vary by resource type and region. Option C is wrong because alphabetical order has no correlation with region stability or age; Google Cloud regions are named geographically (e.g., us-west1, europe-west4) and stability depends on deployment maturity, not naming. Option D is wrong because Google Cloud does not automatically assign regions based on user IP; region selection is a manual decision made during resource creation, and IP-based assignment would violate customer control over data residency and latency requirements.

Practice this question →
54
MCQmedium

A company hosts a web application that receives requests from users globally. To handle failures, they run three identical copies of their application behind a load balancer. When one copy fails, the load balancer automatically stops sending traffic to it. What load balancing feature enables this?

A.Round-robin distribution — traffic cycles evenly across all instances regardless of health.
B.Health checks — the load balancer probes backend instances and removes unhealthy ones from the serving pool.
C.SSL termination — decrypting HTTPS traffic before forwarding to backends.
D.Session affinity — routing the same user to the same backend instance.
AnswerB

Health checks detect failed backends by sending periodic probe requests. Unhealthy backends are removed from rotation; remaining healthy instances absorb the traffic. This is automatic fault detection.

Why this answer

Health checks are the load balancing feature that proactively monitors the status of backend instances by sending periodic probes (e.g., HTTP GET requests, TCP SYN packets) to a configured endpoint. If a health check fails (e.g., non-2xx response, timeout, or connection refused), the load balancer automatically marks that instance as unhealthy and stops routing new traffic to it, ensuring high availability and fault tolerance.

Exam trap

Cisco often tests the distinction between traffic distribution algorithms (like round-robin) and health monitoring features, leading candidates to mistakenly believe that round-robin inherently handles failures because it 'spreads traffic evenly,' when in fact it has no awareness of instance health.

How to eliminate wrong answers

Option A is wrong because round-robin distribution is a traffic routing algorithm that cycles requests evenly across all instances regardless of their health; it does not detect or react to failures, so it cannot automatically stop sending traffic to a failed copy. Option C is wrong because SSL termination is a feature that offloads the decryption of HTTPS traffic from backend instances to the load balancer; it has no role in monitoring instance health or removing failed instances from the serving pool. Option D is wrong because session affinity (sticky sessions) ensures that requests from the same user are directed to the same backend instance based on a cookie or source IP; it does not provide any failure detection or automatic removal of unhealthy instances.

Practice this question →
55
MCQhard

A company uses two different public cloud providers (AWS for their North American operations and Google Cloud for their European operations) to meet data residency requirements and avoid vendor lock-in. Which deployment model does this represent?

A.Hybrid cloud
B.Multi-cloud
C.Multi-region
D.Distributed cloud
AnswerB

Multi-cloud is the deliberate use of two or more different public cloud providers. Using AWS for North America and Google Cloud for Europe is a classic multi-cloud strategy.

Why this answer

This scenario describes using two distinct public cloud providers (AWS and Google Cloud) to meet data residency and avoid vendor lock-in, which is the definition of a multi-cloud deployment model. Multi-cloud involves using multiple public cloud services from different vendors, as opposed to combining public and private infrastructure (hybrid cloud) or simply deploying across multiple regions within a single provider.

Exam trap

Cisco often tests the distinction between multi-cloud and hybrid cloud, where candidates mistakenly choose hybrid cloud because they confuse 'multiple clouds' with 'mixed public and private infrastructure.'

How to eliminate wrong answers

Option A is wrong because hybrid cloud refers to a mix of private (on-premises) and public cloud infrastructure, not multiple public cloud providers. Option C is wrong because multi-region means deploying resources across multiple geographic regions within a single cloud provider, not across different providers. Option D is wrong because distributed cloud involves a single public cloud provider extending its services to different physical locations (e.g., edge or on-premises), not using multiple independent cloud vendors.

Practice this question →
56
MCQeasy

A small business wants to host a static website with minimal management overhead. They want high availability and low cost. Which Google Cloud service should they use?

A.Compute Engine with Apache
B.Cloud Storage with a load balancer
C.App Engine Standard Environment
D.Cloud Run
AnswerB

Cloud Storage hosts static content and the load balancer provides HTTPS and high availability.

Why this answer

Cloud Storage with a load balancer is ideal for hosting a static website because it serves content directly from object storage, requires no server management, and the load balancer provides high availability by distributing traffic across multiple regions. This combination offers low cost (pay only for storage and egress) and minimal operational overhead, as there are no virtual machines or application runtimes to maintain.

Exam trap

Google Cloud often tests the misconception that any serverless or managed compute service (like App Engine or Cloud Run) is the best choice for static content, when in fact object storage with a load balancer is simpler and cheaper for purely static assets.

How to eliminate wrong answers

Option A is wrong because Compute Engine with Apache requires managing virtual machines, patching the OS, and configuring Apache, which contradicts the requirement for minimal management overhead and is not cost-effective for a static site. Option C is wrong because App Engine Standard Environment is designed for dynamic web applications with a runtime (e.g., Python, Java) and incurs costs for idle instances, making it overkill and more expensive for a static website. Option D is wrong because Cloud Run is a serverless container platform intended for request-driven applications, not static content; it adds unnecessary complexity and cost compared to directly serving files from Cloud Storage.

Practice this question →
57
Multi-Selecthard

A company's application uses a relational database for transactional data (orders, payments) and a separate NoSQL database for user session data and product catalog. Why might an architect choose two different database types for the same application?

Select 2 answers
A.Using two databases reduces costs by splitting storage between cheaper providers.
B.Different data patterns suit different database types — relational databases for ACID-compliant transactions, NoSQL for high-throughput flexible-schema lookups. This is called polyglot persistence.
C.Two databases provide automatic redundancy — if one fails, the other takes over.
D.Regulatory requirements mandate separating financial data from operational data in different databases.
AnswersB, D

Relational DBs (ACID, SQL, joins) handle orders/payments. NoSQL (flexible schema, horizontal scale, key-value) handles sessions and catalog. Using the right database type per workload is polyglot persistence.

Why this answer

Option B is correct because it describes polyglot persistence, where an application uses multiple database types to handle different data patterns optimally. Relational databases enforce ACID properties (Atomicity, Consistency, Isolation, Durability) essential for transactional data like orders and payments, ensuring data integrity. NoSQL databases, such as document stores or key-value stores, provide high throughput and flexible schemas ideal for session data and product catalogs, which require fast lookups and can tolerate eventual consistency.

Exam trap

The trap here is that candidates confuse using multiple databases for redundancy (Option C) with polyglot persistence, but redundancy requires identical database systems with replication, not different types that cannot interoperate for failover.

Practice this question →
58
MCQhard

A financial services firm is migrating a legacy application to Google Cloud. The application requires static IP addresses that must not change during migration. The network team wants to minimize downtime. Which migration strategy should they use?

A.Use a global load balancer and update DNS
B.Lift and shift the application to Compute Engine with new IP addresses
C.Use Cloud Interconnect to extend the on-premises network
D.Set up a Cloud VPN tunnel and migrate using the same IP addresses
AnswerD

Cloud VPN allows extending the on-premises network to Google Cloud, preserving IP addresses.

Why this answer

Option D is correct because a Cloud VPN tunnel can extend the on-premises network into Google Cloud, allowing the legacy application to retain its existing static IP addresses during migration. By establishing a VPN tunnel, traffic can be routed seamlessly between environments, minimizing downtime as the application is migrated without requiring IP address changes.

Exam trap

The trap here is that candidates often confuse connectivity solutions (like Cloud Interconnect or VPN) with IP address preservation, mistakenly thinking that a dedicated connection alone solves the static IP requirement, when in fact the VPN's ability to extend the same subnet is the key enabler.

How to eliminate wrong answers

Option A is wrong because a global load balancer distributes traffic across regions but does not preserve static IP addresses for the application itself; it introduces a new frontend IP and requires DNS changes, which can cause downtime. Option B is wrong because lifting and shifting to Compute Engine with new IP addresses would break the application's dependency on static IPs, requiring reconfiguration and likely causing extended downtime. Option C is wrong because Cloud Interconnect provides a dedicated connection for bandwidth and reliability but does not inherently allow the application to keep its existing IP addresses; it is a connectivity solution, not an IP migration strategy.

Practice this question →
59
MCQhard

What is DevOps, and how does cloud adoption reinforce DevOps practices?

A.DevOps is a specific programming language designed for cloud applications.
B.DevOps is a culture of collaboration between development and operations teams, reinforced by cloud's managed CI/CD, infrastructure-as-code, and on-demand environments.
C.DevOps means developers take over all IT operations responsibilities, eliminating operations teams.
D.DevOps is only applicable to software startups — traditional enterprises use ITIL for operations.
AnswerB

Cloud enables DevOps by providing tools (Cloud Build, Terraform, Container Registry) and on-demand environments for testing — reducing friction between code and production deployment.

Why this answer

DevOps is a cultural and technical movement that emphasizes collaboration, automation, and integration between software development (Dev) and IT operations (Ops) teams. Cloud adoption reinforces DevOps by providing managed CI/CD services (e.g., AWS CodePipeline, Azure DevOps), infrastructure-as-code tools (e.g., Terraform, AWS CloudFormation), and on-demand environments that enable rapid provisioning, testing, and deployment. This synergy reduces manual overhead and accelerates the software delivery lifecycle.

Exam trap

Cisco often tests the misconception that DevOps is a tool or a role rather than a culture and set of practices, and that cloud adoption is merely about hosting, ignoring how cloud services like managed CI/CD and IaC directly enable DevOps automation.

How to eliminate wrong answers

Option A is wrong because DevOps is not a programming language; it is a set of practices and a cultural philosophy, whereas cloud applications are built using languages like Python, Java, or Go. Option C is wrong because DevOps does not eliminate operations teams; it integrates development and operations roles, often with shared responsibilities, and operations expertise remains critical for monitoring, security, and reliability. Option D is wrong because DevOps is applicable to organizations of all sizes, including traditional enterprises, and ITIL can coexist with DevOps practices (e.g., ITIL for service management, DevOps for agile delivery); the statement that DevOps is only for startups is a common misconception.

Practice this question →
60
MCQmedium

A company runs a batch processing job every night that takes 6 hours on a fixed number of virtual machines. They want to reduce costs without increasing job duration. Which strategy should they use?

A.Use preemptible VMs
B.Increase the number of VMs
C.Purchase committed use contracts
D.Use larger persistent disks
AnswerA

Preemptible VMs are much cheaper and can handle batch jobs if the job is fault-tolerant.

Why this answer

Option C is correct because preemptible VMs are up to 80% cheaper and suitable for fault-tolerant batch jobs. Option A is wrong because persistent disks add cost. Option B is wrong because more VMs increase cost.

Option D is wrong because it is a reserved capacity commitment, which is for predictable workloads and not cheaper for short jobs.

Practice this question →
61
MCQeasy

What is an API (Application Programming Interface), and why is it fundamental to cloud services and digital transformation?

A.An API is a type of database that stores application settings.
B.An API is a standardized interface that allows software components to communicate, enabling programmatic access to cloud services and digital ecosystem integration.
C.An API is a security protocol that encrypts data between applications.
D.APIs are only used by large technology companies and are too complex for small businesses.
AnswerB

APIs are the 'connective tissue' of digital systems. Cloud services expose APIs for programmatic control. Businesses build ecosystems by composing and exposing APIs — the foundation of digital transformation.

Why this answer

Option B is correct because an API is a standardized interface (often RESTful, using HTTP methods like GET, POST, PUT, DELETE) that enables software components to communicate and exchange data. In cloud services, APIs are fundamental because they allow programmatic access to resources (e.g., AWS EC2, Azure VMs) without manual intervention, forming the backbone of automation, orchestration, and integration in digital transformation initiatives.

Exam trap

Google Cloud often tests the misconception that an API is a database or a security protocol, so candidates must remember that APIs are primarily about standardized communication and programmability, not data storage or encryption.

How to eliminate wrong answers

Option A is wrong because an API is not a database; it is an interface for communication, whereas databases (e.g., SQL, NoSQL) store and manage data. Option C is wrong because an API is not inherently a security protocol; while APIs can use security measures like OAuth 2.0 or TLS, their primary purpose is interoperability, not encryption. Option D is wrong because APIs are used by organizations of all sizes, including small businesses, to integrate cloud services, SaaS applications, and microservices, and are not exclusive to large technology companies.

Practice this question →
62
MCQmedium

A solutions architect is explaining why using managed cloud database services (like Cloud SQL or Cloud Spanner) is preferable to running a database on a self-managed virtual machine in most cases. What is the primary operational advantage of managed database services over self-managed databases on VMs?

A.Managed databases are always significantly cheaper than self-managed databases on VMs
B.Managed database services automate operational tasks like backups, patching, HA failover, and scaling — freeing engineering teams to focus on application development rather than database administration
C.Managed databases guarantee better query performance than self-managed databases for all workload types
D.Managed databases provide stronger data encryption than self-managed databases on VMs
AnswerB

This is the core value proposition of managed databases. The cloud provider handles: automated daily backups with point-in-time recovery, OS and database software patching, automatic failover for high availability, and storage scaling. Engineering teams avoid the specialized DBA work required for self-managed databases.

Why this answer

Option B is correct because managed database services like Cloud SQL and Cloud Spanner abstract away the operational overhead of database administration. They automate critical tasks such as automated backups, patch management, high-availability failover, and horizontal scaling, which allows engineering teams to focus on application logic rather than managing database servers, replication, or storage.

Exam trap

Cisco often tests the misconception that managed services are always cheaper or always faster, when the primary advantage is operational automation and reduced administrative burden, not cost or performance guarantees.

How to eliminate wrong answers

Option A is wrong because managed databases are not always significantly cheaper; they often have higher per-hour costs than self-managed VMs, though they can reduce total cost of ownership by eliminating administrative labor and infrastructure overhead. Option C is wrong because managed databases do not guarantee better query performance for all workload types; performance depends on instance size, query optimization, and workload characteristics, and self-managed databases can be tuned more aggressively for specific use cases. Option D is wrong because both managed and self-managed databases can implement strong encryption (e.g., AES-256 at rest, TLS 1.3 in transit); encryption is a configuration choice, not an inherent advantage of managed services.

Practice this question →
63
MCQeasy

A developer needs to run a custom analysis script on a large dataset once a month. The script runs for about 10 minutes. They want to avoid provisioning servers and only pay for the actual compute time used. Which Google Cloud compute option should they choose?

A.App Engine Standard Environment
B.Compute Engine preemptible VM
C.Google Kubernetes Engine with a single pod
D.Cloud Functions
AnswerD

Cloud Functions is serverless, execute on demand, and charge only for compute time.

Why this answer

Cloud Functions is the correct choice because it is a serverless, event-driven compute service that automatically scales to zero when not in use, charging only for the actual compute time consumed during execution. The 10-minute monthly script fits within Cloud Functions' 9-minute maximum timeout (recently extended to 60 minutes for HTTP-triggered functions in some regions), making it ideal for infrequent, short-lived tasks without provisioning servers.

Exam trap

Google Cloud often tests the misconception that serverless options like Cloud Functions cannot handle long-running tasks, but the 9-minute (or extended 60-minute) timeout is sufficient for many batch jobs, leading candidates to incorrectly choose preemptible VMs or Kubernetes for what is effectively a short-lived, infrequent workload.

How to eliminate wrong answers

Option A is wrong because App Engine Standard Environment requires an app to be deployed and running continuously, incurring costs even when idle, and it is designed for always-on web applications rather than infrequent batch jobs. Option B is wrong because Compute Engine preemptible VMs are short-lived instances that can be terminated at any time within 24 hours, requiring manual provisioning and management, and they charge per second of uptime even if the script runs only once a month. Option C is wrong because Google Kubernetes Engine with a single pod still requires a cluster of nodes to be provisioned and running, leading to continuous costs for the underlying VMs, and it introduces unnecessary orchestration overhead for a simple monthly script.

Practice this question →
64
MCQmedium

A company's finance team wants to understand why their cloud bills vary significantly month to month, unlike their fixed on-premises IT costs. Which fundamental cloud pricing characteristic explains this variability?

A.Cloud providers change their prices frequently, causing unpredictable costs
B.Consumption-based pricing means cloud costs scale directly with actual usage, unlike fixed on-premises costs
C.Cloud providers apply hidden fees that vary randomly each month
D.Cloud costs are fixed like on-premises costs; the variability must be caused by billing errors
AnswerB

This is the correct explanation. Cloud is utility-like pricing: a compute-heavy month costs more than a quiet month. Finance teams must shift from thinking about fixed IT budgets to variable cost management tied to business activity levels.

Why this answer

Option B is correct because cloud computing operates on a consumption-based (pay-as-you-go) pricing model, where costs are directly tied to the amount of resources consumed (e.g., compute hours, storage GB, data transfer). Unlike fixed on-premises IT costs, which are incurred regardless of actual usage (e.g., hardware depreciation, facility leases), cloud bills fluctuate as usage scales up or down. This fundamental characteristic explains the month-to-month variability observed by the finance team.

Exam trap

Google Cloud often tests the misconception that cloud pricing is unpredictable or error-prone, when in fact the variability is a deliberate feature of consumption-based pricing, not a flaw or hidden fee.

How to eliminate wrong answers

Option A is wrong because cloud providers do not change their prices frequently; instead, they typically announce price reductions or new tiers well in advance, and pricing is stable over short periods. Option C is wrong because cloud providers are transparent about their pricing models and do not apply hidden fees that vary randomly; all charges are itemized in the billing dashboard based on metered usage. Option D is wrong because cloud costs are not fixed like on-premises costs; the variability is a direct result of consumption-based pricing, not billing errors, and cloud billing systems are highly accurate.

Practice this question →
65
MCQmedium

A company is planning a cloud migration and wants to understand the difference between 'lift and shift' and 'cloud-native' approaches. Which statement correctly distinguishes these two migration strategies?

A.Lift and shift uses containers; cloud-native uses virtual machines.
B.Lift and shift moves applications to the cloud with minimal changes; cloud-native re-architects applications to leverage cloud-specific features and managed services.
C.Lift and shift is only possible for new applications; cloud-native is for existing applications.
D.Lift and shift costs more long-term; cloud-native costs more short-term due to licensing.
AnswerB

Lift and shift is fast with minimal changes but doesn't fully leverage cloud. Cloud-native requires more effort but maximizes benefits like autoscaling, managed databases, and serverless.

Why this answer

Option B is correct because 'lift and shift' (rehosting) involves moving applications to the cloud with minimal or no changes, often using Infrastructure as a Service (IaaS) to replicate the on-premises environment. In contrast, 'cloud-native' (re-architecting) redesigns applications to use cloud-specific features like auto-scaling, managed databases, and serverless compute, fully leveraging the cloud's elasticity and pay-as-you-go model.

Exam trap

The trap here is that candidates often confuse the tools (containers vs. VMs) with the strategy, assuming lift and shift always uses containers and cloud-native uses VMs, when in fact the opposite is true for typical implementations.

How to eliminate wrong answers

Option A is wrong because lift and shift typically uses virtual machines (VMs) to replicate on-premises infrastructure, not containers; cloud-native applications often use containers (e.g., Docker) and orchestration (e.g., Kubernetes) for microservices, not VMs. Option C is wrong because lift and shift is primarily used for existing legacy applications to migrate quickly, while cloud-native is often applied to new applications but can also involve re-architecting existing ones. Option D is wrong because lift and shift can lead to higher long-term costs due to inefficient resource utilization and licensing, while cloud-native may have higher initial development costs but lower operational costs over time due to optimized resource usage and managed services.

Practice this question →
66
MCQmedium

A startup needs to quickly deploy a web application with minimal infrastructure management. They want to focus on code, not servers. Which Google Cloud service model is most appropriate?

A.Software as a Service (SaaS) using Gmail
B.Function as a Service (FaaS) using Cloud Functions
C.Infrastructure as a Service (IaaS) using Compute Engine
D.Platform as a Service (PaaS) using App Engine
AnswerD

App Engine automatically scales and manages the runtime environment, allowing developers to focus solely on code.

Why this answer

App Engine is a fully managed Platform as a Service (PaaS) that abstracts away the underlying infrastructure, allowing developers to deploy web applications without managing servers or operating systems. It automatically handles scaling, load balancing, and patching, which aligns with the startup's requirement to focus on code rather than infrastructure management.

Exam trap

Google Cloud often tests the distinction between PaaS and FaaS by presenting a scenario that requires a full web application, where candidates mistakenly choose FaaS (Cloud Functions) because they confuse 'serverless' with 'no infrastructure management,' ignoring that FaaS is unsuitable for long-running HTTP applications with stateful sessions.

How to eliminate wrong answers

Option A is wrong because Gmail is a Software as a Service (SaaS) application, not a service model for deploying custom web applications; it provides no platform for code deployment or customization. Option B is wrong because Cloud Functions is a Function as a Service (FaaS) designed for event-driven, stateless functions, not for hosting a complete web application with persistent HTTP routing and session management. Option C is wrong because Compute Engine is Infrastructure as a Service (IaaS) that requires manual provisioning, configuration, and management of virtual machines, which contradicts the goal of minimizing infrastructure management.

Practice this question →
67
MCQmedium

A company is evaluating whether to use a content delivery network (CDN) for its e-commerce website. Which scenario would most benefit from CDN implementation?

A.A small business whose customers are all located within 10 kilometers of the company's single data center
B.An e-commerce site with global customers that serves high-resolution product images and videos, where page load speed directly affects conversion rates
C.A real-time financial trading application that requires unique, uncacheable price data delivered to a single city's traders
D.An internal HR system used exclusively by employees in the company's headquarters
AnswerB

This is the ideal CDN scenario: geographically distributed users, highly cacheable content (product images and videos), and a business metric (conversion rate) that is demonstrably sensitive to latency. CDN edges serve cached content locally, dramatically reducing page load times for international visitors.

Why this answer

Option B is correct because a CDN caches static content like high-resolution images and videos at edge servers geographically closer to users, reducing latency and improving page load speed. For an e-commerce site with global customers, faster load times directly boost conversion rates, making CDN implementation highly beneficial.

Exam trap

Cisco often tests the misconception that CDNs are a universal performance solution, but the trap here is that CDNs only benefit cacheable, static, or geographically distributed content, not real-time or localized traffic.

How to eliminate wrong answers

Option A is wrong because customers are all within 10 km of a single data center, so latency is already minimal and a CDN would provide negligible benefit. Option C is wrong because real-time financial trading data is unique and uncacheable, so a CDN cannot serve stale or cached content, and the single-city user base doesn't require global distribution. Option D is wrong because an internal HR system used only by employees at headquarters has no geographic distribution or performance issues that a CDN would solve.

Practice this question →
68
MCQeasy

Which term describes the model where the cloud provider is responsible for the security of the cloud infrastructure, while the customer is responsible for security within their own cloud environment (data, applications, access management)?

A.Zero trust security model
B.Shared responsibility model
C.Defense in depth strategy
D.Identity federation model
AnswerB

The shared responsibility model defines that Google Cloud secures the infrastructure ('security of the cloud') while customers secure their data and applications ('security in the cloud').

Why this answer

The shared responsibility model defines the division of security responsibilities between the cloud provider and the customer. Google secures the physical infrastructure, hardware, hypervisor, and core services. The customer secures what they put in the cloud: data classification, access control, application security, network configuration, and compliance.

The boundary between provider and customer responsibility varies by service model (IaaS vs. PaaS vs. SaaS).

Practice this question →
69
MCQmedium

A company runs a critical application on Compute Engine in us-central1. They plan to create a disaster recovery (DR) site in us-west1 that can be activated within minutes if the primary region fails. What is the most cost-effective DR strategy that meets the recovery time objective (RTO) of 30 minutes?

A.Cold standby with regular backups to Cloud Storage.
B.Warm standby in us-west1 with preemptible VMs and persistent disk snapshots.
C.Active-active deployment in both regions with load balancing.
D.Use a managed instance group in us-west1 with replication from the primary.
AnswerB

Snapshots can be used to create disks quickly, and preemptible VMs reduce cost.

Why this answer

Option B is correct because a warm standby using preemptible VMs and persistent disk snapshots provides a cost-effective DR solution that can be activated within minutes. Preemptible VMs are significantly cheaper than regular VMs, and persistent disk snapshots stored in Cloud Storage can be restored quickly to create new disks in us-west1, meeting the 30-minute RTO without the high cost of an always-on active-active deployment.

Exam trap

Google Cloud often tests the misconception that 'warm standby' always means running full instances, but here preemptible VMs combined with snapshots provide a low-cost warm standby that can be activated quickly, unlike cold standby which is too slow or active-active which is too expensive.

How to eliminate wrong answers

Option A is wrong because cold standby with regular backups to Cloud Storage typically has a much longer RTO (hours to days) due to the time required to restore full backups and provision infrastructure, failing the 30-minute RTO. Option C is wrong because active-active deployment in both regions with load balancing is the most expensive option, as it requires running full production capacity in both regions continuously, which is not cost-effective for a DR-only requirement. Option D is wrong because a managed instance group in us-west1 with replication from the primary implies continuous replication and running instances, which incurs ongoing costs similar to active-active, and does not leverage cost-saving measures like preemptible VMs or snapshot-based recovery.

Practice this question →
70
Multi-Selecteasy

Which THREE of the following are compute services offered by Google Cloud? (Choose exactly 3.)

Select 3 answers
A.Compute Engine
B.Cloud Functions
C.Cloud Storage
D.App Engine
E.Cloud SQL
AnswersA, B, D

IaaS virtual machines.

Why this answer

Compute Engine is a core Google Cloud compute service that provides virtual machines (VMs) running on Google's infrastructure. It allows you to create and manage VM instances with custom machine types, persistent disks, and networking configurations, making it a fundamental compute offering for running general-purpose workloads.

Exam trap

The trap here is that candidates confuse storage and database services (Cloud Storage, Cloud SQL) with compute services, because all are part of Google Cloud's core offerings, but only services that execute code or run applications qualify as compute.

Practice this question →
71
MCQeasy

A developer wants to run her application code without managing any servers, operating systems, or runtime environments. She wants to focus entirely on writing business logic. Which cloud service model best fits this requirement?

A.Infrastructure as a Service (IaaS), where the developer provisions virtual machines and installs the runtime
B.Platform as a Service (PaaS), where the developer deploys code to a managed platform that handles the OS and runtime
C.Serverless / Functions as a Service (FaaS), where the developer writes and deploys code functions and the provider manages all underlying infrastructure automatically
D.Software as a Service (SaaS), where the developer uses a fully managed application built by the cloud provider
AnswerC

FaaS/serverless is the model where the developer's only concern is the business logic in the function. There are no servers to configure, no OS to patch, no capacity to plan. The runtime is automatically managed and scaled by the provider.

Why this answer

Serverless/FaaS (Option C) is the correct choice because it abstracts away all server, OS, and runtime management, allowing the developer to deploy individual functions that execute in response to events. The cloud provider automatically scales and manages the underlying infrastructure, so the developer writes only business logic without provisioning or patching anything.

Exam trap

Google Cloud often tests the distinction between PaaS and FaaS by describing a scenario where the developer wants to avoid managing servers and runtimes, leading candidates to choose PaaS because it abstracts the OS, but the key difference is that FaaS also eliminates runtime management and allows function-level granularity, which PaaS does not fully achieve.

How to eliminate wrong answers

Option A is wrong because IaaS requires the developer to provision and manage virtual machines, install the OS, configure the runtime, and handle patching—contradicting the requirement to avoid server and OS management. Option B is wrong because PaaS still involves managing the runtime environment (e.g., choosing a runtime version, configuring scaling rules) and the developer must deploy an entire application, not just functions; it does not eliminate all infrastructure concerns as FaaS does. Option D is wrong because SaaS provides a fully built application that the developer uses, not a platform for writing and deploying custom business logic.

Practice this question →
72
Multi-Selecteasy

Which TWO of the following are common use cases for deploying workloads to the cloud? (Choose 2)

Select 2 answers
A.High-frequency trading requiring microsecond latency
B.Air-gapped, classified workloads with no internet connection
C.Running a legacy mainframe application that requires dedicated hardware
D.Running a global SaaS application for customers worldwide
E.Data backup and disaster recovery
AnswersD, E

Cloud enables global distribution and easy scaling.

Why this answer

Option D is correct because cloud platforms like AWS, Azure, and GCP provide global infrastructure with multiple regions and edge locations, enabling SaaS applications to serve customers worldwide with low latency via CDNs and load balancers. Option E is correct because cloud storage services (e.g., Amazon S3, Azure Blob Storage) offer durable, cost-effective off-site backup and automated disaster recovery through replication across Availability Zones or Regions, often with 99.999999999% durability.

Exam trap

Google Cloud often tests the misconception that 'cloud is suitable for all workloads,' but the trap here is that candidates may select options like A or C because they sound like 'advanced' use cases, failing to recognize that cloud's shared infrastructure and network dependency make it unsuitable for ultra-low-latency or air-gapped scenarios.

Practice this question →
73
MCQhard

An architect is evaluating whether to use a relational database or a NoSQL database for a new application that must store product catalog data. Products have highly variable attributes — a book has ISBN, author, and genre; a bicycle has frame size, wheel diameter, and material. Which database characteristic makes NoSQL document databases advantageous for this use case?

A.NoSQL databases always provide faster query performance than relational databases for all use cases
B.NoSQL document databases support flexible schemas where each document can have different fields — making them well-suited for product catalogs where different product types have different attributes
C.NoSQL databases support ACID transactions better than relational databases, making them safer for product catalog updates
D.NoSQL databases are simpler to query because they don't require learning SQL
AnswerB

Schema flexibility is the key advantage here. In a relational table, all rows share the same columns — a shared schema requires either many NULL columns (one per possible attribute across all product types) or complex entity-attribute-value designs. Document databases store each product as a flexible JSON document, accommodating variable attributes naturally without schema changes.

Why this answer

NoSQL document databases, such as MongoDB, store data in flexible, schema-less documents (often JSON or BSON). This allows each document to have a different set of fields, making them ideal for product catalogs where a book and a bicycle have entirely different attributes (e.g., ISBN vs. frame size). Relational databases require a predefined schema with fixed columns, forcing you to either create many sparse columns or use complex join tables to handle variable attributes.

Exam trap

Google Cloud often tests the misconception that NoSQL is always faster or simpler than SQL, but the real advantage here is schema flexibility, not performance or ease of querying.

How to eliminate wrong answers

Option A is wrong because NoSQL databases do not always provide faster query performance; relational databases can be faster for complex joins and aggregations, and performance depends on the specific use case and indexing. Option C is wrong because NoSQL databases typically relax ACID guarantees (e.g., eventual consistency) to achieve scalability, while relational databases offer stronger ACID transactions, making them safer for critical updates. Option D is wrong because NoSQL databases often require learning their own query languages or APIs (e.g., MongoDB's aggregation pipeline), and SQL is a standardized, widely understood language; the simplicity of querying depends on the task, not the database type.

Practice this question →
74
Drag & Dropmedium

Drag and drop the steps to set up a Cloud Storage bucket with uniform bucket-level access into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

The process begins with accessing Cloud Storage, then creating a bucket, naming it, selecting storage settings, and enabling uniform access control.

Practice this question →
75
MCQhard

A company's cloud architect explains that their new system uses 'eventual consistency' for some data operations. A business stakeholder asks why the system won't always show the most up-to-date data immediately. What is the trade-off being made?

A.Eventual consistency is a bug — the system should be fixed to always show current data.
B.Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously.
C.Eventual consistency means data is eventually deleted, which reduces storage costs.
D.Eventual consistency only applies to deleted data — new data always appears immediately.
AnswerB

In eventually consistent systems, writes propagate asynchronously. All replicas converge to the same value within a short time window. This enables higher throughput and availability than strong consistency, which requires synchronous coordination across all nodes.

Why this answer

Option B is correct because eventual consistency is a deliberate design choice in distributed systems (such as those using Amazon DynamoDB or Apache Cassandra) where the system prioritizes high availability and low-latency reads/writes over immediate consistency. Under the hood, data updates propagate asynchronously to replicas, and all nodes will eventually converge to the same value via mechanisms like gossip protocols or vector clocks, but there is a window where stale data may be returned. This trade-off is fundamental to the CAP theorem, which states that in a distributed data store, you can only guarantee two of Consistency, Availability, and Partition Tolerance simultaneously.

Exam trap

Google Cloud often tests the misconception that eventual consistency is a fault or a temporary bug, when in fact it is a deliberate design trade-off to achieve high availability and partition tolerance in distributed systems.

How to eliminate wrong answers

Option A is wrong because eventual consistency is not a bug; it is a deliberate architectural trade-off defined in the CAP theorem, and fixing it to always show current data would require sacrificing availability or partition tolerance. Option C is wrong because eventual consistency does not mean data is eventually deleted; it refers to the timing of data propagation across replicas, not data retention or deletion policies. Option D is wrong because eventual consistency applies to all data operations (writes, updates, deletes), not just deleted data; new data may also not appear immediately on all nodes until the asynchronous replication completes.

Practice this question →
Page 1 of 2 · 98 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Fundamental Cloud Concepts questions.

Start 20-question session