Free DP-500 Exam Braindumps (page: 5)

Page 4 of 46
View Related Case Study

How should you configure the Power BI dataset refresh for the dbo.SalesTransactions table?

  1. an incremental refresh of Product where the ModifiedDate value is during the last three days.
  2. an incremental refresh of dbo.SalesTransactions where the SalesDate value is during the last three days.
  3. a full refresh of all the tables
  4. an incremental refresh of dbo.SalesTransactions where the SalesDate value is during the last hour.

Answer(s): B

Explanation:

The sales data in SQLDW is updated every 30 minutes. Records in dbo.SalesTransactions are updated in SQLDW up to three days after being created. The records do NOT change after three days.



View Related Case Study

What should you configure in the deployment pipeline?

  1. a backward deployment
  2. a selective deployment
  3. auto-binding
  4. a data source rule

Answer(s): D

Explanation:

Development Process Requirements
Litware identifies the following development process requirements:
SQLDW and datalake1 will act as the development environment. Once feature development is complete, all entities in synapseworkspace1 will be promoted to a test workspace, and then to a production workspace.
Power BI content must be deployed to test and production by using deployment pipelines.

Create deployment rules
When working in a deployment pipeline, different stages may have different configurations. For example, each stage can have different databases or different query parameters. The development stage might query sample data from the database, while the test and production stages query the entire database.

When you deploy content between pipeline stages, configuring deployment rules enables you to allow changes to content, while keeping some settings intact. For example, if you want a dataset in a production stage to point to a production database, you can define a rule for this. The rule is defined in the production stage, under the appropriate dataset. Once the rule is defined, content deployed from test to production, will inherit the value as defined in the deployment rule, and will always apply as long as the rule is unchanged and valid.

You can configure data source rules and parameter rules.

Incorrect:
Not B: if you already have a steady production environment, you can deploy it backward (to Test or Dev, based on your need) and set up the pipeline. The feature is not limited to any sequential orders.


Reference:

https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-get-started#step-4---create-deployment-rules



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You need to populate the CustomersWithProductScore table.

How should you complete the stored procedure? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Please note: there may be another answer; FLOAT. What do you say about the selected answer? Please comment below or message me. Thank you


Reference:

https://docs.microsoft.com/en-us/sql/t-sql/queries/predict-transact-sql



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You need to create a measure to count orders for the market basket analysis.

How should you complete the DAX expression? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: SalesTransactions[Order Number]
Scenario: Perform market basket analysis to understand which products are commonly purchased in the same transaction.

Order Number to analyze products within the same transactions, that is within the same Order.

Note: SUMX SUMMARIZE specifies the relationship to be used in a specific calculation as the one that exists between columnName1 and columnName2.

Box 2: CALCULATETABLE
CALCULATETABLE evaluates a table expression in a modified filter context.

Note: USERELATIONSHIP can only be used in functions that take a filter as an argument, for example: CALCULATE, CALCULATETABLE, etc.

Incorrect: NOT CALCULATE
There's also the CALCULATE function. It performs exactly the same functionality, except it modifies the filter context applied to an expression that returns a scalar value.

Box 3: INTERSECT
INTERSECT returns the row intersection of two tables, retaining duplicates.

Syntax: INTERSECT(<table_expression1>, <table_expression2>)

Incorrect:
Not KEEPFILTERS:
Does not match the syntax: KEEPFILTERS(<expression>)

Not CROSSJOIN:
CROSSJOIN teturns a table that contains the Cartesian product of all rows from all tables in the arguments. The columns in the new table are all the columns in all the argument tables.


Reference:

https://docs.microsoft.com/en-us/dax/calculatetable-function-dax
https://docs.microsoft.com/en-us/dax/userelationship-function-dax
https://docs.microsoft.com/en-us/dax/intersect-function-dax






Post your Comments and Discuss Microsoft DP-500 exam with other Community members: