Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft PL-400 Exam - Topic 2 Question 78 Discussion

You are deploying a Power Apps app that uses the custom connector for ServiceNow.The app loads very slowly for some users. You determine that all records from ServiceNow are being retrieved for every user.The app must load only incidents that are assigned to each user.You need to limit the number of records that the connector returns.What should you do?
C) Apply the Azure APIM parameter and D) Apply a connector policy template
A) Apply a Lifecycle Services asset scope
B) Apply a business process flow

Microsoft PL-400 Exam - Topic 2 Question 78 Discussion

Actual exam question for Microsoft's PL-400 exam
Question #: 78
Topic #: 2
[All PL-400 Questions]

You are deploying a Power Apps app that uses the custom connector for ServiceNow.

The app loads very slowly for some users. You determine that all records from ServiceNow are being retrieved for every user.

The app must load only incidents that are assigned to each user.

You need to limit the number of records that the connector returns.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C, D

C: The change tracking feature in Microsoft Dataverse provides a way to keep the data synchronized in an efficient manner by detecting what data has changed since the data was initially extracted or last synchronized. Deletions and creations are tracked.

D: On modified Order Lines, not on Modified Orders.


https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-change-tracking-synchronize-data-external-systems

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/behavior-format-date-time-attribute

by Venita at Oct 03, 2023, 08:17 PM

Limited Time Offer

25%

Off

Get Premium PL-400 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Marge
6 months ago
Sounds like a no-brainer, but I'm not sure about the implementation.
upvoted 0 times
...
Herminia
6 months ago
Wait, why would we need a connector policy for this?
upvoted 0 times
...
Mammie
7 months ago
I think option D could work too.
upvoted 0 times
...
Lezlie
7 months ago
Definitely go with option C!
upvoted 0 times
...
Martin
7 months ago
You need to filter records by user.
upvoted 0 times
...
Buddy
7 months ago
I definitely remember that we shouldn't retrieve all records at once. Applying a connector policy template sounds familiar, but I'm not entirely confident.
upvoted 0 times
...
Luisa
8 months ago
I feel like the Azure APIM parameter could be relevant here, but I can't recall the specifics of how it works with connectors.
upvoted 0 times
...
Devon
8 months ago
I think we practiced a question like this where we had to filter records based on user roles. Was it about applying a business process flow?
upvoted 0 times
...
Cary
8 months ago
I remember something about limiting data retrieval in Power Apps, but I'm not sure if it's through a connector policy or something else.
upvoted 0 times
...
Shawna
8 months ago
I've worked with ServiceNow before, so I have a good idea of how to handle this. I think applying a connector policy template is the way to go to filter the records.
upvoted 0 times
...
Francesco
8 months ago
I'm a bit confused on the differences between the options. I'll need to review the details of each one to determine the best solution.
upvoted 0 times
...
Rosalind
8 months ago
Okay, let's see. I think the key is to limit the number of records returned from ServiceNow. Maybe one of the options like applying a connector policy template could work?
upvoted 0 times
...
Adell
8 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the best approach here.
upvoted 0 times
...
Kimi
8 months ago
This seems straightforward. I'd go with applying the Azure APIM parameter to limit the number of records returned.
upvoted 0 times
...
Willard
8 months ago
I've got this! Risks and opportunities are opposites, so the statement must be true. I'll mark A and move on to the next question.
upvoted 0 times
...
Felicia
8 months ago
I'm leaning towards B. I think the Knowledge Module may need to be customized specifically for the aggregation functions, even if the rest of the Mapping logic is handled automatically.
upvoted 0 times
...
Nicolette
8 months ago
Hmm, I'm not sure about this one. I'll have to think it through carefully.
upvoted 0 times
...
Veronique
1 year ago
Option D is the way to go, my friend. Limiting those ServiceNow records is key - can't have your app loading like a turtle on a treadmill, am I right?
upvoted 0 times
Geraldine
12 months ago
That makes sense. I'll make sure to implement that to improve the app's performance. Thanks for the advice!
upvoted 0 times
...
Ocie
12 months ago
Yes, applying a connector policy template will help limit the number of records retrieved from ServiceNow for each user.
upvoted 0 times
...
Mammie
1 year ago
Option D is the way to go, my friend. Limiting those ServiceNow records is key - can't have your app loading like a turtle on a treadmill, am I right?
upvoted 0 times
...
...
Rodrigo
1 year ago
C) Apply the Azure APIM parameter - I'm a bit skeptical about this one. Connecting to ServiceNow through Azure APIM feels like an overly complex solution when we could just use a connector policy template.
upvoted 0 times
Ashlyn
1 year ago
C) Apply the Azure APIM parameter
upvoted 0 times
...
Darrin
1 year ago
B) Apply a business process flow
upvoted 0 times
...
Caitlin
1 year ago
A) Apply a Lifecycle Services asset scope
upvoted 0 times
...
...
Makeda
1 year ago
B) Apply a business process flow - Hmm, I'm not sure how that would help limit the records returned from the ServiceNow connector. Seems a bit off the mark for this particular issue.
upvoted 0 times
Elke
1 year ago
B) Apply a business process flow - I see what you mean, it might not directly address the issue of limiting records from the connector.
upvoted 0 times
...
Leandro
1 year ago
D) Apply a connector policy template - This could be the solution to restrict the records fetched from ServiceNow.
upvoted 0 times
...
Francesco
1 year ago
C) Apply the Azure APIM parameter - That might help filter the records returned to only those assigned to the user.
upvoted 0 times
...
Flo
1 year ago
A) Apply a Lifecycle Services asset scope - That could work to limit the records returned based on user access.
upvoted 0 times
...
...
Jolanda
1 year ago
A) Apply a Lifecycle Services asset scope - I don't think this is the right solution, as it's more about managing the lifecycle of the app rather than optimizing the connector performance.
upvoted 0 times
...
Lenna
1 year ago
D) Apply a connector policy template - this seems like the right choice to limit the records returned from the ServiceNow connector. It's the most targeted approach to the problem at hand.
upvoted 0 times
Antonio
1 year ago
A) Apply a Lifecycle Services asset scope - that might work too, but it seems like the connector policy template is more specific to this issue.
upvoted 0 times
...
Harrison
1 year ago
D) Apply a connector policy template - this seems like the right choice to limit the records returned from the ServiceNow connector. It's the most targeted approach to the problem at hand.
upvoted 0 times
...
...
Martina
1 year ago
I'm not sure about that. Maybe applying the Azure APIM parameter could also help in limiting the records returned.
upvoted 0 times
...
Fanny
1 year ago
I agree with Adelle. Applying a connector policy template seems like the best option to improve app performance.
upvoted 0 times
...
Adelle
1 year ago
I think we should apply a connector policy template to limit the number of records returned.
upvoted 0 times
...

Save Cancel