引導式測驗 · 硬 等級

NVIDIA NeMo 護欄測驗

測試五個 NeMo 軌道階段、Colang 和配置角色、工具呼叫實施、評估以及配置的防護措施的限制。

相關引導路徑Nvidia 尼莫護欄
問題 1 的 8

Which NeMo rail stage is intended to validate user input before a model is called?

預覽每個問題8 問題

當您參加測驗時,就會出現答案和解釋。

  1. Which NeMo rail stage is intended to validate user input before a model is called?
    • 檢索
    • Execution
    • 輸入
    • 輸出
  2. Where do retrieval rails act in a retrieval-augmented application?
    • During model pretraining
    • On documents or chunks returned by retrieval
    • Only on the final user-facing response
    • After a tool has executed
  3. Which rail type controls tool or function calls and their arguments?
    • 輸入
    • 檢索
    • Dialog
    • Execution
  4. Which function does a dialog rail serve in NeMo Guardrails?
    • Validate image file codecs only
    • Replace all retrieval logic
    • Train the base LLM
    • Constrain guided conversational flow across turns
  5. How do YAML and Colang fit into the documented toolkit?
    • YAML configures settings and rails; Colang expresses conversational flows and guardrail logic
    • Colang stores the model weights
    • YAML is only a log format
    • Both are names for an output classifier
  6. Why should tool authorization be enforced at the execution boundary?
    • Retrieved chunks execute automatically
    • A response filter cannot undo an external action already performed
    • Dialog rails always block every unsafe tool
    • A user prompt is a secure permission token
  7. What determines whether a NeMo rail uses an LLM, external service, or custom code?
    • The user’s browser
    • A universal default shared by all installations
    • The chosen configuration and implementation
    • The name of the rail alone
  8. What does adding NeMo Guardrails establish about system safety?
    • A configurable set of controls that still requires scenario testing and other safeguards
    • That human review is never useful
    • That prompts can no longer contain hostile instructions
    • A guarantee against every attack and factual error