@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dsec-access-design/C2> a edu:Question ;
    rdfs:label "C2 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    owl:sameAs <https://bitbucket.org/reffa/ontology/id/task/dsec-access-design/C2> ;
    schema:hasPart <https://knobit.org/id/register/data-security#SE-352>,
        <https://knobit.org/id/register/data-security#SE-353> ;
    schema:identifier "C2" ;
    schema:position 2 ;
    schema:text "Segregation of duties across a job's roles, 1 each. (a) JB-011 collections team lead holds RL-011 COLLECTOR (propose_payment_plan) and RL-012 TEAM_LEAD (approve_payment_plan): each role is clean on its own, but together they break SD-010 for one person. The answer reports the job, both roles and the rule. (b) Resolved by design: JB-011 removed from RL-011 (or given a role without propose_payment_plan), its duties still covered by RL-012; the absence cover the draft gives as the reason is met without the conflict (the team lead reassigns the case to another collector with assign_cases) or sent as an open question - not by a monitoring report or an instruction that team leads must not approve their own proposals."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-security#SE-352> rdfs:label "dsec-access-design C2: the team lead holds propose and approve through two clean roles"@en .

<https://knobit.org/id/register/data-security#SE-353> rdfs:label "dsec-access-design C2: the cross-role conflict removed by design, absence cover kept"@en .