Do you need to understand product as a Scrum Master

Does your team expecting you to help remove technical impediments by knowing functional and technical details ?

Balaji, they expect to remove functionsl blockers atleast. They are expecting for me to understand atleast whats going on. Its hard for me to communicate or understand anything without knowing that lingo 

One of the best SMs I have met had no technical knowledge what so ever; however, they used to be a teacher and that experience allowed him to have all other qualities that a SM requires. 

You should schedule some time with the PO so that they can explain the product to you if you wish to start understanding it at a high level. 

As a SM, you should be giving the developers direction so that they can resolve the majority of impediments themselves, especially around technical issues. 

Hello, 
I know this post is from 2022 and not sure if anyone would see this. I wanted to ask anyways.. 
I'm in the same situation in a financial work and the language is difficult. My question is, is it different/better understood in a non-financial area for ScrumMasters?

You need to be sufficiently literate to be satisfied that, when you look at the Developers' forecast of work, it can be Done by the end of the Sprint with the Sprint Goal met. You don't have to do any of the work yourself unless you are also a Developer, including impediment removal, you may instead facilitate their removal by others.

Every organization will have terminology that is unique to them.  Every industry has terminology that is unique to it.  There may be times where a single term is used in many organizations or industries but it could have different meanings or implications in different organizations. Anywhere you go you will have to learn the terminology.  And the need for a Scrum Master to understand the terminology will vary based on the organizations as well.  

Remember, the Scrum Guide does not provide a job description, it describes an accountability and the responsibilities for whoever takes on that accountability.  Your actual job description will have more information on what you will need to know in order to do your job at that organization.  As far as the Scrum framework goes, it says nothing about knowing specific terminology other than that introduced in the Guide.

To provide an opposite view, I used to be a sysadmin, developer and (until recently) IT architect. I'm now working as scrum master and I feel my knowledge of IT is actually getting in the way. My background is mostly infrastructure and datacenter, and the team is 100% cloud oriented. They have invited me a couple of times to take a class or a basic entry-level exam to get to know their language better. I have refused every time, because I want to stay out of the technical aspects of the work. 

For me, it's trusting the devs (and challenging them) to explain to me what they need to get done and what is getting in the way. I feel that explaining it to me gives them a more abstract view of any problems, and allows them to see other solutions or take action themselves. Promoting self-organisation.

And it's about having to trust myself to be able to 'feel' when the team gets stuck on something. In my experience you don't need to speak the 'language' to detect that they need help.

It is a good question,

I'd say that the better the understanding, the better the position to advise and coach. However, it is not a must-have from the start. There are plenty of things Scrum Master can work with while building the understanding and awareness about the product and the overall surrounding environment. 

It is important to be transparent with the team about it and also clarify the accountabilities of Scrum Master. Those are rarely well understood.