112-51 · Question #3
Cibel.org, an organization, wanted to develop a web application for marketing its products to the public. In this process, they consulted a cloud service provider and requested provision of developmen
The correct answer is B. Platform-as-a-service. The type of cloud service requested by Cibel.org in the above scenario is Platform-as-a-service (PaaS). PaaS is a cloud-based service that delivers a range of developer tools and deployment capabilities. PaaS provides a complete, ready-to-use, cloud-hosted platform for developing
Question
Cibel.org, an organization, wanted to develop a web application for marketing its products to the public. In this process, they consulted a cloud service provider and requested provision of development tools, configuration management, and deployment platforms for developing customized applications. Identify the type of cloud service requested by Cibel.org in the above scenario.
Options
- ASecurity-as-a-service (SECaaS)
- BPlatform-as-a-service
- CInfrastructure-as-a-service {laaS)
- Dldentity-as-a-service {IDaaS)
How the community answered
(66 responses)- A2% (1)
- B88% (58)
- C8% (5)
- D3% (2)
Explanation
The type of cloud service requested by Cibel.org in the above scenario is Platform-as-a-service (PaaS). PaaS is a cloud-based service that delivers a range of developer tools and deployment capabilities. PaaS provides a complete, ready-to-use, cloud-hosted platform for developing, running, maintaining and managing applications. PaaS customers do not need to install, configure, or manage the underlying infrastructure, such as servers, storage, network, or operating system. Instead, they can focus on the application development and deployment process, using the tools and services provided by the cloud service provider. PaaS solutions support cloud-native development technologies, such as microservices, containers, Kubernetes, serverless computing, that enable developers to build once, then deploy and manage consistently across private cloud, public cloud and on-premises environments. PaaS also offers features such as scalability, availability, security, backup, and monitoring for the applications. PaaS is suitable for organizations that want to develop customized applications without investing in or maintaining the infrastructure.
Topics
Community Discussion
9Think of cloud services like renting space to cook a meal. With IaaS you rent the raw kitchen, bare walls and appliances, and you bring everything else. With PaaS you rent a fully equipped kitchen where the stove, the counters, the ventilation, and the prep tools are already set up, so you just focus on cooking the dish. That is exactly what Cibel.org asked for: development tools, configuration management, and a deployment platform, meaning the provider handles the underlying environment and Cibel just writes the application code. The correct answer is B, Platform-as-a-service (PaaS). The giveaway words in the scenario are "development tools, configuration management, and deployment platforms," which are the signature offerings of PaaS. SECaaS (A) handles outsourced security controls, IaaS (C) gives you raw compute, storage, and networking that you manage yourself, and IDaaS (D) is strictly about identity and access management services. None of those three match the ask for a ready-made development and deployment environment, so PaaS is the only fit here.
The answer here is B, Platform-as-a-Service (PaaS), and the key is in what Cibel.org actually asked for: development tools, configuration management, and deployment platforms. That combination is the textbook definition of PaaS, because the cloud provider is handing over a ready-made environment where the customer builds and deploys their own application without managing the underlying servers or networking. If they had asked for raw compute, storage, or virtual machines they could configure themselves, that would be IaaS. SECaaS and IDaaS are niche service models focused on security controls and identity management respectively, so those do not fit this scenario at all. Anyone who picked C, think about it this way: with IaaS you are renting the building materials, but with PaaS you are renting the fully equipped workshop where you just show up and build.
The workshop analogy is solid, but the real trap on my first attempt was confusing who manages the runtime: with PaaS that responsibility belongs to the provider, and exam writers love to hide that detail in a phrase like "without installing or maintaining the operating system."
The key phrase is "development tools, configuration management, and deployment platforms" for building customized applications. That is the textbook definition of PaaS: the cloud provider gives you the runtime environment, middleware, and dev tools so your team writes and deploys code without managing the underlying servers or OS. IaaS stops at raw compute and storage, SECaaS is for outsourced security functions, and IDaaS handles identity and authentication, so none of those fit what Cibel.org actually asked for. When you see any combo of "development platform plus deployment plus configuration management" in a scenario, circle PaaS immediately. Saw almost this exact wording on my 112-51 sitting last fall. I second-guessed myself for a second because the scenario mentioned a web application and I briefly thought IaaS, but then I re-read and noticed they wanted the tools and deployment layer handed to them, not just the servers. That locked it in. B, no hesitation, and I moved on. Trust the keywords on this exam, they are not trying to trick you, they are telling you the answer.
I almost went with C because "deployment platforms" made me think hardware and infrastructure, but the key phrase that snapped me back was "development tools and configuration management," which are squarely in the PaaS lane. PaaS gives you the environment to build and deploy apps without managing the underlying servers, and that is exactly what Cibel.org asked for.
Some of you might be tempted by C because "cloud service provider" sounds like raw infrastructure, but the moment the scenario lists development tools, configuration management, and deployment platforms, that is the PaaS fingerprint, not IaaS, which stops at virtualized compute, storage, and networking and leaves the tooling layer entirely to you. The answer is B, Platform-as-a-Service, and the mnemonic to lock this in is PaaS equals "Platform for Programmers," meaning the provider hands you the whole build-and-deploy runway so your developers never touch the underlying OS or hardware.
That mnemonic works well, and a quick addition that helped our group was pairing it with a counter-example, because AWS EC2 alone is IaaS but once you layer Elastic Beanstalk on top of the same underlying instances, you have crossed into PaaS territory, which shows the tooling layer is really what defines the boundary.
Honestly I kept going back and forth but I landed on C, IaaS, because when the senior at my job explained it, he said IaaS gives you the raw building blocks like servers, storage, and networking so you can set up your own deployment environment however you want, and that sounds exactly like what Cibel.org is getting here. The question mentions configuration management and deployment platforms, which in my head lines up with controlling the underlying infrastructure yourself rather than having someone hand you a ready-made app framework.
Yusuf, configuration management tools and deployment platforms like Puppet, Chef, and Heroku sit at the PaaS layer, not IaaS, because they abstract away the raw server provisioning and hand you a managed environment where you focus on deploying and configuring your application, not the hardware underneath.