Five regional hospitals that share the same healthcare regulatory obligations want cloud infrastructure that is provisioned for their exclusive use, governed jointly by them, and not open to other organizations. Which deployment model best fits this requirement?
Select an answer to reveal the explanation.
Short Explanation
Picture a clinic building shared by a handful of practices that follow the same rules, and you can't get a key unless you're one of them. That's a community cloud. The trap is private cloud, which is for one organization, not five.
Full Explanation
NIST SP 800-145 defines a community cloud as infrastructure provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns, such as mission, security requirements, policy and compliance considerations. It may be owned, managed and operated by one or more of the organizations, a third party, or a combination, and it may exist on or off premises. Five hospitals with the same regulatory obligations, exclusive use and joint governance match that definition. A private cloud is provisioned for exclusive use by a single organization comprising multiple consumers, such as business units; five independent hospitals are separate organizations. A hybrid cloud composes two or more distinct cloud infrastructures bound together for portability, and nothing in the scenario calls for combining models. A public cloud is provisioned for open use by the general public, which contradicts the requirement that other organizations be excluded. Exam caveat: a community cloud can be operated by a third party; who runs it does not change the model, which is defined by who may use it. Operational check: confirm a community governance agreement defines membership, shared cost, incident handling and how a member exits with its data.