Internet Technology - Quiz - FHNW
Internet Technology - Quiz - FHNW
Internet Technology - Quiz - FHNW
-
- 1 / 171
-
Flashcards
Authentication is the process of the server proving its identity to the client.
In monolithic architecture, the application is built as multiple independent pieces of code.
Partner APIs are accessible to a predefined group through authentication and authorization.
In client-server architecture, protocols such as FTP and SMTP are exclusively used.
An Internet Service Provider (ISP) is a company that helps connect networks using both physical cables, such as Ethernet, and wireless methods.
The Hypertext Transfer Protocol (HTTP) is designed to enable communications between clients and servers.
Credentials are secret pieces of information used to prove the client's identity, such as a username and password.
The Swagger Editor supports YAML and JSON formats.
JSON Schema does not validate data and is not useful for automated testing or ensuring the quality of client-submitted data.
Web-based APIs are used only within a single application or system.
Ubiquitous Language using Domain Model is a key concept in Domain Driven Design (DDD).
JSON is a text format that is completely language independent.
Entities in DDD are objects with an individual identity and are usually stored in databases.
APIs only follow a client-server architecture and do not include protocols or definitions.
DDD principles can be mapped to REST APIs.
An Internet Service Provider (ISP) is a company that helps connect one network to another using either physical cables, such as Ethernet, or wireless methods.
Swagger UI is automatically generated from the OpenAPI specification.
HTTP is based on client-server principles, allowing a client system to establish a connection with the server machine for making a request.
Monolithic architecture has all components inter-dependent and required to run the application.
API integration does not involve managing translations in inter-API communication.
RESTful logic usually follows all REST principles, while REST-based logic usually follows some but not all REST principles.
The cost of web application development tools is generally low, with many options available for research and education, and pricing models are usually clear and inexpensive.
The example of using fetch() to retrieve data from an API is:
fetch('API_URL')
.then(response => response.json())
.then(data => console.log(data));
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:
Informational responses (100 - 199)
Successful responses (200 - 299)
Redirection messages (300 - 399)
Client error responses (400 - 499)
Server error responses (500 - 599)
The status codes listed below are defined by RFC 9110
SSL certificates are self-signed and do not require verification by a CA
In Single Page Applications (SPAs), most logic is on the client-side, with the server used primarily for data storage.
Controlling APIs involves managing a catalog and ensuring security.
JSON is an ideal data-interchange language.
Consuming APIs can be done directly or via third-party developers.
Security concerns in web application development are negligible and do not involve privacy issues.
Tiers are about where your code runs.
Monolithic architecture is easy to deploy but difficult to scale or maintain as the code grows.
REST constraints include Uniform Interface, Stateless, Cacheable, Client-Server, and Layered System.
Microservices communicate via heavyweight protocols.
An API is a set of definitions and protocols for communication with a service, often referred to as a contract.
Access tokens are used to prove the server's identity to the client.
The Transmission Control Protocol (TCP) ensures reliable transfer of data but not dependable transfer.
One organizational challenge with APIs is staying competitive by creating APIs rapidly.
RESTful refers to logic implementing REST architecture and providing an interface to the implementing software.
Web-based APIs are commonly used over the internet and examples include RESTful APIs, SOAP APIs, and GraphQL APIs.
