Flask

Question 1

Web App

Answer 1

Application software that runs on a web server. –Dynamic site, web site, site, app

Question 2

End-user

Answer 2

The person who actually uses a particular product. –User, client, customer

Question 3

Front-end

Answer 3

A part of the system concerned with dealing with user interaction. –“frontend,” “front end,” presentation layer

Question 4

Back-end

Answer 4

A part of the system concerned with running application logic and storing application data. –“backend,” “back end,” data access layer

Question 5

Web APIs

Answer 5

Software built to translate messages between a user (often another program) and a web server. –web Application programming interface

Question 6

Client

Answer 6

Within the client-server model, a computer who sends a request for a resource to a server, and receives back a response

Question 7

Server

Answer 7

Within the client-server model, a computer who receives requests for a resource from a client, and sends back a response

Question 8

Web Server

Answer 8

Within the client-server model, a server that is specifically connected to a client over the web

Question 9

HTTP

Answer 9

A specific protocol that determines how a clients and web servers communicate

Question 10

Sending a request

Answer 10

The act of sending an HTTP request from a client to a server –Calling an API, making a request, requesting

Question 11

Endpoint

Answer 11

Another name for the “path” of a resource, usually in the context of an API–Path, request URL, route

Question 12

HTTP Method(HTTP verbs)

Answer 12

A word that describes the operation that the client wants to perform. The request method implies the nature of the request, whether it’s fetching a resource, sending new information, or something else. – required

Question 13

Path (or request URL)

Answer 13

The URL that the requested resource is located at. Depending on context, this may include parts of the URL such as http://, adadevelopersacademy.org/, or not. – required

Question 14

Query Parameters

Answer 14

Key-value pairs that describe information that can make this request more specific. Query params ultimately affect and become part of the request URL. –no required

Question 15

HTTP Headers

Answer 15

Colon-separated pairs of information to describe additional details that the server may need. –no required

Question 16

HTTP Body

Answer 16

Additional resources that need to be sent to the server. – no required

Question 17

Status Code

Answer 17

A number that indicates if a request was successful or unsuccessful, and why.–required

Question 18

Status Message

Answer 18

A description attached to the status code – required

Question 19

The requests package

Answer 19

A Python package. The package defines methods whose responsibility is to make HTTP requests and receive HTTP responses.

Question 20

REST

Answer 20

An architecture style for applications and APIs that uses the HTTP protocol and uses client-server architecture

Question 21

Uniform Interface

Answer 21

A REST design principle that that prefers reliable and predictable endpoints, and doesn’t prefer custom endpoints

Question 22

CRUD

Answer 22

Create, Read, Update, Delete.” An acronym that describes the four basic operations to work with saved resources

Question 23

Model

Answer 23

A representation of a single concept relevant to the application. The model defines the state and behavior for that concept. –Data model, resource, entity, domain model

Question 24

Database Migration

Answer 24

When working with relational databases, a representation of a change in a database’s schema. Migrations must be created and then applied to databases

Question 25

Deployment

Answer 25

The process of making software available to be used