BTS SIO common mistakes
BTS SIO · Understand the traps and how to avoid them.
In the support scenario (incident ticket, deployment of a service), the candidate describes tools and steps in general terms ("j'installe le serveur, je configure le réseau") without stating a verifiable procedure: no prerequisite checks, no test/validation step, no rollback plan, no traceability (ticket update, documentation).
Candidates memorize the shape of a 'mise en situation' and assume the examiner rewards mentioning the right tool. The BTS SIO grid rewards the demonstrated method: analyse du besoin, choix justifié, mise en œuvre, tests, documentation, and the candidate has often never written a procedure down end to end during the two years.
What to do instead
Before the exam, build a reusable written template for any support scenario: contexte et besoin, contraintes (droits, budget, sécurité), solution retenue et pourquoi, étapes numérotées avec commandes/écrans clés, tests de recette (au moins deux cas dont un cas d'erreur), procédure de retour arrière, mise à jour du ticket et du dossier d'exploitation. Apply it to three past scenarios and have it corrected against the grid.
For the 'Conception et développement' part, the candidate jumps straight to code or to a partial MCD and never produces the intermediate deliverables: no dictionnaire des données, no cardinalities justified, no passage MCD→MLD, no jeu d'essai written before coding, and a personalization of the code that breaks the imposed framework or naming conventions.
Time pressure and the habit of coding first in projects. Candidates also underestimate how much of the mark sits on the design artefacts and on respecting the given cahier des charges rather than on a working program.
What to do instead
Train on a fixed sequence: extraire les entités et associations du texte, écrire le dictionnaire des données (nom, type, taille, contrainte), justifier chaque cardinalité en une phrase, dériver le MLD, puis seulement coder. Prepare a standard jeu d'essai table (cas nominal, cas limite, cas d'erreur) and fill it before writing the code. Re-read the consignes to check imposed names, framework and constraints.
On cybersecurity questions, the candidate answers with a list of tools (pare-feu, antivirus, VPN, chiffrement) without linking each measure to an identified risk, a threat model or a security objective (disponibilité, intégrité, confidentialité, traçabilité), and without considering the human and organisational dimension (procédure, sensibilisation, gestion des habilitations).
Tool names are easy to memorize and feel like a complete answer. Candidates rarely practise writing a short analyse de risques, so they never learn to justify a measure by the risk it reduces.
What to do instead
Use a fixed reasoning chain in every answer: actif concerné → menace → vulnérabilité → impact → mesure technique → mesure organisationnelle → indicateur de vérification. Practise on the EBIOS RM logic (or the simplified grille used in class) with three scenarios: poste de travail compromis par phishing, accès distant, fuite de données personnelles. Always add the RGPD angle when personal data is involved.
In Culture générale et expression, the candidate writes a personal opinion essay or a summary of the documents instead of a structured synthèse: no confrontation of the documents, no explicit problématique, paragraphs organised by idea rather than by document, and paraphrases that stay too close to the source wording.
The exercise is often taught late and practised little; candidates fall back on the dissertation habits from lycée. They also confuse 'synthèse' with 'résumé' and do not know that the marking grid rewards the confrontation of documents and reformulation.
What to do instead
Practise the three-step method on a corpus of three or four documents: tableau de confrontation (idée / doc 1 / doc 2 / doc 3), formulation of a problématique that the corpus can actually answer, then a plan in two or three parts where each paragraph cites at least two documents. Rewrite each paraphrase into your own words and check the word count. Do one timed exercise per week in the last two months.
In Expression et communication en langue anglaise, the candidate translates word for word from French, produces long unstructured sentences, and in the oral part reads a prepared text instead of interacting; professional vocabulary (IT support, project, security) is missing or misused.
Written English is often trained through grammar drills, not through professional writing tasks; the oral is rarely rehearsed under exam conditions, so candidates script it and lose marks on interaction and pronunciation.
What to do instead
Build a personal lexicon of about 150 IT/professional terms (ticket, troubleshooting, backup, rollout, phishing, compliance) and reuse them in short written productions (email de relance, compte rendu de réunion, description d'incident). For the oral, rehearse a two-minute presentation of your projet with a mind map, not a script, and practise answering unprepared follow-up questions with a partner or recorded on your phone.
In Mathématiques pour l'informatique, the candidate gives a numerical result without stating the hypothesis, the formula, the unit or the interpretation; on probability and statistics questions they confuse P(A|B) with P(A∩B), and on base conversions or Boolean algebra they skip the intermediate steps so a single error is invisible and uncorrectable.
Candidates reproduce memorized results from corrections rather than reasoning; the maths in the BTS is applied, so the expected answer is a justified calculation linked to an IT situation (débit, capacité, fiabilité, tests), not a bare number.
What to do instead
Adopt a written protocol for every exercise: données et hypothèses, formule littérale, substitution, résultat avec unité, interprétation en une phrase. Drill conditional probability with contingency tables before formulas. For bases and Boolean algebra, always show the conversion columns or the truth table. Re-do the exercises of the two previous sessions without looking at the correction.
In Algorithmique appliquée, the candidate writes code that works on the example given but does not handle edge cases (empty list, single element, duplicates, out-of-range input), does not state the complexity, and uses poorly named variables; the algorithm is not tested with a trace table.
Candidates test with the single example from the statement and stop as soon as it prints the expected output. Complexity and edge cases are often seen as optional theory rather than as part of the expected answer.
What to do instead
For every algorithm, write the specification first (entrées, sorties, préconditions, postconditions), then a trace table on at least three inputs including an empty or degenerate case, then the code with explicit names. State the complexity in a sentence and justify it. Keep a personal list of the classic patterns (recherche, tri, parcours de tableau, accumulation) with their complexity.
In Économie, management et droit de l'informatique, the candidate answers with general knowledge or opinion and does not mobilize the legal or managerial notions precisely: no distinction between contrat de prestation and contrat de travail, confused notions of responsabilité, propriété intellectuelle, données personnelles, or management reasoning without any reference to a model (parties prenantes, organisation, décision).
This domain feels like 'culture' to candidates, so they write essays. The vocabulary is close to everyday language, which hides the fact that the examiner expects precise legal qualifications and a structured management analysis.
What to do instead
Build a one-page fiche per notion with: définition exacte, texte ou principe de référence, exemple concret en SSII, conséquence pratique. Cover at minimum: contrat, responsabilité contractuelle et délictuelle, propriété intellectuelle et licences, RGPD et CNIL, obligations de l'employeur, parties prenantes et structures organisationnelles. In each answer, name the notion, define it, apply it to the case, conclude.
During the oral defense of the projet (support and development), the candidate narrates the project chronologically ("d'abord j'ai fait ci, ensuite j'ai fait ça") instead of presenting need, choices, difficulties and results, cannot justify a technical choice against an alternative, and does not know the figures of their own project (nombre d'utilisateurs, volumes, délais, coûts).
The project was lived as a task list, not as a reasoned approach. Candidates prepare slides but not answers to 'pourquoi ce choix?' and 'qu'auriez-vous fait autrement?', which are exactly the questions the jury asks.
What to do instead
Restructure the presentation around four blocks: contexte et besoin, solution et alternatives écartées avec justification, mise en œuvre et difficultés rencontrées avec la manière dont elles ont été résolues, bilan et pistes d'amélioration. Learn by heart ten key figures of your project and prepare written answers to the ten most likely jury questions, including the technical and security ones.
Across all domains, the candidate manages time badly: spends too long on a question they cannot solve, leaves whole exercises blank rather than writing a partial reasoned answer, and does not re-read the consignes (nombre de lignes, format attendu, documents autorisés) before starting.
Exam stress combined with a habit of perfectionism on the first exercise. Candidates also underestimate how much credit partial reasoning earns on a grid, and they discover the format requirements only at the end.
What to do instead
In the last month, do at least three full timed mock exams per written discipline. Apply a rule: five minutes maximum on a blocked question, write what you know, flag it, move on. Spend the first three minutes reading all the consignes and allocating time per exercise. Keep the last ten minutes for checking format requirements (length, units, naming, documents to hand in).