CWISA-102 practice question 2 of 15
What is an advantage of using HTTP-based processing?
Full set: 67 questionsThe primary advantage of using HTTP-based processing is its simplicity and the widespread familiarity within the developer community. HTTP is a text-based protocol with a straightforward request-response model and a small set of well-defined methods (e.g., GET, POST, PUT, DELETE). This simplicity, combined with its role as the foundation of the World Wide Web, means that a vast number of developers already understand its principles. Consequently, there is extensive support for HTTP in virtually all programming languages, frameworks, and tools, which significantly lowers the barrier to entry for creating and consuming web services and APIs. Why Incorrect Options are Wrong
A. It is more secure than other transports, when using SSH HTTP is not inherently secure. Security is provided by layering it over TLS (HTTPS). Using SSH is a tunneling method, not a native feature of HTTP.
B. It is faster than any other APIs This is incorrect. API speed depends on many factors. Other protocols, such as gRPC (which uses HTTP/2) or custom TCP-based protocols, can offer lower latency.
D. It Is more secure than any other APIs This is false. HTTP is a clear-text protocol. The security of an API depends on its implementation (e.g., using HTTPS, authentication, authorization), not just the protocol. --- References
1. Mozilla Developer Network (MDN) Web Docs. In its overview of HTTP, MDN highlights the protocol's simplicity as a key design feature. It states, "HTTP is simple... HTTP messages can be read and understood by humans, providing easier testing for developers, and reduced complexity for newcomers." Source: MDN Web Docs, "An overview of HTTP," section "Simple." (developer.mozilla.org/en-US/docs/Web/HTTP/Overview)
2. Internet Engineering Task Force (IETF) RFC 7230. This document, which defines the message syntax and routing for HTTP/1.1, is built upon the foundational principles of its predecessors. The architecture described emphasizes a stateless, request-response paradigm that is simple to implement and scale, contributing to its widespread adoption. Source: IETF RFC 7230, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing," Section 2.1 "Client/Server Messaging" and Section 2.2 "Stateless." (https://doi.org/10.17487/RFC7230)
3. University of California, Berkeley, Courseware. In course materials for CS 162 (Operating Systems and System Programming), lectures on distributed systems often compare protocols. The discussion on HTTP for APIs (like REST) emphasizes its use of well-understood, universal standards and its firewall-friendly nature as significant advantages over more complex binary protocols. Source: UC Berkeley EECS, CS 162 Lecture Slides, "Lecture 23: Distributed Systems," section on Remote Procedure Calls and REST. (Accessed via course materials available at eecs.berkeley.edu)
Keep practicing
Take the free CWISA-102 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other CWISA-102 practice questions
- Question 1Which one of the following is NOT a typical Smart City application?
- Question 3You have implemented a wireless mesh network. All mesh nodes are properly configured for …
- Question 4Which one of the following items has driven large serving 5- to 18-year-old students?
- Question 5What organization maintains and publishes the 802.15.4 Standard?
- Question 6What factor severely limits the range of systems operating in the 60GHz band?
- Question 7You are implementing a smart office wireless solution for a small business. The business …
