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 2 of 4
Builds a small, task-relevant, typed toolset with clear semantics rather than exposing an entire internal API surface.
Chooses Vertex AI shared or reserved capacity using traffic shape, reliability, geography, cost, and workload prioritization.
Bounds expensive inputs, outputs, retrieval, tools, retries, concurrency, and fan-out while preserving fair service.
Uses provenance, content isolation, constrained authority, behavioral checks, and deterministic enforcement to contain hostile external instructions.
Combines bounded instructions, source context, a narrow schema, abstention, semantic validation, review, observability, and rollout.
Designs a bounded and reversible first AI feature with measurable value, controlled data, validation, evaluation, observability, fallback, and human oversight.
Combines product policy, input and output controls, context-aware handling, human escalation, appeals, and measurable safety quality.
Pauses durable execution with a clear action preview, verifies approver authority, handles expiry and changed state, and resumes idempotently.
Stores only useful, scoped, attributable memories with extraction, verification, retrieval, expiry, correction, and deletion.
Coordinates private endpoints, DNS, egress policy, dependent services, observability, and recovery without confusing network isolation with authorization.
Coordinates lifecycle rules across application state, provider storage, files, embeddings, caches, traces, evaluations, and backups.
Makes AI involvement, limitations, evidence, consequential decisions, correction, escalation, and accountability visible to users.
Carries source permissions into ingestion and query-time filtering while failing closed across retrieval, caching, and citations.
Evaluates verified outcomes, trajectory quality, safety, efficiency, recovery, and important slices in realistic environments.
Separates storage from processing location, verifies provider and feature-specific retention, and minimizes sensitive inputs.
Combines application authorization, scoped platform resources, tenant budgets, admission control, usage attribution, and noisy-neighbor protection.
Keeps credentials in trusted executors and replaces broad reusable secrets with scoped references and short-lived authority.
Applies purpose limitation, selective retrieval, redaction, pseudonymization, and field-level policy before model calls.
Constrains source-to-sink combinations with least privilege, egress policy, argument checks, approval, and information-flow awareness.
Carries trusted tenant scope through retrieval, caches, memory, tools, traces, evaluations, and asynchronous execution.
Uses infrastructure and configuration as code, immutable behavior versions, environment-specific resources, evaluation gates, and drift detection.
Checkpoints authoritative state, reconciles ambiguous tool outcomes, preserves approvals, and resumes without repeating completed work.
Builds system-specific adversarial testing around realistic assets, identities, channels, tools, and measurable impact.
Contains compromised AI capabilities, preserves evidence, scopes derived data and actions, remediates boundaries, and verifies safe recovery.