AI Agents Professional Practice Exam Questions and Answers – Part 17/17

Answer: B. Implement a comprehensive lineage and metadata tracking ledger that logs every step of the agent's reasoning, the exact source data accessed, the specific prompt templates utilized, and the human supervisor approval signatures.

The correct answer satisfies the requirement by implementing an immutable ledger that captures reasoning steps, source data, and human approvals. For the exam, look for comprehensive logging features that establish accountability; options altering memory buffers or network protocols fail to provide actual lineage.

Answer: B. Train the base model using Constitutional AI frameworks to enforce self-correction principles, backed by a real-time safety evaluation model that scores output toxicity before presentation.

The correct answer is effective because Constitutional AI trains models to self-correct against safety principles, while a secondary evaluation model actively blocks toxicity. Candidates should recall that safety alignments rely on structured behavioral frameworks, whereas manipulating memory or temperature yields no reliable safeguard.

Answer: D. A sudden, highly coordinated spike in Request-Per-Minute (RPM) volume from a single IP pool, where the queries contain randomized variations of public benchmark datasets designed to systematically reconstruct the model's decision boundaries.

The correct answer correctly identifies the attack because extraction relies on massive, coordinated query volumes designed to map decision boundaries using benchmark variations. For the exam, focus on abnormal traffic patterns and systematic data probing rather than internal database faults or tokenizer configurations.

Answer: A. Implement feature attribution methodologies such as Integrated Gradients or layer-wise token attention visualization, paired with comprehensive system logging of prompt templates and RAG source contexts.

Feature attribution techniques like Integrated Gradients and strict system logging provide the required transparency for auditing LLM outputs. For the exam, remember that visibility relies on tracking inputs and applying mathematical attribution rather than just changing prompting strategies or modifying internal weights.

Answer: A. The orchestration framework did not treat untrusted external data fields with strict input sanitization boundaries, allowing semantic data to be interpreted as executive system commands.

A blind prompt injection occurs when untrusted external data is not properly isolated from system instructions. The key is failing to treat external data as untrusted, which allows the malicious payload to hijack the model's instruction path. Temperature and token limits do not prevent this.

Answer: D. The underlying LLM serving infrastructure is experiencing high prompt-processing or pre-fill saturation, likely due to an inflation of input token payload sizes or queuing delays in the KV-cache management engine.

Time to First Token spikes when the serving infrastructure struggles to process the input prompt and pre-fill the KV cache. Look for pre-fill saturation or queuing delays when diagnosing this metric. Token generation settings and vector database retrievals do not directly impact this initial processing latency.

Answer: D. The governance layer must be capable of programmatically querying and exporting all centralized telemetry logs, RAG metadata history, and user profile sessions linked to that specific consumer's identifier.

The Right to Know under CCPA requires the enterprise to query and export all user-linked telemetry and retrieval histories. Fine-tuning the model or deleting the tokenizer does not extract the requested interaction logs. Governance frameworks must maintain explicit data provenance for compliance.

Answer: B. Deploy an automated output-filtering layer that scans generated completions for matches against known proprietary or copyrighted text databases, paired with a low-temperature RAG architecture grounded entirely in licensed company files.

Using automated output filtering against copyrighted databases and grounding responses in licensed RAG files mitigates intellectual property risks. Setting high temperatures or stripping punctuation fails to actively prevent copyright infringement. Lowering generation variance is key here.

Answer: D. Isolate the core foundational models from any fine-tuning pipelines, routing all specialized clinical data through temporary context windows using a Retrieval-Augmented Generation (RAG) pattern backed by a zero-retention data privacy agreement.

Isolating static base models and routing sensitive data through temporary RAG context windows prevents weights from being updated. This architectural choice guarantees no patient data leaks into parametric memory. Modifying temperatures or ignoring file indexes does not isolate the model.

Answer: B. Implement hard per-user and per-session Token-Per-Minute (TPM) caps at the API gateway layer, combined with an automated context truncation filter that drops input payloads exceeding a pre-defined length.

Implementing hard token-per-minute caps and input truncation filters at the gateway directly neutralizes adversarial prompt-bloat attacks. This enforces predictable API consumption. Fine-tuning weights or stripping punctuation does not limit the computational cost of massive input payloads.

Answer: D. Sanitize and de-bias the training/fine-tuning datasets, implement counterfactual fairness testing during evaluation, and apply hard constraint filtering to remove explicit demographic proxies from input contexts.

Mitigating algorithmic bias requires actively curating datasets, removing demographic proxies, and implementing counterfactual fairness testing. Altering the tokenizer or memory buffer does not address structural biases ingrained in the training data. Use hard constraints to block biased inferences.

Answer: A. The lack of access control and encryption creates an internal data exfiltration risk, potentially allowing unauthorized employees to steal the model weights and replicate proprietary IP outside the corporate perimeter.

Leaving model weights unencrypted on a shared drive exposes the firm to internal data exfiltration and intellectual property theft. This allows unauthorized users to copy and replicate the proprietary model. Tokenizer errors and distance metric shifts are not valid security risks.

Answer: A. Enforce a text generation temperature of 0.0, set a fixed random number generator seed value parameter, and pin the precise model checkpoint version string within the API payload.

Setting temperature to zero, fixing the random seed, and pinning the exact model version minimizes token variance and ensures deterministic completions. For the exam, always look for these three controls together when a scenario demands strict auditability and generation consistency.

Answer: A. Implement an LLM router strategy: deploy a small, highly specialized fine-tuned model (e.g., a 7B parameter model) to handle standard classification requests, and escalate low-confidence or ambiguous queries to the frontier model.

The correct answer works because a routing strategy uses smaller, specialized models for routine classifications, cutting costs significantly. Escalating only ambiguous queries to frontier models maintains overall system accuracy without incurring massive computational expenses.

Answer: A. Incorporate a context-compression algorithm (such as LLMLingua) or deploy a hierarchical routing agent that selectively fetches only the precise policy segments needed for the specific query before invoking the model.

The correct answer mitigates token bloat by deploying context compression or utilizing hierarchical routing to fetch only relevant policy chunks dynamically. Expanding the context window simply accommodates the bloat rather than resolving the underlying inefficiency of the system.

Answer: D. Configure an external runtime state validator or "watchdog" monitor that intercepts consecutive, identical tool/output outputs and triggers a circuit breaker to halt execution.

Production-grade autonomous loops must be protected by system-level interceptors. Implementing programmatic circuit breakers prevents infinite reasoning loops from causing massive token cost spikes. Standard rate limiting handles traffic volume but cannot stop repetitive internal logic failures.

Answer: A. Ground the model using a strict Retrieval-Augmented Generation (RAG) architecture over verified internal product databases, set the inference temperature near 0.0, and enforce structured JSON parsing.

The correct answer works because grounding responses in verified databases restricts outputs to factual data, while a low temperature reduces creative variance. On the exam, always associate hallucination mitigation with Retrieval-Augmented Generation and strict schema enforcement rather than infrastructure changes.

Answer: B. A valid SOC 2 Type II certification encompassing the Trust Services Criteria of Security, Confidentiality, and Availability, alongside an established ISO/IEC 27001 ISMS validation.

SOC 2 Type II and ISO 27001 certifications provide verified audits confirming that infrastructure providers maintain strict data isolation and operational boundaries. This directly addresses the CTO's requirement. Unindexed files or vector search indexes do not constitute formal compliance certifications.