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

Question 1

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?

Accepted Answer

Each service can be updated and deployed independently, enabling teams to release changes faster with lower risk and without full-application downtime.. 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.

Answer

Microservices always cost less than monolithic applications to run.

Answer

Microservices eliminate the need for testing because each service is small enough to be bug-free.

Answer

Microservices allow applications to run on any hardware without modification.

Question 2

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

Accepted Answer

Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances.. 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.

Answer

Horizontal scaling adds CPU/memory to existing servers; vertical scaling adds more servers.

Answer

Horizontal scaling is for databases only; vertical scaling is for web servers.

Answer

Horizontal scaling requires application downtime; vertical scaling is always online.

Question 3

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

Accepted Answer

An API is a standardized interface that allows software components to communicate, enabling programmatic access to cloud services and digital ecosystem integration.. 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.

Answer

An API is a type of database that stores application settings.

Answer

An API is a security protocol that encrypts data between applications.

Answer

APIs are only used by large technology companies and are too complex for small businesses.

Question 4

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?

Accepted Answer

The company has regulatory requirements that mandate physically dedicated (single-tenant) infrastructure or strict hardware-level isolation.. 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.

Answer

The company wants to pay less for cloud services.

Answer

The company wants the fastest possible internet speeds for their applications.

Answer

The company has fewer than 10 employees and doesn't need multi-tenant scale.

Question 5

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

Accepted Answer

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

Answer

DevOps is a specific programming language designed for cloud applications.

Answer

DevOps means developers take over all IT operations responsibilities, eliminating operations teams.

Answer

DevOps is only applicable to software startups — traditional enterprises use ITIL for operations.

Question 6

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?

Accepted Answer

Exactly 3 minutes and 47 seconds of compute time.. 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.

Answer

4 minutes (rounded up to the nearest minute).

Answer

1 hour (traditional cloud billing minimum).

Answer

5 minutes (rounded up to the nearest 5-minute interval).

Question 7

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

Accepted Answer

Proximity to users (for low latency), data residency requirements, available services in the region, and pricing.. 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.

Answer

Always choose `us-central1` because it has the most services and lowest cost.

Answer

The alphabetical order of region names — 'a' regions are newer and more stable.

Answer

Google assigns regions automatically based on the user's IP address at account creation.

Question 8

A Virtual Private Cloud (VPC) in Google Cloud provides network isolation. What does 'network isolation' mean in this context, and why is it important?

Accepted Answer

VPC provides a logically isolated private network where resources are separated from other customers' networks by default, preventing unauthorized cross-customer traffic.. Option B is correct because a Google Cloud VPC provides a logically isolated private network within the shared Google Cloud infrastructure. This isolation ensures that resources in one customer's VPC cannot directly communicate with resources in another customer's VPC by default, preventing unauthorized cross-customer traffic. This is achieved through software-defined networking (SDN) constructs like virtual firewalls and routing tables, not through physical separation.

Answer

Network isolation means the VPC blocks all internet access — resources cannot communicate with external services.

Answer

Network isolation means all traffic within the VPC is automatically encrypted.

Answer

A VPC requires dedicated physical hardware separate from other customers to ensure isolation.

Question 9

What does 'durability' mean for cloud storage services, and how is it different from 'availability'?

Accepted Answer

Durability measures the probability data won't be lost; availability measures the percentage of time data can be accessed — a service can be temporarily unavailable while data remains durable.. Durability measures the probability that stored data will not be lost or corrupted over time, typically expressed as a percentage (e.g., 99.999999999% for Amazon S3). Availability measures the percentage of time a service is operational and accessible, often defined in SLAs (e.g., 99.99% uptime). A service can be temporarily unavailable (e.g., due to maintenance) while the data remains intact and durable, so they are distinct concepts.

Answer

Durability and availability are the same thing — both measure how often data can be accessed.

Answer

Durability refers to network speed; availability refers to storage capacity.

Answer

High availability automatically guarantees high durability, so both terms describe the same SLA.

Question 10

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?

Accepted Answer

Health checks — the load balancer probes backend instances and removes unhealthy ones from the serving pool.. 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.

Answer

Round-robin distribution — traffic cycles evenly across all instances regardless of health.

Answer

SSL termination — decrypting HTTPS traffic before forwarding to backends.

Answer

Session affinity — routing the same user to the same backend instance.

Question 11

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?

Accepted Answer

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

Answer

Using two databases reduces costs by splitting storage between cheaper providers.

Answer

Two databases provide automatic redundancy — if one fails, the other takes over.

Question 12

A web application's homepage loads user-specific data (shopping cart, recent orders) on every visit. The data changes frequently. An engineer suggests caching this data in a Redis cache between the web tier and the database. What is the primary benefit of this caching layer?

Accepted Answer

Caching reduces database load and improves response times by serving frequently accessed data from fast in-memory storage.. Option B is correct because caching user-specific data like shopping carts and recent orders in Redis reduces the load on the primary database by serving frequently accessed data from fast in-memory storage. This improves response times for the web application, as Redis can deliver data in microseconds compared to the millisecond latency of a typical relational database query. The caching layer acts as a temporary, high-speed buffer that offloads read-heavy traffic from the database, which is especially beneficial for data that changes frequently but is read often.

Answer

Caching encrypts data in transit between the web tier and database.

Answer

Caching permanently stores user data so the database can be deleted.

Answer

Caching automatically synchronizes data between multiple database replicas.

Question 13

What is 'infrastructure as code' (IaC), and what problem does it solve compared to manually configuring cloud resources through a web console?

Accepted Answer

IaC defines infrastructure in version-controlled code files, enabling reproducible, automated, and consistent environment provisioning versus error-prone manual console configuration.. Infrastructure as Code (IaC) is the practice of managing and provisioning cloud resources through machine-readable definition files (e.g., YAML, JSON, HCL) rather than through manual processes like clicking in a web console. The core problem it solves is eliminating the error-prone, inconsistent, and non-reproducible nature of manual configuration by enabling version-controlled, automated, and repeatable deployments. Tools like Terraform, AWS CloudFormation, and Azure Resource Manager (ARM) templates are common IaC implementations that enforce desired state configuration and drift detection.

Answer

IaC is a programming language specifically for writing cloud applications.

Answer

IaC is a tool that automatically discovers and documents existing cloud infrastructure.

Answer

IaC requires writing custom Python scripts for every cloud resource type.

Question 14

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?

Accepted Answer

Stateless applications can be scaled horizontally without session loss because any instance can handle any request — enabling easy addition/removal of instances.. 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.

Answer

Stateless applications use less storage because they don't store any data.

Answer

Stateless applications are more secure because they don't remember who the user is.

Answer

Stateless applications eliminate the need for databases since no data is stored.

Question 15

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?

Accepted Answer

Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously.. 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.

Answer

Eventual consistency is a bug — the system should be fixed to always show current data.

Answer

Eventual consistency means data is eventually deleted, which reduces storage costs.

Answer

Eventual consistency only applies to deleted data — new data always appears immediately.