MENU
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 company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant a pp.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Use Postman to export the custom connector. Then use Postman to import the connector into the production environment.
Does the solution meet the goal?
Suggested Answer: B
Get Premium PL-400 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
DO
Dorothy
11 months ago
Agreed, using Postman seems a bit off for deployment.
TR
Trinidad
11 months ago
Definitely a no, it needs to be done through the Azure portal.
AL
Alysa
11 months ago
Wait, can you really export and import connectors like that?
DA
Darrel
12 months ago
I don't think Postman is the right tool for this.
MA
Malcom
12 months ago
That sounds like a solid plan!
ST
Stefany
1 year ago
I think the solution might not meet the goal because I recall that connectors need to be published through the Azure interface for proper visibility settings.
LA
Lashawna
1 year ago
I feel like exporting with Postman could work, but I'm uncertain if it meets the requirement of being tenant-specific.
KR
Krystina
1 year ago
I remember a practice question where we had to deploy a connector, and I think we used a different method that involved Azure CLI. This feels a bit off.
KA
Kattie
1 year ago
I'm not entirely sure if using Postman is the right approach for exporting and importing the connector. I thought we might need to use Azure Portal instead.
BR
Brynn
1 year ago
Okay, I think I've got a handle on this. The key is that the connector needs to be accessible only to users in the tenant, so using Postman to export and import it seems like a good solution. As long as I'm careful to follow the right steps, I think I can get this deployed correctly.
AH
Ahmed
1 year ago
Hmm, I'm not sure if the Postman solution is the best approach here. Since the connector is tied to a single tenant, there might be some Azure-specific deployment or configuration steps I should consider. I'll need to review the Azure documentation to see if there's a more appropriate way to handle this.
DI
Dick
1 year ago
I'm a bit unsure about this one. The question mentions that the connector was created as a single tenant app, so I'm not sure if Postman is the right tool to use. Maybe there's a more Azure-specific way to deploy and manage the connector in the production environment.
CH
Chauncey
1 year ago
This seems like a straightforward question. I'll focus on understanding the requirements first - the custom connector needs to be deployed to a production environment and be accessible only to users in the tenant. Using Postman to export and import the connector seems like a logical approach.
LA
Latonia
1 year ago
Hmm, I'm a bit confused about the different conditions here. Do I need to enable the feature in the admin settings and also get the customer's approval?
DA
Daron
1 year ago
Wasn't there a question like this where we discussed how segment revenue plays a role? Maybe it's about 10% of combined revenue?
MA
Maryann
2 years ago
I agree with Nicholle, using Postman for exporting and importing the connector seems like a valid approach.
NI
Nicholle
2 years ago
But Postman is a popular tool for API development, it could work well for this scenario.
SK
Skye
2 years ago
I disagree, I don't think using Postman is the best way to deploy the custom connector.
NI
Nicholle
2 years ago
I think the solution meets the goal.
DO
Dorthy
2 years ago
I think the solution is sufficient, as long as it achieves the goal of deploying the custom connector to the production environment.
DE
Devora
2 years ago
I'm not sure, maybe there could be a better way to ensure visibility and accessibility only to users in the tenant.
CH
Chaya
2 years ago
I agree with Ronny, using Postman seems like a good way to deploy the custom connector.
CH
Christene
2 years ago
I agree with Josephine. Postman might work, but it doesn't feel like the most reliable or scalable solution for deploying a production-ready custom connector. I'd prefer a more Azure-native approach.
TY
Tyisha
2 years ago
Haha, Postman? Really? That's like using a hammer to fix a watch. I bet the developers who came up with this solution are the same ones who use Excel as a database.
SA
Salley
2 years ago
Yeah, there are probably better tools for that task.
EN
Ena
2 years ago
Using Postman for deploying a custom connector seems like an odd choice.
MA
Markus
2 years ago
I agree, it's very versatile and user-friendly.
FI
Filiberto
2 years ago
Postman is a great tool for API development.
JO
Josephine
2 years ago
I'm not sure if using Postman is the best approach here. Shouldn't there be a more secure and official way to deploy the connector to the production environment, perhaps through the Azure portal or a CI/CD pipeline?
EM
Emmanuel
2 years ago
I agree, it seems like a quick and efficient way to move the connector to production.
MA
Margurite
2 years ago
I think using Postman is a valid approach for deploying the custom connector.
LA
Lazaro
2 years ago
Using Postman to export and import the custom connector seems like a valid solution. It's a straightforward approach that should meet the requirement of making the connector visible and accessible only to users in the tenant.
GA
Gaston
2 years ago
Yes
AI
Aileen
2 years ago
No
RA
Raina
2 years ago
Yes
RO
Ronny
2 years ago
I think the solution meets the goal.