What do event-driven rules for third-party risk do?
Options:
A.
Auto-generate issue records when third parties are not compliant
B.
Auto-generate and send questionnaires and document requests to engagements and third parties
C.
Auto-generate engagements when risk intelligence scores fall below specified levels
D.
Auto-generate and send email notifications to third parties for engagements
Answer:
B
Explanation:
Event-driven rules automate outreach. When a defined event occurs, the rule automatically generates and sends questionnaires and document requests to engagements and third parties. This removes the need for a manager to manually create assessments in response to changes, for instance a new engagement, a tier change or the approach of a renewal date.
The rules do not generate issue records when third parties are not compliant; issues arise from assessment responses or manual identification during review. They do not create engagements when risk intelligence scores decline, because engagements represent contractual relationships and are not produced by monitoring data; score-based activity is handled by provider-based submission rules and security score triggers. Although email notifications may accompany the process, the rule's purpose is not to send standalone notifications; the substantive output is the assessment content issued to the recipient.
For implementation, an event-driven rule should be planned with its triggering condition, the target third parties or engagements, and the templates to send. Because a rule can issue requests to many external parties at once, it should be tested in a sub-production instance and reviewed by the risk manager before activation.
[Reference: Study Guide – Third-party Supporting Processes: Event-Driven Management Rules and Automated Assessment Distribution.]
Question 6
Which benefits result from creating Question Banks? Choose two
Options:
A.
An entire category and all its metrics from a question bank can be added to a questionnaire template
B.
The auto assessment generator can randomly select metrics from a question bank to create a questionnaire template
C.
Responses to individual metrics belonging to a question bank will be tracked in the question bank
D.
Individual metrics from a question bank can be added to a questionnaire template
Answer:
A, D
Explanation:
Question Banks provide a reusable library of assessment content from which questionnaire templates are built. Two benefits follow directly from how banks are structured. An entire metric category, together with all of its metrics, can be added to a questionnaire template in a single action, which accelerates construction of large questionnaires. Individual metrics can also be selected and added independently, giving authors fine-grained control over the content.
The auto assessment generator does not randomly select metrics from a bank to produce a questionnaire template; random selection would yield unpredictable and non-repeatable assessments, which is incompatible with the consistency that risk scoring requires. Responses are likewise not tracked in the bank. A bank holds definitions, whereas responses are recorded against the assessment or questionnaire instance issued to a particular respondent, preserving each third party's answers separately.
In practice, banks reduce duplication and improve governance. A control question revised in the bank can be reused with confidence, and authors do not have to recreate common categories such as security governance or business continuity for every questionnaire. Teams should organize banks by subject area, so authors can locate categories quickly and combine them into templates matched to tiers.
[Reference: Study Guide – Assessment Configuration: Question Banks and Questionnaire Template Authoring.]
Question 7
Which table stores Third-party Risk Tasks?
Options:
A.
sn_vdr_risk_asmt_task
B.
sn_vdr_risk_asmt_activity
C.
sn_vdr_risk_task
D.
sn_vdr_risk_assessment_task
Answer:
A
Explanation:
Third-party risk tasks are stored in the table sn_vdr_risk_asmt_task. The table records follow-up work connected to assessments and issues, such as obtaining additional evidence or confirming a remediation step, and it extends the Planned Task table, so tasks inherit planning features such as scheduling and assignment. The table is part of the same scoped family as the assessment and issue tables, which share the sn_vdr_risk_asmt prefix.
The remaining names are not the delivered table. A table named for an activity, a table using a shortened sn_vdr_risk_task prefix, and a table carrying a longer assessment_task name resemble the real one but do not correspond to the application's data model. Using any of them in a report, import or script would fail or yield no data.
Knowing the exact table name is useful in several practical scenarios. Reports on overdue remediation work, access control rules, and integrations that create tasks all reference it. When exposing tasks to third-party contacts through the portal, the portal widgets and access controls also operate against this table, so any customization must respect those controls to keep each third party limited to its own tasks.
[Reference: Study Guide – Third-party Supporting Processes: Third-party Risk Tasks and Data Model.]
Question 8
Which features apply to Third-party Risk Issues? Choose two
Options:
A.
Generate audit tasks for the third-party risk team
B.
Provide third parties direct access to update and respond to Issues
C.
Can be generated on-demand or automatically due to an incorrect answer
D.
Can only be seen by the customer's risk team
Answer:
B, C
Explanation:
Third-party Risk Issues have two characteristics reflected in the correct options. They can be generated on demand by an assessor or automatically, for example when a response to a question in an external assessment is evaluated as incorrect. They also support collaboration with the third party: contacts use the Third-party Portal to view and respond to issues raised by the risk team, so remediation evidence can be exchanged without email.
Generating audit tasks is not a feature of issues. Audit work belongs to audit management and engagements, while issues in this application drive remediation conversations with the third party. The statement that issues can only be seen by the customer's risk team is also incorrect, because third-party contacts see issues that have been shared with them and are assigned within their organization.
For design purposes, this duality matters: internal-only issues exist for matters not intended for the third party, while shared issues move through states that include third-party submission and finalization. Visibility is governed by the state and by the access granted to the third-party contact, not by a blanket restriction.
Automatic issue generation should be paired with sensible thresholds to avoid flooding assessors with low-value records.
[Reference: Study Guide – Third-party Supporting Processes: Issue Creation, Collaboration and Portal Access.]