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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft Exam AZ-400 Topic 6 Question 65 Discussion

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

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.

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


by Janey at Oct 13, 2022, 02:42 AM

Limited Time Offer

25%

Off

Get Premium AZ-400 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Velda
3 days ago
I remember Jekyll being a popular choice for static site generation, especially with Markdown. It seems like a solid option here.
upvoted 0 times
...
Deandrea
7 days 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.
upvoted 0 times
...
Melvin
9 days 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.
upvoted 0 times
...
Alyce
10 days ago
“Decreases external dependencies” doesn't sound like a typical benefit of CI. I might lean towards the faster feedback loop being more relevant.
upvoted 0 times
...
Thea
13 days 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.
upvoted 0 times
...

Save Cancel