Discuss Microsoft AZ-400 Exam Topic 6 Question 65

You use GitHub for source control of .NET applications.

You need to deploy a documentation solution that meets the following requirements:

Documents will be written in Markdown as developers make code changes

Changes to the documents will trigger the recompilation of a static website.

Users will access the documents from the static websites

Documents will be stored in a GitHub repository

Which two tools can you use to compile the website? Each correct answer presents a complete solution.

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

Get Premium AZ-400 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

13 comments · newest first

My 11 months ago

Jekyll is the go-to for static sites!

Shasta 11 months ago

Wait, Medium? That doesn't seem right...

Fletcher 12 months ago

Definitely Jekyll and DocFX!

Rikki 12 months ago

I thought WordPress could work too?

Felicitas 1 year ago

Jekyll and DocFX are great for this!

Janae 1 year ago

I practiced a question similar to this, and I feel like Jekyll and DocFX were the answers. I hope I remember correctly!

Paola 1 year ago

DocFX sounds familiar too. I think it’s specifically designed for documentation and works well with .NET.

Luther 1 year ago

I'm not entirely sure about Medium; I think it's more of a blogging platform than a static site generator.

Velda 1 year ago

I remember Jekyll being a popular choice for static site generation, especially with Markdown. It seems like a solid option here.

Melvin 1 year ago

Okay, let me break this down step-by-step. Saving changes just keeps them locally, Commit applies them to the local repo, and Commit and Push would send them to the remote. I think B, Commit, is the right answer here.

Alyce 1 year ago

“Decreases external dependencies” doesn't sound like a typical benefit of CI. I might lean towards the faster feedback loop being more relevant.

Thea 1 year ago

Definitely go with a Varying Attribute Dimension. That way you can easily see the customer's status history and how it's evolved over time. Seems like the most flexible and robust solution for this requirement.

Deandrea 1 year ago

Okay, I've got this. The key here is to focus on the most important step before updating the risk register. I think reassessing the risk to confirm the impact is the best approach.

Microsoft AZ-400 Exam - Topic 6 Question 65 Discussion