引導式測驗 · 中等 等級

Brisk 教學與 AI 瀏覽器擴充測驗

查看 AI 瀏覽器擴充功能、Brisk 如何描述其產品,以及學校在課堂使用前應進行的檢查。

問題 1 的 8

What should a school review before installing an AI browser extension?

預覽每個問題8 問題

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

  1. What should a school review before installing an AI browser extension?
    • Permissions, data flow, retention and institutional approval
    • Only the extension icon
    • Whether it opens more tabs
    • The number of toolbar buttons
  2. Brisk describes connected product experiences. What should an educator confirm?
    • That every feature is in every school plan
    • Specific feature and account availability in their context
    • That product names equal legal approval
    • That help pages need not be read
  3. A teacher adapts a reading passage with an extension. Which review is important?
    • Share it without reading
    • Ask AI whether it is accurate
    • Check that the adaptation preserves key ideas and context
    • Remove all challenging ideas
  4. Why review the Student Data Privacy Addendum and district agreement?
    • They determine lesson standards
    • They certify output accuracy
    • They remove the need for teacher judgment
    • They clarify obligations and handling of student information
  5. Which is a lower-risk way to pilot a feature?
    • Upload identifiable essays immediately
    • Use teacher-created non-sensitive samples and record quality and access issues
    • Ask students to test it without review
    • Assume a free tool needs no review
  6. Who decides whether extension-drafted feedback is appropriate to share?
    • The extension automatically
    • The student browser
    • The educator who reviews it against the work and lesson goal
    • A second AI system
  7. What practical risk comes from browser context?
    • A user may invoke the tool while viewing confidential content
    • The extension changes all passwords
    • It permanently prevents pages from loading
    • It stops browser updates
  8. Why revisit official product documentation?
    • Browsers cannot update extensions
    • Policies never change
    • Documentation replaces district approval
    • Features and integrations can change