Lab Course 1 - Programming and Web Development Exam Review

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/57

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards covering general programming concepts, database management, web security, authentication, and CSS styling frameworks based on the Lab Course 1 lecture notes.

58 Terms

1
New cards

HTTP (HyperText Transfer Protocol)

The stateless communication protocol of the Web between a client (browser) and a server that operates on a request/response model, treating each request independently.

2
New cards

HTTP GET

An HTTP method used to retrieve (read) data from a server without modifying server state.

3
New cards

HTTP POST

An HTTP method used to create a new resource on the server.

4
New cards

HTTP PUT

An HTTP method used to completely replace an existing resource on the server.

5
New cards

HTTP PATCH

An HTTP method used to apply partial updates to an existing resource on the server.

6
New cards

HTTP DELETE

An HTTP method used to remove a specified resource from the server.

7
New cards

HTTP Status Code Families

Three-digit numeric codes divided into five categories by their initial digit: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).

8
New cards

Common HTTP Status Codes

Key response codes: 200 OK (successful request), 201 Created (resource created after POST), 400 Bad Request (invalid data), 401 Unauthorized (missing or invalid authentication), 403 Forbidden (authenticated without permissions), 404 Not Found (resource does not exist), and 500 Internal Server Error (unexpected server crash).

9
New cards

REST API

An architectural style for network APIs built on HTTP where data is represented as identifiable resources using distinct URLs, characterized by client-server separation, statelessness, cacheability, and uniform interfaces.

10
New cards

JSON (JavaScript Object Notation)

A lightweight, language-independent text format for structured data exchange based on key-value pairs, which is more compact than XML and natively matches JavaScript objects.

11
New cards

Encapsulation

The OOP pillar that hides the internal state of an object and only exposes public methods or interfaces, such as using private fields with getters and setters.

12
New cards

Inheritance

The OOP pillar where a child class inherits properties and methods from a parent class to prevent code duplication.

13
New cards

Polymorphism

The OOP pillar allowing the same method name to execute distinct behaviors based on the concrete object type via overriding or overloading.

14
New cards

Abstraction

The OOP pillar that exposes only essential concepts and functionalities while hiding internal implementation details using abstract classes and interfaces.

15
New cards

MVC (Model-View-Controller)

An architectural design pattern separating an application into three distinct components: Model (data and business logic), View (user interface presentation), and Controller (request handler that coordinates Model and View).

16
New cards

Git

A distributed version control system that tracks source code modification history and enables multiple developers to collaborate on the same codebase.

17
New cards

Git Branch

An independent line of development branching off from a specific point in a repository history, allowing parallel work without altering the main branch.

18
New cards

Git Merge Conflict

A conflict occurring when Git cannot automatically merge two branches that modified the exact same section of a file, requiring manual resolution of conflict markers (<<<<<<

19
New cards

Pull Request (PR)

A formal proposal on platforms like GitHub, GitLab, or Bitbucket to merge code changes from one branch into another, serving as a hub for discussion and review.

20
New cards

Code Review

The process where peer developers examine proposed code before merging to identify bugs, check security, verify performance, uphold team standards, and share knowledge.

21
New cards

Trello

A visual project management tool based on the Kanban methodology that organizes workflows using Boards, Lists (e.g., To Do, In Progress, Done), Cards, Labels, Members, and Due dates.

22
New cards

IDE (Integrated Development Environment)

A comprehensive software suite combining a code editor, compiler or interpreter, debugger, package manager, and version control integration into a single application (e.g., IntelliJ IDEA, Visual Studio, PyCharm).

23
New cards

Browser DevTools

Integrated browser tools used to inspect, debug, and optimize web applications via panels including Elements, Console, Network, Sources, Application, and Performance.

24
New cards

Postman

A desktop/web tool utilized to test, debug, and document HTTP APIs without writing client code, supporting custom requests, collections, environment variables, and automated tests.

25
New cards

SDLC (Software Development Life Cycle)

A structured 7-phase process for software creation consisting of Requirements Gathering, Analysis and Planning, Design, Implementation (Coding), Testing, Deployment, and Maintenance.

26
New cards

Agile vs. Waterfall

Agile is an iterative, flexible methodology structured in short cycles (typically 2 weeks) with continuous client feedback; Waterfall is a rigid, sequential model where each phase must finish before the next begins.

27
New cards

Scrum Sprint

A fixed timebox of 1 to 4 weeks during which a development team delivers a usable increment, featuring Sprint Planning, Daily Standups (15 minutes), Sprint Reviews, and Sprint Retrospectives.

28
New cards

SOLID Principles

Five OOP design principles: Single Responsibility (one reason to change), Open/Closed (open for extension, closed for modification), Liskov Substitution (subtypes must be substitutable for base types), Interface Segregation (specific interfaces over generic ones), and Dependency Inversion (depend on abstractions, not concretions).

29
New cards

DRY (Don't Repeat Yourself)

A software principle stating that every piece of logic must have a single, unambiguous representation within a codebase to eliminate duplicate code and simplify maintenance.

30
New cards

KISS (Keep It Simple, Stupid)

A design principle emphasizing that systems work best if kept simple, avoiding unnecessary abstractions, premature optimizations, and overly complex design patterns.

31
New cards

Unit Test

An automated test that validates the expected behavior of the smallest testable piece of code (such as a single function or method) in total isolation from the rest of the application.

32
New cards

RDBMS (Relational Database Management System)

A database system that manages data structured in interrelated tables with rows and columns using Structured Query Language (SQL), such as MSSQL, MySQL, Oracle Database, and PostgreSQL.

33
New cards

Primary Key

A column or set of columns in a database table that uniquely identifies each record; it strictly forbids duplicate values and cannot contain NULL values.

34
New cards

Foreign Key

A column in a relational table that references the Primary Key of another table, ensuring referential integrity across related data.

35
New cards

Unique Key

A database constraint enforcing that all values in a column remain distinct from one another, while permitting a single NULL value unlike a Primary Key.

36
New cards

Many-to-Many Relationship (N:M)

A database relationship where multiple rows of Table A connect to multiple rows of Table B, implemented using an intermediate junction table containing composite foreign keys.

37
New cards

SQL CRUD Operations

The four foundational database operations: Create (INSERT), Read (SELECT), Update (UPDATE), and Delete (DELETE).

38
New cards

SQL JOINs

Clauses combining rows from multiple tables based on related keys: INNER JOIN returns matching rows from both, LEFT JOIN returns all left rows plus matched right rows, RIGHT JOIN is the inverse of LEFT, and FULL JOIN returns all rows from both tables.

39
New cards

Database Index

An auxiliary data structure (typically a B-Tree) that speeds up data retrieval queries (SELECT) on frequently filtered columns, while slightly slowing down INSERT, UPDATE, and DELETE operations.

40
New cards

1NF (First Normal Form)

A normalization level requiring every column cell to hold a single atomic value (no sets or repeating groups) and every row to be unique.

41
New cards

2NF (Second Normal Form)

A normalization level that fulfills 1NF and ensures every non-key column is fully functionally dependent on the entire Primary Key, eliminating partial key dependencies.

42
New cards

3NF (Third Normal Form)

A normalization level that fulfills 2NF and removes transitive dependencies, ensuring non-key columns do not depend on other non-key columns.

43
New cards

SQL Constraints

Rules enforced on columns to protect data integrity, including NOT NULL (disallows nulls), CHECK (enforces a boolean condition), DEFAULT (supplies fallback values), UNIQUE (guarantees unique values), and FOREIGN KEY (enforces referential integrity).

44
New cards

Stored Procedure vs. User Defined Function

A Stored Procedure executes a precompiled sequence of SQL operations, accepts IN/OUT parameters, can modify tables, and is not required to return a value; a Function must always return a value and is callable within SQL expressions without modifying data.

45
New cards

ACID Properties

The four defining properties of reliable database transactions: Atomicity (all-or-nothing execution), Consistency (maintains valid states), Isolation (concurrent transactions execute independently), and Durability (committed changes persist through crashes).

46
New cards

SQL Injection

A security vulnerability where attackers inject raw SQL commands into application inputs to alter database queries, prevented primarily through parameterized queries (prepared statements) and ORMs.

47
New cards

Authentication vs. Authorization

Authentication confirms the identity of a user ('Who are you?'), while authorization determines the access permissions granted to an authenticated identity ('What are you allowed to do?').

48
New cards

JWT (JSON Web Token)

A compact, URL-safe standard token for securely transmitting claims composed of three dot-separated components: Header (algorithm and token type), Payload (claims data), and Signature (server cryptographic validation).

49
New cards

Access Token vs. Refresh Token

An access token has a short lifespan (e.g., 15 minutes) and authorizes protected requests; a refresh token has a longer lifespan (e.g., 7 days) and is exchanged to issue a new access token without requiring re-login.

50
New cards

httpOnly Cookie

A secure client-side storage mechanism that cannot be accessed by client-side JavaScript, protecting sensitive authentication tokens against Cross-Site Scripting (XSS) attacks.

51
New cards

Bcrypt Password Hashing

A slow, one-way cryptographic hashing function incorporating a random salt to ensure identical passwords have unique hashes, along with adjustable cost factors (rounds) to prevent brute-force attacks.

52
New cards

CORS (Cross-Origin Resource Sharing)

A browser security mechanism that restricts web applications on one origin from requesting resources located on a different origin unless explicit HTTP access-control headers permit it.

53
New cards

XSS (Cross-Site Scripting)

A security exploit where malicious JavaScript is injected into trusted web applications and executed in the victim's browser, mitigated by output escaping, CSP headers, input sanitization, and httpOnly cookies.

54
New cards

HTTPS and SSL/TLS

An encrypted communication protocol using TLS certificates issued by a Certificate Authority to authenticate web servers and safeguard data transmissions against Man-in-the-Middle eavesdropping.

55
New cards

Bootstrap Grid System

A responsive, 12-column flexbox-based layout framework built around container, row, and col-* classes across breakpoints (sm, md, lg, xl).

56
New cards

Tailwind CSS

A utility-first CSS framework that provides low-level utility classes directly mapped to CSS properties, featuring PurgeCSS to eliminate unused styles and a tailwind.config.js configuration file.

57
New cards

Responsive Web Design

An interface design methodology enabling web layouts to dynamically adapt to varying screen viewports using CSS media queries, standard breakpoints (576px, 768px, 992px, 1200px), and relative units.

58
New cards

Flexbox vs. CSS Grid

Flexbox is a one-dimensional CSS module designed for distributing items along a single axis (row or column), whereas CSS Grid is a two-dimensional layout system that manages rows and columns simultaneously.