Which application enables you to define multiple approval levels based on business-rule definitions?
Risk Approver Configuration
Approval Configurator
Approver Levels
TPRM Approvals
The Approval Configurator is the application used to define multiple approval levels based on business-rule definitions. Part of the GRC approver framework, it lets an administrator build configurations in which conditions determine which approvers are required and at what level, so that approval requirements adapt to attributes of the record being approved, for example its risk rating or its financial impact.
The alternative names are not delivered applications. A Risk Approver Configuration, an Approver Levels module and a TPRM Approvals module sound plausible, but approvals in this context are not managed by a dedicated third-party risk approvals application; the shared configurator serves that purpose across GRC products.
The use of business rule definitions is what distinguishes this from a fixed approval chain. Rather than hard-coding approvers into workflows, the administrator expresses conditions and levels declaratively, which makes the arrangement maintainable as organizational structure changes. In Third-party Risk Management this supports governance of issue acceptance, exceptions and similar decisions that warrant escalating scrutiny.
When implementing, define approver groups first, then create the configuration with its levels and conditions, and test with sample records to confirm the right approvers are invoked at each level.
Which baseline methods can assign a Third-party Risk Assessment to a third party? Choose three
Manual
Automated based on Third-party categorization
Automated based on Security Score rule
Automated based on Third-party Tier rule
Automated based on Business Services supported by the third party
A third-party assessment can be assigned in three baseline ways. An assessor or manager can create it manually for a chosen third party. It can be assigned automatically when the third party's tier changes, because the assessment configuration includes a trigger for tier changes that selects the template mapped to the new tier. It can also be assigned automatically through a Security Score rule, which responds to a change in the third party's security score from a risk intelligence provider.
Categorization and supported business services are not baseline triggers. Although categories and services describe the third party and may inform tiering, no out-of-the-box rule assigns an assessment solely because of them. Achieving that behavior would require customization or an event-driven rule.
The design intent is to link assessment effort to risk. A change in tier indicates that the third party's criticality has moved, and a change in security score signals deterioration or improvement that may justify reassessment. Manual assignment remains available for exceptions and ad hoc due diligence.
Implementers should define the tier-to-template mapping and score thresholds carefully, since poorly tuned rules can send redundant assessments and burden both the third party and the risk team.
A Third-party Risk Manager needs to run a report that displays due Third-party Assessments. On which table should this report be run?
[sn_vdr_risk_assessment]
[sn_vdr_risk_asmt_task]
[sn_vdr_risk_asmt_assessment]
[sn_vdr_risk_asmt_issue]
External third-party risk assessments are stored in the table sn_vdr_risk_asmt_assessment. Each record carries the assessment state, due date, assigned third party, and the template used to generate it, which makes this table the correct basis for any report on assessments that are open, overdue or approaching their due date. Typical report conditions filter on State (for example Sent or Responses Received) combined with a Due date comparison against the current date.
The remaining tables serve different purposes. sn_vdr_risk_asmt_task holds the tasks raised for follow-up work, so a report there would count remediation activity rather than assessments. sn_vdr_risk_asmt_issue holds issues identified from responses or reviewers, and reporting against it describes findings, not due assessments. The first option does not correspond to the assessment record used by the application and would return nothing meaningful.
When building dashboards for a Third-party Risk Manager, the assessment table also supports grouping by third party, tier or engagement, which allows overdue exposure to be presented per relationship. Keeping assessment, task and issue reporting on their own tables avoids double counting where one assessment generates several issues.
Which additional record is created when an element classification is created?
Classification component definition
Classification component criteria
Engagement component definition
Engagement component criteria
Creating an element classification automatically generates a corresponding classification component definition record. The component definition describes the components that will be evaluated for elements assigned that classification, and it provides the structure to which scoring criteria are later attached. The platform produces it to guarantee that every classification has a definition ready for configuration.
Classification component criteria are different records. They hold the detailed conditions used to evaluate each component and are configured by the administrator after the definition exists; they are not created automatically with the classification. Engagement component definitions and criteria belong to the engagement side of the model, where scoring is applied to engagements, and they are not generated when an element classification is created.
Understanding this sequence is useful when configuring a custom classification. After creating the classification, the administrator opens the generated component definition, adds the components that matter for that type of element, and then defines criteria that translate answers into scores. Skipping the criteria leaves the classification without meaningful scoring, even though the definition record exists.
Testing with a sample element confirms that scores calculate as intended before the classification is used in production assessments.
If a Third-party Risk Issue is intended for internal use only, which states can be skipped? Choose two
Analyze
Finalize with Third-party
New
Submitted to Third-party
The Third-party Risk Issue lifecycle contains states that govern internal analysis and external collaboration. Two of them, Submitted to Third-party and Finalize with Third-party, exist solely to move the issue to the third-party contact for response and then to conclude it with that party. When an issue is intended for internal use only, no external exchange occurs, so those two states can be skipped.
The remaining states carry no such exemption. New is the entry state at which the issue is created, and it cannot be bypassed because every issue must begin there. Analyze is where the assessor evaluates the finding, determines severity and decides on the treatment, which applies equally to internal and shared issues; internal matters still require analysis before being resolved or accepted.
This design allows a single issue model to serve two purposes. Issues relating to internal controls or sensitive observations stay within the risk team, while issues that require evidence or action from the third party flow through the portal. Marking an issue as internal-only at creation determines which path it follows, and it should be set deliberately, since an issue exposed to the third party cannot be recalled in practice.
How do Third-party Risk questionnaires and document requests appear on the Third-party Portal?
As separate requests and can be assigned to different third-party contacts
As a single assessment assigned to a single engagement contact
As separate requests and can only be assigned to the same third-party contact
As a single assessment assigned to a single third-party contact
Within an external assessment, questionnaires and document requests are tracked as independent items, and the Third-party Portal presents each as a separate request. Because they are separate, they can be assigned to different third-party contacts. A primary contact can delegate a questionnaire to a colleague with the subject knowledge, for example a security officer, while a legal or compliance contact handles the document requests.
The statement that they appear as a single assessment is incorrect, as the assessment is the parent record that groups the requests, whereas the contact sees and works through the individual items. The restriction that they can only be assigned to the same contact is also wrong; delegation to multiple eligible contacts is a supported capability intended to mirror how real organizations distribute responsibility. The reference to assigning to a single engagement contact introduces a concept that is not part of this behavior, since assignment is made to third-party contacts, not to engagement contacts.
For implementation, ensure that all intended respondents exist as contacts on the third-party record before the assessment is issued, and that the primary contact understands the delegation process. This reduces delays caused by a single person being a bottleneck.
When the GRC: Policy and Compliance Management application is installed, which GRC related list appears on a Third-party Risk Issue record?
Policies
Policy Exceptions
Configuration baseline
Citations
When GRC: Policy and Compliance Management is installed alongside Third-party Risk Management, the Third-party Risk Issue record gains a Policies related list. This allows an issue to be associated with the internal policies that the finding relates to, so that a deficiency identified at a third party can be traced to the policy requirement it affects.
The other lists are not the ones added by this integration. Policy Exceptions track approved deviations from policy and are managed within the policy application's own exception process; they are not the related list displayed on the issue. Configuration baseline belongs to configuration compliance for technical assets. Citations are references to authoritative content such as regulatory requirements, and they sit within the compliance content model rather than being displayed as a related list on a third-party issue.
The practical benefit is traceability. A risk team can show an auditor which policies are implicated by a third party's failure to meet an expectation, and policy owners can see external findings that bear on their policies. Implementers should confirm that the plugin is active and that the related list is configured on the issue form for the relevant roles.
Which type of record is each question in an assessment?
GRC Task[sn_grc_task]
Assessment Metric [asmt_metric]
Task [task]
Assessment Instance [asmt_assessment_instance]
Within the ServiceNow Assessments framework that underpins Third-party Risk Management, a questionnaire is a collection of metrics, and each non-scripted metric is a single question presented to the respondent. Metrics are stored in the Assessment Metric table [asmt_metric], grouped beneath a Metric Category, and the category belongs to a Metric Type, which is the questionnaire template held in asmt_metric_type.
When a questionnaire is issued, the platform generates an Assessment Instance [asmt_assessment_instance] for the respondent, an d the answers given are written as instance question records that point back to the originating metric. The separation is deliberate: the metric is design-time content, the instance is run-time content, and the answer is a response record.
Option A is incorrect because sn_grc_task is a GRC work-item table and carries no questionnaire content. Option C, the base task table, represents generic work and plays no part in questionnaire structure. Option D identifies the container delivered to the respondent, not the individual question inside it.
Implementers who extend questionnaires, whether by adding metrics, weighting categories or building question banks, therefore operate against asmt_metric and its parent categories rather than against the instance tables.
Elements may be defined for an engagement. What do these elements represent?
An external organization on which the third party relies to provide goods, services, or support
Component criteria for the engagement applicable to the third party's delivery of goods, services, or support.
Risk areas defined for the engagement applicable to the third party's delivery of goods, services, or support.
The goods, services, or support that is provided by the third party
In Third-party Risk Management, an element extends the engagement model by representing an external organization on which the third party relies to provide goods, services or support. This allows risk to be assessed beyond the contracted party, covering the dependencies that sit beneath an engagement, commonly described as fourth-party exposure.
Each element is classified, and the classification determines the scoring model applied, which is why elements can be assessed with their own questionnaires and contribute to engagement-level risk.
The other options describe different constructs. The goods, services or support provided by the third party describe the engagement itself, not its elements. Component criteria describe how classifications are evaluated, and are configured on the classification side rather than being the element. Risk areas are the categories into which assessment content and scores are organized and apply to assessments generally; they are not what an element represents.
During implementation, decide which dependencies warrant element records. Capturing every minor subcontractor produces administrative overhead, whereas capturing critical dependencies provides the concentration and resilience visibility that risk managers expect from engagement-level assessments.
Which benefits does the Third-party Portal offer? Choose two
The Third-party Portal consolidates all communications and artifacts to a single system of truth
Third-party Portal allows the Third-party Risk Assessor team to reassign parts of a Inherent Risk Assessment
The Third-party Portal matches a database of documents to document requests
The Third-party Portal reduces risk for an organization by enabling secure communications with the third-party
The Third-party Portal can be leveraged by the third party to work with other partners
The Third-party Portal delivers two principal benefits. It consolidates communications and artifacts, including responses, documents, issues and tasks, into one system of record, which gives the organization a single, auditable source of truth in place of scattered email threads. It also reduces risk by providing a secure, access-controlled channel for exchanging sensitive information with the third party, so that assessment evidence is not transmitted through unmanaged email.
Reassignment of parts of an inherent risk assessment is not a portal benefit; the inherent risk assessment is an internal exercise completed by the organization's own users, and the portal is for external contacts. The portal does not match a database of documents to document requests; it receives the documents that contacts upload against each request, and the assessor evaluates them. Nor is the portal a collaboration tool for the third party's other partners: access is limited to the relationship between the third party and the customer.
When presenting the value of the portal to stakeholders, emphasize traceability and control. Every response, upload and status change is recorded against the assessment, supporting audit and enabling reporting on turnaround times and outstanding items.
What can be stated about the number of third-party contacts?
A third party must have one designated internal third-party manager
A third party can designate more than one contact as the primary, but must have a minimum of one primary contact
A third party can only designate one contact as the primary contact, but may have multiple non-primary contacts
A third party can only designate one contact as the primary and must have a minimum of one non-primary contact
Each third party can have several contacts, and the contact model allows more than one of them to be designated as primary. The firm requirement is that every third party must have at least one primary contact, since that person receives assessments, can manage the team of additional contacts and delegate work in the Third-party Portal. Without a primary contact, assessment assignment has no accountable recipient.
The statement requiring one designated internal third-party manager is incorrect; internal ownership is handled through other roles and fields and is not a constraint on the contact count. The statements limiting a third party to a single primary contact are also incorrect, because multiple primaries are supported. Requiring at least one non-primary contact is not a rule either, since a third party can operate with only one primary contact.
When multiple primary contacts exist, the behavior for assigning an assessment depends on the assessment engine in use, which means implementers should test how assignments are distributed before go-live. Primary contacts can invite further contacts through Manage Team, and good practice is to maintain at least two primaries so that an absence does not stall an assessment.
What is the benefit of using both TPRM and GRC/IRM?
Non-compliant controls automatically adjust the risk score for a third-party entity
Primary third-party contacts can then see their overall non-compliant risk score
All compliance controls are automatically visible to the third-party risk manager
Third-party Risk engagements automatically match with Audit engagements
Using Third-party Risk Management together with GRC or Integrated Risk Management connects external assessment results to the organization's control framework. When a third party gives an unsatisfactory answer to a question mapped to a control objective, the associated control can be marked non-compliant, and that non-compliance feeds into the calculated risk score for the entity. The risk posture therefore reflects control failures that originate from third-party evidence, not only from the assessment score.
The other statements do not describe actual behavior. Primary third-party contacts do not see an internal non-compliant risk score through the portal, since internal control status is not exposed to external parties. Compliance controls are not automatically visible to every third-party risk manager, because visibility remains subject to roles and access. Third-party risk engagements are not automatically matched with audit engagements, as these are different record types governed by separate processes.
In practice this integration gives risk teams a single view in which vendor findings, controls, issues and policy exceptions are linked. It requires that questions are associated with control objectives and that the relevant applications are installed and configured.
By default, when are reminder notifications for outstanding assessments sent to the third-party contact? Choose two
14 day after due date
30 days prior to due date
3 days prior to due date
7 days prior to due date
Third-party Risk Management ships with scheduled reminder notifications addressed to the third-party contact who owns an outstanding assessment. In the baseline configuration these reminders are issued 30 days before the due date and again 7 days before the due date, giving the contact an early prompt and a final prompt while there is still time to respond through the Third-party Portal.
The other values offered are not part of the default schedule. A reminder at 3 days prior is not delivered by default, and a notice 14 days after the due date is not a baseline reminder; overdue handling is treated separately from pre-deadline reminders. Organizations that want a tighter cadence can adjust the schedule, but that is a customization, not default behavior.
From an implementation standpoint, reminders depend on the assessment remaining open, a valid contact email address on the third-party contact record, and the relevant notification and scheduled job being active. Recipients are resolved from the contact assigned to the questionnaire or document request, so reassigning an item redirects subsequent reminders.
Which features apply to Third-party Risk Issues? Choose two
Generate audit tasks for the third-party risk team
Provide third parties direct access to update and respond to Issues
Can be generated on-demand or automatically due to an incorrect answer
Can only be seen by the customer's risk team
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.
How does ServiceNow enable companies to manage third parties without relying on emails and spreadsheets?
Third-party Platform
Primary Third-party
Third-party Manager Workspace
Third-party Portal
The Third-party Manager Workspace gives risk teams a consolidated environment for managing the third-party portfolio. It brings together oversight of third parties and engagements, assessments, tasks, issues, reporting and remediation, and replaces the manual coordination that typically relies on email threads and spreadsheets. Centralizing these activities provides a single, current view, along with an auditable history of actions.
The Third-party Portal is the external-facing counterpart. It is designed for third-party contacts to respond to questionnaires, document requests, issues and tasks, so it addresses how third parties interact with the organization, not how the organization manages its third-party program. Primary Third-party refers to a type of contact and is not an application or capability. Third-party Platform is not a defined component of the solution.
In implementation terms, the workspace is where assessors and managers work daily, and its configuration determines which lists, dashboards and actions they see. Role assignment governs access to workspace content, and administrators should verify that the correct roles are granted to the risk team. Changes to workspace behavior are governed by the application scopes that deliver it.
TESTED 17 Nov 2026