Cloud Model Selection for Low Compliance Enterprise
Short answer
A Public cloud is the appropriate deployment model for mainstream business processes with light data volumes and low regulatory overhead due to its cost-effectiveness and scalability.
Question
Key Takeaways
The question tests the distinction between deployment models (Public/Private) and service models (IaaS/PaaS/SaaS), identifying the trap of selecting a service model when a deployment context is described.
This question evaluates the selection of an appropriate cloud deployment model based on business process maturity, data volume, and regulatory requirements. It establishes that public cloud is the optimal fit for mainstream processes with low compliance overhead.
Common mistake: Learners often choose SaaS because it handles 'mainstream' applications like email or CRM, failing to recognize that SaaS is a service model, not a deployment model, and may not address the infrastructure-level needs implied by the analysis.
Expert Analysis
Why the Answer Is Correct
The correct answer is A (Public Cloud) because the scenario describes a deployment context rather than a specific service layer. Public clouds are designed for mainstream, non-sensitive workloads where cost-efficiency and scalability are prioritized over strict isolation. The findings of 'light data volumes' and 'low regulations' indicate that the enterprise does not require the dedicated, isolated resources of a private cloud, making the shared, multi-tenant nature of the public cloud the most economical and suitable choice.
Why the Other Options Are Wrong
PaaS (Option C) and SaaS (Option D) are service delivery models, not cloud deployment models. While they can be hosted on public clouds, they do not describe the where or how the infrastructure is managed in the context of enterprise-wide infrastructure analysis. Private Cloud (Option B) is incorrect because it is typically reserved for organizations with high security, compliance, or sensitive data requirements, which contradicts the 'low regulations' finding. Selecting a service model (SaaS/PaaS) ignores the fundamental classification of cloud architecture asked for by the question.
Community Comment Notes
Community consensus largely supports Option A, though some confusion exists regarding SaaS. One commenter noted that SaaS solutions like Salesforce handle mainstream processes but failed to distinguish that SaaS is a service type, not the underlying deployment model. Another user correctly pointed out that PaaS and SaaS are not cloud models in the same category as Public/Private, reinforcing the need to select the deployment model first. The majority vote aligns with the technical distinction that Public Cloud is the overarching deployment strategy for such environments.
Official Reference
- https://www.cisco.com/c/en/us/solutions/cloud/index.html
- https://aws.amazon.com/what-is-cloud-computing/
These links open the official vendor documentation in a new tab.
Exam Strategy
Always distinguish between Cloud Deployment Models (Public, Private, Hybrid, Community) and Cloud Service Models (IaaS, PaaS, SaaS). When the question asks 'which cloud model' in the context of infrastructure ownership and regulatory burden, look for deployment terms first. If options mix both types, the one addressing the physical/logical location and sharing model is usually the intended answer for high-level architectural questions.
Frequently Asked Questions
Why isn't SaaS the correct answer for mainstream processes?
Can PaaS be considered a cloud model?
Community Votes
66% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 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 5
-
Doobiedoo 👍 2 Answered AA. public cloud: Mainstream business processes: Public clouds are well-suited for handling common business applications and workflows. Light data volumes: Public clouds can efficiently handle moderate data volumes, making them a cost-effective option. * Low regulations or compliance overheads: Public cloud providers often have robust security and compliance measures in place, making them suitable for organizations with low regulatory requirements. While private clouds offer more control and customization, they can be more expensive and complex to manage. PaaS and SaaS are more specialized models that might not be as suitable for a large enterprise with diverse needs.
-
i9t6 👍 2 Answered DWhy not SaaS? O365, ServiceNow, SalesForce, etc etc, no need of public cloud to develop such type of "Mainstream" processes. or to use the solutions of the cloud providers
-
kalulosu 👍 1I think correct answer is A. Public clouds are well suited for mainstream business processes, light data volumes, and low regulatory and compliance burdens. It allows companies to leverage cloud resources in a flexible and cost-effective manner.
-
The1BelowAll 👍 1 Answered APublic Cloud is the correct answer, the SaaS and PaaS are also Public Cloud.
-
sandccie 👍 1 Answered AA. Public Cloud. PaaS SaaS are not cloud models...
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.