引導式測驗 · 中等 等級
歐盟數位服務法推薦系統測驗規則
測試 DSA 的保薦人透明度義務、第 38 條規定的較窄提供者範圍以及所需揭露和控制的實際限制。
問題 1 的 8
How does Article 19 affect Article 27 coverage for micro and small platforms?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- How does Article 19 affect Article 27 coverage for micro and small platforms?
- They are excluded from Article 27 but not from any DSA duties
- They become covered only if they publish their ranking source code
- They are generally excluded from Section 3, but a designated VLOP remains covered regardless of provider size
- They are always covered, even when small and not designated as a VLOP
- What must a platform’s Article 27 explanation include about main parameters?
- Only a general statement that “AI personalizes your feed”
- The most significant criteria and reasons for their relative importance
- Every model weight and source-code file
- A complete list of each user’s personal data
- When does Article 38 require a non-profiling option for each recommender system?
- When a VLOP or VLOSE uses recommender systems
- For every online platform, regardless of size or designation
- Only when a user requests access to source code
- Only for marketplace product recommendations
- A platform offers several feed-ordering options. Where should the selection function be reachable under Article 27?
- Only through customer support after a written request
- Only in the platform’s source-code repository
- Only inside a downloadable annual transparency report
- Directly and easily from the interface section where information is prioritized
- Does Article 27 require a platform to disclose all source code and model weights?
- No; it only requires a privacy policy with no recommender explanation
- No; it requires intelligible disclosure of main parameters and available user options
- Yes, source code must be public for every ranking model
- Yes, but only when ranking uses machine learning
- Is a chronological feed the only way to satisfy Article 38?
- No; the required option is one that is not based on profiling, and the article does not prescribe a specific feed design
- Yes; every recommendation must be removed entirely
- No; an option based on profiling is sufficient if clearly labeled
- Yes; the text names chronological ordering as the required option
- A compliance team audits a recommender after a major ranking change. What should it compare?
- The explanation against a competitor’s public feed only
- The product’s source code against an unrelated open-source model
- The number of recommendations against an arbitrary fixed target
- The user-facing explanation and controls against the deployed system and service scope
- Which statement best captures the DSA duties and their scope limits?
- Article 19 exempts all VLOPs from both Articles 27 and 38
- The DSA requires every recommender to use chronological ranking
- Article 27 covers eligible platform recommenders subject to Article 19; Article 38 adds a non-profiling option for VLOPs/VLOSEs
- Article 27 and Article 38 impose identical duties on every EU website