SISIS
Free SISIS practice questions
10 questions from our SISIS practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Incident Management
During discovery workshops, a customer says agents should be able to raise a major incident candidate, but only a designated group should accept it and run the major incident process. Which configuration supports this with the least customisation?
- ARaise the Priority 1 threshold in the priority lookup so only that one group can set Critical priority
- BAdd a Major checkbox to the incident form and create a UI policy that limits who can tick it
- CCreate a separate major incident table that extends Task and restrict it with access controls
- DActivate Major Incident Management and grant that group the major_incident_manager role Correct answer
Answer and explanation: Major Incident Management provides the proposal and acceptance flow, where users propose candidates and members with the major_incident_manager role accept or reject them, so it meets the need without custom code. A custom checkbox with a UI policy recreates functionality that already exists and lacks the workbench and communication features. Priority lookups calculate priority and cannot restrict who promotes a major incident. A custom table would split major incidents from standard incident reporting and SLAs.
Question 2 of 10, Incident Management
A network outage generates 40 incidents from different callers. The service desk wants every caller to receive updates when the agent works on one master record, and wants all of them resolved together. What is the recommended approach?
- ACreate a problem record and add the 40 incidents to its related incidents list
- BCreate a change request and add all 40 incidents to its Incidents Caused by Change list
- COpen one incident task per caller under the first incident and close the other incidents
- DRelate the 40 incidents as child incidents of one parent incident and work the parent Correct answer
Answer and explanation: Parent and child incidents are designed for this: comments and work notes on the parent propagate to children, and resolving the parent resolves the children. Linking incidents to a problem supports root cause work, but resolving the problem does not drive caller updates in the same way. The Incidents Caused by Change list is for incidents that a change caused, not for grouping an outage. Incident tasks divide work among teams and would leave the other callers without their own records.
Question 3 of 10, Incident Management
A service desk wants the major incident team to send regular stakeholder updates by email and SMS during a P1 outage, tracked as tasks on the incident. Which application supports this?
- AA scheduled report emailed hourly to a distribution list of the stakeholders
- BNotification preferences configured individually by each affected stakeholder
- CIncident Communication Management with communication plans and tasks Correct answer
- DService Level Management with breach warnings on the major incident record
Answer and explanation: Incident Communication Management attaches communication plans to incidents and creates communication tasks for timed updates through channels such as email and SMS. Notification preferences let users control what they receive but do not plan or track stakeholder updates. SLA breach warnings notify the people who own the work about timing, not stakeholders about status. A scheduled report sends data on a timer and has no task tracking or message content tailored to the outage.
Question 4 of 10, Change Management
A team performs the same low-risk firewall rule update every week and wants it pre-approved. How should this be set up?
- AClone last week's Normal change each time so its approvals copy over to the new record
- BCreate an Emergency change each week because it skips the Assess state and moves faster
- CSubmit a Standard Change Template proposal so an approved template is published in the catalog Correct answer
- DCreate a Normal change each week and ask the CAB manager to approve it by email in advance of the work
Answer and explanation: A Standard Change Template proposal is reviewed and approved once, and the published template lets requesters raise pre-approved standard changes from the Standard Change Catalog. Weekly Normal changes keep the full approval cycle and email approvals bypass the audit trail. Emergency changes are for urgent unplanned work and misusing them distorts reporting. Cloning a Normal change does not carry over approvals; the new record must be approved again.
Question 5 of 10, Change Management
A customer wants a Cloud Infrastructure change process with its own states and transition rules, separate from Normal changes, without scripting the state model. What should the specialist configure?
- AA copy of the Normal change workflow with renamed activities
- BA new change model with its own states and state transitions Correct answer
- CA new table extending change_request with a custom state field
- DA new choice value on the Type field plus client scripts for states
Answer and explanation: Change models let administrators define states, transitions and transition conditions for a change process without code, and they are the supported way to add new change processes. A new Type choice with client scripts only affects the form and leaves server-side transitions unmanaged. Copying a legacy workflow does not create a new state model and adds maintenance. A new extended table fragments change reporting and creates upgrade debt.
Question 6 of 10, Change Management
A customer wants change risk calculated from a questionnaire that the requester completes, combined with automated risk conditions. Which capability provides this?
- AChange risk assessment questionnaires combined with the risk calculator Correct answer
- BA record producer that sets Risk from the answers to its variables
- CA survey sent to the requester after the change has been closed
- DA Normal change workflow that asks the change manager to type the risk
Answer and explanation: Change risk assessments present a questionnaire whose scored answers set risk, and they can be combined with the risk calculator's conditions to produce the final value. A record producer captures data at creation but has no scoring model and is not used for later reassessment. Asking the change manager to enter risk ignores the requester's input and is not repeatable. A survey after closure cannot influence approval routing.
Question 7 of 10, Service Catalog and Request Management
A catalog item should be visible to all users in the Finance department except contractors. How should user criteria be applied?
- AAvailable For: Finance department; Not Available For: contractor criteria Correct answer
- BNot Available For: every department except Finance, with no Available For value
- CAvailable For: contractor criteria; Not Available For: Finance department
- DAvailable For: Finance department and contractor criteria in one Match All record
Answer and explanation: Available For grants access to Finance and Not Available For removes contractors, and Not Available For takes precedence over Available For. Swapping the lists would expose the item to contractors only. Match All on one record would require users to be both Finance and contractors, granting access to exactly the wrong group. Listing every other department is hard to maintain and still lets Finance contractors see the item.
Question 8 of 10, Service Catalog and Request Management
A catalog item must show a Justification field only when the requester chooses a premium laptop model. Which configuration should be used without writing script?
- AA business rule that hides the variable on insert
- BAn access control on the Justification variable
- CA UI policy on the sc_req_item table form layout
- DA catalog UI policy conditioned on the model Correct answer
Answer and explanation: Catalog UI policies control visibility, mandatory and read-only behaviour of variables based on other variable values, without scripting. A regular UI policy on sc_req_item applies to the requested item form fields, not item variables while ordering. A business rule runs on the server after submission and cannot hide a field in the form. Access controls restrict data by role, not by the value of another variable.
Question 9 of 10, Service Catalog and Request Management. Choose 2.
A record producer for HR address changes must set fields on the target record from variables. Which two approaches are supported? (Choose two.)
- AUse a catalog client script onLoad to write to the target record
- BSet fields in the record producer script using the current object Correct answer
- CAdd a UI policy on the target table that reads catalog variables
- DSelect Map to field on the variable and choose the target field Correct answer
- ECreate a business rule on sc_req_item to copy values to the target
Answer and explanation: Variables can be mapped directly with Map to field, and the record producer script can set fields on current using producer values. UI policies on the target table run on forms and cannot read submitted catalog variables. Client scripts run in the browser before submission and cannot write to the produced record. Record producers do not create requested items, so a business rule on sc_req_item never runs.
Question 10 of 10, Problem Management
Which state sequence does a problem follow in the base Problem Management state model?
- ANew, Assess, Authorize, Scheduled, Implement, Review, Closed, Canceled
- BDraft, Review, Published, Retired, with a Known Error flag
- CNew, Assess, Root Cause Analysis, Fix in Progress, Resolved, Closed Correct answer
- DNew, In Progress, On Hold, Resolved, Closed, Canceled
Answer and explanation: The base problem state model runs New, Assess, Root Cause Analysis, Fix in Progress, Resolved and Closed. New, In Progress, On Hold and Resolved belong to incidents. Assess, Authorize, Scheduled and Implement are Normal change states. Draft, Review, Published and Retired describe the knowledge article lifecycle.