UPMSP Vocational IT/ITeS common mistakes
UPMSP Vocational IT/ITeS · Understand the traps and how to avoid them.
Describing ITeS as only software development or hardware repair, or saying a BPO is not part of the IT-ITeS industry. For example, listing 'making apps' and 'fixing computers' as the only ITeS activities and leaving out transcription, medical coding, or KPO work.
The syllabus title joins 'IT' and 'ITeS', so candidates memorise the phrase as one word and revise only the software half. BPO examples appear in the textbook but are not linked back to the definition of IT-enabled services.
What to do instead
Make a two-column table: IT (hardware, software, networking, development) versus ITeS (BPO, KPO, LPO, transcription, medical coding, payroll processing). Then classify ten local jobs into the correct column and state the test that decides it: is the service delivered mainly through IT and communication rather than by manufacturing a product?
Writing a workplace email as one long line with no subject, no salutation, and chat abbreviations such as 'plz' and 'u'. In a role-play answer, the candidate writes 'sir plz send report fast' and considers it complete.
Everyday messaging habits carry over. Candidates have seen far more WhatsApp messages than formal emails and have never been shown that an email is judged on structure as well as content.
What to do instead
Use a fixed five-line template: subject line with purpose and deadline, salutation, one short paragraph with the request and date, closing, and name with designation. Practise converting three chat messages into that template and check that the subject alone tells the reader what action is needed.
Entering a phone number or PIN that begins with zero into a spreadsheet cell and accepting the result after the leading zero disappears. A ten-digit mobile number becomes nine digits, and the candidate submits the sheet without noticing.
Spreadsheet software treats the entry as a number, and numbers do not keep leading zeros. Candidates assume the screen shows exactly what was typed, so they do not check the entry after pressing Enter.
What to do instead
Before typing identifiers, format the column as Text, or type an apostrophe before the first digit. After data entry, verify the first and last record and use a count of characters or a simple LEN formula to confirm that each number still has the expected length.
Building a document by pressing Enter at the end of every line and using repeated spaces to indent the first line. As soon as one word is added, the paragraph breaks in the middle and the indent collapses.
This is a typewriter habit. The candidate sees the correct shape on screen and does not realise that the layout is created by manual line breaks rather than by paragraph formatting.
What to do instead
Press Enter once per paragraph only and let text wrap. Set first-line indent and spacing through the Paragraph dialog, then switch on formatting marks to see where paragraph marks and spaces actually are. Reformat one already-broken paragraph to prove the difference.
Sorting a marks table by selecting only the marks column, so the names and roll numbers stay in their original rows and no longer match the marks. The candidate then reports the highest scorer from the wrong row.
Sorting looks like a single-column operation, and the warning dialog is dismissed without reading it. Candidates also confuse relative and absolute references, so a fixed rate such as a tax percentage is copied down and shifts away from its cell.
What to do instead
Always select the whole table, including headings, before sorting, and confirm that 'my data has headers' is set. For any fixed value, lock the cell with dollar signs, for example =B2*$F$1, and copy the formula down while checking the formula bar for two or three rows.
Calling the effect between one slide and the next an 'animation', and calling the movement of a bullet point on a single slide a 'transition'. In a practical task, the candidate applies animation to the whole slide and then cannot explain why every object moves together.
Both features sit next to each other on the ribbon and both mean 'movement' in ordinary language. The distinction is rarely tested aloud, so the two labels get swapped without correction.
What to do instead
Use a memory pair: transition = whole slide to whole slide; animation = one object inside one slide. Build a three-slide file, apply one transition to each slide and one entrance animation to a single bullet, then label each effect in writing.
Saying that Google Chrome is a search engine, or that a URL and a domain name are the same thing. In an HTML question, the candidate writes an opening tag without its closing tag and uses <br> in place of a paragraph.
The browser is the first screen seen, so it is assumed to be the search tool. HTML is learned by copying code rather than by understanding the page skeleton, so tag pairing and nesting are not checked.
What to do instead
Draw the chain: browser (Chrome) opens a page; search engine (Google) is a website used inside the browser; URL is the full address, and the domain is its main part. Write the skeleton from memory (html, head, title, body, h1, p) and close every tag, checking nesting with a simple indentation.
Choosing a column such as 'Name' as the primary key because it appears first in the table, or treating NULL as the same as zero or an empty string. In a query, the candidate writes GROUP BY before WHERE or leaves out the FROM clause.
The primary key is remembered as 'the important column' rather than as a uniqueness rule. NULL is read as 'nothing', which in everyday language means zero or blank. SQL is memorised as a word list rather than as a clause order.
What to do instead
Test any proposed key against two rules: it must be unique and never empty. Use a roll number or ID. Write NULL as 'unknown', not zero. Memorise the clause order SELECT - FROM - WHERE - GROUP BY - HAVING - ORDER BY and run five small queries against a three-column table to fix it.
Answering a security scenario by choosing an easy password such as '1234' or 'password', and clicking a link in an unexpected email asking for login details. In a green IT question, the candidate throws an old monitor or battery into the ordinary dustbin.
Convenience is prioritised over risk because the candidate has not connected a stolen password to a real consequence. E-waste is not visible in daily life, so it is treated like household rubbish.
What to do instead
Use a four-point security checklist for every scenario: strong unique password, second factor where available, verify the sender before clicking, lock the screen when leaving. For green IT, learn three routes only: donate or resell working equipment, send e-waste to an authorised recycler, and switch off or use power-saving settings when idle.
In a customer-service scenario, responding to a complaint with 'that is not our problem' or arguing about who is right. In an entrepreneurship answer, defining an entrepreneur only as 'a person who starts a business to earn money', with no mention of risk, planning, or organising resources.
Complaint handling is answered as an ordinary conversation rather than as a process. Entrepreneurship is summarised from a one-line definition, and the functions such as risk-bearing and resource organisation are not revised.
What to do instead
Use a three-step service reply: acknowledge the customer's problem, state what you will do and by when, then confirm the outcome. For entrepreneurship, memorise four functions (planning, organising resources, risk-bearing, innovation) and attach one concrete example to each before writing the definition.