Back-End Development

Question 1

API (Application Programming Interface)

Answer 1

A set of rules that allows different software applications to communicate.

Question 2

Database

Answer 2

A structured collection of data stored electronically, often using SQL or NoSQL.

Question 3

Deployment

Answer 3

The process of releasing a software application to production.

Question 4

Repository (Repo)

Answer 4

A storage location for code, usually in version control systems like GitHub or GitLab.

Question 5

Rollback

Answer 5

Reverting an application to a previous version after a failed deployment.

Question 6

Commit

Answer 6

Saving changes to a local version control system before pushing them to a repository.

Question 7

Merge Conflict

Answer 7

An issue that occurs when two branches of code have conflicting changes.

Question 8

CI/CD (Continuous Integration/Continuous Deployment)

Answer 8

A method of frequently delivering code changes with automation.

Question 9

Endpoints

Answer 9

The URLs where APIs accept requests from clients.

Question 10

Standup

Answer 10

A short daily meeting (usually 15 minutes) where team members give status updates.

Question 11

Sprint

Answer 11

A set time period (usually 1–2 weeks) during which specific work has to be completed.

Question 12

Task

Answer 12

A specific unit of work, often part of a larger story or feature.

Question 13

Blocker

Answer 13

Something that prevents a developer from progressing with their task.

Question 14

ETA (Estimated Time of Arrival)

Answer 14

An estimated time when a task will be completed.

Question 15

In progress

Answer 15

Work that is currently being done.

Question 16

Code review

Answer 16

When another developer reviews your code before it gets merged or deployed.

Question 17

Ticket

Answer 17

A tracked unit of work in tools like Jira or Trello.

Question 18

PR (Pull Request)

Answer 18

A request to merge code into a shared branch in version control (like Git).

Question 19

Sprint Planning

Answer 19

A meeting to decide which tasks the team will work on during the next sprint.

Question 20

Story Point

Answer 20

A unit of measurement to estimate the effort needed to complete a task (often based on complexity, not time).

Question 21

Technical Debt

Answer 21

Shortcuts in code or design that may work for now but cause problems later.

Question 22

Refactoring

Answer 22

Improving existing code without changing its behavior.

Question 23

Feasibility

Answer 23

How practical or possible a task or feature is to implement.

Question 24

Edge Case

Answer 24

A situation that occurs outside of normal conditions and needs special handling.

Question 25

Backlog

Answer 25

A prioritized list of tasks and features to be completed in future sprints.

Question 26

Sprint Goal

Answer 26

The overall objective or theme for a sprint cycle.

Question 27

Velocity

Answer 27

The average number of story points a team can complete in a sprint.

Question 28

Diff

Answer 28

A file showing what code was added, changed, or removed.

Question 29

Readability

Answer 29

How easy the code is to read and understand.

Question 30

Maintainability

Answer 30

How easy the code is to update or change in the future.

Question 31

Best Practice

Answer 31

Recommended way of writing or structuring code based on experience or standards.

Question 32

Convention

Answer 32

Agreed rules or style guide in a codebase (naming, formatting, etc.).

Question 33

DRY (Don't Repeat Yourself)

Answer 33

A principle that encourages reducing duplication in code.

Question 34

Refactor

Answer 34

To restructure existing code without changing its external behavior.

Question 35

Debug

Answer 35

To find and fix errors in code.

Question 36

Bug

Answer 36

A flaw in code that causes incorrect or unexpected behavior.

Question 37

Stack Trace

Answer 37

A report that shows the function call sequence leading to an error.

Question 38

Log Output

Answer 38

Messages printed to the console to show what's happening in the program.

Question 39

Break Point

Answer 39

A set point in code where execution stops, usually for debugging.

Question 40

Exception

Answer 40

An error that disrupts the normal flow of execution.

Question 41

Runtime Error

Answer 41

An error that occurs while a program is running.

Question 42

Null Pointer

Answer 42

An error that happens when you try to access something from a nil/undefined variable.

Question 43

Regression

Answer 43

A bug that appears after a new change breaks something that previously worked.

Question 44

Grooming / Refinement

Answer 44

Reviewing backlog items, clarifying requirements, and estimating effort.

Question 45

Scalability

Answer 45

The system’s ability to handle growth in users, requests, or data.

Question 46

Caching

Answer 46

Storing temporary data to speed up performance.

Question 47

Load Balancing

Answer 47

Distributing network traffic across servers for efficiency

Question 48

Rate Limiting

Answer 48

Restricting the number of API requests per client.

Question 49

Authentication

Answer 49

Verifying a user’s identity.

Question 50

Authorization

Answer 50

Deciding what resources a user is allowed to access.

Question 51

Throughput

Answer 51

The amount of work or requests the system can handle in a time frame.

Question 52

Edge Case

Answer 52

Rare or extreme conditions that must still be handled.