Vendor lock-in is a significant risk that directly impacts operational costs. It occurs when a customer becomes dependent on a specific cloud provider's proprietary services, APIs, or data formats, making it difficult and expensive to migrate to another vendor. This lack of portability can lead to escalating subscription fees over time, as the provider faces little competitive pressure. The high switching costs—including data egress fees, application re-architecting, and staff retraining—effectively lock the customer into a single ecosystem, negatively impacting long-term operational expenditure (OpEx).

B. Higher rack density: This is a measure of data center efficiency. It is a characteristic of the provider's infrastructure and not a direct operational cost risk for the customer.

C. Increased PUE (Power Usage Effectiveness): A higher PUE indicates lower energy efficiency for the data center operator. This is the provider's concern, not a direct risk that increases the customer's operational costs.

D. Reduced data transfer latency: This is a performance benefit of using the cloud, not a risk. Lower latency improves application responsiveness and user experience.

---

1. National Institute of Standards and Technology (NIST). (2011). NIST Cloud Computing Reference Architecture (NIST Special Publication 500-292).

Section 6.3, "Challenges and Risks," page 30: The document explicitly lists "Vendor Lock-in" as a key business risk. It describes the difficulty in moving cloud services from one provider to another, which creates dependency and can lead to unfavorable long-term pricing, directly affecting operational costs.

2. HPE Education Services. (2021). Architecting HPE Hybrid Cloud Solutions, Rev. 21.41 (Student Guide).

Module 1: Introduction to Hybrid Cloud: This courseware discusses the challenges of public cloud adoption. It highlights that while public clouds offer OpEx models, risks like vendor lock-in can lead to unforeseen cost increases and a loss of financial control, as switching providers becomes economically unfeasible.

3. Armbrust, M., et al. (2009). Above the Clouds: A Berkeley View of Cloud Computing (Technical Report No. UCB/EECS-2009-28). EECS Department, University of California, Berkeley.

Section 5, "Top 10 Obstacles and Opportunities for Cloud Computing," page 11: This foundational academic paper identifies "Vendor Lock-In" as obstacle #2. It states, "customers are worried that if they use one vendor’s proprietary APIs, they will be unable to extract their data and programs to run on a competing service," which has clear implications for cost and operational flexibility.