ServiceNow Certified Implementation Specialist – Third-party Risk Management Questions and Answers
What is the definition of “Risk Management”?
Options:
Process to identify, assess, and respond to risks, threats and vulnerabilities that could compromise the business
The process of conforming to standards, policies, and remediation of audit findings
The elimination of vulnerable surface area in an enterprise environment
Policies/Standards/Procedures established to ensure an organization is aligned with corporate strategy and expectations are clearly defined
Answer:
AExplanation:
Risk management is the process of identifying, assessing and responding to the risks, threats and vulnerabilities that could compromise the business. It is a continuous cycle: risks are identified, their likelihood and impact are analyzed, and a response, whether mitigation, transfer, acceptance or avoidance, is selected and monitored.
The alternatives describe neighboring disciplines. Conforming to standards and policies and remediating audit findings describes compliance management, which concerns adherence to requirements rather than the evaluation of exposure. Eliminating vulnerable surface area describes a technical hardening activity, a possible response to a risk but not the discipline itself; moreover, elimination of all exposure is rarely achievable or economical. Establishing policies, standards and procedures aligned to corporate strategy describes governance, which sets direction and expectations within which risk management operates.
Third-party risk management applies the same cycle to external relationships. The organization identifies the risks introduced by each supplier or partner, assesses them through questionnaires and evidence, and responds through issues, tasks, exceptions or termination. Understanding this definition is foundational, since the application's tiering, assessment and remediation features map directly to the identify, assess and respond stages.
Besides direct third-party assessments, which other hierarchical entities can contribute to the overall third-party risk rating? Choose two
Options:
Advanced risk assessments
Engagements
Child third parties
Entity class rules
Answer:
B, CExplanation:
The overall risk rating of a third party is not derived solely from its own direct assessments. It also takes into account entities arranged beneath it in the hierarchy. Engagements contribute, because they represent the specific products or services supplied and carry their own assessment results. Child third parties, such as subsidiaries recorded with the primary third party as their parent, also contribute, with their risk ratings feeding into the primary third party's rating, which is calculated as a weighted average.
Advanced risk assessments are not a hierarchical entity; they describe a type or depth of assessment and not a level in the hierarchy that rolls into the rating. Entity class rules are configuration constructs that classify or drive behavior and are not entities that contribute a rating.
The rollup supports a realistic view of exposure. A parent organization with a high-risk subsidiary, or a low-risk third party with a single critical engagement, should not appear uniformly low risk. Implementers should therefore model subsidiaries as separate records with the Parent field populated and define engagements for the distinct services provided, so that the rating reflects the whole relationship.
Weighting should be reviewed so that no single child distorts the result.
Which Vendor Management Workspace feature displays the geographic locations of active third parties and engagements?
Options:
World atlas view
Third-party location page
Third-party geographic view
Risk concentration map
Answer:
DExplanation:
The Risk concentration map in the Vendor Management Workspace presents the geographic locations of active third parties and engagements. Pins on the map reveal where relationships are clustered, and filters for risk rating and engagement type allow the analyst to narrow the view, for instance to high-risk engagements within a region. The feature supports concentration analysis, which asks whether too much of the organization's dependency is exposed to a single location, such as a region affected by a natural disaster or geopolitical event.
The other names are not workspace features. A world atlas view, a third-party location page and a geographic view are plausible descriptions of the function but are not the name of the delivered capability.
The map relies on location data held on third-party and engagement records. Where addresses or countries are missing or inconsistently entered, the map is incomplete, so data quality is a precondition for its usefulness. Implementers should confirm that location fields are populated during data load, and that the roles viewing the map have access to the underlying records.
If the customer does not provide clean data, which baseline solutions are available in the platform? Choose three
Options:
System import transform map scripts
System definition fix scripts module
Integration hub ETL plugin
Service graph connector
Field normalization plugin
Answer:
A, C, EExplanation:
When source data is unclean, the platform offers several baseline means of improving it during load. System Import transform map scripts allow field values to be cleansed, reformatted or conditionally mapped as import set rows are transformed into target records, so inconsistent names, codes or formats can be corrected in flight. The IntegrationHub ETL capability provides data preparation transforms before data is mapped to target classes and attributes, which supports normalization of structured source data. Field normalization rules and the normalization plugin standardize values such as names and units so that equivalent entries are represented consistently.
A system definition fix scripts module is not a data cleansing facility; fix scripts perform one-time upgrade or data corrections and are not a configured pipeline for incoming data. The Service Graph Connector is a packaged integration for bringing configuration data from a specific source into the CMDB. It is a source-specific connector, not a general mechanism for cleansing customer-supplied data.
Implementers should therefore choose the least complex tool that addresses the defect, applying transform scripts for targeted fixes and normalization for broad standardization. Cleansing before the load is preferable to repairing records afterward, because duplicate third parties produce unreliable rollup scoring.
Which additional record is created when an element classification is created?
Options:
Classification component definition
Classification component criteria
Engagement component definition
Engagement component criteria
Answer:
AExplanation:
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.
Which related list is used to relate a Third party assessment question to a Control Objective record?
Options:
Questionnaire templates
Category metrics
Third-party questions
Assessment metrics
Answer:
DExplanation:
Assessment questions are stored as assessment metrics, and the association between a question and a Control Objective is managed through the Assessment metrics related list on the Control Objective record. Adding a metric to this list establishes the mapping that allows a response to a questionnaire item to influence the compliance status of controls tied to the objective.
Questionnaire templates is not the correct list because it groups the templates themselves, not the individual questions linked to a control objective. Category metrics refers to metrics within a category, which relates to questionnaire structure and not to control alignment. Third-party questions does not describe a delivered related list, since questions in this application are metrics.
The mapping is the foundation of the integration between third-party risk and GRC. Once questions are associated with control objectives, responses can mark the related controls as compliant or non-compliant, and the effect can influence risk scoring. Implementers should therefore prepare the control framework first, then relate metrics, and confirm through testing that a deliberately incorrect response produces the expected change in control status.
Maintaining these relationships requires attention whenever questionnaires are revised, since a new or replaced metric will not carry the mapping automatically.
As the final step before closing the Third-party Risk Assessment, which task(s) would the Risk Assessor typically perform?
Options:
Flag questions for follow up
Review comments and evaluates the risk
Create issues within the assessment
Perform a tiering assessment
Answer:
BExplanation:
The closing step of an external assessment is the assessor's review of the comments gathered during the exercise and an evaluation of the overall risk. By this stage the responses have been received, questions have been scored, and any follow-up has been completed, so the assessor consolidates the evidence into a conclusion before the record is closed.
The remaining activities belong earlier in the lifecycle. Flagging questions for follow-up happens while responses are being reviewed, since it identifies items needing clarification before the assessment can conclude. Creating issues is also performed during review, typically once responses are available, so that remediation can be tracked in parallel; waiting until the final step would leave no time to resolve them. A tiering assessment is a separate process that determines the third party's tier from inherent risk and is not part of closing an individual assessment.
Closing an assessment is a controlled event: the rating becomes authoritative and may drive downstream actions such as tier updates, notifications or control compliance. Assessors should therefore confirm that issues have been raised and that comments are complete before changing the state, because corrections after closure are more difficult to explain to auditors.
Which actions are required before a risk intelligence report can be requested? Choose two
Options:
A risk intelligence sample report must be downloaded by the user
The Order reports field of the provider record must be set to true
The Sanctioned report request field of the provider record must be set to yes
A risk intelligence request type record must be created for the provider
The copyright agreement field on the Risk Intelligence Report request form must be set to true.
Answer:
B, DExplanation:
Risk intelligence reports are ordered from external providers through the risk intelligence capability of Third-party Risk Management. Two configuration items gate the request. First, the provider record must have the Order reports option enabled; without it, the provider is treated as a source of scores or data only and cannot be selected when requesting a report. Second, a risk intelligence request type must exist for that provider, because the request type defines which report is available and populates the report selection on the request form.
Downloading a sample report is an optional reference step and does not enable ordering. The sanctioned-report field is not a prerequisite for requesting reports, and the copyright agreement setting on the request form is not a configuration action that must be completed beforehand.
In practice, an administrator registers the provider, enables ordering, and then defines request types that match the provider's catalog of reports. Only then will users with the appropriate role see the report as requestable from the third-party record, and the resulting report can be attached to the third party for use in assessments and reviews.
All Assessment Metrics in a Metric Category are scored, rolled up, and assigned what score range?
Options:
0-5
0-10
0-20
0-100
Answer:
DExplanation:
Within a metric category, each assessment metric is scored, and the individual scores are rolled up into a category score expressed on a normalized scale of 0 to 100. The same scale applies to the scores of categories and to the resulting assessment and risk scores. A common range allows scores from different categories and assessments to be combined, compared and measured against thresholds.
Narrower ranges such as 0 to 5, 0 to 10 or 0 to 20 are not the convention for the roll-up. Individual metrics may have their own response weightings, but they are normalized when aggregated, which makes the category result comparable regardless of the number of questions or the weights of each.
The practical significance is in rating configuration. Risk rating thresholds, for example the boundaries separating low, moderate and high risk, are defined against the normalized scale, and category weights determine how each category contributes to the assessment score. Misunderstanding the scale leads to poorly set thresholds and ratings that do not reflect the organization's tolerance.
When designing questionnaires, assign metric weights thoughtfully, review category weights for balance, and test sample responses to confirm that the resulting scores and ratings behave as intended before releasing the template for production use.
Which types of requests may an employee make when selecting the Request third-party risk due diligence option? Choose four
Options:
Duplicate an engagement
Cancel an engagement
Offboard an engagement with due diligence
Reassess an existing engagement for contract renewal
Reassess an existing engagement
Onboard a new engagement
Answer:
C, D, E, FExplanation:
The Request third-party risk due diligence option lets an employee submit a structured request that starts due diligence on a third party or engagement. The supported request types are onboarding a new engagement, reassessing an existing engagement, reassessing an existing engagement for contract renewal, and offboarding an engagement with due diligence. Each type determines the questions the requester answers and the assessment activity that follows.
Duplicating an engagement is a record-management operation and cancelling an engagement is a lifecycle action; neither requests due diligence, so both are excluded. Offboarding without due diligence also exists as a lifecycle path, but it is not offered here because the selection is specific to due-diligence requests.
The value of this design lies in its consistency. A business user who wants to engage a supplier does not need to understand questionnaires or tiering; the request captures context such as the engagement, the products or services involved, and the business owner, and the risk team then drives the assessment. Reassessment variants allow existing relationships to be re-evaluated at renewal without creating duplicate third-party records.
What can be stated about the number of third-party contacts?
Options:
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
Answer:
BExplanation:
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.
Which create actions can be initiated from the Rule Actions tab of a Provider-Based Submission Rule? Choose three
Options:
Create assessment
Create issue
Create third party
Create primary contact
Create task
Create recipient
Answer:
A, B, EExplanation:
A Provider-Based Submission Rule evaluates incoming data from a risk intelligence provider and responds to defined conditions. The Rule Actions tab lets an administrator specify the records the rule will generate when its conditions are satisfied. The create actions available are Create assessment, Create issue and Create task, each applied to the third parties identified by the rule.
These three actions correspond to the principal work records of the application: an assessment to gather evidence, an issue to track a concern needing remediation, and a task to track follow-up work. Together they allow an externally sourced signal, such as a deterioration in a provider score, to trigger a proportionate internal response without manual intervention.
Creating a third party or a primary contact is not offered because the rule operates on third parties that already exist; it acts on them and does not register them. A recipient is not a work record either. Recipients define who is notified and are configured as notification targets rather than created as an action outcome.
During implementation, test each rule with representative provider payloads to confirm that the intended third party is matched and that duplicate assessments or issues are not generated on repeated submissions.
Which table contains the third-party records?
Options:
Company [core_company]
Department [cmn_department]
User [sys_user]
Vendor [sn_vdr_vendor]
Answer:
AExplanation:
Third-party records in Third-party Risk Management are held in the Company table [core_company]. The application builds on the platform's existing company data model, where an organization flagged as a third party carries the attributes the application needs, such as tier, risk rating and related contacts. This avoids a parallel data store and lets other ServiceNow applications that reference companies, including procurement and contract management, work with the same record.
The Department table [cmn_department] represents an internal organizational unit and has no relationship to external parties. The User table [sys_user] holds individual people; third-party contacts are people who extend this table, but the third party itself is the organization, not the individual. A table named sn_vdr_vendor is not the store for third-party records and should not be used as the target for imports or reports.
For implementation, this has direct consequences for data loading. Import sets and integrations with supplier management systems should target the Company table, with the third-party indicator set and parent relationships populated where subsidiaries exist, so that tiering, assessment generation and rollup scoring behave correctly.
Which application enables you to define multiple approval levels based on business-rule definitions?
Options:
Risk Approver Configuration
Approval Configurator
Approver Levels
TPRM Approvals
Answer:
BExplanation:
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.
At what point will the tiering value be updated on the third-party record?
Options:
When the inherent risk assessment record state is Responses Received
When all inherent risk assessments have been completed
When the inherent risk assessment record state is closed
When all inherent risk assessments have been sent
Answer:
CExplanation:
Tiering is driven by an inherent risk assessment completed for the third party. The calculated tier is written back to the third-party record only when the inherent risk assessment reaches the Closed state. Closing the record is the point at which the outcome is formally accepted, and therefore the point at which the tier field is updated.
Earlier states do not trigger the update. When the record is in Responses Received, the answers are in but still subject to review, so the result is provisional. Updating at that point could propagate an unvalidated value into assignment rules that depend on tier. Completion of all inherent risk assessments is not the condition either, because the update operates on the individual assessment record, not on the aggregate of every assessment issued. Sending the assessments has no relationship to the outcome, as no result exists until responses are scored.
This sequence matters operationally because tier changes can launch downstream assessments through assignment rules. Delaying the update until closure ensures that automation acts only on approved values. Assessors who want a tier to take effect must therefore close the inherent risk assessment instead of leaving it in a review state.
How does ServiceNow enable companies to manage third parties without relying on emails and spreadsheets?
Options:
Third-party Platform
Primary Third-party
Third-party Manager Workspace
Third-party Portal
Answer:
CExplanation:
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.
If a Third-party Risk Issue is intended for internal use only, which states can be skipped? Choose two
Options:
Analyze
Finalize with Third-party
New
Submitted to Third-party
Answer:
B, DExplanation:
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.
Which element-classification values are included in the ServiceNow baseline for Third-party Risk Management? Choose three
Options:
Service
Principal
Product
Manufacturer
Facility
Answer:
A, C, EExplanation:
The baseline element classifications delivered with Third-party Risk Management are Service, Product and Facility. A classification describes the nature of what a third party's dependency provides, and it determines the scoring model and the element questionnaires applied. The sample content accordingly includes questionnaires directed at products and at facilities, reflecting the different risk questions each category raises: a facility is assessed for physical security and continuity, whereas a product is assessed for security of the product itself.
Principal and Manufacturer are not baseline classifications. They may describe roles in a supply relationship, but they are not delivered values, and an organization wishing to use them would have to create them as additional classifications.
Because classifications are reusable, defining them once allows many elements to share the same scoring model, which promotes consistent assessment. When adding custom classifications, define the associated component definitions and criteria so that the new classification produces meaningful scores. Excessive custom classifications fragment reporting, so organizations should first test whether the three baseline values adequately describe their dependencies.