New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft PL-500 Exam - Topic 2 Question 41 Discussion

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

You have a flow that interacts with different SharePoint sites. You add the flow to a solution.

You redeploy the solution to production each time you make a change to the flow. You do not want to change the SharePoint site URL every time you redeploy the solution.

You need to configure the solution. Which solution component should you use?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Aretha
3 months ago
I thought managed identity was the answer, but now I'm confused!
upvoted 0 times
...
Rolland
3 months ago
B is not the right fit here, just saying.
upvoted 0 times
...
Elinore
3 months ago
Wait, are we really using connection references for this? Seems off.
upvoted 0 times
...
Tommy
4 months ago
I think A could work too, but not sure it's the best choice.
upvoted 0 times
...
Detra
4 months ago
Definitely go with D, connection reference is the way to go!
upvoted 0 times
...
Arlyne
4 months ago
Managed identity seems off for this scenario. I really think it’s either environment variable or connection reference, but I can't decide which one is better.
upvoted 0 times
...
Corinne
4 months ago
I feel like this question is similar to one we practiced where we had to choose between connection references and environment variables. I think connection reference might be more appropriate here.
upvoted 0 times
...
Amos
4 months ago
I'm not entirely sure, but I remember something about environment variables being useful for storing URLs. Could that be the answer?
upvoted 0 times
...
Elouise
5 months ago
I think we might need to use a connection reference since it allows us to manage connections without changing the flow itself.
upvoted 0 times
...
Allene
5 months ago
I'm feeling pretty confident about this one. The connection reference is definitely the way to go. It allows us to decouple the SharePoint site URL from the flow itself, so we can update it in one place without having to touch the flow every time.
upvoted 0 times
...
Brynn
5 months ago
Okay, I've got this. The key here is that we don't want to change the SharePoint site URL every time we redeploy the solution. That means we need a solution component that can store that URL in a centralized location, and the connection reference seems like the best option for that.
upvoted 0 times
...
Rickie
5 months ago
Hmm, I'm a bit confused here. I'm not sure if a connection reference is the right solution, or if we should be using an environment variable instead. I'll need to think this through a bit more carefully.
upvoted 0 times
...
Amber
5 months ago
This seems like a straightforward question. I think the solution component we should use is a connection reference, since that allows us to store the SharePoint site URL and reuse it across different flows without having to change it every time we redeploy the solution.
upvoted 0 times
...
Elenora
5 months ago
This looks like a tricky one. I'll need to carefully read through the details to make sure I understand the issue before selecting an answer.
upvoted 0 times
...
Alonso
5 months ago
This seems like a straightforward question about creating a hot spot on a graphic to run a macro. I think I can handle this one.
upvoted 0 times
...
Jesusita
5 months ago
I'm confident I can solve this. The key is to use the formula for cost performance index and plug in the right numbers.
upvoted 0 times
...
Lavonna
10 months ago
Connection reference? More like 'connection perfection'! Nailed it, just like I'm going to nail this exam.
upvoted 0 times
Rory
8 months ago
C) Managed identity
upvoted 0 times
...
Wilburn
8 months ago
B) Web resource
upvoted 0 times
...
Rolland
9 months ago
A) Environment variable
upvoted 0 times
...
...
Wenona
10 months ago
Ah, the age-old SharePoint site URL dilemma. I'd go with the connection reference - it's the option that makes the most sense and won't have me tearing my hair out every time I redeploy.
upvoted 0 times
Dylan
9 months ago
D) Connection reference
upvoted 0 times
...
Katina
10 months ago
C) Managed identity
upvoted 0 times
...
Elliott
10 months ago
B) Web resource
upvoted 0 times
...
Alona
10 months ago
A) Environment variable
upvoted 0 times
...
...
Tyisha
10 months ago
Environment variable? What is this, amateur hour? Connection reference is the clear winner here. Keeps things nice and tidy.
upvoted 0 times
...
Julian
10 months ago
Connection reference, for sure! Changing those URLs every time would be a nightmare. Plus, it's probably the most straightforward solution component to use here.
upvoted 0 times
Troy
9 months ago
Connection reference, for sure! Changing those URLs every time would be a nightmare. Plus, it's probably the most straightforward solution component to use here.
upvoted 0 times
...
Arlette
9 months ago
D) Connection reference
upvoted 0 times
...
Cecil
10 months ago
C) Managed identity
upvoted 0 times
...
Alaine
10 months ago
B) Web resource
upvoted 0 times
...
Amie
10 months ago
A) Environment variable
upvoted 0 times
...
...
Bernardine
11 months ago
I'm not sure. Maybe we should consider using connection reference instead?
upvoted 0 times
...
Paris
11 months ago
Hmm, this looks like a tricky one. I'm thinking the connection reference might be the way to go, since it can help us avoid changing the SharePoint site URL every time we redeploy.
upvoted 0 times
...
Tasia
11 months ago
I agree with Kallie. Environment variable will allow us to easily update the SharePoint site URL without redeploying the solution.
upvoted 0 times
...
Kallie
11 months ago
I think we should use environment variable.
upvoted 0 times
...

Save Cancel