MENU
You have a Fabric workspace named Workspace1.
You plan to configure Git integration for Workspace1 by using an Azure DevOps Git repository. An Azure DevOps admin creates the required artifacts to support the integration of Workspace1 Which details do you require to perform the integration?
Suggested Answer: B
Get Premium DP-700 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
27 comments · newest first
LE
Leana
10 months ago
I agree with codeNinja, option B sounds right to me!
KE
Keena
10 months ago
I think it's just the organization, project, repo, and branch.
VE
Verona
10 months ago
Definitely the Git repo URL and folder are essential!
NI
Nieves
11 months ago
Wait, do we really need a PAT for this? Seems a bit much.
EL
Elouise
11 months ago
You need the project, Git repo, branch, and folder for sure.
FR
Frederica
11 months ago
I'm a bit confused about the personal access token; I thought that was only needed for authentication, not for the integration itself.
MA
Marion
11 months ago
I practiced a similar question, and I believe the organization name is important too, so I might lean towards option B.
JU
Junita
11 months ago
I think we definitely need the Git repository URL, but I can't recall if the Git folder is necessary for the integration.
ER
Erin
12 months ago
I remember something about needing the project and Git repository details, but I'm not sure if the branch is also required.
GE
Georgiana
12 months ago
The Git repository URL and folder seem like the most critical pieces of information. As long as I have those, I can probably figure out the rest of the setup.
MA
Marvel
1 year ago
Okay, I've got this. The details I need are the organization, project, Git repository, and branch. That should give me everything I need to connect Workspace1 to the Azure DevOps Git repo.
VA
Vallie
1 year ago
Hmm, I'm a bit confused. I thought we might also need the organization and personal access token (PAT) for authentication. I'll have to double-check the requirements to be sure.
NA
Nathalie
1 year ago
I think the key details I would need are the project, Git repository, branch, and Git folder. That seems like the most comprehensive set of information to get the integration set up.
MI
Mickie
1 year ago
Yes, we do need the personal access token for authentication along with the Git repository URL.
NI
Nina
1 year ago
But don't we also need the personal access token for Git authentication?
TR
Trina
1 year ago
B is the way to go. Anything less and you're just setting yourself up for a world of pain. Don't forget the pain!
AL
Alaine
1 year ago
No, we just need the project, Git repository, branch, and Git folder.
KA
Kathryn
1 year ago
I think we need the organization, project, Git repository, and branch.
TI
Tijuana
1 year ago
D for sure! The PAT is essential for authentication, and the repo URL is a no-brainer. Can't forget those details!
EI
Eileen
1 year ago
Yes, you definitely need the personal access token for authentication. And the Git repository URL is crucial for the integration.
VI
Viki
1 year ago
D for sure! The PAT is essential for authentication, and the repo URL is a no-brainer. Can't forget those details!
GA
Gail
1 year ago
I believe the organization, project, Git repository, and branch are needed.
MI
Mickie
1 year ago
I agree with Nina, those details are necessary for the integration.
NI
Nina
1 year ago
I think we need the project, Git repository, branch, and Git folder.
IZ
Izetta
1 year ago
Option B seems the most comprehensive. We need the organization, project, repo, and branch to set up the integration, right?
GO
Goldie
1 year ago
I agree, option B provides all the necessary information for configuring Git integration.
AN
Anglea
1 year ago
Yes, that's correct. We need all those details to set up the integration properly.