Question 570 A multi-tenant customer model uses USERPRINCIPALNAME() in a DAX role filter. One staff member’s UPN changed after a domain migration and now sees no assigned accounts. What is the safest correction? Hardcode the employee’s previous UPN into every fact row Grant the employee workspace Member so the role filter stops applying Use a public report link rather than fix identity mapping Update the authorized identity-to-account mapping for the actual signed-in UPN and test the role as the user Explanation Correct Answer D:Dynamic RLS resolves the current authenticated UPN and joins it to the allowed account mapping. The mapping must match that identity. Incorrect Answers A:Old hardcoded identities become stale and risk incorrect authorization. B:Member bypasses Viewer RLS and adds editing rights instead of repairing authorization data. C:Public access would remove the intended user-specific control.
Question 571 A university plots student ages in ten-year intervals. The registrar wants to distinguish cohorts 20–24 and 25–29. What change gives the needed resolution? Increase bin width to 25 years Hide the age field and use a single count Card Change Age to a column of unrelated random integers Use five-year numeric bins with well-defined boundaries for the same age values Explanation Correct Answer D:Narrower bins separate the requested five-year groups; wider bins combine them. Incorrect Answers A:Twenty-five-year bins blur the cohorts even more. B:One total removes the distribution. C:Random replacements break age meaning.
Question 572 A healthcare analytics team enables report-reader personalization, allowing approved staff to swap a chart from bar to line. An employee expects this to reveal fields hidden by their permissions. What principle must the report owner enforce? Personalization changes authorized visual presentation and must not bypass dataset permissions or RLS Personalization automatically grants Build and unrestricted model access to every Viewer Personalization removes all semantic-model row restrictions Personalization alters the raw source and writes the changed chart type back to tables Explanation Correct Answer A:The feature is for per-reader visual exploration; ordinary access-control rules and model permissions still determine usable fields and rows. Incorrect Answers B:Visual personalization does not by itself grant a new security role or unrestricted Build rights. C:RLS is enforced by the semantic model independently of report visual choices. D:Personalization is a consumer-facing report interaction, not a source-database mutation.
Question 573 A user creates a weekly report subscription for a colleague who lacks permission to open the underlying report. What should be corrected before expecting useful delivery? Put a shared database password in the email subject Add the colleague as workspace Admin by default Confirm appropriate content permissions and licensing/capacity for the recipient Disable semantic-model RLS before sending Explanation Correct Answer C:Email delivery does not substitute for report/model access and entitlement requirements. Incorrect Answers A:Passwords in email are unsafe and do not create report rights. B:Workspace Admin would overgrant authoring control. D:RLS should remain enforced for consumers.
Question 574 A hospital quality measure is DIVIDE([LateEncounters], [AllEncounters]) and is formatted as Percentage with zero decimals. This month it sees 18 late encounters out of 60. What should the card display? 0.3% because DIVIDE returns a fraction 18% because there were 18 late records 42%, subtracting the late count from the total 30% Explanation Correct Answer D:18/60 = 0.30; Percentage format multiplies the display by 100 to show 30%. Incorrect Answers A:0.3 is the underlying decimal; when formatted as Percentage it displays 30%, not 0.3%. B:The count 18 has no percentage meaning without the total. C:The count 42 is on-time encounters and the corresponding share would be 70%, not 42%.
Question 575 A model has QueryA referencing QueryB and QueryB referencing QueryA. Both were created from an earlier common stage, and refresh now reports a cyclic reference error. What should be changed? Increase the report font size to allow the cycle to render Append QueryA to itself until the cycle resolves Disable RLS on the model and retry Break the circular dependency by having both outputs reference an upstream stage without referencing each other Explanation Correct Answer D:Power Query dependencies must form an acyclic evaluation graph; mutual references cannot be resolved. Incorrect Answers A:Visual fonts do not affect M dependency graphs. B:Self-appends add more dependencies and data, not fix a cycle. C:Row security is unrelated to query reference resolution.
Question 576 A financial cooperative has DisbursementDate transactions and wants Year-to-Date DAX measures and an unbroken month axis, including months with no transactions. The organization closes its fiscal year on June 30 rather than December 31. A conventional year-to-date measure currently rolls on January 1. What change addresses the boundary? Use a fiscal-aware time-intelligence calculation or year-end date configured for June 30 Change only the label of the year visual Delete all dates in July Use a currency format string on the measure Explanation Correct Answer A:Time-intelligence expressions must use the intended fiscal-year boundary to reset accumulations at June 30. Incorrect Answers B:Year captions do not alter accumulated date ranges. C:Removing dates loses transaction history. D:Numeric format has no effect on date filter context.
Question 577 A BI analyst for a transit authority wants to test whether branch footfall and total Fare tend to increase together, while showing each of 80 branches as one point. Each branch also has a numeric employee-count measure, and the analyst wants it visible alongside the two scatter axes. Which encoding extends the original chart? Bubble size bound to employee count Line chart replacing the two numeric axes A single total card A map without coordinates Explanation Correct Answer A:Bubble size is a third numeric channel on the scatter chart. Incorrect Answers B:A line does not preserve the branch-wise two-axis relationship. C:A card collapses branch-level detail. D:A map needs spatial location, not three nongeographic measures.
Question 578 A confidential REST source requires a token. An author suggests choosing Anonymous in Power Query and hardcoding the token in a report title. What is the security problem? Authentication secrets must be configured with a supported credential mechanism, not exposed through report content Anonymous connections always enforce the same restrictions as authenticated ones Putting tokens in visible report text is a recommended secret-management method The app audience automatically encrypts a visible title for each viewer Explanation Correct Answer A:Source credentials belong in managed connection/authentication settings and should not be exposed in report UI. Incorrect Answers B:Anonymous access cannot prove an identity required by the source. C:Visible titles reveal tokens to people who can view the report. D:Audience scoping is not per-title secret encryption.
Question 579 A live operations report uses a supported DirectQuery model. The author needs the report page to requery at a configured interval while it remains open. Which feature is suited to the requirement? A new date-table relationship to force constant queries Automatic page refresh with an interval supported by the model and capacity Scheduled nightly Import refresh as the only update path A static report bookmark containing the last observed values Explanation Correct Answer B:Automatic page refresh can rerun eligible report queries on a configured cadence; the interval depends on the dataset and capacity settings. Incorrect Answers A:Relationships control data filtering, not periodic query scheduling. C:Nightly Import refresh is not automatic minute-by-minute page requerying while open. D:Bookmarks restore report state but cannot continuously acquire new source values.
Question 580 A maintenance system emits a separate row whenever TaskID T8 changes from Open to Assigned to Resolved. Operations needs time-to-resolution and transition history. Which source design is appropriate? Retain the state-change events with TaskID and event time/version; deduplicate only true duplicate deliveries Remove duplicates on TaskID and keep one arbitrary state Replace all event times with a single timestamp Append each state change as a new task with an unrelated randomly generated TaskID Explanation Correct Answer A:Repeated task IDs across events reflect history, not automatically duplicate records. Incorrect Answers B:Dropping transitions prevents duration and status-sequence calculations. C:Constant times destroy the transition chronology. D:Random task IDs break linkage among one task’s states.
