Cloud Deployment Models Questions and Answers

Answer: A

Correct answer: provisioned for one organisation only

A private cloud is defined by exclusive use: the infrastructure serves a single organisation, whoever owns it and wherever it stands. It may be run in the organisation’s own data centre or hosted by a third party, and it is certainly not free - dedicated capacity generally costs more per unit than shared capacity does.

Answer: B

Correct answer: Both A and R are true, and R is the correct explanation of A

Both are true and the reason gives the definition. Exclusivity is what makes a cloud private, so a hosted private cloud on a provider’s premises, with dedicated hardware and a separate tenancy, qualifies just as an on-premises one does. Conflating private with on-premises is the commonest error in this subject, and it obscures the distinction that actually matters - who else is on the hardware.

Answer: C

Correct answer: A-2, B-4, C-1, D-3

Four models distinguished by who shares the infrastructure. Public is open to the general public and shared among unrelated tenants. Private is exclusive to one organisation. Community is shared by organisations with a common concern - a regulator, a sector, a research consortium. Hybrid is two or more of these bound together so that data and applications can move between them.

Answer: D

Correct answer: the parts are bound together technically

The binding is what makes it hybrid: shared identity, connected networks, a common management plane, portable workloads or data replicated between the parts. Two unconnected environments used for different things are simply two environments. That definition is what the following items about multi-cloud and cloud bursting both rest on.

Answer: A

Correct answer: Both A and R are true, and R is the correct explanation of A

Both are true and the reason gives the criterion. The hybrid model is about combining *deployment models* - typically private with public - not about counting providers. Two public clouds, however tightly integrated, remain the same model twice over, and the word for that is multi-cloud. The distinction matters because the two arrangements are adopted for quite different reasons.

Answer: B

Correct answer: 1 and 2 only

Statements 1 and 2 define the two terms correctly. Statement 3 collapses a real distinction: hybrid is about spanning deployment models and is usually driven by data residency, existing investment or latency, while multi-cloud is about spanning providers and is usually driven by resilience, negotiating position or the wish to use a particular service. An estate can be both, or either alone.

Answer: C

Correct answer: overflowing from private to public at peak

Cloud bursting keeps the steady baseline load on private capacity, which is cheaper when well utilised, and sends only the peaks to the public cloud, which is paid for by the hour. It is the most attractive-sounding hybrid pattern - and, as the next item says, among the hardest to realise.

Answer: D

Correct answer: Both A and R are true, and R is the correct explanation of A

Both are true and the reason names the two obstacles. The application must run unchanged in both environments, which rules out anything depending on a specific hypervisor, appliance or licence; and the data must be reachable from both at acceptable latency, which usually means replicating it continuously or accepting a slow link at exactly the moment of peak demand. Those two conditions are why bursting is described far more often than it is implemented.

Answer: A

Elastic capacity beyond what has been bought is exactly what a private cloud cannot offer. The other three are the three usual reasons an organisation keeps its own cloud. Owned capacity is finite. Bursting is the usual workaround for that.

Answer: B

Government agencies or hospitals within one jurisdiction are the usual examples. It spreads the cost of meeting a shared compliance requirement across several bodies. Members share a concern. Government and health bodies are typical members.