引導式測驗 · 中等 等級
歐盟人工智慧法案對通用人工智慧模型的義務測驗
將第 53 條職責應用於 GPAI 提供者、下游使用者、開源模型、培訓摘要和當前合規時間表。
問題 1 的 8
Which item must a GPAI provider make publicly available under Article 53?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- Which item must a GPAI provider make publicly available under Article 53?
- A sufficiently detailed summary of training content
- Every training example and personal record
- All confidential evaluation logs
- A guarantee that downstream systems are compliant
- Which information does a provider make available to downstream AI-system providers?
- Only the model’s public marketing name
- Information on capabilities and limitations needed to integrate the model and meet downstream duties
- The confidential weights of every model
- A list of all users of the model
- What does Article 53(1)(c) require concerning copyright?
- A policy to comply with EU copyright and related-rights law, including rights reservations
- A claim that all training is fair use
- A license for every work in all circumstances
- Automatic deletion of all copyrighted material
- Which Article 53 duties may be exempted for qualifying free/open-source GPAI models?
- All Article 53 duties, including systemic-risk duties
- Only technical documentation and downstream integration information in points (a) and (b)
- The copyright policy and public training summary only
- No duties for any model
- Where is regulator-facing technical documentation generally provided under Article 53?
- It is published on every provider’s website
- It is provided to the AI Office or national competent authorities upon request
- It is sent only to end users
- It is filed as a patent
- When did the GPAI obligations enter into application for new models?
- August 2, 2025
- February 2, 2025
- December 2, 2027
- August 2, 2028
- What transition does the Commission describe for GPAI models placed on the market before August 2, 2025?
- They are permanently exempt
- They must comply by August 2, 2027
- They must comply the next day
- They are treated as AI systems but never as models
- What should a team check before relying on the open-source exception?
- Yes, permanently
- Assume exemption regardless of license and disclosure
- A patent filing
- Check all license, public-information, and systemic-risk conditions