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.
77 results across 1 active filter
Page 3 of 4
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.
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.
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.
Explains the operating, security, governance, and integration capabilities that surround managed model inference without treating a platform as the application.
Distinguishes model-directed execution from explicit application control and explains when each is appropriate.
Designs index records that support filtering, authorization, freshness, citations, diagnosis, and safe reprocessing.
Applies parsing, schema and domain validation, authorization, confirmation, idempotency, limits, and audit before execution.
Defines MCP as a client-host-server protocol for discovering and using tools, resources, and prompts without confusing interoperability with safety.
Places provider guardrails as one configurable defense while preserving application authorization, validation, testing, and incident evidence.
Prefers typed APIs for reliable actions and reserves UI automation for constrained cases with stronger observation, approval, and recovery.
Uses pre-filtering for authorization and hard constraints while recognizing engine-specific recall and performance behavior.