Microsoft PL-900 Microsoft Power Platform Fundamentals Exam Dumps and Practice Test Questions Set 4 Q61-80

Visit here for our full Microsoft PL-900 exam dumps and practice test questions.

Question 61: 

Which Power Automate feature ensures a flow pauses until specific data becomes available or a condition is met?

A) Delay action
B) Condition control
C) Do until control
D) Switch control

Answer: C) Do until control

Explanation:

The delay action in Power Automate is designed to pause the execution of a flow for a specific duration of time. This can be useful when waiting for processes that are time-dependent, such as waiting for a system to update or for a scheduled interval. However, the delay action does not check whether a specific condition or data state has been met. It simply pauses for a set period and then continues the flow regardless of whether the required data or condition is available. This limitation makes it unsuitable when the goal is to pause a flow until a particular condition becomes true.

The condition control evaluates a specified condition and determines which branch of the flow should continue based on whether the condition is true or false. While it can help in decision-making within a flow, it does not inherently wait or re-evaluate the condition repeatedly. It performs a single evaluation and then moves along the selected branch. Therefore, it cannot continuously monitor for changes in data or status and does not ensure that the flow pauses until the condition is satisfied.

The do until control is specifically built to handle scenarios where a flow must wait for a condition to be true before proceeding. It repeatedly checks the specified condition in a loop and only exits when the condition evaluates as true. This allows flows to respond dynamically to changes in data or system status. The do until control is often combined with a timeout or a maximum iteration limit to prevent indefinite loops, making it a powerful tool for automating processes that require data availability checks or conditional triggers.

Switch control is used to handle multiple branching paths based on the evaluation of a single value. It allows flows to route to different branches depending on the case value but does not continuously monitor or wait for conditions to become true. It performs a one-time evaluation and then executes the selected branch. Since the question specifies pausing a flow until a condition is met, the do until control is the only option that fits this requirement. It ensures that the flow will remain in a loop, checking the condition repeatedly until it can safely continue.

Question 62: 

Which Power BI object enables a single calculation to be reused across multiple visualizations?

A) Measure
B) Column
C) Relationship
D) Field parameter

Answer:  A) Measure

Explanation:

A measure in Power BI is a calculation created using DAX (Data Analysis Expressions) that produces a dynamic result based on the current context in a report. Measures are recalculated automatically as users interact with visuals, slicers, or filters, making them highly reusable across multiple visualizations. For example, a total sales measure will update its value depending on the date range or product category selected, allowing consistent calculations across all visuals that reference it.

Columns, in contrast, are static or calculated at the row level and stored in the data model. While calculated columns can perform operations on row data, they do not automatically adjust in response to filters in the same way measures do. Columns are tied to each row of data rather than the aggregation or context that measures provide, which limits their reusability for dynamic report calculations.

Relationships in Power BI define how tables are connected to each other within a data model. While they are critical for combining data from multiple tables and enabling proper filtering, relationships do not perform calculations themselves. They support data navigation and aggregation but cannot produce a reusable calculation across visuals.

Field parameters allow report authors to dynamically switch between metrics or dimensions in a visual, which provides flexibility for analysis but does not create reusable calculations. They are more about toggling what is displayed rather than performing the calculation itself. The requirement in the question is a calculation that can be reused across visuals, making the measure the correct choice. Measures provide dynamic, context-aware calculations that adapt to filters and slicers, fulfilling this need exactly.

Question 63: 

Which capability of Dataverse allows generating meaningful names instead of GUIDs for identifying records?

A) Primary name column
B) Calculated field
C) Choice column
D) Lookup column

Answer:  A) Primary name column

Explanation:

The primary name column in Dataverse is the field designated to hold the main descriptive identifier for a record. This column allows users to see meaningful names rather than GUIDs when browsing data in tables, forms, or views. It is critical for usability because GUIDs, while unique, are not human-readable. The primary name column is automatically used in lookups, search results, and display forms, providing consistent readability across the system.

Calculated fields perform computations based on other column values. While they can automate numerical or text calculations, they are not designed to replace GUIDs with readable names. Calculated fields are supplementary and dynamic in nature but are not the primary identifier of a record.

Choice columns allow users to select predefined values from a list. They provide structured input options but are not inherently unique identifiers. They are useful for categorization or selection purposes but do not replace the GUID or generate descriptive record names for identification.

Lookup columns create relationships to other tables by referencing related records. While they can display the related record’s primary name, they themselves do not serve as the main identifier for the current table. Their purpose is relational rather than descriptive for the record itself. In this context, the primary name column is the feature that ensures records are identifiable with meaningful, human-readable names instead of GUIDs, making it the correct answer.

Question 64: 

Which Power Apps capability lets you build an app directly from an existing SharePoint list?

A) Generate app
B) Canvas app from blank
C) Model-driven app
D) Portal app

Answer:  A) Generate app

Explanation:

Generate app is a Power Apps feature that allows users to quickly create a fully functional app directly from a SharePoint list. It automatically generates the standard three-screen layout (browse, details, and edit screens) and connects the app to the SharePoint list data source, significantly reducing development time. This feature is ideal for users who need rapid deployment of apps without manual design work.

Canvas app from blank requires the app creator to design the layout and user interface from scratch. While it provides full flexibility in design and functionality, it does not automatically connect to data or generate screens. This manual approach is time-consuming and not suitable for quickly generating an app from a SharePoint list.

Model-driven apps rely on Dataverse tables rather than SharePoint lists. They are based on data structure and relationships within Dataverse, automatically generating forms, views, and navigation based on the underlying schema. Therefore, model-driven apps cannot directly consume a SharePoint list as a data source without additional steps such as data migration.

Portal apps are designed to create websites that allow external users to interact with data. While they are powerful for external-facing scenarios, they do not automatically generate mobile or desktop apps from SharePoint lists. The requirement in the question is to build an app directly from SharePoint, which makes the generated app feature the correct choice.

Question 65: 

Which component of Power Virtual Agents determines how the bot responds when a user asks a question?

A) Topics
B) Entities
C) Variables
D) Triggers

Answer:  A) Topics

Explanation:

In Power Virtual Agents, topics are the central component that defines how a chatbot interacts with users. They determine the conversation paths, the responses provided, and how the bot interprets user intent. Each topic includes trigger phrases, conditions, and responses, allowing the bot to understand when a user asks a question or expresses a particular intent. Trigger phrases are examples of what users might type or say to engage the bot, helping it recognize the relevant topic to respond to. Conditions within a topic can further guide the conversation based on specific inputs or context, and the responses are the actual content the bot delivers to the user. By combining these elements, topics allow the bot to provide meaningful, structured, and context-aware interactions. They form the backbone of the bot’s logic, making them critical for ensuring that the bot behaves in a way that aligns with user expectations.

Entities are used to extract specific pieces of information from user input, such as dates, names, locations, or numerical values. These pieces of data are often required to complete tasks or provide more precise responses, such as booking a meeting or retrieving customer details. While entities play an essential role in capturing structured information, they do not determine what the bot will say in response. Instead, they support the conversation by providing data that topics can use to make decisions or customize responses. Entities work in tandem with topics but are not responsible for controlling the flow or content of the conversation itself.

Variables in Power Virtual Agents are temporary storage containers that hold information during a conversation. They can store user input, results from actions, or calculations performed by the bot. Variables are essential for maintaining context throughout a conversation, enabling the bot to reference prior inputs and make decisions based on previous interactions. However, variables alone do not define the bot’s responses. They provide information that topics can use, but the logic for how the bot replies is determined by the topic, not the variable itself.

Triggers are the initial conditions that start a topic. They are typically specific phrases or keywords that the bot uses to recognize when to begin a conversation path. While triggers are critical for initiating interactions, they do not contain the full conversation logic or response content. Triggers only serve as entry points, after which the topic takes over to manage the dialogue. Since the question focuses on which component determines the bot’s responses, topics are the correct answer because they encapsulate the triggers, the response logic, and the conversation paths, ultimately guiding how the bot interacts with users.

Question 66: 

Which Power BI feature helps users compare different report states during presentations?

A) Bookmarks
B) Tooltips
C) Drill-through
D) Filters

Answer:  A) Bookmarks

Explanation:

Bookmarks in Power BI are a powerful feature designed to capture the exact state of a report at any given moment. This includes filters, slicers, visual selections, drill positions, and the layout of visuals on the canvas. Essentially, a bookmark acts like a snapshot of the report, allowing users to return to a particular configuration quickly or present different perspectives without manually resetting visuals each time. This makes them especially useful in scenarios where you need to guide an audience through multiple views of data during presentations, compare insights, or highlight specific findings sequentially.

Tooltips, by contrast, provide contextual information when a user hovers over a visual. While tooltips enhance the understanding of data points by displaying additional detail such as underlying values or calculations, they do not retain the state of the report. Hovering over one visual may trigger a tooltip for a specific data point, but this does not affect the report layout or filter selections, so it cannot be used to revisit or present different report states.

Drill-through allows users to navigate from a summary page to a more detailed page that is focused on a particular data dimension, such as a specific product, customer, or region. While drill-through is useful for exploring data in more depth, it does not preserve multiple states for comparison purposes. Each drill-through action is designed to take the user to a focused view rather than capture and return to previous report configurations, so it cannot serve the purpose of presenting or comparing multiple states within the same session.

Filters are used to adjust the data displayed in visuals based on certain criteria, such as date ranges, categories, or numerical thresholds. Filters are essential for exploring specific subsets of data, but they are dynamic changes applied at runtime and do not store states for later reference. Unlike bookmarks, which save both the visual arrangement and applied filters, standard filters only change what is currently displayed without creating reusable snapshots. Considering all these factors, bookmarks are the feature specifically intended to capture and revisit different report states, making them the correct choice.

Question 67: 

Which type of Dataverse column stores Yes/No values?

A) Two-options
B) Choice
C) Lookup
D) Currency

Answer:  A) Two-options

Explanation:

Two-options columns in Dataverse are designed to store binary values, typically representing Yes/No, True/False, or On/Off states. This type of column is simple but highly effective for fields where only one of two possible states can exist. The interface often presents these values as toggle switches or radio buttons, making them easy for end users to select. Because these columns are inherently binary, they are the correct solution when a developer or analyst needs to store and reference data that represents a simple dichotomy.

Choice columns, on the other hand, provide multiple predefined options that a user can select from. While choice columns are versatile and useful for categorization or multi-state selection, they are not inherently binary. Each choice column contains a list of options that may exceed two, so they are not suitable for storing simple Yes/No values. Developers often use choice columns when there are three or more states, like Low/Medium/High, instead of a simple binary condition.

Lookup columns link one table to another, enabling relational data modeling within Dataverse. They allow a record to reference another record in a different table, which is useful for maintaining relationships between entities. However, lookup columns cannot store simple Boolean values like Yes/No. They are relational in nature, so their primary function is connecting data tables rather than storing binary states.

Currency columns are designed to store financial values, supporting decimal precision and currency formatting. They are not applicable for storing Yes/No or Boolean values. Currency columns serve the purpose of numeric calculations or financial analysis and are unrelated to binary decision-making fields. Given these distinctions, the two-options column is the correct type for storing Yes/No values in Dataverse because it directly supports binary selection and provides a simple interface for users to choose between two states.

Question 68: 

Which Power Automate flow type is triggered manually by a user?

A) Instant flow
B) Automated flow
C) Scheduled flow
D) Desktop flow

Answer:  A) Instant flow

Explanation:

Instant flows are designed to be triggered manually by a user, either through the Power Automate portal, mobile app, or directly from Power Apps. Users can initiate these flows on demand, typically by pressing a button or selecting an option. This provides control and flexibility for scenarios where automation should only occur when explicitly requested, such as sending a report, triggering notifications, or performing repetitive administrative tasks that need user oversight.

Automated flows run in response to specific triggers, such as receiving an email, creating a record in Dataverse, or updating a SharePoint item. These flows operate automatically without user intervention and are ideal for processes that need to react to events as they occur. Since the question specifies manual initiation, automated flows are not suitable in this context because they are triggered automatically by system events rather than human action.

Scheduled flows execute based on time intervals or recurrence patterns. They can be set to run daily, weekly, or at custom intervals. Scheduled flows are particularly useful for routine tasks like generating reports, sending reminders, or updating datasets. While they provide automation based on time, they do not allow immediate manual triggering on demand, making them inconsistent with the requirement of a manually triggered flow.

Desktop flows are designed to automate tasks on a local machine, often using robotic process automation (RPA) to control desktop applications. While they can be triggered manually, they are primarily intended for local automation rather than cloud-based or cross-service triggers. Therefore, although desktop flows can support manual execution, the specific type in Power Automate that is universally recognized for user-initiated manual triggering is the instant flow.

Question 69: 

Which Power BI capability allows users to build reusable ETL processes across multiple datasets?

A) Dataflows
B) Datasets
C) Queries
D) Slicers

Answer:  A) Dataflows

Explanation:

Dataflows in Power BI are designed to create reusable ETL (extract, transform, load) processes using Power Query logic. They allow users to define a series of data transformation steps once and then apply the same logic across multiple reports or workspaces. This centralized approach promotes consistency in data preparation and reduces redundancy, as the same cleaned and transformed data can be consumed by multiple datasets without having to recreate transformations in each report.

Datasets store cleaned and structured data ready for visualization but are primarily report-specific. While datasets are essential for building visuals and dashboards, they do not inherently provide reusable ETL processes. Any transformations applied to a dataset remain tied to that dataset and cannot be easily shared across multiple projects, limiting reusability compared to dataflows.

Queries within Power BI are used to shape and transform data in a report-specific context. They are essential for preparing data for visuals but are limited to the dataset or report they reside in. Queries do not provide cross-report or cross-workspace reusability by default, which means they are not suitable for building reusable ETL processes intended for broader application.

Slicers are visual elements used to filter data interactively within a report. They allow end users to dynamically change what is displayed but do not provide any data transformation or ETL capabilities. Slicers are strictly for filtering and presentation purposes and have no role in creating reusable extraction or transformation logic. Therefore, dataflows are the correct choice, as they are explicitly designed to create shared ETL pipelines that can be applied consistently across multiple datasets and reports.

Question 70: 

Which Power Apps feature provides a responsive layout automatically based on Dataverse tables?

A) Model-driven app
B) Canvas app
C) AI Builder
D) Component library

Answer:  A) Model-driven app

Explanation:

Model-driven apps in Power Apps automatically generate responsive layouts based on Dataverse tables and their underlying metadata. The system uses the table schema, relationships, and business rules to create user interfaces without requiring extensive manual design. This approach allows developers and business users to quickly deploy applications that are functional, consistent, and optimized for different devices, including desktop and mobile. The focus on data-first design ensures that the app adapts to the structure of the data while maintaining usability.

Canvas apps provide full control over the visual design but require users to manually create layouts. While this flexibility is advantageous for highly customized interfaces, it does not automatically adjust layouts based on the underlying data. Developers must design screens, place controls, and handle responsiveness manually, making canvas apps more labor-intensive for creating adaptive designs.

AI Builder integrates artificial intelligence capabilities into apps, such as object detection, form processing, or predictions. While it adds intelligence to an app’s functionality, it does not handle the automatic generation of responsive layouts. AI Builder enhances data analysis and automation but does not influence the app’s UI structure.

Component libraries store reusable UI components for canvas or model-driven apps. They promote consistency and faster development by providing pre-built elements like buttons, forms, or cards. However, component libraries themselves do not automatically generate responsive layouts from Dataverse tables. They are more of a design aid than a full app generation tool. Considering all these points, model-driven apps are the correct choice because they are designed to provide responsive, data-driven interfaces automatically based on the Dataverse schema.

Question 71: 

Which Power Automate element determines what happens after a trigger fires?

A) Actions
B) Expressions
C) Variables
D) Connectors

Answer:  A) Actions

Explanation:

Actions in Power Automate are the core building blocks that define the steps a flow takes after a trigger is activated. They can perform tasks such as sending emails, creating records, updating data, posting messages, or calling APIs. Actions are directly tied to the outcome of a flow and execute sequentially or conditionally based on logic. Without actions, a flow would have a trigger but no operations to perform, making actions essential for the functional execution of a workflow. They define not only what happens but also the sequence and the conditions under which each step occurs.

Expressions, on the other hand, are formulas used inside actions to manipulate data. They allow for dynamic content, calculations, string manipulations, or conditional logic, but they do not determine the high-level steps that occur after a trigger fires. Expressions modify or analyze data, but they cannot perform standalone operations outside an action. They work within actions to customize behavior, not as primary operational elements of the flow itself.

Variables serve to store temporary data for use within a flow. They are useful for keeping track of counters, storing user input, or managing state across multiple steps. While variables are important for storing and referencing values, they do not execute tasks or define what happens in response to a trigger. They are passive containers rather than active operational steps.

Connectors provide access to external systems like SharePoint, Microsoft 365, SQL Server, or third-party services. They enable actions to interact with data sources, but they do not determine the logic of a flow themselves. Connectors are the means by which actions communicate with systems, rather than the elements that perform steps.

Because the question asks specifically about what determines what happens after a trigger fires, the correct answer is actions. Actions directly execute tasks, use expressions and variables as needed, and leverage connectors to perform operations across systems. They are the fundamental elements that shape the flow’s behavior following a trigger.

Question 72: 

Which Power BI security method ensures only certain users can view specific rows of data?

A) Row-level security
B) Workspace roles
C) App permissions
D) Data classification

Answer:  A) Row-level security

Explanation:

Row-level security in Power BI allows report designers to control access to data at the individual row level. It defines rules or roles that filter data so that users only see the data relevant to them. For example, a salesperson might see only their region’s sales, while a manager could see all regions. This mechanism is applied within the dataset, meaning that the underlying data model enforces visibility rules and ensures data is appropriately restricted.

Workspace roles in Power BI control the permissions that users have for content within a workspace. They determine whether users can view, edit, or publish reports and dashboards but do not filter data within the reports themselves. Workspace roles manage collaboration and access at a higher level than row-level security. They ensure users can access content, but not necessarily which data rows they can see.

App permissions control access to published Power BI apps. These permissions define who can open or interact with an app, but they do not filter the content within a dataset. App permissions are about distribution and accessibility rather than granular security at the data row level.

Data classification in Power BI is a labeling system that identifies data sensitivity, such as confidential or public information. It helps with compliance and governance but does not restrict what rows of data a user can view. Classification is informational and policy-driven, not enforcement-based.

The correct answer is row-level security because it specifically addresses the requirement of restricting access to certain rows based on user roles. Unlike workspace roles, app permissions, or data classification, row-level security enforces data visibility rules directly within the dataset, ensuring that each user sees only the appropriate information.

Question 73: 

Which Power Apps control displays a scrollable list of multiple records?

A) Gallery
B) Label
C) Dropdown
D) Date picker

Answer:  A) Gallery

Explanation:

The gallery control in Power Apps is designed to display multiple records in a scrollable, flexible layout. It can present data in vertical, horizontal, or flexible arrangements, and it allows users to interact with each item individually. Galleries are essential for building apps that need to display lists of items from a data source such as SharePoint, Dataverse, or SQL. They support templates and dynamic data binding, enabling apps to scale across multiple records without manually creating separate controls.

Labels are simple controls that display static or dynamic text. They are suitable for showing single values or calculations but cannot display multiple records in a structured or scrollable format. Labels are read-only and lack interactive capabilities for multiple items.

Dropdowns provide a compact way for users to select one value from a list of options. While they can show multiple choices, they do not allow scrollable displays of complex records or multiple fields per record. Dropdowns are best suited for selection, not for full record presentation.

Date pickers allow users to choose a date from a calendar interface. They serve a specific purpose and do not display lists of records. Their functionality is focused on date input rather than presenting datasets.

Galleries are the only control that meets the requirement for displaying multiple scrollable records. They can handle dynamic data, enable scrolling, and support interactions for each record, making them ideal for building data-centric apps where users need to browse through multiple entries efficiently.

Question 74: 

Which feature of Power Virtual Agents detects relevant user intent from text input?

A) AI-based natural language understanding
B) Variables
C) Skills
D) Sessions

Answer:  A) AI-based natural language understanding

Explanation:

AI-based natural language understanding (NLU) in Power Virtual Agents is the technology that interprets what a user is trying to communicate. It analyzes user input, identifies intent, and maps it to predefined topics or responses. NLU allows chatbots to understand a wide range of phrasing and synonyms, making interactions more flexible and human-like. This capability ensures that users receive accurate answers even if they do not use exact trigger phrases.

Variables in Power Virtual Agents store information collected during a conversation, such as names, numbers, or choices. While they are essential for dynamic responses and logic within a bot, variables do not analyze or interpret user intent. They are reactive storage mechanisms, not processing engines.

Skills extend the functionality of a bot, enabling it to call external services or perform specialized actions. Skills provide capabilities but do not process the natural language input themselves. They rely on NLU to determine what actions are necessary.

Sessions track the state of an ongoing conversation. They allow a bot to remember context and manage flow continuity, but they do not determine the meaning of user input. Sessions maintain conversation flow but cannot interpret intent or select topics.

AI-based natural language understanding is the correct answer because it directly addresses the need to detect intent from text input. It interprets user messages, guides topic selection, and drives the bot’s response logic, which none of the other options provide.

Question 75: 

Which Power Automate action repeats a set of steps for each item in a list?

A) Apply to each
B) Terminate
C) Compose
D) Scope

Answer:  A) Apply to each

Explanation:

The “Apply to each” action in Power Automate loops through a collection of items and performs specified actions on each element individually. This is essential when processing datasets, such as sending emails to a list of users or updating multiple records. The loop executes sequentially or in parallel depending on configuration and ensures that each item is handled consistently according to the defined actions.

Terminate is used to stop a flow at a specific point. It can indicate success, failure, or cancellation but does not perform repeated operations or iterate through items. Terminate is a control mechanism rather than a processing loop.

Compose creates a single value from expressions or formulas but does not iterate over multiple items. It is used for data manipulation or aggregation but cannot repeat actions automatically across a collection.

Scope groups multiple actions into a single container, helping organize flows and manage error handling. While useful for structuring flows, Scope does not inherently repeat actions for each item in a list.

Apply to each is the correct choice because it explicitly handles iteration over a collection of data. It enables repetition of actions, leveraging variables and expressions for dynamic behavior, while other options either manage flow termination, data creation, or grouping rather than looping.

Question 76: 

Which tool within Power BI is used to create calculations that reference multiple tables using relationships?

A) DAX
B) M language
C) Power Query
D) Filters

Answer:  A) DAX

Explanation:

DAX, which stands for Data Analysis Expressions, is a formula language in Power BI designed specifically for creating calculations that operate across multiple tables. It allows users to leverage relationships between tables to compute metrics that involve aggregation, filtering, and contextual calculations. DAX formulas are used to define measures, calculated columns, and calculated tables, making it a crucial tool for advanced data modeling. When calculations depend on understanding relationships between tables, DAX can evaluate these relationships to return accurate and context-sensitive results.

The M language, in contrast, is used primarily in Power Query for data transformation. While M can reshape and clean data, such as merging tables or transforming columns, it does not inherently perform calculations that rely on relationships between tables after the data is loaded into the model. M’s operations happen before the data reaches the analytical model, so it does not support relational calculations in the same way DAX does.

Power Query itself is the interface in Power BI where M language is applied. Users can use it to extract, transform, and load data from various sources. Power Query is excellent for preparing data, removing duplicates, changing data types, and combining tables. However, it is not a tool designed for defining measures or performing calculations that respect table relationships in the final data model.

Filters in Power BI allow users to limit the data that appears in visuals, pages, or the report as a whole. They control the visibility of data but do not create calculations or perform relational computations. Filters cannot evaluate data across multiple tables to create new metrics. Therefore, considering the need to perform calculations referencing multiple tables using relationships, DAX is the correct tool because it is designed specifically to work within the relational model of Power BI and enable dynamic, context-aware calculations.

Question 77: 

Which Power Apps feature supports reusing UI elements across multiple apps?

A) Component library
B) Patch function
C) Data cards
D) Connectors

Answer:  A) Component library

Explanation:

Component libraries in Power Apps are collections of reusable components, including buttons, text boxes, forms, or entire layouts. Once a component is created in a library, it can be shared across multiple apps, ensuring consistency in design and functionality. Component libraries help developers save time and reduce duplication of effort, especially when creating multiple apps that require similar UI elements. They can also be updated centrally so that changes propagate to all apps using the component.

The Patch function in Power Apps is used for modifying or creating records in a data source. While it is a powerful tool for interacting with data, it does not relate to reusing UI elements. Patch focuses on backend data operations, not user interface components.

Data cards are individual UI elements used within forms to display or edit fields from a data source. They are bound to specific data fields, and although they can be customized, they are not designed for reuse across multiple apps unless manually recreated or included in a component.

Connectors integrate apps with external data sources or services, such as SharePoint, SQL Server, or Dataverse. Connectors facilitate communication between apps and data but do not provide reusable UI elements. Therefore, the component library is the only option designed specifically for storing and reusing UI elements across multiple apps.

Question 78: 

Which Dataverse feature ensures data integrity by linking a record to another table?

A) Lookup column
B) Choice column
C) Currency column
D) Text column

Answer:  A) Lookup column

Explanation:

A lookup column in Dataverse establishes a relationship between tables, linking a record in one table to a record in another. This allows for maintaining referential integrity and enables more complex data modeling. Lookups enforce connections so that data remains consistent, and they facilitate navigation and reporting across related tables. They are essential for scenarios where one entity references another, such as linking an order to a customer.

Choice columns, on the other hand, provide a predefined set of options for a field. They are useful for standardizing input but do not create relationships between tables. Choice columns cannot reference another record or enforce data integrity across tables.

Currency columns store monetary values, allowing calculations involving amounts, totals, or financial metrics. They serve a data-type function rather than establishing relationships between records.

Text columns store string data such as names, descriptions, or codes. Like currency columns, they are simple data storage fields and do not link to other tables. Given the need to ensure data integrity by creating a reference to another table, lookup columns are the correct choice.

Question 79: 

Which Power BI feature enables drilling into detailed data on a separate page when clicking a visual?

A) Drill-through
B) Bookmark
C) Tooltip
D) Slicer

Answer:  A) Drill-through

Explanation:

Drill-through in Power BI is a feature that enables users to navigate from a summarized visual on one report page to a separate page that provides more detailed information about a specific data point. This capability is particularly useful for analysts who need to explore granular insights without cluttering the main report page with excessive detail. By using drill-through, report creators can design a focused page containing visuals and metrics that are relevant to the selected item, allowing for a more in-depth analysis of the data. For example, clicking on a bar representing sales in a specific region can take the user to a dedicated page showing product-level sales, customer segments, or trend analysis for that region. This approach keeps summary pages clean while still offering access to detailed data when needed.

Bookmarks, while often mentioned in the context of navigation, serve a different purpose. They capture and save the current state of a report page, including applied filters, slicers, and visual arrangements. Bookmarks are helpful for storytelling, allowing report creators to highlight key insights or create guided navigation through a report. However, bookmarks do not provide a mechanism for drilling into separate pages based on the selection of a visual. They are more about saving and restoring a specific view rather than offering dynamic navigation for detailed analysis.

Tooltips are another feature in Power BI that provides additional context, but they operate differently from drill-through. Tooltips appear as small popup windows when a user hovers over a data point in a visual. They can display extra information such as values, percentages, or even images, which adds context to the visual without changing pages. Tooltips are useful for quick reference and summary insights, but they do not create a dedicated page for detailed analysis. Users cannot interact with a tooltip to explore deeper datasets or additional visuals beyond the summary information it provides.

Slicers are visual elements that allow users to filter data interactively on a report page. They provide a convenient way to focus on specific categories or ranges of data by updating visuals on the same page dynamically. While slicers help narrow down the data shown in a report, they do not provide navigation to a separate page for more detailed examination. They control visibility but do not enable a structured drill-down experience.

Considering these options, drill-through is the correct feature for accessing detailed data on a separate page because it combines interactive navigation with context-sensitive filtering, allowing users to seamlessly move from a summary visual to a dedicated page for deeper analysis while maintaining clarity and focus on the main report.

Question 80: 

Which Power Automate capability helps ensure sensitive data like passwords stays hidden in flows?

A) Secure inputs and outputs
B) Variables
C) Scopes
D) Do until

Answer:  A) Secure inputs and outputs

Explanation:

Secure inputs and outputs in Power Automate hide sensitive data, such as passwords or API keys, from appearing in the run history. This feature is crucial for maintaining security and compliance, especially when flows involve confidential information. It ensures that anyone reviewing the flow’s execution cannot see sensitive details, reducing the risk of data exposure.

Variables in Power Automate are used to store and manipulate data during the execution of a flow. While they can hold values, they are not inherently secure, and sensitive data stored in a variable can still be visible unless additional security measures are applied.

Scopes group multiple actions into a single container, helping with organization and error handling. Scopes can improve readability and structure but do not provide security features for hiding sensitive inputs or outputs.

Do until loops repeatedly execute actions until a condition is met. They are used for controlling flow logic rather than protecting confidential information. Considering these options, secure inputs and outputs is the correct choice because it is specifically designed to mask sensitive data in flows.