The Legend of Korrak

If you havent done the quest from amphitheater of Anguish in zuldrak to kill this guy he does still give credit for the AV quest

you can literally can complete this quest in the zuldrak arena, quick before they hotfix it

For this quest, one of the factions needs to capture the Snowfall Graveyard, which is located
south west of Stonehearth Graveyard, and is the only graveyard neither faction owns.

Shortly after capturing it, Korrak will appear. He does NOT respawn after being killed. So if you
did not get him that first time, you will have to do another one to try and get him.

This mob is not shareable, if one faction tags him, he is grayed out and does not count for a
kill if the other factions kills him while he still has Alliance players attacking him. (Pretty sure
this is the case).

When this quest came out, most players were able to get Korrak as this quest was a must
complete for the high level weapon (at lvl 120, it is ilvl 400), and gives a tremendous amount
of experience.

Unfortunately, at this point in time, in my personal experience, most players all but ignore
Korrak and don't even bother to get him. So if you didn't complete this quest on alts in the
big rush near the beginning, you will most likely not be able to do it now. Don't bother asking,
9/10 most players on your team won't bother to take him down.

Like most of the NPCs, Korrak hits tremendously hard, easily 2-3 shotting most players
regardless of their class. Soloing him is not doable.

Originally, you could kite Korrak from the graveyard to the group, but upon testing, as of the
date of this post, this is no longer possible. At a certain distance (little over halfway down
the mountain), Korrak will automatically reset.

The one method that is doable is to kill the Korrak in Zul'drak, specifically in the Amphitheater
questline. He's easily soloable, but this isn't 100% reliable. I managed to do this for my Rogue,
but on my Paladin, I was not given credit for it. Not sure why this is, but...they may have either
hotfixed it, or it could just be an error.

Either way, the quest sucks, and Blizzard clearly did not think long term regarding it.