Hello Abdul
Take a look at this post:
Based on the debug output you have displayed here, it looks like on SW3, Fa0/14 was originally the root port of the switch, but it is “going down”. Therefore, a new root port had to be designated, and it looks like the switch chose Fa0/16 for the new root port.
On SW2, it looks like Fa0/14 went down on this switch as well. The initial result was that SW2 made itself the root bridge. But in the meantime, it received a superior BPDU on Fa0/16, which informed SW2 that another switch will become the root. Therefore, SW2 changes its own role (it is no longer the root bridge), and thus it must choose a root port, choosing Fa0/16 for this role.
So to answer your question, no SW2 is not the root bridge. It temporarily became the root bridge until it received a superior BPDU. Remember that these events take place quite quickly and can occur in a different order each time. SW3 didn’t get a chance to become root bridge, but immediately received the appropriate BPDU on Fa0/16 to make that root port. While SW2 decided to become the root bridge until a superior BPDU is received, which it was. But these things happen so quickly that the order doesn’t really matter. For users, the quickness of reconvergence is still quite fast.
Fa0/2 is a new port that just came up. It becomes designated immediately simply because it didn’t receive a superior BPDU on that port.
I hope this has been helpful!
Laz