A city builds every lake job against proprietary managed APIs that have no portable equivalent. What lock-in awareness should architects apply?
Select an answer to reveal the explanation.
Short Explanation
Custom-shaped keys only open one landlord’s doors. Heavy use of proprietary managed APIs can make leaving a cloud painful later. Where portability matters, put abstractions and open formats between the city and the vendor-specific bits.
Full Explanation
Vendor lock-in is a cloud decision factor when workloads bind tightly to proprietary managed APIs and control planes. Architects should weigh portability needs, open formats, and abstraction layers against convenience and cost. Assuming lock-in never applies to Big Data platforms understates exit risk. BDPC cloud awareness includes that trade-off without turning into a vendor-bashing exercise.