Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
160 results across 1 active filter
Page 5 of 7
Treats model changes as controlled releases using versioned configuration, fixed evaluations, shadow or canary traffic, monitoring, and rollback.
Uses explicit capability and risk policy to route by task while preserving evaluation, version attribution, budgets, and fallback semantics.
Tracks trust, versions, integrity, provenance, review, and rollback across models, adapters, prompts, datasets, tools, and parsers.
Establishes server trust, audience-bound authorization, least privilege, capability filtering, approval, and safe handling of untrusted results.
Uses workload identity, separate control and data planes, least privilege, scoped model access, and auditable administration.
Protects knowledge ingestion with source trust, provenance, validation, quarantine, review, versioning, and rollback.
Builds a readable request with stable instructions and clearly delimited, provenance-aware untrusted inputs.
Classifies tools by consequence and applies distinct permissions, validation, confirmation, idempotency, and audit controls.
Combines deterministic invariants, severity-aware quality thresholds, slice protection, baseline comparison, and guarded rollout.
Separates user-visible progress from validated completion and prevents partial JSON or tool arguments from triggering side effects.
Maps assets, trust boundaries, untrusted content, model influence, actions, and abuse cases before selecting controls.
Maps risk tiers and policy statements to owned, versioned, testable runtime controls, evidence, exceptions, and review triggers.
Uses inference profiles for capacity while accounting for destination Regions, IAM and SCP policy, residency, quotas, and observable routing.
Selects a production experiment based on user exposure, side effects, measurement needs, cost, and rollback risk.
Checks model, feature, API, region, quota, commercial access, lifecycle, and dependent-service compatibility before rollout.
Builds a resumable tool workflow that validates model proposals, authorizes every action, requires approval for side effects, and remains idempotent under retries.
Builds a provider-neutral model gateway that owns request deadlines, retry classification, budget enforcement, fallback policy, and versioned telemetry.
Instruments an AI workflow with correlated stage spans, low-cardinality versions, usage and outcome signals, and explicit content-capture controls.
Runs containment and recovery for an agent that ingested malicious instructions from retrieved content and attempted an unauthorized outbound tool call.
Reviews a managed AI proposal against data flow, identity, region, retention, quota, observability, portability, and recovery requirements.
Combines quality, reliability, cost, security, privacy, and recovery evidence into a realistic launch and incident game day.
Diagnoses schema-valid quality regressions across inputs, context, prompts, examples, models, schemas, tools, and downstream interpretation.
Separates product policy, orchestration, model access, data and tools, validation, state, and operations into explicit application-owned boundaries.
Explains tokens as model-specific text units and connects tokenization to context limits, output limits, latency, cost, and text behavior.