Which environment is least likely to be placed on a public cloud by a hospital that has a large health information management application?

Question

Options

• Aproduction
• Bdevelopment
• Ctesting
• DQA

• A
  7% (4)
• B
  75% (44)
• C
  15% (9)
• D
  3% (2)

Explanation

Note on the marked answer: Based on healthcare IT principles, the marked answer of B (Development) appears to be incorrect - the correct answer should be A (Production).

Here's why:

A hospital's production environment is least likely to go on a public cloud because it processes real Protected Health Information (PHI), making it subject to strict HIPAA regulations; even with a cloud provider's Business Associate Agreement (BAA), most hospitals keep production on-premises or in a private cloud to minimize breach risk and maintain audit control. Development (B) is actually among the most cloud-friendly environments - it uses synthetic or mock data, benefits from elastic resources, and poses minimal compliance risk, so placing it on a public cloud is common practice. Testing (C) and QA (D) similarly use anonymized or fabricated data and are routinely hosted on public clouds for cost efficiency and isolation from live systems.

Memory tip: Think "PHI stays private" - whichever environment handles real patient data is the one hospitals protect most aggressively. In the SDLC, that's always Production.

If this question came from a practice test or course material, I'd recommend cross-checking it against your official study guide - the answer key may contain a typo. The logic for "least likely on public cloud in healthcare = production" is well-established in HIPAA compliance and healthcare IT frameworks.

No community discussion yet for this question.