Útmutatóhoz kapcsolódó kvíz · Közepes Szint
EU Digital Services Act Rules for Recommender Systems Quiz
Tests the DSA’s recommender transparency duties, the narrower Article 38 provider scope, and practical limits of the required disclosures and controls.
kérdés 1 -ból 8
Hogyan érinti a 19. cikk a 27. cikk hatályát a mikro- és kisplatformokra?
Tekintse meg az összes kérdést8 kérdéseket
A válaszok és magyarázatok megjelennek a kvíz kitöltésekor.
- Hogyan érinti a 19. cikk a 27. cikk hatályát a mikro- és kisplatformokra?
- 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
- Mit kell tartalmaznia a platform 27. cikk szerinti magyarázatának a fő paraméterekkel kapcsolatban?
- 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
- Mikor ír elő a 38. cikk nem profilalkotási lehetőséget az egyes ajánlórendszerekhez?
- 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
- Egy platform számos feed-rendelési lehetőséget kínál. Hol legyen elérhető a kiválasztási funkció a 27. cikk értelmében?
- 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
- A 27. cikk megköveteli a platformtól az összes forráskód és modellsúly közzétételét?
- 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