Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
43 results for “Prompt & Version Management”
Prompt Registry
A versioned store of production prompts with their model bindings, parameters and evaluation results, so a prompt change is a reviewable, traceable, reversible deployment.
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.
Consent Management
Capturing, storing, honouring and evidencing a data subject's permissions for specific processing purposes, including withdrawal.
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.
Prompt Injection
An attack in which text from an untrusted source is interpreted by the model as instructions rather than as data.
Prompt Versioning
Treating prompts as versioned, reviewed, tested artefacts rather than as strings edited in place.
Secrets Management
Storing, distributing, rotating and auditing credentials so that they never live in code, images or configuration files.
Version Vector
A per-replica counter set that lets a system tell whether one version causally descends from another or whether the two are genuinely concurrent.
Backward Compatibility
The property that a new version of a producer continues to work with clients written against the old version.
Blameless Postmortem
An incident review that seeks the systemic conditions that made a failure possible, explicitly excluding individual fault.
Canary Release
Routing a small fraction of traffic to a new version, watching its metrics, and expanding or rolling back based on what they show.
Context Window
The maximum number of tokens a model can attend to in one request, holding the system prompt, history, retrieved context, tools and the answer.
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.
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.
Infrastructure as Code
Defining infrastructure in version-controlled declarative files that a tool reconciles against the real environment.
Key Rotation
Periodically replacing a cryptographic key with a new one while retaining the old for decrypting existing data, so exposure from any single key is bounded.
Managed Service Upgrade Window
The period during which a provider may apply patches or version upgrades to a managed service, usually involving a failover or brief unavailability.
Optimistic Concurrency Control
Allowing concurrent work without locks and detecting conflict at write time by checking that the underlying version has not changed.
Permission Boundary
A policy limiting the maximum permissions an identity can have, used so that the ability to create roles does not become the ability to grant unlimited privilege.
Secret Zero
The credential a workload needs in order to authenticate to the secret manager — the one secret that cannot itself be stored in the secret manager.
Semantic Versioning
A version scheme where the number itself states the compatibility promise — major for breaking, minor for additive, patch for fixes.
Severity Levels
A predefined scale of incident impact that determines who is woken, how fast, and what process applies.
Slowly Changing Dimension
A strategy for handling attributes that change over time, deciding whether history is preserved and how facts attach to the correct version.
Stripe's API Versioning
Stripe pins each account to the API version current when it integrated and transforms requests and responses between versions internally, so integrations never break and the core …
Time Travel
Querying a table as it existed at a previous version or timestamp, made possible by keeping the metadata and files of prior commits.
Workload Identity
Giving a running workload a cryptographically verifiable identity issued by the platform, so it obtains short-lived credentials without a stored secret.
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
You are asked to give an internal AI agent access to the customer database, the ticketing system and outbound email so it can resolve support tickets. What is your response?
What the interviewer is testing Whether you recognise a specific and well documented security pattern, and whether you can propose a workable design instead of
Prompt & Version Management
Prompts as reviewed, versioned, evaluated production configuration.
AI Cost Management
Token accounting, routing, caching and the context-window budget.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
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.
Prompt Injection Defence
Breaking the private-data, untrusted-input, outbound-channel combination.
Secrets Management
Runtime injection, dynamic credentials and rotation applications survive.