Unit 1 Module 2 - Information Technology Practice
This module tests applied productivity skills: word processing, spreadsheets, databases, presentations, web authoring and file management. Questions usually present a task and ask you to choose the right tool, write a correct formula or query, or explain a feature precisely.
Core skills and rules
- Word processing: use styles for consistent headings; a mail merge needs a main document, a data source and merge fields. Templates and section breaks control layout.
- Spreadsheets: every formula begins with
=. A relative reference such asA1changes when copied; an absolute reference such as$A$1does not; mixed references fix only the row or column. Common functions includeSUM,AVERAGE,IF,COUNTIFandVLOOKUP. Charts should match the data type: column for comparison, line for trend, pie for parts of a whole. - Databases: a table stores records (rows) made of fields (columns). A primary key uniquely identifies each record and cannot be null; a foreign key links tables. Queries filter with criteria; reports present output; validation restricts input.
- Presentations: transitions move between slides; animations affect objects on a slide. A slide master enforces consistent formatting.
- Web authoring: HTML uses paired tags such as
<p>...</p>; hyperlinks usehref; relative paths suit files within the same site. - File management: use meaningful names, correct extensions, folders and backups.
Worked example
A spreadsheet has tax rate 15% in A1 and a price of 200 in B2. The formula =B2*(1+$A$1) returns 230. When copied down to row 3, B2 becomes B3 but $A$1 stays fixed, so the tax rate still applies correctly. By contrast, =B2*(1+A1) copied to row 3 would use A2, likely an empty cell, giving the wrong result. The reasoning is the copy behaviour of relative versus absolute references.
Traps that cost marks
- Omitting the leading
=so the entry is stored as text. - Mixing up relative and absolute references when a formula is copied.
- Using
COUNTwhen the question needsCOUNTAorCOUNTIF. - Choosing a primary key that can repeat or be empty.
- Describing mail merge without naming the data source or merge fields.
- Confusing transitions with animations, or leaving HTML tags unclosed.