Sign in
Home/ServiceNow/Risk and Compliance (CIS-RC)/Free questions

ServiceNow Certified Implementation Specialist - Risk and Compliance (CIS-RC) — Free Practice Questions

10 free sample questions from a bank of 296, with the correct answers and explanations. No signup required — start practising right now.

1Which of the following tables exist within the GRC: Profiles application scope? (Choose three.)
  • Document
  • Policy
  • Risk
  • Content
  • Indicator
Answer: A, D, E

The short version

ADE — Profiles scope holds Document, Content, and Indicator. Policy and Risk live in their own apps, not Profiles. The three content-centric tables carry the profile documentation model.

Key concepts in this question

  • GRC Profiles scope: sn_grc namespace area for profiling content and measurement setup.
  • Document table: sn_grc_document stores authority-related documentation objects.
  • Content table: sn_grc_content is the parent for control objectives, citations, and statements.
  • Indicator table: sn_grc_indicator holds continuous-monitoring measurement definitions.
  • App separation: Policy and Risk tables belong to Policy and Risk scopes, not Profiles.

Why ADE is correct

ServiceNow GRC separates applications by scope, and Profiles provides the shared content layer of documents, library content, and indicators used across compliance and risk. Document, Content, and Indicator therefore exist within the Profiles scope as settled keys A, D, and E state. Policy and Risk are distinct application tables outside that scope, which is why they are excluded despite their GRC adjacency.

Why the others are wrong

  • B. Policy belongs to the Policy and Compliance scope, not the Profiles scope.
  • C. Risk belongs to the Risk Management scope, not the Profiles content layer.

CIS-RC exam tip

Profiles equals Document plus Content plus Indicator, keep Policy and Risk out.

2There is a direct relationship between Entity Class and Entity Type when:
  • They have the same Entity Types
  • There is no direct relationship
  • They have the same Entities
  • They leverage the same reporting
Answer: B

The short version

B — Entity Class and Entity Type have no direct relationship. Classes group entities for assessment structure while types drive control generation. The platform keeps those dimensions independent.

Key concepts in this question

  • Entity Class: grouping construct for entities used in advanced and object-based assessments.
  • Entity Type: dimension applied to control objectives to generate entity-scoped controls.
  • Relationship design: ServiceNow models class and type as separate axes without a direct reference.
  • Reporting implication: shared reports join through entities and controls, not a class-type link.
  • Textbook anchor: course material explicitly states no direct relationship exists.

Why B is correct

Entity Classes organize which entities fall into an assessment population, while Entity Types determine how control objectives expand into per-entity controls. Because they serve different modeling purposes, the schema provides no direct reference between the two tables. Settled key B therefore states the platform truth that there is no direct relationship, rather than a shared-type or shared-entity link.

Why the others are wrong

  • A. Same Entity Types would require a direct link that the schema does not provide.
  • C. Same Entities describes assessment population overlap, not a class-type relationship.
  • D. Shared reporting is achieved through downstream joins, not a direct class-type reference.

CIS-RC exam tip

Class groups who is assessed, Type drives controls, no direct link between them.

3Which of the following are Policy Lifecycle states included in the ServiceNow baseline? (Choose two.)
  • Expired
  • Review
  • Acknowledged
  • Published
  • Verified
Answer: B, D

The short version

BD — Baseline Policy lifecycle uses Review and Published. Draft leads to Review, then approval, then Published, then Retired. Expired, Acknowledged, and Verified are not lifecycle states.

Key concepts in this question

  • Policy lifecycle path: Draft, Review, Awaiting Approval, Published, Retired in baseline.
  • Review purpose: owner and stakeholder examination before approval routing.
  • Published meaning: approved and active policy available for acknowledgement and compliance.
  • Retired closure: end-of-life state after Published, not Expired.
  • Distractor states: acknowledgement and verification describe downstream activities, not lifecycle.

Why BD is correct

The baseline Policy lifecycle moves a policy from Draft into Review for feedback, then through approval into Published where it becomes effective. Settled keys B for Review and D for Published name the two states in the option set that sit on that baseline path. The other listed values describe acknowledgement activity or non-baseline labels and never appear as lifecycle states.

Why the others are wrong

  • A. Expired is not a baseline Policy lifecycle state, Retired is the terminal state.
  • C. Acknowledged describes policy acknowledgement instances, not the policy record lifecycle.
  • E. Verified is not part of the baseline Draft to Retired lifecycle chain.

CIS-RC exam tip

Memorize Draft Review Awaiting Approval Published Retired in order.

4Which of the following extends from Content Table? (Choose two.)
  • Citation
  • Policy
  • Control Objective
  • Authority Document
Answer: A, C

The short version

AC — Citation and Control Objective extend Content. Policy and Authority Document sit elsewhere in the model. The two library children inherit Content fields for compliance mapping.

Key concepts in this question

  • Content parent: sn_grc_content supplies common library fields for compliance artifacts.
  • Citation child: excerpt from an authority document mapped to control objectives.
  • Control Objective child: compliance goal that generates controls when combined with entity types.
  • Policy separation: policy records live in their own hierarchy, not under Content.
  • Authority Document separation: authority files are sources cited by citations, not Content children.

Why AC is correct

In the GRC data model, both Citation and Control Objective are modeled as extensions of the Content table so they share library attributes and can participate in citation-to-objective mapping. Settled keys A for Citation and C for Control Objective therefore name the two tables that inherit from Content. Policy and Authority Document belong to different hierarchies and do not extend Content.

Why the others are wrong

  • B. Policy extends the policy hierarchy rather than the Content library table.
  • D. Authority Document is a source object above citations, not a Content child.

CIS-RC exam tip

Content children are Citation and Control Objective, plus Risk Statement nearby.

5Which tables extend from the Task table? (Choose two.)
  • Risk Framework
  • Risk Response Task
  • Risk Statement
  • Risk Event
  • Risk
Answer: B, D

The short version

BD — Risk Response Task and Risk Event extend Task. Framework, Statement, and Risk are business objects, not workflow tasks. The two operational records need assignment, state, and SLA behavior from Task.

Key concepts in this question

  • Task parent value: assignment, work notes, state, and SLA engine for operational work.
  • Risk Response Task: remediation work item created from risk response handling.
  • Risk Event: occurrence record requiring triage and task-style workflow.
  • Non-task objects: framework, statement, and risk define structure rather than assignable work.
  • SLA relevance: response tasks and events carry timelines, so Task inheritance fits.

Why BD is correct

Risk Response Task represents accountable remediation effort with assignees and states, and Risk Event represents an occurrence needing investigation, so both are modeled as Task extensions to gain workflow capability. Settled keys B and D name exactly those two Task children. Framework, Statement, and Risk remain analytical objects without direct Task inheritance.

Why the others are wrong

  • A. Risk Framework defines methodology structure, not assignable task work.
  • C. Risk Statement extends Content for library reuse, not Task for assignment.
  • E. Risk is the assessed business object itself, not a Task-based work item.

CIS-RC exam tip

If it needs assignee plus SLA in Risk, it likely extends Task.

6What are some of the drivers for customers to get the GRC suite of applications? (Choose four.)
  • They would like efficiency
  • They would like integrated reporting
  • They would like transparency
  • They would like automated customer service
  • They would like custom websites
  • They would like workflow driven processes
Answer: A, B

The short version

AB — Efficiency and integrated reporting drive GRC purchase. Customers adopt the suite to replace manual spreadsheets and siloed reports. Transparency and workflow help, but the banked drivers are efficiency plus reporting.

Key concepts in this question

  • Efficiency driver: automated assessments, attestations, and evidence collection reduce manual effort.
  • Integrated reporting: single data model across risk, policy, audit, and compliance for roll-ups.
  • Workflow nuance: workflow-driven processes matter, but the banked pair emphasizes outcome value.
  • Distractor services: customer service automation and custom websites are not GRC purchase drivers.
  • Bank consensus: voting and material support the AB pair for this row.

Why AB is correct

GRC buyers justify the suite by cutting manual governance effort and gaining a unified view of posture across frameworks. Efficiency captures faster cycles and less spreadsheet work, while integrated reporting captures cross-application dashboards and regulator-ready views. Settled keys A and B together express the core business case that appears in ServiceNow value messaging.

Why the others are wrong

  • C. Transparency is a benefit but is not one of the two banked primary drivers here.
  • D. Automated customer service describes CSM, not GRC suite motivation.
  • E. Custom websites describe portal CMS value, unrelated to GRC drivers.
  • F. Workflow-driven processes support the outcome but the banked key favors reporting as the second driver.

CIS-RC exam tip

Sell GRC with efficiency plus one reporting view, not websites or CSM.

7The Calculated Risk Score utilizes data from the Inherent and Residual Risk scores to determine an adjusted ALE and Score. What other data drives the adjustments?
  • Audit Scores
  • Attestation Score
  • Configuration Test Score
  • Control and Indicator Failure Factors
Answer: D

The short version

D — Control and Indicator failures adjust the calculated score. Inherent and residual give the baseline ALE, then real-world failure factors tune it. Audit, attestation, and config scores do not drive that formula.

Key concepts in this question

  • Inherent vs residual: baseline exposure before and after controls in the quantitative method.
  • Annualized Loss Expectancy: monetary exposure adjusted by effectiveness evidence.
  • Failure-factor average: indicator failure plus control failure divided by two forms the adjustment.
  • Excluded scores: audit and attestation inform posture but not this calculated adjustment.
  • Vendor formula: material cites the averaged failure-factor equation directly.

Why D is correct

The calculated risk score starts from inherent and residual inputs, then applies an adjustment reflecting how controls and indicators actually perform. Control failure factor plus indicator failure factor averaged together raises or lowers the adjusted ALE and score. Settled key D names that exact adjustment source, which is why audit, attestation, and configuration test options are incorrect for this formula.

Why the others are wrong

  • A. Audit scores support assurance but do not enter the calculated-score failure average.
  • B. Attestation scores show acknowledgement, not control-performance adjustment.
  • C. Configuration test scores feed indicators indirectly, but the driver is the combined failure factor.

CIS-RC exam tip

Calculated score adjustment equals control plus indicator failures over two.

8The advanced planning capability enables integration of Advanced Audit with PPM. If the advanced planning capability is selected when the audit plan is created, what extra related lists display on the engagement record in addition to the related lists displayed with basic planning? (Choose three.)
  • Time card
  • Resource plan
  • Entities
  • Cost plan
  • Milestones
Answer: A, B, D

The short version

ABD — Advanced planning adds Time card, Resource plan, and Cost plan. Basic planning tracks audit tasks alone. PPM integration brings staffing and spend governance to the engagement.

Key concepts in this question

  • Advanced planning toggle: enables PPM artifacts on the audit engagement record.
  • Time card list: captures actual effort against audit work for variance tracking.
  • Resource plan: allocates people and capacity across engagement phases.
  • Cost plan: budgets and tracks spend alongside resource effort.
  • Non-PPM lists: entities and milestones belong to basic audit scope, not extra PPM lists.

Why ABD is correct

When advanced planning is selected at audit plan creation, the engagement gains related lists sourced from PPM: time cards for actuals, resource plans for allocations, and cost plans for financials. Settled keys A, B, and D name those three PPM additions documented in ServiceNow docs. Entities and milestones already appear or belong elsewhere, so they are not the extra PPM lists.

Why the others are wrong

  • C. Entities support audit scoping in basic planning, not an advanced PPM addition.
  • E. Milestones track phase gates without requiring PPM resource and cost integration.

CIS-RC exam tip

Advanced audit planning equals time plus resources plus costs from PPM.

9Which of the following roles can create issues? (Choose three.)
  • Risk Reader
  • Compliance Reader
  • External Auditor
  • Compliance User
  • Audit User
  • Risk Manager
Answer: D, E, F

The short version

DEF — Compliance User, Audit User, and Risk Manager create issues. Reader and external auditor roles are read-only or narrow. The three user and manager roles hold create rights on issues.

Key concepts in this question

  • Issue creation right: ability to raise an issue from compliance, audit, or risk contexts.
  • User vs reader: user roles transact, reader roles only view records.
  • Manager inclusion: risk manager inherits creation plus management capability.
  • External auditor limit: external participants review evidence without issue authorship.
  • Doc anchor: create-issue guidance lists the three creator roles.

Why DEF is correct

Issues are operational records that need accountable owners in each GRC line, so creation is granted to Compliance User, Audit User, and Risk Manager. Those identities work issues day to day and therefore need authorship. Reader roles and the external auditor lack that transactional right by design, which is why settled keys D, E, and F form the correct trio.

Why the others are wrong

  • A. Risk Reader can view risk data but cannot author issues.
  • B. Compliance Reader is read-only and cannot create issues.
  • C. External Auditor reviews and responds, but does not hold internal issue-create rights.

CIS-RC exam tip

Readers read, users plus managers create issues across GRC.

10What would you use in order to accommodate a customer’s unique process around policy approvals? For example, each policy needs a second layer of approval.
  • Create a new field and create notifications
  • Add a new related list to keep track of who has already approved it and who hasn’t approved yet
  • Add a UI Action to track who the stakeholders are
  • Create a new workflow in the workflow editor
Answer: D

The short version

D — Unique approval chains need a new workflow. Fields, lists, and UI actions track data but do not route approvals. A workflow defines the extra approval layer and its conditions.

Key concepts in this question

  • Second-layer approval: policy needs sequential or parallel approval beyond baseline.
  • Workflow engine: controls states, approvals, timers, and branching for policy records.
  • Field insufficiency: new fields store data without enforcing approval order.
  • Related-list insufficiency: tracking who approved does not route to the next approver.
  • UI Action insufficiency: buttons trigger logic but do not model multi-step approval flow.

Why D is correct

Accommodating a customer-specific process such as two layers of policy approval requires changing how the record moves between states and who must approve at each step. Creating a new workflow in the workflow editor, as settled key D states, provides approval activities, conditions, and escalations to enforce that chain. Field, list, and UI tweaks alone cannot orchestrate the required routing.

Why the others are wrong

  • A. New field plus notifications records data and pings people without enforcing approval sequence.
  • B. Related list tracks approval status but does not route work to the second approver.
  • C. UI Action can surface stakeholders yet lacks stateful approval orchestration.

CIS-RC exam tip

Custom approval layers mean build or edit the workflow, not just fields.

Want the full bank of 296 questions for ServiceNow Certified Implementation Specialist - Risk and Compliance (CIS-RC)? See all practice exams.