Full Stack Web Development Version Control, Tooling & DevOps Flashcards

24 sample cards from the Version Control, Tooling & DevOps deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. In browser DevTools, what is the difference between the Console and Network panels?

   The Console logs messages/errors and runs JavaScript interactively; the Network panel records HTTP requests with their status, timing, headers, and payloads.

2. What is the difference between 'step over', 'step into', and 'step out' when debugging?

   Step over executes a function call without entering it; step into enters the called function; step out runs until the current function returns.

3. What is the purpose of source maps in front-end debugging?

   Source maps map minified/transpiled production code back to the original source, so DevTools can show readable file names, lines, and variable names.

4. What are environment variables, and why are they used in apps?

   They are key-value settings provided by the runtime environment (e.g., API keys, DB URLs, mode flags) used to configure an app without hard-coding values or committing secrets.

5. What is a .env file and why should it usually be git-ignored?

   A .env file stores environment variables as KEY=value pairs for local development; it's git-ignored because it often contains secrets that must not be committed.

6. What distinguishes development, staging, and production environments?

   Development is the local coding environment; staging mirrors production for final testing; production is the live environment serving real users.

7. What does it mean to deploy a static front-end app, and where is it typically hosted?

   It means uploading prebuilt HTML/CSS/JS assets to be served as-is, typically via a CDN or static host (e.g., Netlify, Vercel, GitHub Pages, S3+CloudFront).

8. What is a CDN and how does it improve front-end delivery?

   A Content Delivery Network is a geographically distributed set of cache servers that serve static assets from a location near the user, reducing latency and load.

9. How does deploying a back-end service generally differ from deploying a static front-end?

   A back-end is a long-running server process (needs a runtime, ports, scaling, databases, and process management), whereas a static front-end is just files served by a host/CDN.

10. What does CI/CD stand for, and what does each part mean?

    Continuous Integration (automatically build/test code on each change to catch issues early) and Continuous Delivery/Deployment (automatically release/deploy passing changes).

11. What is a CI/CD pipeline?

    An automated sequence of stages (e.g., install, lint, test, build, deploy) triggered by events like a push or PR to validate and ship code consistently.

12. What is the difference between Continuous Delivery and Continuous Deployment?

    Continuous Delivery automatically prepares releases but requires a manual approval to deploy to production; Continuous Deployment automatically deploys every passing change with no manual gate.

13. What does DNS do, and what is an A record vs a CNAME record?

    DNS resolves domain names to IP addresses; an A record maps a domain to an IPv4 address, while a CNAME record aliases one domain name to another.

14. What does HTTPS provide over HTTP, and what protocol secures it?

    HTTPS provides encryption, integrity, and server authentication over HTTP using TLS (Transport Layer Security), preventing eavesdropping and tampering.

15. What is an SSL/TLS certificate and what does Let's Encrypt provide?

    A certificate cryptographically proves a domain's identity and enables HTTPS; Let's Encrypt is a free, automated Certificate Authority that issues TLS certificates.

16. What is Docker and what core problem does it solve?

    Docker is a containerization platform that packages an app with its dependencies into a portable container, solving 'it works on my machine' by ensuring consistent environments.

17. What is the difference between a Docker image and a Docker container?

    An image is an immutable, read-only template (blueprint) of an app and its dependencies; a container is a running (or runnable) instance created from an image.

18. How do containers differ from virtual machines (VMs)?

    Containers share the host OS kernel and isolate at the process level (lightweight, fast), while VMs each run a full guest OS on a hypervisor (heavier, slower to start).

19. What is a Dockerfile?

    A text file with step-by-step instructions (e.g., FROM, COPY, RUN, CMD) that Docker uses to build an image automatically and reproducibly.

20. What is the difference between the CMD and RUN instructions in a Dockerfile?

    RUN executes commands at image build time (e.g., installing packages); CMD specifies the default command to run when a container starts from the image.

21. What Docker command runs a container from an image, and how do you map a port?

    docker run <image>; map a host port to a container port with -p hostPort:containerPort (e.g., docker run -p 8080:80 nginx).

22. What is a Docker volume and why use one?

    A volume is Docker-managed persistent storage mounted into a container, used so data (e.g., databases) survives container restarts or removal.

23. What is Docker Compose and when is it used?

    Docker Compose is a tool to define and run multi-container applications using a single YAML file (docker-compose.yml), ideal for apps with services like a web server, API, and database.

24. In Docker Compose, what does the command 'docker compose up' do?

    It reads the compose file, builds/pulls images as needed, creates a shared network, and starts all defined services (add -d to run them detached in the background).

What this deck covers

Version Control, Tooling & DevOps flashcards FAQ