المنصة العربية للدراسات المهنيةArab Platform for Professional Studies
العربية
Scope the workload and cloud boundary

Review questions

Scope the workload and cloud boundary

Ask first what the service can demonstrate, then what the workload needs. Virtualization alone does not establish self-service; a human ticket for each capacity change contradicts it for that offer. Browser access alone does not demonstrate heterogeneous client access, and missing pooling evidence means 'not shown' unless a contradictory fact exists. After classifying an offer, map who operates the OS, code, identities and data under the service model and actual agreement; backup tooling does not set customer retention. Express booking requirements with units and windows: 360 search requests a minute average six a second, but do not reveal successful booking volume. Include a concurrent-seat test and ask the data owner for RPO when only RTO is stated. The output is bounded evidence, ownership and requirements, not a claim that cloud branding establishes suitability.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1A supplier offers a virtual server reachable over the Internet, but each capacity increase needs a ticket completed by an employee two days later. What do these facts support about on-demand self-service for this offer?
  2. Question 2A team deploys its code on an application platform whose operating system is managed by the provider. Who still owns testing a defect in booking code?
  3. Question 3Search traffic reaches 360 requests per minute for ten minutes. What is its average per second within that window?