A large enterprise cloud design team is evaluating different cloud consumption models. What is an example of typical PaaS limitations or concerns that should be considered during service design?

Question

Options

• Avendor lock-in
• Bruntime issues
• Clack of control
• Dmulti-tenant security

• A
  85% (41)
• B
  8% (4)
• C
  4% (2)
• D
  2% (1)

Explanation

Platform as a Service (PaaS) abstracts away infrastructure and runtime management, allowing developers to focus on application code. The tradeoff is that applications are typically built against provider-specific APIs, SDKs, managed databases, and middleware (e.g., Google App Engine APIs, Heroku buildpacks, AWS Elastic Beanstalk configs). This deep coupling to a single provider makes migrating the application to a competing PaaS-or back to on-premises-expensive and technically complex, often requiring significant rewrites. This is the defining concern of PaaS: vendor lock-in. Runtime issues (B) are more relevant to IaaS where you manage your own runtime. Lack of control (C) is a general cloud concern applicable across all models. Multi-tenant security (D) is a concern shared across all cloud delivery models and is not uniquely associated with PaaS.

No community discussion yet for this question.