220-1201 Practice Question: Adopting a cloud-first strategy and wants to…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Public cloud

  Why it's wrong here

  A public cloud model involves a single third-party cloud service provider offering computing resources, such as servers, storage, and applications, over the public internet. While convenient and scalable, relying solely on one public cloud provider significantly increases vendor lock-in. This makes it difficult and costly to migrate services or data to a different provider, directly contradicting a strategy aimed at reducing dependency.

• ✗

  Hybrid cloud

  Why it's wrong here

  A hybrid cloud architecture integrates a private cloud (on-premises or hosted) with one or more public cloud services, allowing data and applications to move between them. Its primary benefit is extending private infrastructure to the public cloud for burst capacity or specific workloads, maintaining some control over sensitive data. However, it does not inherently reduce vendor lock-in across multiple public providers because the public component often remains tied to a single major vendor, and the integration itself can create dependencies.

• ✓

  Multi-cloud

  Why this is correct

  Multi-cloud specifically refers to the use of cloud services from multiple distinct public cloud providers simultaneously. This strategy is explicitly designed to mitigate vendor lock-in by distributing workloads, applications, and data across different vendors like AWS, Azure, or Google Cloud. By avoiding over-reliance on a single provider, organizations gain greater flexibility, improved resilience against outages from one vendor, and enhanced negotiation power, directly aligning with a goal to reduce dependency.

• ✗

  Community cloud

  Why it's wrong here

  A community cloud is a collaborative cloud infrastructure shared by several organizations that have common concerns, such as security requirements, compliance, or mission. It can be managed internally or by a third party, but its resources are exclusive to the participating community. While it offers shared benefits for specific groups, its design does not inherently address or reduce vendor lock-in from the perspective of diversifying across multiple public cloud providers; its focus is on shared governance and resources within a defined community.

Go deeper

Related to this question