30-day Systems Administrator exam study plan
This plan organises a month of study around what a systems administrator is expected to know, with hardware and operating systems and Linux sharing the most time. Networking, security and support practice follow, with room for cloud and virtualisation. It assumes about an hour of study on most days, and a longer sitting for each timed mock.
How this guide was made
Written for this site with AI assistance, then checked automatically before publishing. The topic table, sample questions, worked examples and study plan are generated from this site’s question bank: each worked example is recalculated by separate code, and each sample answer says where it came from.
The guide deliberately states no salaries, grades, pass marks or exam dates. Those change, and they could not be checked here, so take them from the advert itself.
This site is independent and is not affiliated with MIFOTRA or any employer.
The 30-day plan
| Day | Focus | What to do |
|---|---|---|
| Week 1 | ||
| 1 | Hardware and operating systems | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 2 | Linux command line | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 3 | Networking fundamentals | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 4 | Cybersecurity | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 5 | IT fundamentals and support practice | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 6 | Cloud and emerging technology | Study, then answer 20 questions untimed and read every explanation, including for the ones you got right. |
| 7 | Review the week | Redo every question you got wrong this week, without looking at the explanations first. |
| Week 2 | ||
| 8 | Hardware and operating systems | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 9 | Linux command line | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 10 | Networking fundamentals | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 11 | Cybersecurity | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 12 | IT fundamentals and support practice | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 13 | Hardware and operating systems | Study, then answer 30 questions untimed and read every explanation, including for the ones you got right. |
| 14 | Timed mock 1 | 50 questions in 60 minutes, in one sitting. Mark it, then list the areas you lost marks in. |
| Week 3 | ||
| 15 | Linux command line | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 16 | Networking fundamentals | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 17 | Cybersecurity | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 18 | IT fundamentals and support practice | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 19 | Hardware and operating systems | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 20 | Linux command line | Study, then answer 40 questions untimed and read every explanation, including for the ones you got right. |
| 21 | Review the week | Redo every question you got wrong this week, without looking at the explanations first. |
| Final stretch | ||
| 22 | Revise: Hardware and operating systems | 40 mixed questions on hardware and operating systems, timed at about a minute each. |
| 23 | Revise: Linux command line | 40 mixed questions on linux command line, timed at about a minute each. |
| 24 | Revise: Networking fundamentals | 40 mixed questions on networking fundamentals, timed at about a minute each. |
| 25 | Revise: Cybersecurity | 40 mixed questions on cybersecurity, timed at about a minute each. |
| 26 | Revise: IT fundamentals and support practice | 40 mixed questions on it fundamentals and support practice, timed at about a minute each. |
| 27 | Revise: Cloud and emerging technology | 40 mixed questions on cloud and emerging technology, timed at about a minute each. |
| 28 | Timed mock 2 | 50 questions in 60 minutes, in one sitting. Mark it, then list the areas you lost marks in. |
| 29 | Mock mistakes | Work through every wrong answer from both mocks until you can explain why the right option is right. |
| 30 | Light review | Skim your notes and formulas for an hour, then stop. Sleep matters more than one more set tonight. |
How the days are divided
The table follows the suggested emphasis for this position. Hardware and operating systems and the Linux command line carry the top weight, so they appear most often in the first three weeks. Networking fundamentals, cybersecurity and IT support practice come next, and cloud topics get time of their own. The final stretch revisits the heaviest areas under time pressure.
Where to spend your study time
The suggested emphasis reflects what this position works with day to day. It is a study guide, not a published exam blueprint.
| Area | Suggested emphasis | Questions in the bank | Practise |
|---|---|---|---|
| Hardware and operating systems | 23% | 961 | Hardware & OS |
| Linux command line | 23% | 360 | In the full bank |
| Networking fundamentals | 15% | 2,636 | Networking |
| Cybersecurity | 15% | 541 | Security |
| IT fundamentals and support practice | 15% | 484 | Hardware & OS |
| Cloud and emerging technology | 8% | 188 | In the full bank |
Make every day hands-on
Reading about a command is not the same as using it. For each day, pick one task to perform on a practice machine: create a user and a group, set permissions on a folder, schedule a backup job, or find the cause of a failed service in its logs. Keep a short notes file of the commands you used, because it becomes your revision sheet for the final week.
When one operating system lags behind
If your first mock shows many more wrong answers on Windows than on Linux, or the other way round, adjust the plan straight away. Swap a few of the stronger system's learning days for the weaker one. The mocks are there to steer the plan, not only to measure it.
Common questions
Do I need a powerful computer to practise?
No. A laptop with enough memory to run one or two small virtual machines is enough for most practice, and free cloud trial accounts are another way to learn cloud services.
What if I cannot study every day?
Keep the review days and both mock days, and combine two lighter learning days into one longer session at the weekend.
More Systems Administrator guides
- Systems Administrator exam: what is tested and how to prepare
- Systems Administrator practice questions with answers
- Systems Administrator calculations with worked answers
- Systems Administrator interview questions and answers
- Systems Administrator skills and qualifications
- Systems Administrator job description and duties
- How to become a Systems Administrator in Rwanda
- Systems Administrator exam mistakes to avoid
- Systems Administrator key topics and quick reference
- Systems Administrator CV: what to include
- Certifications worth getting as a Systems Administrator