Web Development Foundations (D276) Exam Topics and Questions

This topic sets the floor for everything that follows. Before you touch a line of HTML or CSS, the exam expects you to reason about how the web works as a system: how browsers request and render content, what separates design decisions from development decisions, and why those distinctions matter when something breaks. The questions here are deceptively conceptual. Candidates who skim this topic because it sounds introductory are the ones who drop marks on it. Slow down and make sure you can explain the underlying model, not just name it.

The core of this topic is the relationship between client and server. You need to understand what happens between a user typing a URL and a page appearing on screen, including the roles of DNS resolution, HTTP requests and responses, and the browser's rendering pipeline. Know what a static site is and how it differs from a dynamic one, because the exam draws on that distinction in applied scenarios.

Design principles matter here too. Concepts like visual hierarchy, accessibility, and responsive design are not decoration; they are tested as decision-making frameworks. When the exam presents a scenario and asks what a developer should prioritise, knowing which principle governs that situation is what separates a confident answer from a guess. User experience and usability are treated as technical concerns, not aesthetic ones, so approach them that way.

How Web Design and Development Fundamentals is tested

Items in this topic tend to be scenario-based rather than definitional. You will not be asked to recite a definition; you will be asked to identify the correct course of action or the most appropriate design choice given a described situation. That means items reward applied reasoning over memorised vocabulary.

The most common trap is treating foundational concepts as too simple to study carefully. Candidates assume they already know what a web server does or what responsive design means, and they answer from a vague general impression rather than a precise mental model. The exam exploits that vagueness. Two answer options will often both sound reasonable, and the distinguishing factor is a detail you only notice if you studied the concept with some rigour.

Accessibility and usability questions are another place marks are lost. Candidates who treat these as soft topics fare worse than those who understand the specific guidelines and rationale behind them. Items reward knowing why a practice exists, not just that it exists.

Where the first topic asked you to reason about the web as a system, this one asks you to work inside it. HTML Structure and Implementation is where abstract ideas about content and semantics become concrete markup decisions. The exam does not care whether you can write HTML from memory; it cares whether you understand why one element is the right choice over another and what breaks when you get that wrong. Semantic correctness and document structure are the two areas where marks are most often left on the table.

Expect the exam to test your understanding of semantic HTML elements and the reasoning behind them. The difference between a div and a section, or between a button and an anchor, is not cosmetic. Each carries meaning that affects accessibility, SEO, and browser behaviour. Know what each structural element communicates to the browser and to assistive technologies.

Forms are a high-yield area. The exam expects you to know the attributes and input types that control form behaviour, and what happens when they are misused or omitted. Validation, labels, and the relationship between form controls and their associated elements are all fair game. Tables are another area candidates underestimate: knowing when a table is appropriate and how to mark it up accessibly is tested separately from knowing how to make one appear on screen.

How HTML Structure and Implementation is tested

This topic rewards precision. Items will present a snippet of markup or a described document structure and ask you to identify what is wrong, what is missing, or what the best alternative would be. The trap is answering on visual outcome rather than semantic correctness. Two elements might produce the same appearance in a browser and still have very different meanings; items are designed to catch candidates who reason from appearance.

Form-related items are particularly unforgiving. Missing or mismatched label associations, incorrect input types, and absent required attributes are all scenarios the exam uses to test whether you understand how form markup actually functions. Candidates who have only ever written forms by trial and error in a code editor often struggle here because the exam asks about the standard, not the workaround.

Accessibility comes up repeatedly and is rarely flagged as an accessibility question. It arrives disguised as a question about correct markup, which means you need to carry accessibility reasoning into every structural decision, not just the ones that mention screen readers or ARIA.

After HTML establishes what content is, CSS determines how it behaves visually and spatially. This topic is where candidates who learned CSS by copying examples start to feel the pressure, because the exam asks you to reason about layout systems and cascade rules rather than reproduce working code. The two areas that separate passing candidates from those who fall short are the box model and layout models: if you have any uncertainty about how browsers calculate size and position, this is the topic to work through carefully before exam day.

How CSS Styling and Layout is tested

CSS items on this exam are built around scenarios where something does not look or behave as expected, and you must identify the rule or property responsible. That format rewards a clean mental model of specificity, inheritance, and the cascade. Candidates who have memorised property names but cannot predict how conflicting rules resolve will find these items difficult.

The box model is a consistent source of lost marks. Items present a layout scenario and require you to account for padding, border, and margin in calculating dimensions or spacing. The distinction between the standard box model and the alternative box-sizing behaviour is the kind of detail the exam uses to separate candidates who have thought carefully about the topic from those who have not.

Flexbox and grid layout items test whether you know which properties apply to the container and which apply to the child elements. Mixing those up is the most common error. Responsive design questions ask you to reason about media queries and breakpoints in terms of intent, not syntax. Items reward understanding what a rule is trying to achieve, not just what it says.