Dashboard Part 1 Full Quiz
✅ Part 1 · All 4 Topics

Part 1 Full Quiz

15 scenario-based questions covering all topics in Part 1. Select an answer to reveal the explanation.

Questions
1 / 15
Score
0 / 15
Answered
0
Progress
Part 1 — Platform Overview & Navigation 1 / 15
🖥️ Topic 1 — UI Navigation
Scenario: An administrator types incident.list in the Filter Navigator and presses Enter.

What happens next?

💡 Explanation

B is correct. In the Filter Navigator, typing table_name.list opens the list view for that table. incident.list opens the Incident list. To open a new blank form instead, you would type incident.do. C is wrong — the Filter Navigator filters application menus, not the Knowledge Base. D is wrong — reports require Report Designer, not this shortcut pattern.

🖥️ Topic 1 — UI Navigation
Scenario: A new administrator opens the Banner Frame in ServiceNow UI16. They count the navigation menus available at the top.

How many top-level menus does the Banner Frame contain, and what are they?

💡 Explanation

B is correct. The Banner Frame in UI16 contains exactly 4 menus: All (browse all applications), Favorites (user-pinned shortcuts), History (recently visited pages), and Admin (system administration links, visible only to admins). Notifications are a separate bell icon in the topbar, not a navigation menu. Memorise the 4: All, Favorites, History, Admin.

🖥️ Topic 1 — UI Navigation
Scenario: An admin wants to reference the "Assigned To" user's department name on an Incident form using a single expression in a field default value.

Which expression correctly uses dot-walking to get the department name of the assigned user?

💡 Explanation

B is correct. ServiceNow dot-walking syntax uses the dot (.) notation: RelatedTable.Field. To traverse multiple hops, you chain dots: assigned_to.department.name walks from the Incident's Assigned To reference → the user's Department reference → the department's Name field. Arrow notation (A) and bracket notation (C) are not valid ServiceNow dot-walking syntax. Double colon (D) is not used for dot-walking.

🖥️ Topic 1 — UI Navigation
Scenario: A company wants to use Basic Configuration UI16 theme customisation to match their corporate branding. Their instance currently has Next Experience (Polaris) enabled.

[TRAP] What must they do first?

💡 Explanation

B is correct. This is a classic exam trap. Basic Configuration UI16 (System Properties > Basic Configuration UI16) only functions when Next Experience (Polaris) is disabled. When Next Experience is active, the UI uses UX Themes instead for branding — these are completely separate tools. D is wrong because UX Themes and Basic Configuration are not equivalent; they serve the same purpose (branding) but are different systems used in different UI frameworks. No purchase or upgrade is required.

📝 Topic 2 — Lists, Filters & Forms
Scenario: A user on the Incident list view wants to add a "Business Impact" column visible only to themselves, without affecting other users' views.

Which feature should they use?

💡 Explanation

B is correct. Personalize List (gear icon on the list view) lets individual users customise which columns appear in their own list view — changes apply only to that user. System View (C) changes the default for all users. Form Layout (A) and Form Design (D) control the form view layout (individual record page), not the list view columns. Remember: gear icon on list = Personalize List = per-user change only.

📝 Topic 2 — Lists, Filters & Forms
Scenario: An admin right-clicks a column header in a list view to sort records. A developer asks: "What does the breadcrumb trail at the top of the list represent?"

What is the function of breadcrumbs in a ServiceNow list view?

💡 Explanation

B is correct. In ServiceNow list views, the breadcrumb trail (the row of conditions shown above the list) represents the currently active filter conditions. Each "crumb" is a filter segment (e.g., "State = Open" and "Priority = 1"). Clicking a breadcrumb allows you to remove or modify that specific filter condition, interactively narrowing or expanding your list. Option A describes the topbar breadcrumb, which is a different UI element. Options C and D are incorrect.

📝 Topic 2 — Lists, Filters & Forms
Scenario: An admin needs to add a new section with two columns to an Incident form, placing specific fields in each column. A colleague says to use "Form Layout" for this.

[TRAP] Is the colleague correct, and which tool actually creates form sections with column layouts?

💡 Explanation

B is correct. This is a frequently tested distinction. Form Layout (right-click form header → Configure → Form Layout) uses a two-column slushbucket to add, remove, and reorder fields — but it does not create sections or define column splits. Form Design (Configure → Form Design) provides a drag-and-drop grid interface where you can create form sections, set 1- or 2-column layouts within sections, and arrange fields visually. Studio (C) is for scoped app development, not basic form customisation. D completely reverses the roles.

🎨 Topic 3 — Properties & Branding
Scenario: A company wants to change the ServiceNow header colour from the default blue to their corporate green and replace the ServiceNow logo with their own logo. Next Experience is currently disabled.

Where should the administrator go to make these branding changes?

💡 Explanation

A is correct. When Next Experience is disabled, branding changes to the main UI (header colour, banner logo, background) are made in System Properties > Basic Configuration UI16. This provides a UI for uploading a logo and selecting header/navigation colours. Option C (UX Themes) is only available and relevant when Next Experience is enabled. Option B (raw CSS) is possible but not the supported admin workflow. Option D controls Service Portal theming, which affects the end-user portal only, not the main admin UI.

🎨 Topic 3 — Properties & Branding
Scenario: An admin modifies the list column layout on the Incident table and saves it as the default view. A non-admin user then logs in and opens the Incident list.

What view will the non-admin user see by default, assuming they have not personalised their own list?

💡 Explanation

A is correct. In ServiceNow, the System View defines the default column layout seen by all users who have not applied their own personal list customisation. When an admin saves a list layout as the System View, that becomes the default for everyone. A user's Personalize List override takes precedence over the System View only for that specific user. Option B is wrong — admin personalisation does not propagate to other users. Options C and D do not reflect how ServiceNow list views work.

📱 Topic 4 — Mobile & Portal
Scenario: A company deploys both the "Mobile Agent" app and "Now Mobile" app to their employees. A help desk technician needs to manage assigned incidents while away from their desk, including updating work notes and changing incident state.

Which app should the technician use?

💡 Explanation

B is correct. Mobile Agent is specifically designed for fulfillers (IT agents, technicians) to manage and work on assigned tasks — updating incidents, changing state, adding work notes — from their mobile device. It also supports offline mode. Now Mobile (A) is designed for employees/end users for self-service: submitting requests, checking status, and HR tasks. This distinction is heavily tested. The apps are not identical (D). Service Portal (C) is a browser-based self-service portal for end users, not optimised for fulfillers.

📱 Topic 4 — Mobile & Portal
Scenario: An HR department wants to give employees a self-service web experience to submit IT requests, check order status, and access company announcements — accessible from any device browser without installing an app.

Which ServiceNow feature is the best fit?

💡 Explanation

B is correct. The Service Portal is ServiceNow's responsive, browser-based self-service experience for end users. It is built using AngularJS and organised into pages containing widget-based components. Employees access it via browser without installing anything. Now Mobile (A) requires app installation and is designed for on-the-go employees needing a native app experience. Mobile Agent (C) is for fulfillers/IT agents, not employees. UI16 (D) is the main admin/fulfiller interface — it is not designed or appropriate for end-user self-service.

📱 Topic 4 — Mobile & Portal
Scenario: A developer is building a Service Portal page that should display a list of open incidents for the logged-in user. They want to reuse this component across multiple portal pages.

What is the correct ServiceNow term for this reusable component?

💡 Explanation

B is correct. In the Service Portal framework, a Widget is the fundamental reusable unit of UI functionality. Each widget contains its own HTML template, CSS, client-side JavaScript (AngularJS), and server-side script. Widgets can be placed on multiple Portal Pages. A Portal Page (C) is the container — it defines a grid of rows and columns where widgets are placed. "Portal Module" and "Content Block" are not standard ServiceNow Service Portal terms.

📝 Topic 2 — Lists, Filters & Forms
Scenario: A user opens the Incident list and sees 247 records displayed. She wants to see only incidents where Priority = 1 AND State = In Progress. She uses the Filter bar to build this condition.

After running the filter, she clicks the "Priority is 1" breadcrumb segment. What is the most likely result?

💡 Explanation

B is correct. In ServiceNow list views, clicking a breadcrumb condition segment removes that specific filter condition from the active filter, immediately reloading the list with the remaining conditions applied. In this case, clicking the "Priority is 1" breadcrumb removes that condition, leaving "State = In Progress" still active — showing all In Progress incidents regardless of priority. The breadcrumb acts as a live filter toggle, not an editor. Options A, C, and D do not describe actual breadcrumb behaviour.

🖥️ Topic 1 — UI Navigation
Scenario: A developer needs to open a specific Incident record directly without searching. They know the table is "incident" and they want to open a new empty form.

Which Filter Navigator shortcut opens a new blank Incident form?

💡 Explanation

C is correct. The Filter Navigator shortcut pattern table_name.do opens a new blank form for that table. incident.do opens a new empty Incident record. incident.list (A) opens the list view of existing records. incident.new and incident.form are not valid ServiceNow shortcuts. The two key shortcuts to memorise: .list = list view, .do = new form.

📱 Topic 4 — Mobile & Portal
Scenario: A ServiceNow administrator is asked to explain how the Service Portal's layout is structured to a new team member.

Which description correctly explains the Service Portal page structure from outer container to inner element?

💡 Explanation

B is correct. The Service Portal hierarchy is: Portal (the top-level container that holds all pages and applies a theme) → Page (an individual page within the portal) → Row (a horizontal division of the page) → Column (a vertical division within a row) → Widget (the functional component placed in a column). This Bootstrap-grid structure is fundamental to the Service Portal designer. Understanding this hierarchy is essential for the CSA exam.

← Flashcards Back to Dashboard →