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

Microsoft Exam AZ-400 Topic 2 Question 73 Discussion

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

You manage source code control and versioning by using GitHub.

A large file it committed to arepository accidentally.

You need to reduce the sizeof the repository. The solution must remove the file from the repository.

What should you use?

Show Suggested Answer Hide Answer
Suggested Answer: A, D

https://blog.markvincze.com/build-and-publish-documentation-and-api-reference-with-docfx-for-net-core-projects/

https://github.com/dotnet/docfx

DocFX makes it extremely easy to generate your developer hub with a landing page, API reference, and conceptual documentation, from a variety of sources

https://themefisher.com/jekyll-documentation-themes

DOX - Best Jekyll Documentation Theme

Dox is a blazing fast and feature-rich Jekyll documentation theme that is specially crafted for project documentation. You have the flexibility to use this awesome documentation theme with both GitHub and GitLab pages along with standalone projects


Contribute your Thoughts:

Mari
14 days ago
Hmm, this is a tricky one. I think BFG is the way to go, since it's designed specifically for removing large files from Git repositories.
upvoted 0 times
Charisse
4 days ago
I agree, BFG is the best option for removing large files from the repository.
upvoted 0 times
...
...
King
20 days ago
I'm not sure, but I think bfg is a popular choice for reducing repository size.
upvoted 0 times
...
Norah
21 days ago
I agree with Hubert, bfg is the right tool for this situation.
upvoted 0 times
...
Hubert
22 days ago
I think we should use bfg to remove the large file.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77