CSET Industrial and Technology Education - independent subject practice common mistakes
CSET Industrial and Technology Education - independent subject practice · Understand the traps and how to avoid them.
Treating a model calculation as physical operating authorization.
The model omits equipment, legal and practical conditions.
What to do instead
State its classroom scope and obtain actual approved procedures before implementation.
Mixing energy with power.
Rates and totals have different dimensions.
What to do instead
Write units and multiply power by time only under a stated time model.
Using a display’s smallest increment as its accuracy.
Resolution does not measure bias, calibration or total uncertainty.
What to do instead
Read the instrument specification and include relevant uncertainty sources.
Applying a formula outside its stated assumptions.
Memorized expressions can hide geometry, waveform or operating restrictions.
What to do instead
State assumptions and test whether the supplied scenario satisfies them.
Confusing a supplied allowable stress with yield strength.
An allowable limit can incorporate other criteria and margins.
What to do instead
Identify the definition of each stated limit before calculating a ratio.
Ignoring losses in an output calculation.
Ideal input-output relations do not automatically apply to real devices.
What to do instead
Apply the specified efficiency once in the correct direction and check the energy balance.
Comparing lifecycle totals for different services.
Different functional units can make the ranking meaningless.
What to do instead
Normalize the service, boundary and time horizon before comparing impacts.
Reading an obsolete drawing as the current design.
A technically plausible dimension can belong to the wrong revision.
What to do instead
Check drawing identifiers, revision status and linked parts before calculating.
Treating a single good test result as complete approval.
A test samples particular properties under particular conditions.
What to do instead
Match each requirement to the evidence it needs and identify untested conditions.
Rounding intermediate values too early.
Accumulated rounding can change the final comparison.
What to do instead
Retain appropriate guard digits and round at the final reporting precision.
Converting between binary, decimal, and hexadecimal by treating the digits as ordinary base-10 place values, for example writing 0.1 decimal as 0.0001 binary or translating 2 KB as 2000 bytes without noticing the prefix convention the question uses.
Candidates memorize '1 KB = 1024 bytes' from consumer packaging and never build a positional-value model, so digit-by-digit conversion feels like a copying exercise rather than a weighted sum.
What to do instead
Convert by explicit place-value expansion: write each bit's weight (128, 64, 32, 16, 8, 4, 2, 1) above the digit, circle the powers that sum to the target, and group bits in fours for hex. State whether the stem uses SI or binary prefixes before computing.
Ordering the memory hierarchy by capacity instead of by proximity to the CPU, or explaining cache as 'extra RAM' that stores whole programs, so questions about locality, hit rate, or why a loop over a large array runs slowly get answered with speed-of-RAM claims.
The slogan 'cache is fast memory' is recalled in isolation, without a mental picture linking registers, L1, L2, L3, RAM, and disk along shared axes of latency, size, cost, and volatility.
What to do instead
Draw the hierarchy once as a ladder from registers to disk and label each rung with typical latency and typical size. Then rehearse locality: explain why the same loop is faster after a warm-up pass and why row-major traversal of a 2-D array beats column-major.