Punjab PSEB Senior Secondary NSQF IT/ITeS common mistakes
Punjab PSEB Senior Secondary NSQF IT/ITeS · Understand the traps and how to avoid them.
Writing the full form of abbreviations such as OSS, BOSS, DTP, DBM, CBT, and WBT with a wrong expansion or swapping two of them, for example calling OSS 'Open System Software' or BOSS 'Basic Operating System Software'.
NSQF IT/ITeS theory papers test trade terminology directly, and the abbreviations sound alike and are often memorised as a list without meaning; candidates who never link each term to its function confuse the open-source and proprietary office suites.
What to do instead
Build a two-column table of every abbreviation in the syllabus with the exact expansion and one concrete example beside it (OSS = Open Source Software, e.g. LibreOffice; BOSS = Bharat Operating System Solutions, a Linux distribution). Write the expansion five times from memory and self-test weekly by covering the right column.
Confusing a word processor, spreadsheet, and presentation package when asked which application is used for a given task, or naming the wrong default file extension (for example .xlsx for a Writer document or .odt for a Calc sheet).
Candidates practise only one package, usually Writer, and treat the others as reading material; extension questions look trivial so they are skipped during revision, yet they appear every year in objective sections.
What to do instead
Prepare a one-page comparison chart with columns for purpose, key toolbar, and native plus open formats for each package. Then perform each listed task once in LibreOffice and MS Office and note the extension the Save As dialog shows; hands-on memory survives exam pressure better than rote lists.
Answering networking questions with the wrong device or layer, for example saying a switch routes packets between networks, a hub filters by MAC address, or that IP addresses are resolved to names by DNS instead of the reverse.
Hub, switch, router, and gateway are taught together in a single chapter, and candidates memorise names without the function; the OSI and TCP/IP layer mapping is often learned as a diagram rather than as behaviour.
What to do instead
Learn each device by the question 'what does it do with an incoming frame or packet?' Hub broadcasts to all ports, switch forwards by MAC address within a LAN, router forwards by IP address between networks. Draw the four-layer TCP/IP model once from memory and place each device and protocol on it, then redo the placement after a week.
Mixing up the ITeS and BPO service categories, for example labelling payroll processing or medical transcription as a 'domestic voice process' or describing KPO as low-end data entry work.
The ITeS unit lists many service types (BPO, KPO, LPO, transcription, data entry, call centre) that overlap in daily work, and candidates revise from short notes that give definitions without examples, so they classify by the word rather than by the nature of the task.
What to do instead
Make a classification table with the axis 'voice vs non-voice' and 'routine vs knowledge-intensive', then place each service with one real example. KPO and LPO sit on the knowledge-intensive side; data entry and inbound voice support sit on the routine side. Practise with ten new examples and justify each placement in one line.
Describing communication skills in the abstract ('be polite', 'listen well') instead of answering scenario questions about a customer call with the specific step, such as greeting, identifying the customer, active listening, paraphrasing, and confirming resolution.
Candidates treat the soft-skills unit as easy marks and never structure an answer; the paper asks for ordered steps or the correct response to an angry caller, so vague advice earns little credit.
What to do instead
Memorise a call-handling sequence as numbered steps and rehearse it aloud in English and Punjabi. For each practice scenario, write the exact opening sentence, the empathy statement, and the closing confirmation. Also learn the difference between passive, aggressive, and assertive responses with one sample line each.
Confusing the data-processing cycle stages, for example calling validation a stage of processing output, or saying that data and information are the same thing, or placing 'collection' after 'storage'.
The cycle is drawn as a loop in most textbooks, so the linear order is lost; candidates also skip the distinction between data and information because it seems too basic to be examined.
What to do instead
Write the cycle as a numbered list: collection, validation, sorting, processing, storage, output, and feedback. Attach one example from a school office (admission forms collected, checked, sorted by class, entered, stored, marksheets printed). Learn the data-versus-information distinction with a single pair of sentences and reuse it in every definition answer.
Giving a wrong or incomplete keyboard shortcut or menu path for a routine operation, such as using Ctrl+P for paste, Ctrl+X for undo, or stating that page margins are set from the Insert menu.
Shortcuts are learned by watching others rather than by practice, and similar keys (Ctrl+C, Ctrl+X, Ctrl+V) blur together; menu-path questions are answered from memory of an older software version.
What to do instead
Keep a personal shortcut sheet limited to the twenty shortcuts in the syllabus and test yourself by performing each action in the lab without touching the mouse. For menu paths, open the application and physically click Format, then Page Style, and note the exact wording your installed version shows.
Explaining internet and email concepts with outdated or swapped terms, for example saying email is stored on the sender's computer, confusing CC with BCC, or stating that a browser and a search engine are the same.
The internet unit is often studied from old notes, and CC/BCC is a single line in the book that candidates read once; the browser-versus-search-engine distinction is rarely stated explicitly in class.
What to do instead
Learn email by tracing one message: composed in the client, sent via SMTP to the server, stored in the recipient's mailbox, retrieved via POP3 or IMAP. Then write the purpose of To, CC, and BCC in one line each with a privacy example. Define browser (software that displays web pages) and search engine (a website that indexes pages) separately and give two examples of each.
Answering occupational safety and health questions by listing hazards without the control measure, or reversing first-aid and ergonomic advice, for example saying a fire from electrical equipment should be doused with water or that the monitor should be at eye level while the chair is set low.
The safety unit is treated as filler and skimmed the night before; candidates recall the hazard names but not the paired preventive action, and the exam asks for both.
What to do instead
Build hazard-and-control pairs: electrical fire with CO2 extinguisher, never water; eye strain with the 20-20-20 rule; posture with feet flat, screen top at or just below eye level, elbows at about ninety degrees. Add the correct emergency numbers and the reporting step for a workplace injury, then recite the pairs aloud.
In practical or viva sections, producing a document or spreadsheet that is functionally correct but fails the marking checklist, for example leaving the default file name, not saving in the format asked for, omitting a header or footer, or not printing a preview before submission.
Candidates focus on content and forget that practical marking is itemised; the checklist items (file name, format, formatting marks, print preview) are demonstrated once in class and never written down.
What to do instead
Before any practical, write your own submission checklist from the syllabus and paste it on the lab desk: correct file name and folder, required format, header and footer, page setup, print preview, and saved copy. Run through it every practice session so the sequence becomes automatic before the exam day.