Exact2Pass
Which is the most preferred Unique User ID setting and the one you should explore first for UUID setup?
WalkMe ID
Cookie
Variable
jQuery
The Unique User ID (UUID) in WalkMe is used to track individual users for analytics and personalization. The most preferred setting to explore first is aVariable, as it allows Builders to leverage an existing user identifier from the application (e.g., a user ID stored in a JavaScript variable), ensuring accurate and reliable user tracking. Variables are typically provided by the application’s authentication system and are more robust than other methods, which may be less consistent or require additional configuration.
The other options are less preferred:
WalkMe ID(A) is a fallback generated by WalkMe but may not align with the application’s user data.
Cookie(B) can be unreliable due to browser restrictions or clearing of cookies.
jQuery(D) is not a standard method for UUID setup; it’s used for element selection, not user identification.
Extract from Official WalkMe Documentation:
Per the WalkMe Admin Center User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.10: User Identification):
“For UUID setup, the Variable method is the most preferred, as it uses an application-provided user identifier (e.g., a JavaScript variable) for accurate tracking. Explore this option first before fallback methods like WalkMe ID or cookies.”
The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:
“Start with the Variable setting for UUID configuration, as it integrates with the application’s user data, providing the most reliable and consistent user tracking for Insights analytics.”
Option C, Variable, is the most preferred UUID setting.
What is WalkMe known as the leading provider of?
Digital Application Platform
Dynamic Assistance Provider
Direct Adoption Program
Digital Adoption Platform
WalkMe is recognized as the leading provider of aDigital Adoption Platform (DAP), which helps organizations ensure employees and customers effectively use digital tools and platforms. A DAP provides tools like in-app guidance, analytics, and automation to enhance user adoption, streamlineprocesses, and reduce friction in digital experiences.
The other options are incorrect:
Digital Application Platform(A) refers to app development platforms, not adoption.
Dynamic Assistance Provider(B) is not an industry term.
Direct Adoption Program(C) is not a recognized category.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: Introduction to Digital Adoption):
“WalkMe is the leading provider of a Digital Adoption Platform (DAP), delivering solutions that drive effective use of digital platforms through guidance and analytics.”
The courseGetting Started with Building WalkMe Solutionsstates:
“As a Digital Adoption Platform, WalkMe empowers organizations to maximize software adoption and user efficiency with tools like Smart Walk-Thrus and Insights.”
Option D, Digital Adoption Platform, is the correct answer.
How would you write a jQuery selector for the following HTML element:
div#button
#blueBtn
div#blueBtn
div.blueBtn
In jQuery, selectors are used to target HTML elements based on their tag, class, ID, or other attributes. The HTML element
The other options are incorrect or less optimal:
Option A(div#button) incorrectly uses the class name as an ID.
Option B(#blueBtn) is valid but less specific, as it doesn’t confirm the element is a
Option D(div.blueBtn) targets the class, which is less specific than the ID and could match multiple elements.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.7: jQuery Selectors):
“When writing jQuery selectors for WalkMe, prioritize specificity and reliability. For elements with unique IDs, use the format tag#id (e.g., div#blueBtn) to ensure accurate targeting while clarifying the element type.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“For an HTML element like
Option C, div#blueBtn, is the correct jQuery selector.
Which of the options below is a use case for when to use jQuery? Note: There are 3 correct answers to this question.
To redesign the entire layout of the WalkMe balloons.
If the WalkMe element selector algorithm is not consistently identifying your element.
To close the WalkMe menu and start an Onboarding task.
To grab a dynamic value from an on-screen element and incorporate it into a ShoutOut for a personalized experience.
To target a very specific element on your website.
jQuery is a powerful tool in WalkMe for advanced element targeting and dynamic interactions. The correct use cases are:
If the WalkMe element selector algorithm is not consistently identifying your element(B): jQuery selectors provide precise targeting when WalkMe’s default algorithm struggles with dynamic or complex elements.
To grab a dynamic value from an on-screen element and incorporate it into a ShoutOut for a personalized experience(D): jQuery can extract values (e.g., a username) for use in personalized content.
To target a very specific element on your website(E): jQuery allows fine-tuned selectors for elements with unique attributes or structures.
The other options are incorrect:
Redesigning the entire layout of WalkMe balloons(A) is done via Global/Local Design settings, not jQuery.
Closing the WalkMe menu and starting an Onboarding task(C) uses WalkMe’s native APIs or rules, not jQuery.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.7: jQuery Selectors):
“Use jQuery in WalkMe to target specific elements when default selectors fail, extract dynamic values for personalization (e.g., in ShoutOuts), or address complex DOM structures requiring precise element identification.”
The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:
“jQuery is essential for scenarios like inconsistent element detection, grabbing dynamic data for personalized content, or targeting unique elements with custom selectors.”
Options B, D, and E are valid jQuery use cases.
You are building a WalkMe solution to help your users self-serve and prevent common support tickets from being opened repeatedly. You want to add guidance for the top three support tickets to a page on your website and make it stand out for the end user. What is the best solution to allow for quick and easy access?
Create a Survey to ask end users about their feedback.
Create a Mini Menu of content from the top three support tickets and place it next to the support ticket form.
Add it to your list of WalkMe content in the Menu.
Create a large ShoutOut to appear in the middle of the page each time the user visits the page.
To address common support tickets and promote self-service, aMini Menuplaced next to the support ticket form is the best solution. A Mini Menu is a compact, context-sensitive menu that provides quick access to relevant content, such as Smart Walk-Thrus or Resources for the top three support issues. Positioning it near the form ensures it’s highly visible and accessible when users are likely to need help, reducing ticket submissions by guiding users to solutions proactively.
The other options are less suitable:
A Survey(A) collects feedback but doesn’t provide guidance to prevent tickets.
Adding to the WalkMe Menu(C) is less targeted, as users must navigate to find content.
A large ShoutOut(D) is disruptive if shown repeatedly and less effective for ongoing self-service.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.11: Mini Menus):
“Mini Menus are ideal for delivering context-specific content, such as guidance for common issues, directly on a page. Place them near relevant elements, like a support form, to promote self-service and reduce support tickets.”
The courseAdvancing Your Skills in Building WalkMe Solutionsstates:
“To address frequent support tickets, create a Mini Menu with targeted content and position it near the point of need, such as a ticket form, for quick user access and effective self-service.”
Option B, a Mini Menu next to the support ticket form, is the best solution.
How does WalkMe’s Digital Experience Analytics (DXA) support organizations?
By replacing all manual processes with automation
By tracking how users interact with predefined on-screen elements
By creating new applications to replace existing ones
By eliminating the need for employee training
WalkMe’sDigital Experience Analytics (DXA)supports organizations bytracking how users interact with predefined on-screen elements, such as buttons, forms, or pages. This provides insights into user behavior, friction points, and adoption gaps, enabling organizations to optimize processes and improve digital experiences. DXA integrates with WalkMe Insights to deliver actionable data.
The other options are incorrect:
Replacing manual processes(A) is a benefit of automation, not DXA’s primary role.
Creating new applications(C) is outside WalkMe’s scope.
Eliminating training(D) is an exaggeration, as WalkMe supports training, not replaces it.
Extract from Official WalkMe Documentation:
Per the SAP WalkMe Digital Adoption Consultant Study Guide (Section 3.1: Analytics Overview):
“Digital Experience Analytics (DXA) tracks user interactions with predefined elements, offering insights into engagement and pain points to enhance digital adoption.”
The courseWalkMe Fundamentalsexplains:
“DXA helps organizations by monitoring how users interact with on-screen elements, providing data to identify inefficiencies and improve user experiences.”
Option B correctly describes DXA’s support for organizations.
When are SmartTip validation rules evaluated?
When the user refreshes the page.
When the user enters content into a field.
When the user enters content into a field and then clicks or tabs outside of the field.
When the user clicks into a field.
SmartTips in WalkMe are used to provide guidance or validation for form fields, ensuring users input correct data. Validation SmartTips are configured with rules that check the content of a field against specific criteria (e.g., format, length, or value). These validation rules are evaluated when the user enters content into a field and then moves focus away from it, either by clicking outside the field or tabbing to another element. This behavior ensures that the validation occurs after the user has completed their input, providing immediate feedback without interrupting their workflow.
The other options are incorrect:
When the user refreshes the page(A) does not trigger validation, as SmartTips are tied to user interactions with specific fields.
When the user enters content into a field(B) is too early, as validation requires the user to finish inputting and move focus.
When the user clicks into a field(D) triggers the display of guidance SmartTips, not validation rules.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.5: SmartTips):
“Validation SmartTips evaluate their rules when the user enters content into a field and then removes focus from that field, either by clicking elsewhere or tabbing out. This ensures that validation feedback is provided after the user has completed their input.”
The courseAdvancing Your Skills in Building WalkMe Solutionsfurther explains:
“SmartTip validation rules are designed to check field input once the user has finished entering data and moves focus away (e.g., by clicking or tabbing out). This timing balances real-time feedback with non-disruptive user experience.”
Option C accurately describes when SmartTip validation rules are evaluated.
You and your Project Lead just had a conversation with a business stakeholder who wants you to create WalkMe content for their team. They provided you with all of the following information: Sales team members are constantly rushing through entering contract details in your sales platform, which adds to inaccurate data for the business. Once they get to the contract page, there are many fields to fill out that are unique to each client. They often don’t remember which is the correct option from a number of dropdown fields, and the company doesn’t currently have any documentation that explains the dropdown fields. What is the end user behavior (pain point) you need to address with WalkMe content?
The business has inaccurate data
No help documentation currently exists
Sales team members are rushing through entering contract details
Users do not know which is the correct option in the dropdown fields
The end user behavior (pain point) to address is thatusers do not know which is the correct option in the dropdown fields. This specific behavior directly causes the inaccurate data, as sales team members are selecting incorrect options due to a lack of guidance. WalkMe content, such as Guidance SmartTips, can provide real-time instructions for each dropdown field to ensure correct selections, addressing the root cause of the issue.
The other options are related but not the primary pain point:
Inaccurate data(A) is the outcome, not the behavior.
No help documentation(B) is a contributing factor, not the user’s action.
Rushing through details(C) is a secondary behavior, but the core issue is incorrectdropdown selections.
Extract from Official WalkMe Documentation:
Per the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.3: Identifying Pain Points):
“Identify the specific end user behavior causing issues, such as selecting incorrect options in dropdowns, to target WalkMe content effectively, like SmartTips for field guidance.”
The courseGetting Started with Building WalkMe Solutionsexplains:
“Focus on the user behavior driving the problem, such as confusion over dropdown options, to design WalkMe solutions that provide clarity and improve accuracy.”
Option D is the end user pain point to address.
When doing quality assurance and testing content, which of the options below should we be looking for? Note: There are 3 correct answers to this question.
Page load time is under ten seconds.
Content appears as expected.
Balloons are not blocking important site elements.
Smart Walk-Thru triggers work as expected.
The website’s background color matches the corporate branding.
Quality assurance (QA) and testing of WalkMe content focus on ensuring that the content functions correctly, displays appropriately, and enhances the user experience without causing disruptions. The key aspects to check include:
Content appears as expected(B): Verify that WalkMe content (e.g., SmartTips, ShoutOuts) displays with the correct text, styling, and positioning as designed in the Editor.
Balloons are not blocking important site elements(C): Ensure that WalkMe balloons (e.g., Smart Walk-Thru steps or SmartTips) do not obscure critical UI elements, such as buttons or forms, to maintain usability.
Smart Walk-Thru triggers work as expected(D): Confirm that triggers (e.g., clicks, page loads) initiate Smart Walk-Thru steps correctly, ensuring smooth guidance.
The other options are incorrect:
Page load time under ten seconds(A) is a website performance metric, not a WalkMe QA responsibility.
Website’s background color matching corporate branding(E) is outside WalkMe’s scope, as it pertains to the website’s design.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.4: Quality Assurance):
“During QA, verify that content displays correctly, balloons do not block critical UI elements, and Smart Walk-Thru triggers function as intended. These checks ensure a seamless user experience.”
The courseGetting Started with Building WalkMe Solutionsstates:
“QA involves confirming that WalkMe content appears as designed, does not obstruct important page elements, and that triggers for Smart Walk-Thrus execute reliably.”
Options B, C, and D are the correct aspects to focus on during QA.
You have just created a few new pieces of content. Now, you are ready to view how they work together and see how they will look from the end user experience before you publish. Which feature will be best to do this?
Play multiple items
Preview
Play
Publish Settings
ThePreviewfeature in the WalkMe Editor allows Builders to simulate the end-user experience for multiple pieces of content before publishing. It shows how content (e.g., Smart Walk-Thrus, SmartTips, ShoutOuts) appears and interacts on the page, ensuring they work together seamlessly and look as intended from the user’s perspective.
The other options are incorrect:
Play multiple items(A) is not a standard WalkMe feature.
Play(C) typically refers to testing a single Smart Walk-Thru, not multiple content types.
Publish Settings(D) configure deployment options, not preview functionality.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.4: Quality Assurance):
“The Preview feature enables Builders to test multiple pieces of content together, simulating the end-user experience to verify appearance and interactions before publishing.”
The courseGetting Started with Building WalkMe Solutionsexplains:
“Use Preview in the Editor to see how new content will look and function for end users, allowing you to test combinations of content without publishing.”
Option B, Preview, is the best feature for this purpose.
The ShopMe team wants to put a Launcher on every product page. Example URLs of the productpages are as follows:
http://shopme.walkme.com/product/taylor-swift-1989/
http://shopme.walkme.com/product/nicki-minaj-the-pinkprint/
http://shopme.walkme.com/product/beyonce-beyonce/
How would they build the Current URL rule for when this should appear with best practices in mind?
Current URL > is like > shopme.walkme.com/product
Current URL is like > walkme.com
Current URL > contains > /product
Current URL > contains > shopme.walkme.com
To display a Launcher on every product page, the Current URL rule must target the common pattern in the product page URLs. The example URLs share the segment “/product,” which uniquely identifies product pages. Using the ruleCurrent URL > contains > /productensures the Launcher appears on all pages with “/product” in the URL, following best practices for specificity and flexibility. This approach avoids overly broad or restrictive rules and accommodates potential URL variations.
The other options are incorrect:
is like > shopme.walkme.com/product(A) is too specific, missing subpaths like “/taylor-swift-1989/.”
is like > walkme.com(B) is too broad, matching non-product pages.
contains > shopme.walkme.com(D) is also too broad, including non-product pages on the domain.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.9: URL Rules):
“For URL-based rules, use ‘contains’ with a unique URL segment (e.g., ‘/product’) to target specific page types, ensuring flexibility and accuracy for dynamic URLs.”
The courseGetting Started with Building WalkMe Solutionsadvises:
“When targeting pages like product pages, use ‘Current URL contains’ with a distinctive segment like ‘/product’ to capture all relevant pages without including unrelated ones.”
Option C is the best URL rule for the Launcher.
In the Editor, a Shuttle has a full green circle next to it when looking at the Production environment. How would you describe the status of this Shuttle?
Draft mode in Test
Archived in Production
Published to Production but has been modified
Published to Production
In the WalkMe Editor, afull green circlenext to a content item, such as a Shuttle, in the Production environment indicates that the item isPublished to Productionand is live for end users. This status confirms that the Shuttle has been successfully deployed without subsequent modifications or archiving.
The other options are incorrect:
Draft mode in Test(A) would show a different icon (e.g., gray or yellow) in the Test environment.
Archived in Production(B) would show an archived status, not a green circle.
Published but modified(C) would display a modified indicator, not a full green circle.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.10: Publishing and Status):
“A full green circle in the Production environment indicates that the content item, such as a Shuttle, is published and active for end users.”
The courseGetting Started with Building WalkMe Solutionsstates:
“Check the status icon in the Editor: a full green circle in Production means the content is live and published without pending changes.”
Option D correctly describes the Shuttle’s status.
What role does WalkMe(X) play in Digital Adoption?
It provides AI-powered assistance within workflows to enhance user experience
It creates new software applications automatically
It restricts access to applications that users struggle with
It replaces the need for any human training sessions
WalkMe(X)is an AI-powered component of WalkMe’s Digital Adoption Platform that providesAI-powered assistance within workflowsto enhance the user experience. It offers contextual suggestions, automates repetitive tasks, and delivers personalized guidance, making digital platforms easier to use and improving adoption rates.
The other options are incorrect:
Creating new software(B) is not a WalkMe(X) function; it enhances existing applications.
Restricting access(C) is not its role; it focuses on assistance, not restrictions.
Replacing human training(D) is an overstatement; it supports, not eliminates, training.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: WalkMe Fundamentals):
“WalkMe(X) leverages AI to provide contextual, in-workflow assistance, enhancing user experience by delivering personalized guidance and automation.”
The courseWalkMe Fundamentalsstates:
“WalkMe(X) plays a critical role in Digital Adoption by using AI to assist users within workflows, improving efficiency and ease of use.”
Option A correctly describes WalkMe(X)’s role.
Which of the following is a capability of WalkMe’s Smart Walk-Thrus?
Providing step-by-step on-screen guidance in real time
Preventing users from interacting with pop-ups
Removing unused applications from the tech stack
Blocking users from making changes to the software
WalkMe’sSmart Walk-Thrusare designed to deliverstep-by-step on-screen guidance in real time, guiding users through processes within an application. This capability uses interactive balloons and triggers to provide contextual instructions, enhancing user adoption and reducing errors without altering the underlying software.
The other options are incorrect:
Preventing pop-up interactions(B) is not a primary Smart Walk-Thru function, though Launchers can block elements.
Removing unused applications(C) is unrelated to Smart Walk-Thrus; it may relate to Discovery’s License Optimization.
Blocking software changes(D) is not a WalkMe feature, as it focuses on guidance, not restrictions.
Extract from Official WalkMe Documentation:
According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.1: WalkMe Fundamentals):
“Smart Walk-Thrus provide real-time, step-by-step on-screen guidance, helping users navigate processes and complete tasks efficiently within applications.”
The courseWalkMe Fundamentalsstates:
“A core capability of Smart Walk-Thrus is delivering interactive, real-time guidance directly on the screen, simplifying complex processes for users.”
Option A accurately describes a Smart Walk-Thru capability.
When adding new users to an account on a platform, admins must select their permission levels. The company gets a lot of support tickets about users asking what each permission level means or asking to adjust permission levels because they were set up incorrectly. The company already has a help article that lists out all of the permission level definitions, but it isn’t used often. Which of these options would be the best solution to create with WalkMe?
ShoutOut every time admins begin adding a new user
Validation SmartTip
Smart Walk-Thru navigating users to the help Resource
Launcher next to the field that activates a Resource
The issue is that admins frequently submit support tickets due to confusion about permission levels, despite an existing help article. The best WalkMe solution is aLauncher next to the field that activates a Resource, which links directly to the help article. This approach provides context-sensitive access to the documentation exactly where admins need it—near the permission level field—encouraging its use and reducing support tickets without disrupting the workflow.
The other options are less effective:
ShoutOut every time admins add a user(A) is intrusive and not directly tied to the permission field.
Validation SmartTip(B) is for enforcing input rules, not linking to help content.
Smart Walk-Thru to the help Resource(C) is overly complex for simply accessing documentation.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.3: Launchers):
“Launchers placed next to form fields can activate Resources, such as help articles, providing instant access to relevant documentation to reduce user errors and support tickets.”
The courseGetting Started with Building WalkMe Solutionsstates:
“For underutilized help content, place a Launcher near the relevant field to trigger a Resource,ensuring users access guidance in context to resolve confusion efficiently.”
Option D is the best solution to reduce support tickets by leveraging the existing help article.