Java based questions and Manual testing

Round 1 Questions Q1 Where did you apply OAT (Operational Acceptance Testing)? Q2 Give an example of something you tested in OAT. Q3 What is Failover Testing? Can you give an example? Q4 How would you convince a stakeholder NOT to release a product when there is an existing issue? Q5 What is Disaster Recovery testing and how have you approached it? Q6 If CPU memory is fully consumed, how would you empty/free it? Describe how you would set up an alert notification via Gmail. Round 2 Questions Q1 What tools have you used for Monitoring? Q2 Give an example of Failure Testing from your experience. Q3 Based on your CV, what experience do you have specifically for OAT? Q4 What is different about testing for a Public domain vs. a Private domain? What would you do differently for a Public domain? Q5 What tools have you used in your experience? (Interviewer noted: Azure DevOps, Azure Monitor, ServiceNow, Putty) Q6 What does 'early testing of OAT' mean to you? Q7 Explain API testing and validation — how do you approach it? Q8 Have you done any development work? If so, what kind? Q9 What is performance testing? Q10 What is load testing and stress testing? How do they differ? Q11 Explain User Centric experience — how does your UX background inform your testing approach? Q12 Why did you choose to do a Masters in UX? Q13 What is your current role and what types of testing do you carry out? Q14 What is your expertise in QA? Q15 What is Business User Testing and how have you conducted it? Tips for Future Candidates • Be ready to give specific real-world examples for OAT, Failover, and Disaster Recovery — generic answers won't stand out. • Know your monitoring tools inside out: Azure Monitor, Azure DevOps, ServiceNow, Putty were all discussed. • If you have a UX background, be prepared to explain how it adds value to your QA and testing approach. • Stakeholder management is key — prepare a structured answer for how you'd push back on releasing with a known defect. • Understand the difference between load, stress, and performance testing with clear definitions and examples. • API testing knowledge is essential — be ready to explain validation approaches and tools you have used.