Linux Administrator · 10+ Years
Platform standards, governance, operating model, metrics, mentoring, and decision frameworks.
Try each answer before revealing the suggested coaching answer.
25 questions
01How would you standardize Linux filesystem hierarchy across multiple teams as a technical lead or architect?
A technical-leadership answer
Say this first: Linux filesystem hierarchy should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply Linux filesystem hierarchy, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → Linux filesystem hierarchy → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
02How would you define governance, ownership, and success metrics for file permissions?
A technical-leadership answer
Say this first: file permissions should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply file permissions, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → file permissions → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
03A leadership team asks you to improve maturity around users and groups. What roadmap would you propose?
A technical-leadership answer
Say this first: users and groups should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply users and groups, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → users and groups → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
04How would you balance delivery speed, risk, cost, and maintainability for process management?
A technical-leadership answer
Say this first: process management should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply process management, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → process management → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
05How would you mentor teams that use systemd services inconsistently across projects?
A technical-leadership answer
Say this first: systemd services should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply systemd services, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → systemd services → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
06How would you standardize journalctl and logs across multiple teams as a technical lead or architect?
A technical-leadership answer
Say this first: journalctl and logs should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply journalctl and logs, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → journalctl and logs → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
07How would you define governance, ownership, and success metrics for package management?
A technical-leadership answer
Say this first: package management should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply package management, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → package management → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
08A leadership team asks you to improve maturity around shell scripting basics. What roadmap would you propose?
A technical-leadership answer
Say this first: shell scripting basics should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply shell scripting basics, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → shell scripting basics → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
09How would you balance delivery speed, risk, cost, and maintainability for cron jobs?
A technical-leadership answer
Say this first: cron jobs should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply cron jobs, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → cron jobs → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
10How would you mentor teams that use network troubleshooting inconsistently across projects?
A technical-leadership answer
Say this first: The important point about network troubleshooting is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply network troubleshooting, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → network troubleshooting → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
11How would you standardize DNS troubleshooting across multiple teams as a technical lead or architect?
A technical-leadership answer
Say this first: The important point about DNS troubleshooting is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply DNS troubleshooting, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → DNS troubleshooting → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
12How would you define governance, ownership, and success metrics for SSH hardening?
A technical-leadership answer
Say this first: SSH hardening should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply SSH hardening, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → SSH hardening → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
13A leadership team asks you to improve maturity around firewalld/iptables. What roadmap would you propose?
A technical-leadership answer
Say this first: firewalld/iptables should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply firewalld/iptables, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → firewalld/iptables → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
14How would you balance delivery speed, risk, cost, and maintainability for disk partitioning?
A technical-leadership answer
Say this first: disk partitioning should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply disk partitioning, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → disk partitioning → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
15How would you mentor teams that use LVM inconsistently across projects?
A technical-leadership answer
Say this first: LVM should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply LVM, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → LVM → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
16How would you standardize mounts and fstab across multiple teams as a technical lead or architect?
A technical-leadership answer
Say this first: mounts and fstab should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply mounts and fstab, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → mounts and fstab → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
17How would you define governance, ownership, and success metrics for CPU and memory troubleshooting?
A technical-leadership answer
Say this first: The important point about CPU and memory troubleshooting is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply CPU and memory troubleshooting, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → CPU and memory troubleshooting → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
18A leadership team asks you to improve maturity around disk full troubleshooting. What roadmap would you propose?
A technical-leadership answer
Say this first: The important point about disk full troubleshooting is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply disk full troubleshooting, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → disk full troubleshooting → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
19How would you balance delivery speed, risk, cost, and maintainability for log rotation?
A technical-leadership answer
Say this first: log rotation should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply log rotation, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → log rotation → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
20How would you mentor teams that use backup and restore inconsistently across projects?
A technical-leadership answer
Say this first: backup and restore should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply backup and restore, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → backup and restore → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
21How would you standardize patch management across multiple teams as a technical lead or architect?
A technical-leadership answer
Say this first: patch management should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply patch management, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → patch management → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
22How would you define governance, ownership, and success metrics for SELinux/AppArmor basics?
A technical-leadership answer
Say this first: SELinux/AppArmor basics should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply SELinux/AppArmor basics, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → SELinux/AppArmor basics → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
23A leadership team asks you to improve maturity around sudoers configuration. What roadmap would you propose?
A technical-leadership answer
Say this first: sudoers configuration should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply sudoers configuration, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → sudoers configuration → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
24How would you balance delivery speed, risk, cost, and maintainability for performance tuning?
A technical-leadership answer
Say this first: performance tuning should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply performance tuning, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → performance tuning → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
25How would you mentor teams that use incident runbook creation inconsistently across projects?
A technical-leadership answer
Say this first: incident runbook creation should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.
Use a real scenario
Imagine an internal support assistant that answers from approved policy documents. The team must decide how to apply incident runbook creation, verify the result, and explain the user impact. For a Linux Administrator, attach the explanation to an evaluation set and retrieval trace.
Show judgment
- make the decision criteria visible across teams and create a safe default path.
- State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
- Call out prompt injection and unsupported answers and the control that reduces it.
Concrete check
journalctl -u <service> --since "15 min ago"Evidence to mention
Track grounded-answer rate and p95 response time. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.
request or change → guardrail / validation → incident runbook creation → observable result → owner reviewPractice prompt: Explain the escalation route when prompt injection and unsupported answers conflicts with delivery pressure.
No questions match. Try another term.
Further reading
These are original practice questions and suggested answers. Adapt them to your own work and explain evidence, trade-offs, and limitations.