Free Microsoft GH-900 Actual Exam Questions - Question 11 Discussion
gist based on another user's gist?
Maybe D isn’t a thing since you can’t really ask someone to add you to their gist like a repo. Cloning (C) just makes a local copy, so it doesn’t create a new public gist with history. Copying content manually (B) loses the history completely, so that’s out. Forking (A) seems like the only way to keep the history and have your own public gist. So yeah, A’s the best fit here for efficiency and preserving history.
A imo, forking keeps history linked and is way easier than requesting access.
It’s A. Forking is designed exactly for this—creating a new public gist that keeps the entire history intact and linked to the original. D only gives you editing access but doesn’t create a separate gist for you. Cloning or copying just duplicates the content without any connection or history, which isn’t as efficient when you want to maintain that link. So for efficiency and history, forking makes the most sense here.
A. Forking keeps the full history and links back to the original, which none of the other options do as cleanly or efficiently. Copying or cloning loses that connection completely.
Isn’t forking specifically designed to keep the history linked, unlike cloning or copying?
C, cloning duplicates but doesn’t keep the gist history linked like forking does.
It’s A. Fork the gist.