Is this right decision to define 5-6 foreign key in a single table...? If i define 5-6 foreign keys on a single table, are there any performance concerns?

CREATE TABLE [dbo].[PS_CLASSROOM_MST](
    [CLASS_ID] [int] NOT NULL,
    [CLASS_NAME] [varchar](50) NOT NULL,
    [CLIENT_ID] [int] NOT NULL,
    [SCHOOL_ID] [int] NOT NULL,
    [COURSE_ID] [int] NULL,
    [BRANCH_ID] [int] NOT NULL,
    [SESSION_ID] [int] NOT NULL,
    [SECTION] [varchar](10) NULL,
    [STATUS] [bit] NOT NULL,
    [IP_ADDRESS] [varchar](30) NULL,
    [LANGUAGE] [varchar](50) NULL,
    [CLASS_FILE_PATH] [varchar](200) NULL,
    [REMARK] [nvarchar](max) NULL,
    [SECTION_FILE_PATH] [nvarchar](max) NULL,
    [LOCATION_ID] [int] NOT NULL,
 CONSTRAINT [PK_PS_CLASSROOM_MST] PRIMARY KEY CLUSTERED 
(
    [CLASS_ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO

SET ANSI_PADDING OFF
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST]  WITH CHECK ADD  CONSTRAINT [FK_PS_CLASSROOM_MST_PS_BRANCH_MST] FOREIGN KEY([BRANCH_ID])
REFERENCES [dbo].[PS_BRANCH_MST] ([BRANCH_ID])

GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST] CHECK CONSTRAINT [FK_PS_CLASSROOM_MST_PS_BRANCH_MST]
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST]  WITH CHECK ADD  CONSTRAINT [FK_PS_CLASSROOM_MST_PS_COURSE_MST] FOREIGN KEY([COURSE_ID])
REFERENCES [dbo].[PS_COURSE_MST] ([COURSE_ID])
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST] CHECK CONSTRAINT [FK_PS_CLASSROOM_MST_PS_COURSE_MST]
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST]  WITH CHECK ADD  CONSTRAINT [FK_PS_CLASSROOM_MST_PS_LOCATION] FOREIGN KEY([LOCATION_ID])
REFERENCES [dbo].[PS_LOCATION] ([LOCATION_ID])
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST] CHECK CONSTRAINT [FK_PS_CLASSROOM_MST_PS_LOCATION]
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST]  WITH CHECK ADD  CONSTRAINT [FK_PS_CLASSROOM_MST_PS_SCHOOL_MST] FOREIGN KEY([SCHOOL_ID])
REFERENCES [dbo].[PS_SCHOOL_MST] ([SCHOOL_ID])
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST] CHECK CONSTRAINT [FK_PS_CLASSROOM_MST_PS_SCHOOL_MST]
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST]  WITH CHECK ADD  CONSTRAINT [FK_PS_CLASSROOM_MST_PS_SESSION_MST1] FOREIGN KEY([SESSION_ID])
REFERENCES [dbo].[PS_SESSION_MST] ([SESSION_ID])
GO

ALTER TABLE [dbo].[PS_CLASSROOM_MST] CHECK CONSTRAINT [FK_PS_CLASSROOM_MST_PS_SESSION_MST1]
GO
Foreign keys exist to enforce referential integrity i.e. to keep the data clean. This is a good thing.

However, there are no free lunches. The constraint will be checked on writes, adding latency. A FK may have an associated index. As such there will be an overhead during writes. The more FKs, the more overhead. Plus the extra disk and maintenance time.

If you have done design diligently and arrived at this table then I see no prima face problem. If testing at scale shows problems that's the time to consider alternate implementations.