State whether the following is true or false.
A managed Kubernetes service is best described as sitting between infrastructure and platform as a service.
Answer: A
The provider manages the control plane while the customer manages the workloads and often the nodes. It is a good illustration of how the classic three models do not partition the world cleanly. The control plane is the managed part.
Please log in or register to report this question.
A function is invoked 2 million times a month and runs for 200 milliseconds each time. What is the total compute time?
Answer: B
Correct answer: about 111 hours
\[ 2{,}000{,}000 \times 0.2\ \mathrm{s} = 400{,}000\ \mathrm{s}, \qquad \frac{400{,}000}{3600} = 111\ \mathrm{hours}. \] The 400 hours offered leaves the answer in seconds-derived units without dividing by 3600 properly, and 111 hours a month against the 730 hours a continuously running instance would bill is exactly why the model is cheap for this workload.
Please log in or register to report this question.
Assertion (A): Function as a service is most economical for spiky or infrequent workloads.
Reason (R): Billing is by execution time, so an idle function costs nothing at all.
Answer: C
Correct answer: Both A and R are true, and R is the correct explanation of A
Both are true and the reason gives the economics. A function costs nothing while idle, so a workload that runs for minutes a day pays for minutes rather than for a machine standing by. The comparison reverses for sustained load: a function running continuously costs considerably more than a reserved instance of the same capacity, which is why the model suits spikes and not steady traffic.
Please log in or register to report this question.
Containers as a service typically provides
Answer: D
The provider runs the scheduling and the host fleet while the customer supplies the images. It removes much of the operational burden of running an orchestrator oneself. Images remain the customer's. Scheduling and hosts are handled for you.
Please log in or register to report this question.
Match each customer responsibility with the highest model at which it still applies.
List I
A. Patching the guest operating system
B. Choosing a runtime version
C. Writing the application code
D. Managing users and data
List II
1. function as a service
2. infrastructure as a service
3. software as a service
4. platform as a service
Answer: A
Data and identity are the two responsibilities that never transfer, whatever the model in use. Everything else is progressively handed over as one moves up the stack, which is exactly what the shared responsibility model describes.
Please log in or register to report this question.
State whether the following is true or false.
Data and identity remain the customer's responsibility in every service model.
Answer: B
No provider can know who should have access or what the data means. This is why access misconfiguration is the most persistent category of cloud security failure. Meaning stays with the owner. No provider can know who should have access.
Please log in or register to report this question.
The main argument for infrastructure as a service over higher models is
Answer: C
Correct answer: control over configuration and versions
Infrastructure as a service is chosen when the specifics matter - a particular kernel or database version, an unusual network arrangement, a licence tied to the machine, a compliance requirement about where and how software runs. The other three options are claims the model does not support: it means more operational work, not less, and neither better security nor lower cost follows automatically from it.
Please log in or register to report this question.
