Frequently Asked Questions on Parikshak

1. What is “Parikshak”?

Parikshak is an Automated Program Grading & Analysis Tool. It allows examiners to

conduct programming exams in online mode, auto-evaluates candidates’ programming
assignments, gives intuitive feedback to candidates, and does qualitative analysis of
candidates’ programs after the programming test.
2. What programming languages are supported in Parikshak for the Central Bank of
India exam?

For the Central Bank of India examination, Parikshak will support only Java language
version 9.3.

3. Does Parikshak use its own compiler?

No, Parikshak uses the standard compiler and version for each language.

4. What are the types of problems that will be given to the candidates during Central
Bank of India exams?

There will be only one type of problem that will be given to the candidates. The
problem requires the development of a complete program where candidates have to
write the program from start to end. This includes importing libraries, reading
inputs, processing data, and printing output.

5. What is the duration of the exam?

The total duration of the exam will be 3.5 hours with the first half hour for workingon
a paper (without computers) and the next 3 hours for coding on computers. For the
first 30 minutes of the test, typing in Parikshak will be blocked.

6. What is an attempt? Can I get more attempts?

An attempt is one session of the exam duration; for the Central Bank of India exam,
there will be onlyone attempt of 3 hours.

Note: There will be no extra attempt once you close the exam.

7. When can we close the exam?

(i) Once you have solved all the problems; i.e got all “Y” for each problem that you

Page 1 of 7
 needed to solve, or (ii) you are no longer interested to continue the exam. However,
before closing the exam, please contact the Invigilator available in the exam hall.
Note: Once you close the exam, you will not be allowed to log in again.

8. What will happen if the attempt duration is over to solve the problems?

Once the attempt is over, the system will be closed automatically, after which no
submission will be allowed for any of the problems. The evaluation will be considered
only for those solutions for which “Submit to Grader” was done during the attempt
duration.
Note: During the exam, no extra attempt will be given.

9. How can I test/debug my program before submitting my program for evaluation to

Parikshak?

You can provide your own test case in the input box “Provide your own test cases”
and click the “Self Assessment” button.

This will first compile your program and then run the program against your inputs.
You can see the output of your program in the “output” box along with all debug
statements.
Note: Remove or /*comment out */ all the debug statements before “Submit to
Grader” for evaluation.
10. What will happen when a program goes on an infinite loop in Parikshak?

There is no way to find a program that is in an infinite loop, it is known as a classical

problem which cannot be solved. So in Parikshak, a program is killed explicitly when a
problem takes more time and memories than the predefined time and memoriesfor a
particular problem.

11. What will be the different outputs that I get during the “Self Assessment”?
a. Compilation error: When the code has any syntax error.
b. No output: When the code does not produce any output.
c. Correct output: When the code will produce the output without any errors as
expected.
d. Time limit or memory limit exceeded: When the program is in an infinite loop or
taking more time or memory than expected.

12. What is the purpose of “Submit to Grader''?

This is very important for your program to be considered for evaluations. For every
program that you want to be evaluated, you need to do “Submit to Grader”. If you fail
to do it, that program will not be considered for evaluations and no marks will be
awarded irrespective of whether your program is correct or not.

Page 2 of 7
13. What does Parikshak do when we do “Submit to Grader”? What is the grader's
output?

When a program is submitted to the grader for a selected problem; the grader teststhe
program against the hidden test cases based on the problem statement and input
specification of the problem and checks the output as per the output specification.For
every passed (output as expected) test case, you will get a “Y” and for failed (output not as
expected) test cases you will get an “X”. The final grade is a sequence of “Y” and “X” for
each program and each submission. Once you get all “Y”, your program is accepted
against all the test cases and you can move to the next problem.
Note: In case your program has syntax error or giving runtime error, even then the
grader will give only “X” for each test case.

14. How many times can I do “Submit to Grader” for one program?

There is no restriction on the no of times a candidate can perform “Submit to Grader”in

one attempt of 3 hours.
15. What is the input specification of the problem?

This specifies the sequence of the input data; type of data (i.e integer, character,
float, string, etc.) and meaning of each input. Note that, do not print anything on the
screen while reading the input such as “Enter the Number:”, “Number of Rows:” etc.

16. What is the importance of the output specification of the problem?

It is very important to follow the output specification. You should not print/produce any
output other than the output asked in the specification.

Example: If the output specification has been asked for the sum of numbers:

a. The output should be only the number without any other character before or
after i.e. “90”
b. If you print the “sum of the number is 90” instead of just “90”, your program
will be evaluated wrong as “X” during grader evaluation.
17. What are Low, Medium and High complexity problems?
a. Low complexity: The problem will be based on basic operations on Array,
String, Matrix, etc.
b. Medium complexity: The problem will be based on data structures; such as
stack, queue, linked-list, trees, graphs, etc.
c. High complexity: It will be algorithm-based problems; such as sorting,
searching, optimization, etc.

18. How many problems will be given during the exam?

Please refer to the following table:

Page 3 of 7
 Complexity No. of Questions Maximum Marks Per Question Total Marks
Low 2 10 20
Medium 2 15 30

High 1 20 20
Total 5 70

19. Is there an order for solving the questions?

No order needs to be followed; however, it is advisable to solve simple problems first

and then move to the complex ones.
20. Is there any restriction on the libraries in Java language for the Central Bank of
India exam?

There is no restriction from Parikshak for using any standard library available withthe
Java language. However, no third-party library is available or allowed in Parikshak
which is not part of the standard library in the particular version of the language.

21. What should be the filename of my solutions in Parikshak?

For your java files, you have to give the same name of the class which contains the
main function. The filenames should have .java extension.

22. Can we create multiple files for a problem?

No, you just need to create only one file for a problem. All the classes and functions
should be written inside one file only, for a single problem.

23. Any Disclaimer about Parikshak Software? Yes.

Disclaimer: Parikshak program grading is purely input/output based. Central Bank

of India/test conducting body reserves the right to manually examine the submitted
code against malpractices and reported errors related to problem specifications.
When there is adequate ground, Central Bank of India/test conducting body may
override Parikshak's verdict bygranting/denying credit.

*********************************************

Page 4 of 7