Theknowledge_adminrole in ServiceNow provides the ability to manage multiple knowledge bases. This includescreating, editing, publishing, retiring, and configuring settingsfor knowledge bases and articles. #Whyknowledge_admin? Manages all knowledge basesin the instance. Has permissions tocreate, edit, and deleteknowledge bases. Can assignknowledge base-specific rolessuch asknowledge_managerorknowledge_editorto users. Controlsworkflows, article approvals, and permissionsfor knowledge management. #Incorrect Options Explained: A). knowledge_base_admin- This is not a valid ServiceNow role. B). kb_admin- This is not an officially recognized role in ServiceNow. C). sn_kb_admin- This role does not exist in thedefaultServiceNow configuration. The correct role isknowledge_admin. #Reference: Knowledge Management Roles - ServiceNow Docs Managing Knowledge Bases in ServiceNow
CSA Exam Question 137
Tables may be set up with Many to Many relationships. What is a classic example of a scenario where the tables would have many to many relationships?
Correct Answer: B
InServiceNow, aMany-to-Many (M2M) relationshipexists whenrecords in one tablecan be associated withmultiple records in another table, and vice versa. A classic example of anM2M relationshipis: #Vendors can sell multiple products #Products can be sold by multiple vendors Vendors oftensell multiple productsacross different categories. A single product can beavailable from multiple vendors. This requires anintermediary (join) tableto track the many-to-many relationship. A). Requests & Items Incorrectbecause eachRequest (REQ#)can havemultiple requested items (RITM#), but anitem does not belong to multiple requests. This is aone-to-many (1:M) relationship. C). Tasks & Workflows Incorrectbecause workflows are associatedat an individual task level, and while multiple workflows may be involved, they do not create a trueM2M relationship. D). Configuration Items & Classes Incorrectbecause a Configuration Item (CI)belongs to only one class, making this aone-to-many relationship, not M2M. Reference:ServiceNow CSA Documentation - Many-to-Many Relationships ServiceNow Product Documentation - Relationship Types & Example Use Cases(https://docs.servicenow. com) Final answer: B. Vendors can sell multiple products; and products can be sold by multiple vendors.
CSA Exam Question 138
A new Service Desk employee in Latin America complains that the create dates and times are incorrect on their Incident list. What would you suggest to fix this issue?
Correct Answer: E
CSA Exam Question 139
What is the difference between UI Policy and UI Action?
Correct Answer: B
UI Policies and UI Actionsare both part of theServiceNow user interface customizationbut serve different purposes. Used todynamically change form field behaviorsbased on specific conditions. Canmake fields read-only, mandatory, or hiddenwithout requiring scripts. Runson the client-side (browser)to improve performance and responsiveness. Example: If theCategoryisHardware, theSerial Numberfield becomesmandatory. Used tocreate buttons, links, and context menu actions. Can executescriptsto perform specific actions when clicked. Runs on theserver-side or client-sidedepending on configuration. Example: A"Save" buttonthat becomesvisible only to users with a specific role. UI Policy(not UI Action) is responsible for making fieldsread-only, mandatory, or hidden. UI Action(not UI Policy) is responsible for making aSave button visiblefor specific users. ServiceNow Docs: UI Policy Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform- administration/page/administer/form-administration/concept/c_UIPolicies.html ServiceNow Docs: UI Action Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform- administration/page/administer/form-administration/concept/c_UIActions.html UI Policy:UI Action:Why Option A is Incorrect?References from Certified System Administrator (CSA) Documentation:
CSA Exam Question 140
Which of the following are not included in an Update Set, by default? (Choose four.)
Correct Answer: A,B,C,H
InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default. Homepages (A) -Correct Homepages are stored asuser-specific or global content, and they are not included in update sets by default. To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable. Data (B) -Correct Update Setsdo not include actual data, such as incident records, user records, or CMDB data. Onlyconfiguration changes(like fields, forms, and workflows) are captured. Data migration must be handled separately usingData Export or Integration methods. Published Workflows (C) -Correct Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set. To capture it, you mustmanually updatethe workflow before moving it in an Update Set. Report Definitions (H) -Correct Reports and their configurations are not automatically included in Update Sets. You mustmanually include themby marking them as "Captured in Update Set." D: Business Rules(Captured in Update Sets) E: Schedules(Captured in Update Sets) F: Database changes(Captured in Update Sets) G: Related Lists(Captured in Update Sets) I: Scheduled Jobs(Captured in Update Sets) J: Client Scripts(Captured in Update Sets) K: Views(Captured in Update Sets) ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development /page/build/system-update-sets/concept/c_UpdateSets.html ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application- development/page/build/system-update-sets/concept/update-set-best-practices.html Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default): Official References from Certified System Administrator (CSA) Documentation:
