Cloud Digital Leader Fundamental cloud concepts Practice Test 4 — 15 Questions

Question 1

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?

Accepted Answer

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. 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.

Answer

Eventual consistency is acceptable because users will eventually see each other's edits after a short delay, and this enables higher performance

Answer

Consistency doesn't matter for this use case because each user edits different parts of the document

Answer

This workload requires a relational database because only SQL can handle concurrent user edits correctly

Question 2

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?

Accepted Answer

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. 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.

Answer

A region is a single data center building; an availability zone is a floor within that building

Answer

A region is equivalent to an availability zone; both terms refer to a single data center

Answer

An availability zone is larger than a region and spans multiple geographic areas for global redundancy

Question 3

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?

Accepted Answer

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. 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.

Answer

NoSQL databases always provide faster query performance than relational databases for all use cases

Answer

NoSQL databases support ACID transactions better than relational databases, making them safer for product catalog updates

Answer

NoSQL databases are simpler to query because they don't require learning SQL

Question 4

A company's IT team is planning its network architecture for a Google Cloud deployment. They want to ensure that their development, staging, and production environments are completely isolated from each other at the network level. What is the most effective way to achieve this isolation in Google Cloud?

Accepted Answer

Deploying each environment (dev, staging, prod) in separate VPC networks — optionally in separate Google Cloud projects — to achieve complete network isolation with no default connectivity between environments. Option B is correct because deploying each environment in separate VPC networks (optionally in separate projects) provides complete network isolation by default. In Google Cloud, VPC networks are isolated entities with no inherent peering or connectivity; traffic between them requires explicit VPC peering or VPN configurations. This ensures that development, staging, and production environments cannot communicate at the network layer unless intentionally connected, meeting the requirement for complete isolation.

Answer

Using separate subnets within the same VPC for each environment, with firewall rules blocking cross-subnet traffic

Answer

Using different IP address ranges for each environment within the same network

Answer

Using Cloud IAM to restrict developers from accessing production resources, which achieves the same isolation as network separation

Question 5

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?

Accepted Answer

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. 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.

Answer

Scaling up adds more servers to handle increased load; scaling out makes each server more powerful by adding CPU and RAM

Answer

Both scaling up and scaling out describe the same approach — adding more cloud resources to handle increased demand

Answer

Scaling up is only possible in cloud environments; on-premises systems can only scale out

Question 6

A company is planning a cloud architecture and needs to decide between a monolithic application design and a microservices architecture. What is the most significant operational trade-off between these two approaches in a cloud environment?

Accepted Answer

Microservices enable independent deployment and scaling per component but introduce distributed systems complexity (network overhead, distributed tracing, service discovery, consistency challenges); monoliths are simpler to operate but scale and deploy as a unit. Monoliths are simpler to develop, test, and deploy initially but scale as a unit and create tight coupling — a change to one part requires deploying the whole application. Microservices enable independent deployment and scaling of components but introduce distributed systems complexity (network calls, service discovery, distributed tracing, eventual consistency). Neither is universally better — the trade-off depends on team size, domain complexity, and operational maturity.

Answer

Monoliths can only run on-premises, while microservices were designed specifically for cloud environments

Answer

Microservices are always cheaper to operate in the cloud because each service uses fewer resources than a monolith

Answer

Monolithic applications cannot be scaled horizontally in cloud environments

Question 7

A business analyst needs to understand why cloud services bill differently for compute (VMs) versus object storage. Compute VMs are billed per second while they are running; Cloud Storage is billed per GB-month of data stored. Which cloud pricing principle explains why these billing units are different?

Accepted Answer

Cloud resources are billed based on their natural unit of consumption: compute time for VMs (per second running) and data volume over time for storage (per GB-month) — matching billing to how each resource is actually consumed. Option B is correct because cloud providers align billing units with the natural consumption pattern of each resource. Compute VMs consume CPU and memory continuously while running, making per-second billing the most granular and fair measure of actual usage. Object storage, by contrast, incurs cost primarily from the capacity occupied over time, so billing per GB-month directly reflects the resource's persistent footprint. This principle ensures customers pay only for what they use, in the unit that matches the resource's operational behavior.

Answer

Cloud providers bill different resources differently to maximize revenue by charging the highest rates for the most-used services

Answer

Storage is charged per GB-month because cloud providers cannot measure storage usage per second accurately

Answer

The billing difference is a temporary situation; cloud providers are working toward a single universal billing unit for all services

Question 8

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?

Accepted Answer

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. 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).

Answer

Google's private backbone uses faster optical fiber than public internet service providers

Answer

Google's private backbone is free for customers while public internet egress incurs data transfer charges

Answer

Using Google's backbone eliminates the need for application-level TLS encryption because the network is inherently secure

Question 9

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?

Accepted Answer

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. 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.

Answer

Eventual consistency is sufficient; the game can show slightly stale state to some players without impact on gameplay

Answer

Consistency doesn't matter for gaming databases because games update state so frequently that any inconsistency resolves within milliseconds

Answer

The game should avoid databases entirely and use local storage on each player's device to ensure fast, consistent state access

Question 10

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?

Accepted Answer

VPC firewall rules that control inbound and outbound network traffic to VMs based on IP ranges, protocols, and ports. 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.

Answer

Cloud IAM policies that grant or deny permissions for external systems to access VM resources

Answer

Cloud Storage bucket policies that restrict access to VM storage volumes

Answer

DNS records that determine which internet addresses can resolve the VM's hostname

Question 11

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?

Accepted Answer

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). 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.

Answer

All three models (IaaS, PaaS, SaaS) require the same amount of customer-owned hardware since cloud supplements rather than replaces on-premises systems

Answer

Only SaaS eliminates the need for customer servers; IaaS and PaaS still require on-premises hardware for hybrid connectivity

Answer

The service model doesn't affect hardware ownership — hardware purchase decisions are independent of whether the company uses cloud services

Question 12

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?

Accepted Answer

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. 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.

Answer

Latency is the total amount of data that can be transferred per second between the user and the application

Answer

Latency is the percentage of time the application is available versus unavailable

Answer

Latency is the number of requests the server can handle simultaneously before performance degrades

Question 13

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?

Accepted Answer

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. 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.

Answer

Managed services are always less expensive than self-managed alternatives on VMs

Answer

Managed services guarantee better performance than self-managed deployments in all scenarios

Answer

Using managed services eliminates the need for any cloud expertise within the engineering team

Question 14

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?

Accepted Answer

Setting Cloud Billing budget alerts that notify stakeholders when spending approaches defined thresholds, enabling early detection and response to abnormal spending patterns. 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.

Answer

Requiring all cloud resource creation to go through a central IT approval process to prevent accidental VM creation

Answer

Reviewing cloud bills at the end of each month to identify cost anomalies and address them retroactively

Answer

Using Reserved Instances for all VM workloads to reduce per-hour costs, making accidental long-running VMs less expensive

Question 15

A company is deciding whether to store a large video archive (hundreds of terabytes, accessed perhaps twice per year for legal holds) in Google Cloud. Which Cloud Storage class is designed for this infrequently accessed, long-term archival use case?

Accepted Answer

Archive storage, which offers the lowest storage cost for data accessed less than once per year, accepting higher retrieval costs and latency for infrequent access. Archive storage is the correct choice because it is specifically designed for data that is accessed less than once per year, offering the lowest storage cost among Google Cloud Storage classes. This aligns perfectly with the use case of a large video archive accessed only twice per year for legal holds, where higher retrieval costs and latency are acceptable trade-offs for long-term preservation.

Answer

Standard storage, which provides the lowest latency and highest availability for frequently accessed data

Answer

Nearline storage, for data accessed approximately once per month

Answer

Coldline storage, for data accessed approximately once per quarter