Викторина, связанная с руководством · Средний Уровень
Правила викторины по Закону ЕС о цифровых услугах для рекомендательных систем
Проверяются обязанности DSA по прозрачности рекомендаций, более узкая сфера действия поставщика согласно статье 38, а также практические ограничения требуемого раскрытия информации и контроля.
Вопрос 1 из 8
Как статья 19 влияет на сферу действия статьи 27 для микро- и малых платформ?
Предварительный просмотр каждого вопроса8 вопросы
Ответы и пояснения появляются по мере прохождения теста.
- Как статья 19 влияет на сферу действия статьи 27 для микро- и малых платформ?
- 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
- Что должно включать пояснение платформы по статье 27 об основных параметрах?
- 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
- Когда статья 38 требует возможности непрофилирования для каждой рекомендательной системы?
- 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
- Платформа предлагает несколько вариантов заказа кормов. Где должна быть доступна функция отбора согласно статье 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
- Требует ли статья 27, чтобы платформа раскрывала весь исходный код и веса моделей?
- 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