C90-02 practice question 10 of 15

REST services share a uniform contract and therefore cannot be deployed in cloud environments without a multi-device broker mechanism.

Full set: 89 questions
Answer options
A: True
B: False
Correct Answer:
FALSE
Explanation

The statement is fundamentally incorrect. REST (Representational State Transfer) is an architectural style that is exceptionally well-suited for and widely used in cloud environments. Its core constraints, including the uniform interface (often referred to as a "uniform contract"), promote loose coupling, scalability, and interoperability, which are essential characteristics for cloud-based services. The uniform interface simplifies the architecture, allowing diverse clients (including those on different devices) to interact with the service in a standardized way. Far from preventing cloud deployment, this feature is a primary reason for REST's prevalence in cloud computing. Furthermore, while a broker mechanism like an API Gateway is a common and recommended pattern for managing, securing, and scaling cloud services, it is not a mandatory prerequisite for deploying a REST service in a cloud environment.

Why Incorrect

The "True" option is incorrect because it posits a false cause-and-effect relationship. It incorrectly claims that the uniform contract of REST services is a barrier to cloud deployment, which is the opposite of established cloud architecture principles. The vast majority of public cloud platform APIs (e.g., AWS, Azure, Google Cloud) are themselves RESTful, demonstrating that REST is not only compatible with but is the de facto standard for cloud service interaction.

References

1. Arcitura Education Inc., "Cloud Technology Concepts Study Kit C90.01," Module 3: Cloud Technology Mechanisms, Section: REST Services. This section describes REST services as a common and lightweight framework for creating APIs for cloud services. It highlights that the uniform interface constraint allows for loose coupling, which is a key design goal for scalable, cloud-based solutions. It does not state that this constraint prevents deployment or requires a broker.

2. Fielding, R. T. (2000). Architectural Styles and the Design of Network-based Software Architectures. Doctoral dissertation, University of California, Irvine. Chapter 5: Representational State Transfer (REST). Fielding's dissertation, the origin of REST, defines the uniform interface as a core constraint that simplifies and decouples the architecture, enabling components to evolve independently. This decoupling is a foundational principle that makes REST ideal for large-scale, distributed systems like the cloud.

3. Pautasso, C. (2013). RESTful Web Services: Principles, Patterns, Emerging Technologies. In: Bouguettaya, A., Sheng, QZ., Daniel, F. (eds) Web Services Foundations. Springer, New York, NY. https://doi.org/10.1007/978-1-4614-7518-72 This publication explains that "the uniform interface constraint simplifies the overall system architecture... The benefit is that all components are interoperable and that the architecture is more scalable" (Section 2.2.2). This directly contradicts the premise that the uniform contract is a barrier.

4. MIT OpenCourseWare. (2018). 6.172 Performance Engineering of Software Systems, Fall 2018. Lecture 20: Cloud Computing. Course materials on cloud computing from reputable institutions consistently present REST APIs as the standard mechanism for interacting with and building upon cloud infrastructure services (e.g., storage, compute, databases), demonstrating their inherent compatibility and central role in cloud environments.

Scroll to Top