Community resourceWorksheet
OCR H446 1.3.4 Web Technologies exam transition
Part 8 of 8 · H446 1.3.4 · Web technologies
The assessment closing the H446 1.3.4 sequence, meant to be worked independently and without checking answers along the way. It asks for HTML, CSS and JavaScript written to briefs, then for explanation of indexing and ranking and evaluation of where processing belongs.
Students will:
- write a page, an external stylesheet and a function to stated briefs under examination conditions
- diagnose an identifier mismatch between a page and its script
- explain how a page is discovered, indexed, updated and removed, and why results can lag
- compare pages with different incoming-link profiles and state the limits of that reasoning
- justify where each task in a service route runs, including why a server repeats a browser check
Inside: 2 explanation cells, 1 multiple-choice question, 1 fill-in-the-blanks cell and 8 written answers. 64 marks, about 55 to 70 minutes.
Series: H446 1.3.4 · Web technologies, part 8 of 8.
Shared by Coding PathwayVerified teacher
- 12 cells
- About 60 minutes
- CC BY-SA 4.0
- Shared 31 Aug 2026
- Updated 3 Sept 2026
Preview
The whole resource, exactly as a class sees it. Answers and marking are held back.
Web Technologies examination transition
Complete this assessment independently and without checking answers as you go. Use the command words, supplied evidence and context carefully; correctness is held where the platform supports it.
Which statement correctly distinguishes HTML, CSS and JavaScript?
- AHTML controls all behaviour, CSS stores data, and JavaScript supplies structure
- BHTML ranks pages, CSS crawls links, and JavaScript stores the search index
- CAll three are server-only languages
- DHTML structures content, CSS controls presentation, and JavaScript supplies behaviour
- href
- src
- .card
- #total
- =card
Write HTML for a page containing title Swap Shelf, h1, paragraph, image with src/alt/height/width, an ordered two-step list, and a form with named text, password and submit inputs.
Indent the complete html/head/body structure.
Students type their answer here.
Write external CSS so all h1 elements use white text on #503070; class hint uses font-family Verdana and font-size 16px; id summary has a solid black 2px border and width 360px. Explain one difference from inline CSS.
Use element, class and id selectors.
Students type their answer here.
The page has inputs with IDs first and second and an empty element id sum. Complete or write JavaScript that reads both values, calculates their total, displays it in sum, and returns it. Then diagnose an ID mismatch.
Trace variable and DOM states. Minor syntax inaccuracies should not obscure correct logic.
Students type their answer here.
A new repair-café page is linked from a known directory, later changes its opening times, and is eventually removed. Explain discovery, index add/update/removal and what a user query searches. Include why results can lag behind the live page.
Use crawler → collect → provider index → query.
Students type their answer here.
Page P receives one incoming link from a highly important site. Page Q receives three incoming links from low-importance sites. Compare their possible PageRank positions and propose one defensible action for each. State two limitations of your conclusion.
Use link direction and source importance; do not calculate.
Students type their answer here.
For an event-ticket service, classify and justify: apply CSS; browser warning for an empty field; authoritative ticket-limit check; central availability query; record payment status; display the returned result. Explain why the server repeats important validation.
Follow client request, server decision and client display.
Students type their answer here.
A small heritage project wants its new archive pages to be discoverable and well placed, while keeping uploads responsive and protecting shared records. Discuss indexing, PageRank and client/server-side processing. Recommend actions and a processing split, evaluating benefits, drawbacks and limits.
Keep three mechanisms distinct and apply every claim to the project.
Students type their answer here.
Give a concise boundary note for each: (1) why PageRank calculation/code is not required here; (2) why JavaScript is not always a location label even though browser JavaScript is an OCR client-side example; (3) why client-server network organisation is different from client/server-side processing.
Protect the H446 model while remaining technically honest.
Students type their answer here.
Review your responses
Check every response against its command word and the supplied constraints. Strengthen unsupported assertions with an accurate mechanism and a contextual consequence before submitting.