Preview

The whole resource, exactly as a class sees it. Answers and marking are held back.

Web Technologies consolidation

Complete the sections in order, beginning with closed-book retrieval and then applying the ideas in the integrated contexts. No new required knowledge is introduced.

Episode A: a community equipment page

The page needs an h1, a linked image, an unordered equipment list and a form that accepts a named quantity. The CSS brief asks for the h1 to be white on dark green. JavaScript reads the quantity, doubles it for a two-day booking and displays the result in element id estimate.

Written answer8 marks

Write or precisely describe the HTML fragments for the image, list, form inputs and estimate element. Then write the external h1 CSS rule. Make every attribute, selector and declaration consistent.

Use Appendix 5d structures. Several valid page orders are possible.

Students type their answer here.

Written answer8 marks

Write JavaScript that reads quantity from element id quantity, calculates quantity * 2, writes the result to estimate, and returns it. Explain what fails if the HTML uses id Estimate with a capital E.

Record read, calculation, write and return as separate states.

Students type their answer here.

Apply the ideas together

The next section combines earlier ideas in a changed context. Complete it independently, returning to a worked model only when you have identified a specific misconception to repair.

Episode B: discovery, rank and booking decisions

The page is new. A council directory links to it, a crawler revisits it, and the provider adds a record. Later, an established repair organisation also links to the page. The browser validates quantity format; the service must check stock in its shared database.

Written answer8 marks

Explain the page's journey from council link to a query result. Then explain how the established organisation's incoming link could affect PageRank without claiming an exact score or guaranteed position.

Keep crawler/index/query and directed-link reasoning separate.

Students type their answer here.

Written answer8 marks

Allocate and justify these tasks: render HTML, apply CSS, show an immediate quantity warning, revalidate quantity, check central stock, record the booking and display the returned decision. Explain why the browser warning cannot authorise the booking.

Follow request to server and response to browser.

Students type their answer here.

Multiple choice1 mark

Which event is specifically an indexing event rather than a PageRank relationship?

AAn important page adds an incoming link to the target
BA directed graph shows A → P
CA crawler revisits a changed page and updates the provider's stored record
DA target receives several links of different importance

Fill in the blanks4 marks

HTML supplies structure, CSS supplies checkpoint gap 1, and JavaScript supplies behaviour. A query searches the provider's checkpoint gap 2. PageRank considers checkpoint gap 3 links. Protected database decisions remain checkpoint gap 4 side.

Review your responses

Use the evidence in your completed responses to identify the first model, state transition or reasoning link that needs improvement. Correct that point, then reapply it to the changed context.