SAL1 case studies
SAL1 · Put your knowledge to work in context.
SAL1 is an exam code that appears in certification listings, but at the time of writing we could not match it with confidence to a single certifying body or a published content outline. That matters, because it shapes everything below: rather than invent a domain structure, we describe how exams of this type are usually built and how a candidate should approach one whose blueprint is uncertain. The SAL1 case studies are 5 cases and about 3,672 words.
1Backup window overrun versus the dispatch window
Meridian Freight runs a nightly backup from 01:00 to 05:00 across 340 servers. For six weeks the job has finished between 06:40 and 07:20, overlapping the 06:00 dispatch window when the order-routing platform needs full disk I/O.
708 words, about 4 min2Patching a 9.8 vulnerability into a change freeze
Northgate Health's radiology imaging platform runs an end-of-life server OS that cannot be upgraded before the new year. A file-transfer component on the same host has a publicly exploited vulnerability rated 9.8, reachable only from the internal clinical VLAN after authentication.
736 words, about 4 min3Three simultaneous escalations, six analysts
You are duty manager for a 24/7 service desk with six analysts on shift. At 09:12 a P1 is raised: the payment gateway is returning errors on roughly 30% of transactions.
747 words, about 4 min4Memory leak three weeks before peak
Orion Retail's order service runs in 12 containers. Memory grows about 4% per hour and each container is OOM-killed and restarted roughly every 30 hours; each restart produces a 90-second spike in errors.
731 words, about 4 min5Access review findings with a month-end deadline
A quarterly access review at a 900-person insurer found three things. Forty-one accounts on the claims system belong to leavers; twelve of those hold admin rights and show activity in the last 30 days.
750 words, about 4 min