Courseiva
Self-Service and AutomationhardMultiple ChoiceObjective-mapped

SNOW-CSA Self-Service and Automation Practice Question

An administrator is designing a catalog item for software requests. The item must capture the user's department automatically and pre-populate the cost center. Which feature should be used to achieve this?

⚠ Common exam trap

Watch out — candidates often confuse client-side scripts (Catalog Client Scripts or Client Scripts) with server-side default value logic, assuming scripts are needed for pre-population when system properties provide a simpler, no-code solution.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Variable default value using system properties

Using a variable default value with a system property allows the catalog item to automatically populate the department and cost center fields based on the logged-in user's data. System properties can reference user attributes (e.g., sys_user.department) to dynamically set default values without requiring client-side scripts or UI policies.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Catalog Client Script

    Why it's wrong here

    A Catalog Client Script executes on the client-side and cannot automatically retrieve the user's department from their server-side profile without an explicit Asynchronous JavaScript and XML (AJAX) call. The requirement for automatic capture and pre-population necessitates a mechanism that inherently accesses server-side user data, typically through default value scripts or variable attributes, which execute before or as the form loads. Client Scripts are primarily utilised for dynamic client-side form validation, making fields mandatory, or showing/hiding elements based on user interactions within the form, such as populating a field based on another field's selection.

  • UI Policy

    Why it's wrong here

    UI policies control visibility and mandatory fields, not default values.

  • Variable default value using system properties

    Why this is correct

    Defaults can be set to user's department and cost center from user record.

  • Client Script

    Why it's wrong here

    Client Scripts execute on the client side after the form loads, so they cannot pre-populate a field before the form is rendered or automatically capture the user's department from a system record without a separate asynchronous call. This option is tempting because Client Scripts are commonly used to set field values based on user interactions, such as showing or hiding sections, and would be the correct choice if the requirement were to dynamically update the cost centre after a user selects a specific option on the form.

About these practice questions

This SNOW-CSA question is part of Courseiva's 504-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This SNOW-CSA practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CSA exam.