Free Microsoft GH-100 Actual Exam Questions - Question 11 Discussion
repository. What is the first step you should take to mitigate the risk?
Maybe D is a bit extreme as a first step since deleting the repo won’t stop someone from having already cloned it or accessed the secret elsewhere. GitHub support can’t magically scrub all copies either. The priority should be to revoke or rotate the secret first so it can’t be used anymore, then deal with cleaning the history. So B still feels like the safest move to stop any immediate damage before worrying about history rewriting or repo deletion.
B/C? Revoking the secret first is critical to stop any immediate misuse, then cleaning the history comes next to avoid exposure later. Deleting or contacting GitHub won’t stop current leaks quickly enough.
B/C? The secret needs to be invalidated immediately, so revoking first makes sense, but cleaning the history should follow quickly to avoid future exposure. Deleting or contacting GitHub seems less direct.
It’s B for me too. Even if you clean the repo history or delete it, anyone who already copied the secret can still use it. So the priority has to be revoking or rotating the secret first to prevent any damage. After that, you can think about cleaning history or other steps. Options like contacting GitHub or deleting the repo don’t immediately stop the leaked secret from being usable.
B imo, revoking the secret cuts off any immediate damage. Cleaning history or deleting the repo won’t stop someone who already grabbed it, so rotating first is just safer.
B. Rotating the secret is crucial because cleaning the repo alone doesn’t stop someone who already grabbed the token. You want to cut off access ASAP before worrying about history cleanup.
B. Even if you clean the history or delete the repo, the secret could already be leaked. Rotating it right away is the only sure way to stop unauthorized access immediately.
I see why B is popular, but wouldn’t starting with C prevent future accidental exposures in forks or clones? Or is the risk already too high before you can clean history?
B. Revoking the secret immediately prevents misuse even if someone already copied it. Fixing history or other cleanup comes later to avoid further exposure.
B imo, because even if you clean the repo later, the secret might already be compromised. Revoking it first stops any damage right away before doing any cleanup.
Totally agree, revoking the secret first makes sure it can't cause damage. B
B is the way to go first—revoke or rotate the secret ASAP. Cleaning history or deleting repo comes after you make sure the secret can’t be used.