Quiz
Fourteen questions about the most useful things in this learning series. Think of your answer first, then reveal the explanation and compare. No marks, no timer, and nothing gets saved.
The essentials, in your own words
What are the three basic layers of a tech stack?
The front end draws the screens and reacts to clicks. The service layer runs the features, permissions, and rules. The database stores information and answers requests to read or change it.
Review the three layersFor example
DuckBuddy’s front end shows a hobby filter, its service searches for profiles you may see, and its database stores the people and their hobbies.
What do HTML, CSS, JavaScript, and React do in the front end?
HTML defines the page structure. CSS controls its appearance and layout. JavaScript makes the page interactive. React is an example of a JavaScript library for building reusable interface parts.
Review the front endFor example
HTML gives a profile card a name field and button, CSS arranges and colors them, and JavaScript responds when you click Connect. React can reuse the same card design for every person.
Which layer decides what a feature does and whether you are allowed to use it?
The service layer runs the feature’s programming and rules. It checks who is asking, validates their input, checks permissions, and decides what to ask the database. Hiding a button in the front end is not enough to protect an action.
Review the service layerFor example
When you turn email notifications off, the service checks your account and saves that preference for you—not for a different user whose ID someone typed into a request.
What is the difference between a database, its schema, and its data?
A database is the organized store. Its schema defines the structure: tables, fields, types, relationships, and rules. Its data is the actual stored values inside that structure.
Review database versus schemaFor example
A profiles table with name, hobby, and city fields is part of the schema. Anna, hiking, and Austin are data. For a database-driven menu, the schema defines label and parent-menu fields; the data supplies the actual menu options.
Why might one company use several different kinds of database?
Different information has different needs. A company can choose the best tool for each job: structured records, flexible documents, fast temporary information, or connections between people. More databases also mean more work to operate and keep consistent.
Review the DuckBuddy database exampleFor example
The illustrative DuckBuddy stack uses PostgreSQL for profiles, Redis for fast temporary information, and Neo4j for relationships that help suggest friends.
What does DNS do—and which part of a URL does it look up?
DNS finds a network address for a website’s domain name. It does not look up the page path, search filter, or database records. Browsers can reuse a recent DNS answer, so every click does not require a new lookup.
Review DNSFor example
For https://duckbuddy.net/people?hobby=hiking, DNS looks up duckbuddy.net. The /people path and hobby=hiking filter travel in the request afterward.
What does HTTPS protect, and does it give someone permission to see private data?
HTTPS encrypts messages in transit, protects against changes along the way, and helps the browser verify the server it is talking to. It does not replace the service’s checks of who you are and what you may access.
Review HTTPSFor example
A hiking-profile request and its answer travel encrypted. The service still must leave out profiles or fields the viewer is not permitted to see.
What are CRUD’s four actions, and which one does a hiking search use?
CRUD means Create, Read, Update, and Delete: add information, look it up, change it, or remove it. Searching for existing hiking profiles is Read; simply viewing the results does not change their records.
Review CRUDFor example
Book a room: Create a booking. Open its details: Read it. Change its time: Update it. Remove a record: Delete it, if the application’s rules allow deletion.
Are an HTTPS method and a CRUD action the same thing?
No. An HTTP method describes the browser-to-service request; CRUD describes operations on stored data. GET commonly asks to read, and POST commonly submits something, but one request can cause several database actions.
Review methods versus CRUDFor example
One POST to Like a post can Create your like record and Update a like count. The HTTPS method is POST; the database work includes both Create and Update.
How does a click get information from the database back onto the screen?
The browser sends an HTTPS request to company servers. The service checks the request and asks the database for permitted information. The database answers the service, which sends an HTTPS response back. The front end draws the result. In the examples here, the browser does not directly access the private database.
Review the seven-step journeyFor example
Choose Hiking → request /people?hobby=hiking → service checks access → database reads matching profiles → service returns results → profile cards show Anna in Austin.
What is the difference between authentication and authorization?
Authentication confirms who you are. Authorization checks what you are allowed to do. Being signed in does not mean you may view every record or change someone else’s settings.
Review access-related termsFor example
A CRM recognizes your sign-in session, then separately checks whether your company and role allow you to view contact 42.
What comes back in a response besides the information you asked for?
A response has a status code and headers, and often a body containing HTML or JSON data. 200 means success, 404 means not found, 401 means authentication is missing or invalid, and 403 means access is forbidden.
Review responses, JSON, and status codesFor example
A successful search with no hiking matches can return 200 and an empty list. That is different from 404 for a page that does not exist.
Why do different company types choose different stacks?
They have different jobs, scale, reliability needs, budgets, existing systems, and team skills. The stacks in this project are typical examples, not verified private internals or the only valid choices.
Compare typical company stacksFor example
A bank needs dependable transaction records and strict access checks. A social network also needs fast feeds, chats, and relationship lookups. Their priorities can lead to different tools.
Why can a small feature request require changes in more than one layer?
A visible control may need new front-end behavior, a service request and rules, and database fields or records. The team also considers testing, privacy, existing data, and deployment. Not every feature needs all layers to change.
Explore a feature requestFor example
Adding a notification preference needs a toggle on screen, service code to validate and save it, and stored preference data. Changing only a button’s color usually needs front-end work, not a new database column.
Got most of them?
You know the big picture: what each layer does, how a click travels, and why feature changes can touch more than the screen. Revisit any answer that surprised you, then try applying what you learned to a feature request.