400-007 · Question #370
The cloud like the Internet is a massive network of independent resources that are designed to be fault tolerant. Software components that run in the cloud have no dependencies on the underlying…
The correct answer is A. separation of resources from representation E. self-descriptive messages. Two REST architectural constraints are especially critical for cloud fault tolerance: separating resources from their representations and using self-descriptive messages. Both support stateless, loosely coupled communication across infrastructure that may fail at any time.
Question
The cloud like the Internet is a massive network of independent resources that are designed to be fault tolerant. Software components that run in the cloud have no dependencies on the underlying infrastructure which may fail at any time. Which two constraints of REST are important when building cloud-based solutions? (Choose two )
Options
- Aseparation of resources from representation
- Bmigration of resources by representations
- Cdistribution of resources through platforms
- Dhyper-scale as the engine of application state
- Eself-descriptive messages
How the community answered
(21 responses)- A95% (20)
- C5% (1)
Why each option
Two REST architectural constraints are especially critical for cloud fault tolerance: separating resources from their representations and using self-descriptive messages. Both support stateless, loosely coupled communication across infrastructure that may fail at any time.
Separation of resources from their representations (part of REST's uniform interface) ensures clients reference abstract resource identifiers rather than implementation-specific formats, keeping the application decoupled from any particular infrastructure node that may fail.
Migration of resources by representations is not a defined REST architectural constraint; it is fabricated terminology.
Distribution of resources through platforms describes an infrastructure concern and is not one of the six recognized REST architectural constraints.
Hyper-scale as the engine of application state misquotes the actual REST constraint HATEOAS (Hypermedia as the Engine of Application State); hyper-scale is an infrastructure concept, not an architectural constraint.
Self-descriptive messages require each request to carry all processing context, enabling stateless communication where any server instance can handle any request - essential in cloud environments where nodes are ephemeral and interchangeable.
Concept tested: REST constraints for fault-tolerant cloud design
Source: https://learn.microsoft.com/en-us/azure/architecture/best-practices/api-design
Topics
Community Discussion
No community discussion yet for this question.