गाइड से जुड़ी प्रश्नोत्तरी · कठिन स्तर

NVIDIA NeMo Guardrails Quiz

Tests the five NeMo rail stages, Colang and configuration roles, tool-call enforcement, evaluation, and limits of configured safeguards.

संबंधित मार्गदर्शक पथNvidia Nemo Guardrails
प्रश्न 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