Exam AZ-400 All QuestionsBrowse all questions from this exam
Go to Exam
Question 167

DRAG DROP -

Your company has a project in Azure DevOps named Project1.

All the developers at the company have Windows 10 devices.

You need to create a Git repository for Project1. The solution must meet the following requirements:

• Support large binary files.

• Store binary files outside of the repository.

• Use a standard Git workflow to maintain the metadata of the binary files by using commits to the repository.

Which three actions should you perform in sequence on each developer’s device? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

    Correct Answer:

Discussion
t_k_r

Configure PAT Perform installation of Git LFS Track GIT LFS https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage

buzzerboy

i dont think the order of PAT or installation of GIT LFS matter. You can do either one first.

vLabz

there is no "install LFS step", it is "custom install of Git along with LFS". therefore, this needs to be the first step on a localmachine. Once installed you may configure your PAT on your local repo that you have cloned. Remind that the questions is about actions on local developer machines, "Configure PAT" is not the fact of getting a PAT from the server...

[Removed]

t_k_r I think your answer is correct, but the URL you provided does not support your answer. However, this URL does ... https://andrewlock.net/creating-a-git-repo-with-azure-repos-and-trying-out-git-lfs/ It is a long article with a lot of info that's not pertinent to this question, but ultimately the steps you outlined (configure PAT, install Git LFS support, track Git LFS) are covered in this article, in the order you listed.

yana_b

1. Create a PAT 2. Perform installation of Git LIS 3. Set the feels tracking https://andrewlock.net/creating-a-git-repo-with-azure-repos-and-trying-out-git-lfs/

Aravindking

Bard AI explanation : A. Perform a custom installation of Git for Windows that includes Git Large File Storage (LFS). B. Configure Git Large File Storage (LFS) file tracking. C. Configure personal access token (PAT)-based authentication.

vLabz

The only possible solution is : - Custom install of Git for Windows - Configure PAT authentication - Configure LFS Tracking These are *local machine* actions on developers machines. - You need first to install git, no git no other action is possible - Configure PAT is done in git, it is the act of setting the PAT as a credential, it is not getting the pat from Azure DevOps. Configuring the PAT allows to clone the repo. - Configure LFS tracking must be done inside the repo, that is why you need to configure the PAT first and cloned the repo. In this scenario, any developer can configure some trackings and push the .gitattributes file (the LFS conf for the current repo)

sondrex

PAT Perform LFS Configure LFS

Fal991l

To create a Git repository for Project1 that supports large binary files, stores binary files outside of the repository, and uses a standard Git workflow to maintain the metadata of the binary files by using commits to the repository, you should perform the following actions in sequence on each developer’s Windows 10 device:

Fal991l

Configure personal access token (PAT)-based authentication (B): This will allow the developer to authenticate with Azure DevOps and access the Git repository for Project1. Perform a custom installation of GIT for Windows that includes GIT Large File Storage (LFS) (E): This will install the necessary tools on the developer's device to support the use of Git LFS. Configure GIT Large File Storage (LFS) file tracking (D): This will enable Git LFS file tracking, allowing the developer to work with large binary files in a standard Git workflow. Note that these actions should be performed in the correct order to achieve the desired result. By following these steps, developers will be able to work with large binary files in a Git repository for Project1 without storing them in the repository itself, using a standard Git workflow to maintain the metadata of the binary files by using commits to the repository.