Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Artifact Management”
Artifact Promotion
Moving one immutable build between repositories as it earns trust, rather than rebuilding it for each environment.
Model Inventory
A complete register of models in use with their purpose, owner, risk tier and validation status — the artifact everything else in model governance depends on.
Application Portfolio Management
Maintaining an inventory of every application with its owner, cost, business value and technical health, and using it to decide what to invest in, replace or retire.
Artifact Signing
Cryptographically signing build outputs so that deployment can verify what is being run was produced by the expected pipeline from the expected source.
Consent Management
Capturing, storing, honouring and evidencing a data subject's permissions for specific processing purposes, including withdrawal.
Focus Management
Deliberately controlling where keyboard focus sits after an interface change, which is what makes a dynamic application usable without a mouse.
Global Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
Identity and Access Management
The system of record for principals, credentials and permissions, and the policy engine that decides what each principal may do.
Offset Management
How a consumer records its position in a stream, and the decision that determines whether processing is at-least-once or at-most-once.
Secrets Management
Storing, distributing, rotating and auditing credentials so that they never live in code, images or configuration files.
Telemetry Cost Management
Controlling observability spend through sampling, retention tiering and cardinality limits without losing diagnostic capability.
Blameless Postmortem
An incident review that seeks the systemic conditions that made a failure possible, explicitly excluding individual fault.
Build Attestation
A signed statement about how an artifact was produced — by which builder from which source — that a deployment gate can verify rather than trust.
Cross-Cutting Concern
A responsibility that legitimately appears throughout a system rather than in one module, such as logging, authorisation, tracing or transaction management.
Device Group Rollout
Applying configuration or firmware to a fleet in ordered cohorts with health checks between them, because a bad change applied to everything at once has no remedy.
Dynamic Secrets
Credentials generated on demand for a specific consumer with a short lease, rather than stored, shared and rotated periodically.
Envelope Encryption
Encrypting data with a locally-generated data key, then encrypting that key with a master key held in a key management service, and storing the wrapped key alongside the ciphertext.
FinOps Operating Phases
The inform, optimise and operate cycle through which an organisation builds cost management into normal engineering practice.
Golden Record
The single authoritative version of an entity assembled from conflicting sources, and the survivorship rules that decide which value wins.
Hardware Security Module
A tamper-resistant device that generates and stores keys and performs cryptographic operations without the key material ever being extractable.
Incident Command
Assigning explicit roles during an incident — commander, operations lead, communications lead, scribe — so coordination does not compete with diagnosis.
Incident Severity Levels
A small, agreed scale of incident severity that determines response, escalation and communication without requiring debate during the event.
A front-end team wants to replace their global state library because "state management is unmanageable". How do you evaluate the request?
Ask what is actually in the store The complaint almost always resolves to one distinction not having been made: server state versus UI state . Server state is d
A team's pipeline takes 80 minutes from commit to a deployable artifact and engineers have stopped watching it. How do you approach fixing it?
Measure per stage before changing anything Get the duration of every stage over the last few hundred runs, with the distribution rather than the mean. The shape
A deployed model performed well in validation and its business metric has declined over four months. Nothing has been deployed. What do you investigate?
The model did not change; its world did Three distinct causes, and they need different responses: Data drift. The input distribution has moved — a new customer
A team's CI suite fails roughly one run in three for reasons unrelated to the change. Everyone reruns until green. How do you recover the situation?
Recognise what has actually been lost The suite is no longer a gate. Once the team's reflex on red is "rerun", that reflex is applied to genuine failures too, a
A vendor SaaS product embeds a model that scores customers, and its output drives an automated decision in your process. Your model governance framework covers models you build. What do you do?
The obligation does not transfer with the outsourcing You are accountable for the decision. That the scoring is performed by a vendor changes who operates the m
An AI feature launched two months ago now costs more per month than the rest of the platform. What do you investigate?
Get cost per request, decomposed Token cost splits into input and output, and they price differently. Break the bill down by feature, by user, and by input vers
An LLM feature that worked last week now gives worse answers. Nothing was deployed. How do you find out what changed, and what should have been in place?
What the interviewer is testing Whether you treat an AI feature as a system with configuration and dependencies, or as a black box that mysteriously drifts. Wha
An estate has database passwords in environment variables across 200 services. Design the migration to a secrets manager.
Sequence it by risk, not by convenience Phase 0 — stop the bleeding. Secret scanning in CI and on the existing repositories, blocking new commits containing cre
Equifax was breached in 2017 through a vulnerability with a patch available two months earlier. Beyond "patch faster", what architectural and governance failures does that imply?
The case, as publicly reported Apache Struts vulnerability CVE 2017 5638 was disclosed in March 2017 with a patch available. An internet facing dispute portal a
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
AI Cost Management
Token accounting, routing, caching and the context-window budget.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Exception & Waiver Management
Time-boxed, owned deviations with a remediation date, rather than permanent silence.
Flaky Test Management
Quarantine, detection, and the trust a suite loses once red stops meaning broken.
Fleet Management
Inventory, health, configuration and grouping across devices you will never see.
Identity & Access Management
Workload identity, roles, permission boundaries and usage-based review.
Incident Management
Command roles, severity levels and mitigation before diagnosis.
Key Management
Rotation, separation of duty, envelope encryption and crypto-shredding.
Log Management
Aggregation, retention tiering, search and the cost of keeping everything.
Master Data Management
One authoritative record for a customer or product across systems that each have their own.
Model Risk Management
Inventory, validation, monitoring and challenge for models that make consequential decisions.
Prompt & Version Management
Prompts as reviewed, versioned, evaluated production configuration.
Secrets Management
Runtime injection, dynamic credentials and rotation applications survive.
Test Data Management
Realistic data without copying production personal data into a weaker environment.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.