Public Cloud Provider Ownership in Shared Responsibility Model
Short answer
AD Hardware maintenance and Hardware capacity management are functions owned by the public cloud provider under the shared responsibility model.
Question
ownership.
Which two functions does a public cloud provider own? (Choose two.)
Key Takeaways
The main trap is selecting infrastructure-related tasks that customers actually perform (like automation or architecture) instead of physical/hardware-level management which the provider retains.
Identify which two functions a public cloud provider owns from options including hardware maintenance and capacity management. Understand the boundary between 'of the cloud' and 'in the cloud' responsibilities.
Common mistake: Choosing C (Infrastructure deployment automation) because it sounds like 'infrastructure,' but this is a customer-side DevOps task, whereas the provider owns the underlying hardware capacity (D) and maintenance (A).
Expert Analysis
The Shared Responsibility Model is the core concept here. In public cloud infrastructure (IaaS), the provider owns and manages everything 'of' the cloud, while the customer owns everything 'in' the cloud.
A. Hardware maintenance: Correct. The provider manages physical servers, storage devices, and networking gear. Customers do not touch hardware.
D. Hardware capacity management: Correct. The provider handles scaling, provisioning, and managing the underlying resource pool to ensure availability. This is part of the infrastructure layer owned by the CSP.
Why B and C are wrong: These are customer responsibilities. Infrastructure architecture (designing VPCs, subnets) and deployment automation (Terraform scripts, CI/CD pipelines) are 'in the cloud' tasks performed by the customer.
Why E is wrong: Fixing application security issues is a customer responsibility ('security in the cloud'). While the provider secures the underlying OS/hypervisor, the application code, data, and access controls are the customer's duty.
The most attractive trap is confusing 'Infrastructure Deployment Automation' (C) with 'Hardware Capacity Management' (D). Both involve managing resources, but C is a software/process task done by the customer, while D is a physical/logical capacity task done by the provider.
Official Reference
https://cloud.google.com/architecture/framework/security/shared-responsibility-shared-fate
This link opens the official vendor documentation in a new tab.
Exam Strategy
When faced with Shared Responsibility questions, mentally split the stack into Physical/Data Center (Provider) vs. Application/Data (Customer). Any option involving physical components, power, cooling, or raw hardware scaling belongs to the provider. Any option involving configuration, code, or logical network design belongs to the customer.
Frequently Asked Questions
Does the cloud provider manage virtual machine scaling?
Who fixes vulnerabilities in the guest OS?
Community Votes
50% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 25 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 25
-
cookieMr 👍 8The Cloud Provider is responsible for the security "of the cloud" infrastructure. This includes the underlying hardware, data centers, networking, and the core services. It takes care of managing and protecting these foundational components to ensure the availability, reliability, and security of the cloud infrastructure. The customer is responsible for the security "in the cloud" or the security of their applications and data running on cloud services.
-
KC_go_reply 👍 4Infrastructure would mean the cloud provider would manage your VMs etc, so I disagree
-
Kamlakar 👍 4AD are correct!
-
ucsdmiami2020 👍 3Per Google docs, at a minimum when considering IaaS, the cloud provider is responsible for Hardware, Boot, Hardened Kernel and IPS, Storage and etc. https://cloud.google.com/architecture/framework/security/shared-responsibility-shared-fate
-
Waffle0906 👍 2The Cloud Provider takes care of infrastructure. This includes hardware, data centers, networking, and the core services.
Show 20 more comments
-
Ritesh_Sahu 👍 2A & D is the right answer
-
Swollenbadger 👍 2Giveaway = "hardware"
-
chai_gpt 👍 2AD is correct
-
Surek 👍 2Answer is AD
-
dwibo1 👍 1I'd say A & D. CSP is generally responsible for the maintenance of all its hardware. Whereas customer is responsible for how the application-side is run in those hardware.
-
azrap 👍 1Hardware Maintenance and Infrastructure Deployment A and C. Hardware capacity is cover under Infrastructure Devployment
-
Pou1ze 👍 1Hardware is closely related to Cloud provider (Share Responsability Model)
-
Sp4nner 👍 1Keyword "HARDWARE". no client will touch hardware hence answers are A&D
-
gireeshbengeri 👍 1Hardware maintainance is from cloud provider even security handling
-
juangt 👍 1Cloud provider takes care of HW maintenance and Capacity management
-
KanikaA 👍 1Hardware maintenance & capacity mgmt is managed by cloud provider.
-
lzuccolo 👍 1Mantenimiento del hardware y capacidad/ampliacion del mismo
-
star2anand 👍 1A. Hardware Maintenance and D. Hardware capacity management
-
Jackey0117 👍 1A. Hardware maintenance B. Infrastructure architecture
-
ealcober 👍 1theres no hardware keyword. bad pointed.
-
xxdrei 👍 1Key Word: "Hardware" By: Arjay
-
SrR97 👍 1A Y D son correctas
-
zambonini 👍 1Solution A and D
-
prachisri 👍 1CD answer
-
AntimSapien 👍 1A and D
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CDL Questions
Access 84 questions with complete answers and detailed explanations.
View Full CDL Practice Test →