Suggested Answer:C🗳️
PaaS should have the following key capabilities and characteristics: - Support multiple languages and frameworks: PaaS should support multiple programming languages and frameworks, thus enabling the developers to code in whichever language they prefer or the design requirements specify. In recent times, significant strides and efforts have been taken to ensure that open source stacks are both supported and utilized, thus reducing ג€lock-inג€ or issues with interoperability when changing CSPs. - Multiple hosting environments: The ability to support a wide variety of underlying hosting environments for the platform is key to meeting customer requirements and demands. Whether public cloud, private cloud, local hypervisor, or bare metal, supporting multiple hosting environments allows the application developer or administrator to migrate the application when and as required. This can also be used as a form of contingency and continuity and to ensure the ongoing availability. - Flexibility: Traditionally, platform providers provided features and requirements that they felt suited the client requirements, along with what suited their service offering and positioned them as the provider of choice, with limited options for the customers to move easily. This has changed drastically, with extensibility and flexibility now afforded to meeting the needs and requirements of developer audiences. This has been heavily influenced by open source, which allows relevant plug-ins to be quickly and efficiently introduced into the platform. - Allow choice and reduce lock-in: PaaS learns from previous horror stories and restrictions, proprietary meant red tape, barriers, and restrictions on what developers could do when it came to migration or adding features and components to the platform. Although the requirement to code to specific APIs was made available by the providers, they could run their apps in various environments based on commonality and standard API structures, ensuring a level of consistency and quality for customers and users. - Ability to auto-scale: This enables the application to seamlessly scale up and down as required to accommodate the cyclical demands of users. The platform will allocate resources and assign these to the application as required. This serves as a key driver for any seasonal organizations that experience spikes and drops in usage.
The PaaS model is really use by cloud provider to develop their own solution that is a market differenciator and that's ease the lock-in. On the other hand the objective of PaaS is to give an homogenous implementation of middleware. so Answer : A
Vendor lock-in can also be reduced, when you implement your environment in a manner to move to another platform easily (e.g., portability). Therefore, your statement is not 100% accurate. In fact, PaaS platforms can support a variety of middleware and programming languages as stated from "bessonf", allowing developers to choose the tools and technologies that best suit their needs. Therefore, I stay with the given answer: "Ability to reduce lock-in".
By its definition - Homogenous is "the same" PaaS is more akin to a heterogeneous model. I have to go with the stated answer. Ability to reduce lock-in
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
bessonf
Highly Voted 3 years, 11 months agoMo22
Most Recent 6 months, 3 weeks agoa_vi
7 months, 3 weeks agoTraceSplice
8 months agoAwraith
1 year, 8 months agoccKane
11 months, 2 weeks agoreckert001
3 years, 8 months ago