Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail company is migrating its relational databases to Google Cloud and is comparing two deployment options:
During a budget review, the finance director notes that raw monthly infrastructure costs for Compute Engine appear lower than Cloud SQL. However, the cloud architect advises evaluating both long-term total cost of ownership (TCO) and customization requirements.
Which statement accurately compares the TCO and flexibility tradeoffs between these two cloud service models?
Building a realistic total cost of ownership (TCO) model and long-term cloud budget requires evaluating all direct and indirect expenses associated with running workloads in the cloud. Effective cloud financial governance (FinOps) looks at the complete lifecycle of an application rather than just the base compute rate.
This option fails because relying solely on direct monthly resource billing rates leads to severe budget shortfalls. Both IaaS and PaaS environments incur costs beyond basic compute and storage usage. Comprehensive cloud budgets must account for commercial software licenses, engineering and operations personnel, network data transfer (egress), and anticipated workload growth.
This option would be valid if it stated that long-term cloud budgets across both IaaS and PaaS must look beyond raw monthly compute rates to comprehensively include infrastructure costs, software licenses, personnel effort, network utilization, and anticipated growth.
To prevent unexpected cost overruns across any cloud service model, organizations use the Google Cloud Pricing Calculator during architecture design, enforce Committed Use Discounts (CUDs) for predictable workloads, and configure Cloud Billing budgets and alerts to track actual spend against forecasted growth.
In cloud computing, the shared responsibility model dictates which operational tasks the customer handles versus what the cloud provider manages. Moving from on-premises to IaaS, PaaS, and Software as a Service (SaaS) progressively shifts management responsibilities—and the associated operational overhead—away from the customer and onto Google Cloud.
This option reverses the operational responsibilities and cost implications of IaaS and PaaS. Self-hosting a database on Compute Engine (IaaS) does not include automated database administration; the customer remains fully responsible for managing the guest operating system, database software, patches, and backups. Conversely, Cloud SQL (PaaS) never requires customers to manage physical hardware, as Google Cloud manages all underlying physical data centers, servers, and storage across every cloud service model.
This explanation would only make sense if the descriptions of the two models were swapped: managed PaaS reduces ongoing personnel expenses through built-in maintenance and automation, while self-hosted IaaS increases operational TCO by requiring dedicated staff to manage the guest OS and database software.
A common mistake during cloud migration is assuming that lifting and shifting virtual machines to IaaS automatically eliminates system administration costs. While IaaS removes physical data center expenses, true operational savings on patching and database management are realized by modernizing onto PaaS or SaaS offerings.
Flexibility and customization in the cloud refer to the degree of control an organization has over the underlying computing stack, including hardware configurations, processor architectures, operating system kernels, and network settings. Different service models offer varying levels of abstraction depending on how much control a workload requires.
This option inaccurately swaps the customization capabilities of IaaS and PaaS. A managed PaaS offering like Cloud SQL intentionally restricts root access to the underlying host operating system so that Google Cloud can guarantee stability, apply automated security patches, and maintain Service Level Agreements (SLAs). In contrast, Compute Engine (IaaS) does not restrict users to fixed templates; it provides full administrative access to the OS and highly customizable virtual hardware.
This statement would be accurate if it stated that IaaS (Compute Engine) provides root access to customize the guest operating system and select specific machine families, whereas managed PaaS (Cloud SQL) abstracts the OS and restricts low-level host access to ensure reliability.
There is a fundamental inverse relationship between management convenience and infrastructure control. As you move up the continuum from IaaS to PaaS and SaaS, Google Cloud handles more of the operational heavy lifting, which naturally reduces the customer's ability to tweak low-level system components.
When evaluating cloud computing models on Google Cloud, organizations must balance solution flexibility against total cost of ownership (TCO). Infrastructure as a Service (IaaS), such as Compute Engine, provides raw virtualized compute, storage, and networking resources. Platform as a Service (PaaS) and managed database services, such as Cloud SQL, abstract the underlying infrastructure and operating system so teams can focus purely on their application data and business logic.
Comparing cloud service models requires looking beyond raw virtual machine rates. Recognizing that IaaS maximizes infrastructure customization at the cost of higher operational overhead, while PaaS trades low-level OS control for a significantly lower long-term TCO, enables leaders to make sound architectural and financial decisions.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated