There are many types of northbound interfaces, from SMP, CORBA, SNMP to REST, which can be said to be in full bloom. However, the northbound interfaces of various devices are gradually evolving to…

Question

Options

• AREST standardizes URI naming
• BREST adopts stateless design
• CREST realizes front-end and back-end coupling
• DREST has good cross-platform compatibility

• A
  2% (1)
• B
  4% (2)
• C
  84% (42)
• D
  10% (5)

Explanation

Option C is the correct answer because it states the opposite of what REST actually does - REST is specifically designed to achieve front-end and back-end decoupling, not coupling. Coupling tightly binds components together, which reduces flexibility and portability; REST's resource-based, stateless architecture deliberately separates the client (front-end) from the server (back-end), allowing each to evolve independently.

Options A, B, and D are all genuine advantages of REST: A is valid because REST uses standardized URI naming conventions to identify resources consistently across systems; B is valid because REST's stateless design means each request carries all necessary information, improving scalability and reliability; D is valid because REST communicates over HTTP with JSON or XML, making it language- and platform-agnostic.

Memory tip: Remember the key selling points of REST with the acronym S-U-C - Stateless, URI standardized, Cross-platform compatible. If an answer claims REST increases coupling, it's the odd one out - REST is famous for doing the opposite.

No community discussion yet for this question.