{"id":16479,"date":"2026-09-19T07:35:34","date_gmt":"2026-09-19T07:35:34","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16479"},"modified":"2026-09-19T07:35:34","modified_gmt":"2026-09-19T07:35:34","slug":"servicenow-cis-itsm-practice-test-questions-and-exam-dumps-part1-q1-20","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cis-itsm-practice-test-questions-and-exam-dumps-part1-q1-20\/","title":{"rendered":"ServiceNow CIS-ITSM Practice Test Questions and Exam Dumps Part1 Q1-20"},"content":{"rendered":"<p>&nbsp;<\/p>\n<p><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/cis-itsm-exam-dumps\"><b>ServiceNow CIS-ITSM Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/p>\n<p>&nbsp;<\/p>\n<p><b>Q1.<\/b><span style=\"font-weight: 400;\"> You are importing a CSV file into Power BI. One column contains dates in the format <\/span><span style=\"font-weight: 400;\">MM\/DD\/YYYY<\/span><span style=\"font-weight: 400;\">, but Power BI is interpreting some values incorrectly. What should you do in Power Query?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Change the column data type to Text permanently<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use Change Type with Locale and select the appropriate locale<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a calculated column using DAX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Load the data into Power BI and change the format in the model<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Power Query provides the Change Type with Locale option, which is useful when dates, numbers, or currencies are formatted according to a specific regional convention. Selecting the correct locale ensures that Power BI interprets values such as <\/span><span style=\"font-weight: 400;\">03\/04\/2026<\/span><span style=\"font-weight: 400;\"> according to the intended date format. Simply changing the column to Text prevents Power BI from treating the values as dates, which would make date analysis more difficult. Changing the format in the model only affects how a correctly typed date is displayed and does not necessarily correct an incorrect interpretation during import. Therefore, using Change Type with Locale is the appropriate solution for regional date-format issues.<\/span><\/p>\n<p><b>Q2.<\/b><span style=\"font-weight: 400;\"> You have a sales table containing millions of rows and a separate Product dimension table. Which modeling approach should you use to optimize the Power BI model?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a many-to-many relationship between Sales and Product<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a one-to-one relationship between Sales and Product<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a one-to-many relationship from Product to Sales<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Merge the Product table into the Sales table<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">A star schema is generally the preferred modeling approach in Power BI. In this scenario, the Product table acts as a dimension containing unique product records, while Sales is the fact table containing multiple transactions for each product. Therefore, the appropriate relationship is one-to-many, with Product on the \u201cone\u201d side and Sales on the \u201cmany\u201d side. This structure provides efficient filtering and supports clear DAX calculations. A many-to-many relationship should generally be avoided unless the business requirement truly requires it. Merging the tables can unnecessarily increase fact-table size and reduce the benefits of dimensional modeling.<\/span><\/p>\n<p><b>Q3.<\/b><span style=\"font-weight: 400;\"> You need to create a measure that calculates total sales regardless of filters applied to the Product table. Which DAX expression is most appropriate?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALCULATE([Total Sales], ALL(Product))<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUM(Product[Sales])<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FILTER(Product, Product[Sales] &gt; 0)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALCULATE(Product[Sales], VALUES(Product))<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">CALCULATE<\/span><span style=\"font-weight: 400;\"> function modifies the filter context in which a measure is evaluated. Using <\/span><span style=\"font-weight: 400;\">ALL(Product)<\/span><span style=\"font-weight: 400;\"> removes filters from the Product table while retaining other applicable filters unless they are also removed. For example, a measure such as <\/span><span style=\"font-weight: 400;\">CALCULATE([Total Sales], ALL(Product))<\/span><span style=\"font-weight: 400;\"> can calculate total sales across all products even when a report user selects a particular product or category. The other options either use incorrect table\/column references or do not remove the Product filter context. Understanding filter context and the behavior of <\/span><span style=\"font-weight: 400;\">CALCULATE<\/span><span style=\"font-weight: 400;\"> is essential for developing effective DAX measures in Power BI.<\/span><\/p>\n<p><b>Q4.<\/b><span style=\"font-weight: 400;\"> A Power BI report contains a Date table. You want to analyze sales by year, quarter, month, and day. What should you do?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use the automatic date hierarchy only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a dedicated Date table with appropriate date attributes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Convert the Date column to Text<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create separate Sales tables for each year<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">A dedicated Date table provides greater control over time-based analysis and is a recommended modeling practice. It can contain columns such as Date, Year, Quarter, Month Number, Month Name, and Week. The Date table should normally contain a continuous range of dates and be related to the fact table through the appropriate date column. Marking it as a Date table can also help Power BI recognize the intended time dimension. Although automatic date\/time functionality can be convenient for simple reports, a dedicated Date table is more flexible and supports customized time intelligence calculations and consistent filtering across the model.<\/span><\/p>\n<p><b>Q5.<\/b><span style=\"font-weight: 400;\"> You want to allow report users to select a specific product category and have all visuals on the page respond to the selection. Which Power BI feature should you use?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bookmark<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Slicer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tooltip<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drillthrough<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">A slicer is an interactive filtering visual designed to allow report users to select values directly on a report page. For example, a Category slicer can contain values such as Electronics, Furniture, and Clothing. When a user selects a category, visuals connected to the same data model generally respond to the filter context. Bookmarks are used primarily to capture report states and navigation configurations. Tooltips provide additional information when users hover over data points, while drillthrough allows users to navigate to a detailed page based on a selected value. Therefore, a slicer is the most appropriate feature for interactive category filtering.<\/span><\/p>\n<p><b>Q6.<\/b><span style=\"font-weight: 400;\"> A company wants to show monthly revenue trends over the past two years. Which visualization is generally most appropriate?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Line chart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pie chart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Gauge<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Card<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">A line chart is well suited for displaying trends over time because it connects data points sequentially, making increases, decreases, and patterns easier to identify. For monthly revenue across two years, the horizontal axis can represent months while the vertical axis represents revenue. A pie chart is more appropriate for showing parts of a whole at a point in time and can become difficult to interpret with many categories. A gauge generally focuses on progress toward a target, while a card displays a single key value. Therefore, a line chart provides the clearest representation of a continuous monthly revenue trend.<\/span><\/p>\n<p><b>Q7.<\/b><span style=\"font-weight: 400;\"> You have a calculated column that determines profit for every sales transaction. You instead want a calculation that dynamically responds to report filters. What should you create?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A measure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A static column<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A relationship<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A Power Query parameter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Measures are calculated dynamically based on the current filter context of a Power BI report. This makes them appropriate for calculations such as total profit, profit margin, and year-to-date revenue that need to respond to slicers, visual filters, and other report selections. Calculated columns are evaluated during data refresh and store a result for each row, which can increase model size. A relationship connects tables, while a Power Query parameter is primarily used to control query behavior. If the objective is to create a calculation that changes dynamically when users filter the report, a measure is generally the correct choice.<\/span><\/p>\n<p><b>Q8.<\/b><span style=\"font-weight: 400;\"> In Power Query, you need to remove duplicate customer records based on the Customer ID column. What should you do?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove duplicates after selecting Customer ID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replace Customer ID values with null<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Group the entire dataset by date<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable query refresh<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Power Query includes a Remove Duplicates operation that can be applied after selecting one or more columns. If Customer ID uniquely identifies a customer, selecting that column and choosing Remove Duplicates retains one row for each distinct Customer ID. This is useful when preparing dimension tables where unique customer records are required. Replacing values with null does not eliminate duplicate records, while grouping by date addresses a completely different transformation requirement. Disabling refresh prevents new data from being retrieved but does not solve duplication. Therefore, selecting Customer ID and using Remove Duplicates is the appropriate Power Query transformation.<\/span><\/p>\n<p><b>Q9.<\/b><span style=\"font-weight: 400;\"> You need to combine two tables that contain customer information from two different regions. The columns have the same structure, and you want to add the rows together. Which Power Query operation should you use?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Merge Queries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Append Queries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Split Column<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pivot Column<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Append Queries is used when you need to combine rows from two or more tables with compatible structures. For example, if NorthRegionCustomers and SouthRegionCustomers have the same customer columns, appending them creates a single table containing records from both regions. Merge Queries serves a different purpose: it combines tables horizontally by matching values in one or more key columns, similar to a database join. Split Column separates values into multiple columns, while Pivot Column transforms row values into columns. Therefore, when the requirement is to stack rows from similarly structured tables, Append Queries is the correct Power Query operation.<\/span><\/p>\n<p><b>Q10.<\/b><span style=\"font-weight: 400;\"> A report contains a matrix showing sales by country and city. Users want to click a country and see the cities within that country. Which feature provides this functionality?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drill-down<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data refresh<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row-level security<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query folding<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Drill-down allows users to move through different levels of a hierarchy within a visual. In this example, Country can be the higher level and City can be the lower level. Users can select a country and drill into the corresponding cities to examine more detailed information. Data refresh updates the underlying data, row-level security controls which records users are allowed to see, and query folding concerns how Power Query transformations are translated back to the source system. Therefore, drill-down is the appropriate feature for navigating from country-level information to city-level detail within a matrix.<\/span><\/p>\n<p><b>Q11.<\/b><span style=\"font-weight: 400;\"> You need to calculate sales for the previous year based on the current filter context. Which DAX function is commonly used for this purpose?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SAMEPERIODLASTYEAR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTROWS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DISTINCT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CONCATENATE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">SAMEPERIODLASTYEAR<\/span><span style=\"font-weight: 400;\"> is a DAX time-intelligence function that returns a date set corresponding to the same period one year earlier. It is commonly used with <\/span><span style=\"font-weight: 400;\">CALCULATE<\/span><span style=\"font-weight: 400;\"> to create a previous-year sales measure, such as <\/span><span style=\"font-weight: 400;\">CALCULATE([Total Sales], SAMEPERIODLASTYEAR(&#8216;Date'[Date]))<\/span><span style=\"font-weight: 400;\">. This allows the measure to dynamically respond to the current date filter context. Functions such as <\/span><span style=\"font-weight: 400;\">COUNTROWS<\/span><span style=\"font-weight: 400;\"> count rows, <\/span><span style=\"font-weight: 400;\">DISTINCT<\/span><span style=\"font-weight: 400;\"> returns unique values, and <\/span><span style=\"font-weight: 400;\">CONCATENATE<\/span><span style=\"font-weight: 400;\"> combines text. Effective time-intelligence calculations generally require a properly configured Date table and an appropriate relationship between the Date table and the fact table.<\/span><\/p>\n<p><b>Q12.<\/b><span style=\"font-weight: 400;\"> A Power BI report needs to display the percentage contribution of each product category to total sales. Which visualization is most suitable for comparing several categories?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bar chart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Gauge<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Card<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">KPI visual only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">A bar chart is effective for comparing values across multiple categories, including percentage contribution to total sales. It allows users to compare category sizes using the length of bars, which is generally easier to interpret than comparing angles or areas. A gauge is designed primarily for showing progress toward a target, while a card is intended to display a single important value. A KPI visual can compare a current value against a target or status, but it is not inherently designed to compare numerous categories. Therefore, a bar chart provides an effective way to display and compare the percentage contribution of multiple product categories.<\/span><\/p>\n<p><b>Q13.<\/b><span style=\"font-weight: 400;\"> You want to prevent certain users from viewing sales records belonging to other regions. Which Power BI feature should you configure?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bookmarks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row-level security<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drillthrough<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conditional formatting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Row-level security (RLS) restricts the data that users can access based on defined roles and filtering rules. For example, a regional manager could be assigned a role that allows access only to sales records for their specific region. RLS can be implemented using static filters or dynamic security based on user information. Bookmarks control saved report states, drillthrough provides navigation to detailed report pages, and conditional formatting changes the appearance of visuals based on values. RLS is therefore the appropriate Power BI feature when the requirement is to restrict individual users or groups from viewing unauthorized rows in a dataset.<\/span><\/p>\n<p><b>Q14.<\/b><span style=\"font-weight: 400;\"> A Power Query transformation can be translated into a native query executed by the source database. What is this process called?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query folding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data profiling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data lineage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Visual interaction<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Query folding occurs when Power Query translates compatible transformation steps into operations that can be executed by the underlying data source. For example, filtering rows or selecting specific columns from a SQL database may be pushed back to SQL Server rather than processing all data locally. This can improve performance and reduce the amount of data transferred to Power BI. Not every transformation supports query folding, and its availability depends on the connector and source system. Data profiling analyzes data quality, data lineage describes relationships between data assets, and visual interaction controls how report visuals affect each other.<\/span><\/p>\n<p><b>Q15.<\/b><span style=\"font-weight: 400;\"> You have a sales table and a Date table. The Date table contains unique dates, while the Sales table contains many transactions for each date. What relationship should you create?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One-to-one<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Many-to-many<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One-to-many from Date to Sales<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Many-to-one from Date to Sales<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">The Date table should be on the \u201cone\u201d side because each date should appear only once in the Date table. The Sales table is on the \u201cmany\u201d side because multiple transactions can occur on the same date. Therefore, the correct relationship is one-to-many from Date to Sales. This relationship allows filters applied through the Date table to propagate to the corresponding sales records. Maintaining this structure is an important part of a star-schema design. A one-to-one relationship would not support multiple transactions per date, while many-to-many is unnecessary when the Date table contains unique dates.<\/span><\/p>\n<p><b>Q16.<\/b><span style=\"font-weight: 400;\"> You want to allow users to navigate from a summary sales page to a detailed customer page based on the selected customer. Which feature should you configure?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drillthrough<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query folding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data category<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Power Query merge<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Drillthrough allows users to navigate from one report page to another while carrying the selected filter context with them. For example, a summary page might display sales by customer. The user can right-click a customer and select a drillthrough option that opens a customer-detail page filtered to that customer. This is useful for creating detailed analysis pages without overcrowding the main report. Query folding relates to Power Query performance, data categories provide metadata for fields such as geographic information, and Merge Queries combines tables. Therefore, Drillthrough is the appropriate feature for this navigation scenario.<\/span><\/p>\n<p><b>Q17.<\/b><span style=\"font-weight: 400;\"> Which DAX function should you use to count the number of rows in a table?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTROWS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AVERAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RELATED<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">COUNTROWS<\/span><span style=\"font-weight: 400;\"> DAX function returns the number of rows in a specified table. It is particularly useful when you need to count transactions, orders, records, or other table rows. For example, <\/span><span style=\"font-weight: 400;\">COUNTROWS(Sales)<\/span><span style=\"font-weight: 400;\"> returns the number of rows currently visible within the relevant filter context. <\/span><span style=\"font-weight: 400;\">SUM<\/span><span style=\"font-weight: 400;\"> adds numeric values from a column, while <\/span><span style=\"font-weight: 400;\">AVERAGE<\/span><span style=\"font-weight: 400;\"> calculates an arithmetic mean. <\/span><span style=\"font-weight: 400;\">RELATED<\/span><span style=\"font-weight: 400;\"> retrieves a related value from another table when an appropriate relationship exists. Understanding the purpose of core DAX functions is important for PL-300 because measures often combine aggregation functions with filter-context functions to produce dynamic analytical results.<\/span><\/p>\n<p><b>Q18.<\/b><span style=\"font-weight: 400;\"> A Power BI report has several visuals, but selecting a value in one visual does not affect another visual. What should you inspect first?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Edit interactions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data gateway credentials<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workspace capacity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data type formatting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">Power BI provides Edit interactions to control how one visual affects other visuals on the same report page. For example, selecting a bar in a chart can filter or highlight another chart. If a visual does not respond as expected, reviewing the interaction settings is an appropriate first step. Depending on the configuration, an interaction can be set to filter, highlight, or have no effect. Gateway credentials relate to connectivity for certain data sources, workspace capacity relates to service resources, and data type formatting does not determine visual interaction behavior. Therefore, Edit interactions should be inspected first.<\/span><\/p>\n<p><b>Q19.<\/b><span style=\"font-weight: 400;\"> You need to create a visual that displays the current total sales as a single prominent number. Which Power BI visual should you use?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Card<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scatter chart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Treemap<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ribbon chart<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">The Card visual is designed to display a single important value prominently. It is commonly used for KPIs such as total sales, total profit, number of customers, or total orders. A measure can be placed in the Card visual so that the displayed value dynamically changes according to the current filter context. Scatter charts are designed to analyze relationships between numerical variables, treemaps show hierarchical proportions, and ribbon charts can illustrate changes in rankings across categories. Therefore, when the primary requirement is to present one key numerical value clearly and prominently, a Card visual is the appropriate choice.<\/span><\/p>\n<p><b>Q20.<\/b><span style=\"font-weight: 400;\"> You have a Power BI semantic model containing a Sales fact table and Product and Date dimension tables. You want to calculate total sales for products in the &#8220;Electronics&#8221; category while retaining the current date filters. Which DAX approach is appropriate?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALCULATE([Total Sales], Product[Category] = &#8220;Electronics&#8221;)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALL(Product)<\/span><span style=\"font-weight: 400;\"> without any additional filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REMOVEFILTERS(&#8216;Date&#8217;)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTROWS(Product)<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><b><br \/>\n<\/b><span style=\"font-weight: 400;\">CALCULATE<\/span><span style=\"font-weight: 400;\"> is designed to modify filter context while evaluating a measure. The expression <\/span><span style=\"font-weight: 400;\">CALCULATE([Total Sales], Product[Category] = &#8220;Electronics&#8221;)<\/span><span style=\"font-weight: 400;\"> applies a filter to the Product Category while allowing existing filters, including Date filters, to continue affecting the calculation. This means a user viewing sales for a particular month can still see Electronics sales for that month. <\/span><span style=\"font-weight: 400;\">ALL(Product)<\/span><span style=\"font-weight: 400;\"> would remove Product filters rather than specifically selecting Electronics, while <\/span><span style=\"font-weight: 400;\">REMOVEFILTERS(&#8216;Date&#8217;)<\/span><span style=\"font-weight: 400;\"> would remove date filters, producing the opposite of the requirement. <\/span><span style=\"font-weight: 400;\">COUNTROWS(Product)<\/span><span style=\"font-weight: 400;\"> counts product rows and does not calculate sales. Thus, <\/span><span style=\"font-weight: 400;\">CALCULATE<\/span><span style=\"font-weight: 400;\"> with the category filter is appropriate.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; View Full ServiceNow CIS-ITSM Exam Dumps and Practice Test Dumps. &nbsp; Q1. You are importing a CSV file into Power BI. One column contains dates in the format MM\/DD\/YYYY, but Power BI is interpreting some values incorrectly. What should you do in Power Query? Change the column data type to Text permanently Use Change [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16479"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=16479"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16479\/revisions"}],"predecessor-version":[{"id":16499,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16479\/revisions\/16499"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}