Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
19 results for “Structured Logging”
Structured Logging
Emitting log entries as machine-parseable key-value records rather than as formatted prose.
AI Gateway
A shared proxy in front of model providers that centralises routing, keys, quotas, caching, logging and safety policy.
Account Vending
Automated creation of new cloud accounts pre-configured with the organisation's networking, identity, logging, guardrails and cost allocation.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Auditability
The ability to reconstruct who did what, to which resource, when, and from where — reliably enough to be relied upon after the fact.
Capability Map
A structured view of everything a business does, used as the stable frame for mapping applications, investment, ownership and gaps.
Correlation ID
A single identifier attached to one logical operation and included in every log line it produces, anywhere in the system.
Document Store
A store that keeps semi-structured documents — typically JSON — retrievable by key and queryable by their contents.
Landing Zone
A pre-configured, governed cloud environment — accounts, networking, identity, logging, guardrails — into which workloads can be deployed safely.
Quality Attribute Scenario
A structured, testable statement of a non-functional requirement: source, stimulus, environment, artefact, response, response measure.
Technical Proposal
A written argument for a course of action, circulated for review before the work starts, structured so that disagreement surfaces early and cheaply.
Threat Modelling
A structured exercise that identifies what can go wrong with a design, before it is built, by walking the system's trust boundaries.
Well-Architected Review
A structured self-assessment of a workload against defined pillars — operational excellence, security, reliability, performance, cost, and sustainability.
Design the audit logging for a system handling financial transactions. What is logged, where does it go, and what makes it hold up?
What is logged Significant actions only , defined explicitly rather than logging everything — an audit trail nobody can search is not usable evidence: Authentic
You are designing a new service. What must be in place before it goes live so that whoever is paged at 3 AM can diagnose it without you?
What the interviewer is testing Whether observability is designed in or bolted on, and whether you think about the person on call rather than about the tooling.
Structured Logging
Machine-parseable events with stable names and consistent fields.
Logging
What to log, at what level, and what must never appear in a log.
AI Gateways
Centralised routing, keys, quotas, caching, logging and safety policy.
AI Observability
Logging prompts, versions, retrieved context and cost per request.