CLOUD-DIGITAL-LEADER · Question #373
An organization wants to leverage cloud technologies but is concerned about vendor lock-in. What would mitigate this concern?
The correct answer is A. Open standards. Open standards ensure that technologies, APIs, and data formats are interoperable across multiple cloud providers, allowing organizations to migrate workloads freely and avoid dependency on a single vendor's proprietary ecosystem.
Question
An organization wants to leverage cloud technologies but is concerned about vendor lock-in. What would mitigate this concern?
Options
- AOpen standards
- BDatabase services
- CService level agreements
- DScalable infrastructure
How the community answered
(46 responses)- A87% (40)
- B2% (1)
- C7% (3)
- D4% (2)
Why each option
Open standards ensure that technologies, APIs, and data formats are interoperable across multiple cloud providers, allowing organizations to migrate workloads freely and avoid dependency on a single vendor's proprietary ecosystem.
Open standards - such as open APIs, open-source software, and open data formats - ensure that an organization's workloads, data, and applications are portable and interoperable across different cloud providers. By avoiding proprietary technologies, organizations retain the freedom to switch providers or adopt a multi-cloud strategy, which directly mitigates vendor lock-in risk.
Database services are typically provider-specific offerings that can themselves contribute to vendor lock-in if they rely on proprietary query languages or data formats.
Service level agreements define uptime and performance guarantees from a specific provider but do not make workloads portable or reduce technical dependency on that provider.
Scalable infrastructure addresses performance and capacity needs but does not address workload portability or the ability to migrate between cloud providers.
Concept tested: Vendor lock-in mitigation through open standards
Source: https://cloud.google.com/learn/what-is-open-cloud
Topics
Community Discussion
No community discussion yet for this question.