6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.2 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/e5b5053e-0ef6-4c4e-a3f2-42f955f4322c | implement a firewall | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
implement a firewall — Database Administrator
For a Database Administrator, 'implementing a firewall' isn’t about being a network security specialist, but understanding how firewalls protect the database server itself. Daily tasks revolve around configuring firewall rules to allow legitimate database traffic (client connections, replication, backup processes) while blocking everything else – think specific ports for SQL Server, PostgreSQL, Oracle, etc., and limiting access by source IP address. It's about defense in depth; you’re not replacing network firewalls, but adding a layer directly protecting the data. Tools used are often OS-level firewalls (iptables/firewalld on Linux, Windows Firewall) or database-specific firewall features built into some DBMS platforms.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).