Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Master Enterprise AI
| Question | Answer |
|---|---|
| How are AI agents defined in a 2026 enterprise context? | AI agents are generative systems that can plan multi-step tasks, use external tools, maintain state across interactions, and coordinate with other agents to complete work that previously required human orchestration. |
| Regarding planning, how does an AI agent differ from a traditional chatbot? | While a chatbot follows predefined response paths based on intent classification, an AI agent uses an LLM to autonomously generate plans, execute steps, and adjust its strategy based on observed results. |
| What distinguishes the tool usage of an AI agent from that of a chatbot? | Chatbots primarily produce text responses, whereas AI agents call external tools like APIs, databases, and code environments to drive their reasoning steps and perform functional work. |
| In the AI capability spectrum, what defines a Level 1 LLM-Powered Chatbot? | A Level 1 assistant retrieves context from a vector store to answer questions from a document corpus but lacks tool execution and a planning loop. |
| What characterizes a Level 3 ReAct Agent in terms of operation? | A Level 3 agent uses a 'Reasoning + Acting' loop to plan and execute multi-step tasks, observing tool results and adjusting its plan until the goal is achieved. |
| Which three core layers are non-negotiable for any production enterprise AI agent system? | Every production-ready system requires an LLM reasoning layer for decision-making, a tool execution layer for external calls, and a reliability layer for memory and error recovery. |
| What is the primary function of the Tool Execution Layer in agent architecture? | The Tool Execution Layer serves as a controlled interface that uses a tool registry, zero-trust permissions, and isolated sandboxes to safely call external systems and log audit trails. |
| How does the Reliability Layer manage potential 'runaway' agents? | The Reliability Layer prevents infinite loops and unbounded API credit consumption by enforcing hard step limits, time limits, and cost limits on every agent execution. |
| In AI agent architecture, what is the 'Plan-and-Execute' pattern? | The Plan-and-Execute pattern involves a planner LLM generating a full task plan and an executor LLM running each step, often with a critic LLM reviewing results before proceeding. |
| When is a Multi-Agent Orchestrator/Worker pattern most appropriate? | This pattern is used for tasks that are too complex for a single agent or require parallelisable sub-tasks with specialized domain knowledge in different areas. |
| What is the role of Episodic Memory in an enterprise AI agent system? | Episodic memory stores records of past interactions with a specific user, including prior task completions and preferences, to maintain continuity across sessions. |
| How does Semantic Memory contribute to agent functionality? | Semantic memory utilizes vector stores to provide the agent with access to enterprise knowledge such as product documentation, policies, and industry regulations. |
| What is stored within an agent's Procedural Memory? | Procedural memory captures successful task execution patterns, tool sequences, and error recovery strategies that have worked for specific recurring task types. |
| Why is 'idempotency' critical for write-capable tool calls? | Idempotency ensures that write operations carrying unique IDs can be safely retried without creating duplicate records or unintended side effects if the first call fails. |
| How is the 'principle of least privilege' applied to external service APIs? | The agent's OAuth scopes are strictly limited to the minimum permissions required for its specific task, with credentials managed through secure systems like AWS Secrets Manager. |
| What safety mechanism prevents prompt injection from external web content? | Input sanitization layers and separate context compartments for untrusted input ensure that malicious instructions in web content cannot override the agent's primary system prompt. |
| How do irreversibility controls function in an enterprise agent environment? | Irreversibility controls classify tools like financial transactions or record deletions and require a human-in-the-loop approval if the action's impact exceeds a set threshold. |
| What is the purpose of 'retrieval-augmented grounding' in agent responses? | Grounding ensures that all knowledge-sensitive assertions are supported by retrieved source documents, reducing the risk of the LLM generating plausible but factually incorrect hallucinations. |
| Which Human-in-the-Loop (HITL) trigger handles ambiguous or conflicting user input? | The 'ambiguous instructions' trigger pauses the agent and generates a structured escalation request for a human to confirm the intended resolution when reasoning alone cannot solve a conflict. |
| What are the primary goals of the Agent Discovery Sprint (Phase 1)? | The discovery sprint maps the target workflow, classifies tasks by automation readiness, identifies compliance requirements, and determines if there is sufficient data for deployment. |
| What occurs during the Evaluation and Red-Teaming phase (Phase 5)? | Engineers test the agent against hundreds of representative tasks and use adversarial inputs to identify vulnerabilities like prompt injection or runaway loops before production deployment. |
| How is 'shadow mode' used during the staged production deployment phase? | Shadow mode runs the agent in parallel with existing human processes to compare outputs and identify systematic errors without allowing the agent to take live actions. |
| Why do enterprise AI agents require an API gateway for legacy systems? | An API gateway normalizes responses from legacy ERP or HRMS systems, enforces access control, and prevents the agent layer from having direct access to sensitive internal credentials. |
| In multi-agent systems, how does the 'Parallel Worker Pool' increase efficiency? | The Parallel Worker Pool allows an orchestrator to fan out identical tasks to multiple worker agents simultaneously, such as reviewing hundreds of contracts for specific clauses in parallel. |
| What does 'Observability' cover in a production AI agent environment? | Observability includes distributed tracing of reasoning steps, tracking tool call latency, monitoring success rates by task type, and calculating the LLM API cost per completed task. |
| How does multi-tenant isolation protect enterprise clients using a shared agent platform? | Multi-tenant isolation ensures that each client's tools, semantic memory documents, and learned procedural patterns are strictly separated at the storage layer to prevent data leakage. |
| When should an enterprise avoid using an autonomous AI agent for a task? | Enterprises should avoid full autonomy for clinical diagnoses, legal negotiations, high-spend procurement, or any task creating significant contractual obligations that cannot be easily disputed. |
| What is the 'zero-trust' principle in agent tool access? | Zero trust ensures that agents receive the minimum tool permissions required for their specific task, and all actions are logged to an immutable audit trail for continuous compliance monitoring. |
| Why is model version pinning recommended for production AI agents? | Pinning ensures that agent performance remains consistent, as updates to underlying LLM versions can change reasoning behavior and potentially degrade the agent's success rate. |
| What is the primary engineering bottleneck in moving from a demo to a production AI agent? | The gap is not the LLM itself but the engineering of tool architecture, memory design, safety guardrails, evaluation methodology, and a robust observability infrastructure. |
Created by:
mobisoftinfotech