Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A Common Data Service (CDS) environment has two custom entities named Building code and Work item. Building code has a code date custom field and Work item has an elapsed time custom field. Construction workers use a consolidated custom form with data from both entities to fill.in their daily work items.
A JavaScript library is used with these custom entities and fields to apply complex logic.
You need to ensure that the JavaScript library continues to function as originally designed if other developers expand the environment.
Solution:
* In the Building code form, add the JavaScript library in the events tab and the Code date field to the non-event dependencies.
* In the Work item form, add the JavaScript library in the Events tab and the Elapsed time field to the non-event dependencies.
Does the solution meet the goal?

• A. Yes
• B. No

解説: (Fast2test メンバーにのみ表示されます)

Five high schools test a custom app from AppSource. They provide feedback that the Course credit entity should include additional fields that cover information shared by the schools.
You do not have access to each high school organization.
Each high school administrator must be able to apply the updates to the Course credit entity.
You need to deliver a custom program that creates the additional fields.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation:
Step 1: Call the login logic.
Step 2: Retrieve the Course credit entity metadata by using RetrieveEntityRequest with EntityFilters = Attributes and LogicalName The RetrieveEntityRequest.EntityFilters property gets or sets a filter to control how much data for the entity is retrieved.
Step 3: Define the AttributeMetaData for each new field.
Step 4: Call the RetrieveAttributeRequest with LogicalName for each new field.
The RetrieveAttributeRequest contains the data that is needed to retrieve attribute metadata.
Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.messages.retrieveentityrequest.entityfilters?view=dynamics-general-ce-9

A company is building a new model-driven app.
The app must integrate with a number of on-premises and cloud solutions. No VPNs are in place.
You need to determine the method for each integration.
Which methods should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Webhook
With Common Data Service, you can send data about events that occur on the server to a web application using webhooks. Webhooks is a lightweight HTTP pattern for connecting Web APIs and services with a publish/subscribe model.
Box 2: Azure Event Hub
Azure Event Hubs is a big data pipeline. It facilitates the capture, retention, and replay of telemetry and event stream dat a. The data can come from many concurrent sources.
It has the following characteristics:
* low latency
* capable of receiving and processing millions of events per second
* at least once delivery
Box 3: Plugin
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/use-webhooks
https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

A company creates a custom connector to use in a flow named Search Company.
When this custom connector is used, requests must be redirected to a different endpoint at runtime.
You need to apply a policy to the custom connector to route calls to a different endpoint.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation:
Step 1: Select the Search Company custom connector in the Microsoft Flow portal under Custom connectors and select edit.
Login to the Microsoft Flow portal, and on right top corner click on the settings icon and then click on custom connectors option.
Step 2: Select the Definition tab
Policy template are available only for custom connectors. To use a policy template, open Power Automate portal and either create a new custom connector or edit an existing one.
In the custom connector wizard, select the Definition page.
From the Definition page, select New Policy.
Etc.
Step 3: Select New Policy
Reference:
https://docs.microsoft.com/en-us/connectors/custom-connectors/policy-templates

A company is preparing to go live with their Dynamics 365 Customer Engagement solution, but first they need to migrate data from a legacy system. The company is migrating accounts in batches of 1,000.
When the data is saved to Dynamics 365 Customer Engagement, the IDs for the new accounts must be output to a log file.
You have the following code:

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Yes
Box 2: Yes
Even when ReturnResponses is false, the Responses collection will not be empty if errors are returned. If errors are returned, there will be one response item in the collection for each processed request that returned a fault and Fault will be set to the actual fault that occurred.
Box 3: No
ContinueOnError, here set to true: when true, continue processing the next request in the collection even if a fault has been returned from processing the current request in the collection. When false, do not continue processing the next request.
Box 4: Yes
Even when ReturnResponses is false, the Responses collection will not be empty if errors are returned. If errors are returned, there will be one response item in the collection for each processed request that returned a fault and Fault will be set to the actual fault that occurred.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/org-service/execute-multiple-requests