Which table contains the third-party records?
Company [core_company]
Department [cmn_department]
User [sys_user]
Vendor [sn_vdr_vendor]
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.
Third-party contacts are stored in the vm_vdr_contact table, which table does it extend?
sys_user
task
ext_user
core_company
The third-party contact table, vm_vdr_contact, extends the User table [sys_user]. By inheriting from sys_user, a contact receives the standard user attributes, including name, email address and credentials, as well as the capabilities of the platform's authentication and notification services. This is what allows a contact to log in to the Third-party Portal and to receive email notifications from the application.
The task table is a work item parent and has no relevance to person records. The ext_user table is not the parent of contacts. The Company table [core_company] holds organizations; the third-party record is held there, and the contact relates to it through a reference field, not by extending it.
This inheritance has implementation consequences. Contacts are subject to user-level controls such as access control rules, roles and, where configured, restrictions on internal functionality, so the integrity of their role assignments is essential to keeping them confined to the portal. Importing contacts also follows the user data model, so email addresses must be unique and valid, and administrators should confirm that the contact is linked to the correct third party before invitations are sent.
At what point will the tiering value be updated on the third-party record?
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
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.
What is the definition of “Risk Management”?
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
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.
What is the purpose of ServiceNow third-party risk engagements?
They give a third-party risk manager a way of scheduling workshops with the customer to help the third party become compliant
They give a way for a third-party risk manager to assess risks and measure third-party CSAT performance
They give a third-party risk manager a way to assess risks at the products or services level
They give a third-party risk manager a way to assess the validity of the third-party assessment responses
Third-party engagements define the relationship between the organization and a third party in terms of the products or services provided. Their purpose is to allow a risk manager to assess risk at the product or service level, not merely at the level of the company. A single third party may supply a low-risk service and a critical one, and an engagement-level view prevents the critical service from being obscured by an overall rating.
Engagements are not a mechanism for scheduling workshops with the customer, which is unrelated to the risk model. They do not measure customer satisfaction performance; CSAT is a service quality measure outside the scope of risk assessment. They are also not a means of validating the truthfulness of assessment responses. Validation is the responsibility of the assessor, who reviews responses and evidence.
Engagements also link to elements and feed the rollup of risk rating for the third party. Due diligence requests, such as onboarding or renewal reassessment, are made against engagements, so they sit at the center of the lifecycle. During configuration, define engagements for each distinct service or product that carries separate risk, and associate the business owner and the relevant elements so assessments and reporting reflect the real structure of the relationship.
Under what circumstances should a Third-party Risk Issue be created? Choose three
When identifying a risk to a business
When the third party does not include documentation required as part of an assessment
When a response to a question in the risk assessment is not satisfactory
When there is more than one third-party contact submitting responses
When there are items that require additional follow-up
A Third-party Risk Issue records a concern that requires remediation or follow-up in the context of an assessment or engagement. Issues are warranted in three situations from the list: when the third party fails to supply documentation that the assessment required, when a response to a risk assessment question is unsatisfactory, and when items remain that require additional follow-up.
Each of these produces an identifiable gap tied to an assessment artifact, which allows the issue to be assigned, tracked, shared with the third party through the portal where appropriate, and closed with evidence. Some issues are generated automatically from incorrect answers, while others are raised manually by the assessor during review.
Identifying a risk to the business in general terms is a risk management activity and is better represented as a risk record in the risk framework; an issue is narrower and attaches to a specific third-party finding. Having more than one contact submit responses is an operational circumstance that does not itself indicate a deficiency, so it does not justify an issue.
Careful use of issues keeps remediation metrics meaningful, since each issue then reflects a genuine and actionable shortfall.
Which actions are required before a risk intelligence report can be requested? Choose two
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.
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.
Which actions could affect the third party's Risk Assessment rating? Choose three
Answering one or more questions incorrectly
Leaving answers blank
Omitting documentation
Spelling errors
Reassigning a questionnaire to a contact
The risk rating of a third-party assessment is computed from the scored outcomes of its questionnaires and document requests, rolled up through metric categories and weighted by their configured importance. Any behavior by the respondent that changes those scored outcomes can therefore move the rating.
Answering one or more questions incorrectly is the most direct case, since an unfavorable answer earns a lower or negative score against the metric. Leaving answers blank denies the metric any positive score, and an unanswered question is treated as a gap in the evidence, so it also depresses the result. Omitting requested documentation lowers the document request score in the same manner, because the assessment evaluates the evidence supplied, not merely the questionnaire.
Spelling errors in free-text responses have no bearing on scoring, as scoring is driven by selected choices and scripted evaluation rather than orthographic quality. Reassigning a questionnaire to a different contact alters only who completes it; the metrics, weightings and scoring logic remain unchanged, so no rating effect follows from the reassignment itself.
This is why category weights and document request scoring deserve attention during design.
Which parties can change the password for the third-party contact? Choose two
Third-party Contract Relationship Manager
Third-party contact via the Forgot Password link
sys_admin
Third-party Risk Reviewer
Third-party contacts authenticate to the Third-party Portal with credentials stored on their contact record. Two parties are able to change that password. The contact may reset it independently through the Forgot Password link on the portal login page, which is the intended self-service route. A user holding the sys_admin role can also manage the credential, because administrators have authority over user accounts across the platform.
The Third-party Contract Relationship Manager role governs contract and relationship activities and carries no credential-management capability. Likewise the Third-party Risk Reviewer role is oriented toward reviewing assessment results and does not extend to managing user passwords.
This allocation reflects a sound security principle: credential control is limited to the account holder and to platform administration, so business roles cannot alter external access. For support scenarios, a contact who cannot complete the reset process should be referred to an administrator rather than to an assessor or relationship manager.
Administrators should also confirm that the contact record has a valid email address, since the self-service reset relies on it to deliver the reset instructions.
Which functions can be carried out in the Third-party Portal? Choose two
Manage assessment deadlines
Complete assessments
General project management
Host web meetings
Contacts use the Third-party Portal to complete assessments and to manage assessment deadlines. Completing assessments encompasses answering questionnaires, uploading requested documents and submitting responses. Managing deadlines is supported because the portal displays outstanding items with their due dates, which lets the contact prioritize work and respond before reminders escalate.
The portal does not provide general project management. Its scope is limited to risk assessment interactions, namely questionnaires, document requests, issues and tasks assigned by the customer, and it offers no planning, scheduling or resource tools beyond those items. Hosting web meetings is a function of conferencing applications and is outside the capabilities of the portal. Where discussion is required, the interaction occurs through comments and responses recorded on the relevant record, which has the advantage of being retained with the assessment.
For implementation, communicate to third-party contacts exactly what the portal is for. Setting this expectation reduces support requests that stem from contacts seeking features it was never designed to provide, and it focuses the interaction on completing the assessment within the due date.
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 default value is appended to an instance URL to access the scoped Third-party Portal, according to the sn_vdr_risk_asmt.vendor_portal_endpoint system property?
/tpp
/tpvp
/svp
/svdp
The scoped Third-party Portal is reached by appending the /svdp endpoint to the instance URL. The value is defined by the system property sn_vdr_risk_asmt.vendor_portal_endpoint, and its default of svdp corresponds to the application scope for the portal. A contact would therefore browse to the instance address followed by /svdp to reach the login and landing page.
The other values are not baseline endpoints. The abbreviations /tpp and /tpvp resemble plausible third-party portal names but are not defined by default, and /svp omits the d that identifies the vendor-derived scope name. Using a nonexistent suffix returns a page-not-found result for the contact, which commonly generates support requests after go-live.
Administrators may change the property to align the URL with corporate naming conventions, but any change must be communicated to contacts and reflected in notification templates that embed the portal link. Because the portal URL appears in invitations and reminders, the property should be finalized before large-scale invitations are issued.
When troubleshooting access, verify the property value first, then the contact's account status and role assignment.
Which application do you navigate to in order to customize the Third-party Portal?
Service Portal Home
Service Portal
Now Experience Framework
Flow Designer
The Third-party Portal is built on Service Portal, so its pages, widgets, branding and layout are customized through the Service Portal application. An administrator opens Service Portal and works with the portal record, its pages and the widgets it contains. Typical changes include adjusting the logo and theme, modifying the home page layout, and adding or configuring widgets that present assessments, issues and tasks to the contact.
Service Portal Home is a landing module and not the application used to configure a specific portal. The Now Experience Framework is the technology behind workspaces and newer experiences and is not used for this portal. Flow Designer automates processes and would be useful for notification or approval logic, but it has no role in presenting or branding portal pages.
When customizing, work in the scoped application that owns the portal and avoid editing baseline widgets directly. Cloning a widget preserves the ability to receive upgrades on the original while allowing local changes, and updates should be captured in update sets for promotion between instances. Retesting with a contact account confirms that role-based access still behaves correctly.
TESTED 21 Nov 2026
Copyright © 2014-2026 DumpsTool. All Rights Reserved