Which of the following workload descriptions represents a good candidate for hybrid cloud deployment?

Question

Options

• ADevelopers rarely request development/test servers.
• BApplications are updated and deployed annually within a scheduled maintenance window.
• CA single application occupies a single physical server where data cannot be in a public data
• DThe application is subjected to frequent updates, and there is a business need to interface with

• A
  5% (1)
• B
  11% (2)
• C
  5% (1)
• D
  79% (15)

Explanation

Option D is correct because hybrid cloud excels when applications require frequent updates (benefiting from cloud elasticity and rapid deployment pipelines) and must interface with both on-premises/private systems and public cloud services - exactly the use case hybrid was designed for.

• A is wrong because infrequent server requests means demand is low and predictable, making a simple private cloud or even on-premises setup sufficient - there's no burst or agility need to justify hybrid.
• B is wrong because annual updates with scheduled maintenance windows signal a stable, low-churn workload; hybrid cloud's agility advantages are wasted when deployments happen once a year.
• C is wrong because data that cannot be in a public data center points to a private-only deployment, not hybrid - moving any part of it to a public cloud would violate that constraint.

Memory tip: Think of hybrid cloud as the answer whenever you see two opposing needs coexisting - speed/flexibility (frequent updates, burst traffic) plus control/privacy (on-prem data, compliance). If a scenario has only one of those needs, a single environment (public or private) is usually sufficient.

No community discussion yet for this question.