{"id":42205,"date":"2026-07-12T02:24:20","date_gmt":"2026-07-12T06:24:20","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=42205"},"modified":"2026-07-12T02:24:21","modified_gmt":"2026-07-12T06:24:21","slug":"what-are-the-most-common-qa-interview-questions","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/what-are-the-most-common-qa-interview-questions\/","title":{"rendered":"What are the most common QA interview questions?"},"content":{"rendered":"\n<p>H2K Infosys helps aspiring software testers develop the technical knowledge, practical skills, and interview confidence required to build a successful career in quality assurance. Whether you are a fresher entering the software industry or an experienced tester preparing for your next opportunity, understanding the most common <a href=\"https:\/\/www.h2kinfosys.com\/updated-interview-questions\/qa-testing-interview-questions-answers\/\">QA interview questions<\/a> can significantly improve your chances of success.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>Most Common QA Interview Questions<\/strong><\/h1>\n\n\n\n<p><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">Quality Assurance<\/a> professionals play a critical role in software development. They verify that applications meet business requirements, function correctly, and provide a reliable user experience. During a QA interview, employers typically assess a candidate\u2019s understanding of testing concepts, defect management, test documentation, methodologies, tools, and real-world problem-solving.<\/p>\n\n\n\n<p>This guide covers the most common QA interview questions and explains how candidates can answer them effectively.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe title=\"Quality Assurance Interview Question and Answers\" width=\"800\" height=\"450\" src=\"https:\/\/www.youtube.com\/embed\/E7tnmCBF2Yc?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Software Testing?<\/strong><\/h2>\n\n\n\n<p><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">Software testing<\/a> is the process of evaluating a software application to determine whether it meets specified requirements and works as expected. It involves identifying defects, verifying functionality, and assessing the quality, reliability, security, usability, and performance of the system.<\/p>\n\n\n\n<p>A strong interview answer should explain that testing is not limited to finding bugs. Its broader purpose is to reduce business risk and provide confidence that the application is ready for release.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Quality Assurance?<\/strong><\/h2>\n\n\n\n<p>QA, commonly known as QA, is a process-orientated approach used to prevent defects throughout the software development lifecycle. It focuses on improving development and testing processes so that quality is built into the product from the beginning.<\/p>\n\n\n\n<p>Candidates should understand the difference between QA and testing. QA focuses on process improvement and defect prevention, while software testing focuses primarily on product evaluation and defect detection.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Difference Between Quality Assurance and Quality Control?<\/strong><\/h2>\n\n\n\n<p>QA is preventive and process-orientated. It establishes standards, procedures, and development practices designed to prevent defects.<\/p>\n\n\n\n<p>Quality control is corrective and product-orientated. It examines the actual software product to identify defects and verify whether it meets quality standards.<\/p>\n\n\n\n<p>For example, defining a code review process is part of quality assurance, while executing test cases against a completed feature is part of quality control.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Software Testing Life Cycle?<\/strong><\/h2>\n\n\n\n<p>The Software Testing Life Cycle, or STLC, is a structured sequence of testing activities. Its major phases include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirement analysis<\/li>\n\n\n\n<li>Test planning<\/li>\n\n\n\n<li>Test case design<\/li>\n\n\n\n<li>Test environment setup<\/li>\n\n\n\n<li>Test execution<\/li>\n\n\n\n<li>Defect reporting and tracking<\/li>\n\n\n\n<li>Test closure<\/li>\n<\/ul>\n\n\n\n<p>During requirement analysis, testers identify testable requirements and clarify ambiguities. In the planning phase, the QA team estimates effort, selects tools, assigns responsibilities, and defines the testing strategy. Test cases are then prepared, reviewed, executed, and documented.<\/p>\n\n\n\n<p>Interviewers may ask candidates to describe their responsibilities in each STLC phase.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Difference Between Verification and Validation?<\/strong><\/h2>\n\n\n\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Wikipedia:Verifiability\" rel=\"nofollow noopener\" target=\"_blank\">Verification determines<\/a> whether the development team is building the product correctly. It includes reviews, inspections, walkthroughs, and other activities that do not necessarily require executing the software.<\/p>\n\n\n\n<p>Validation determines whether the team is building the correct product. It involves executing the software and confirming that it satisfies user and business requirements.<\/p>\n\n\n\n<p>A simple way to remember the distinction is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Verification: \u201cAre we building the product correctly?\u201d<\/li>\n\n\n\n<li>Validation: \u201cAre we building the correct product?\u201d<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is a Test Case?<\/strong><\/h2>\n\n\n\n<p>A test case is a documented set of conditions, inputs, execution steps, and expected results used to verify a specific application requirement or function.<\/p>\n\n\n\n<p>A well-written test case generally includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Test case identification number<\/li>\n\n\n\n<li>Test scenario or objective<\/li>\n\n\n\n<li>Preconditions<\/li>\n\n\n\n<li>Test data<\/li>\n\n\n\n<li>Execution steps<\/li>\n\n\n\n<li>Expected result<\/li>\n\n\n\n<li>Actual result<\/li>\n\n\n\n<li>Pass or fail status<\/li>\n\n\n\n<li>Comments or supporting evidence<\/li>\n<\/ul>\n\n\n\n<p>Interviewers may ask candidates to write test cases for common objects such as a login page, calculator, elevator, pen, ATM, or e-commerce checkout process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is a Test Scenario?<\/strong><\/h2>\n\n\n\n<p>A test scenario is a high-level description of the functionality that must be tested. It explains what should be tested without listing detailed execution steps.<\/p>\n\n\n\n<p>For example, \u201cVerify that a registered user can log in with valid credentials\u201d is a test scenario. A test case for that scenario would contain specific data, steps, and expected results.<\/p>\n\n\n\n<p>One test scenario may contain multiple test cases covering positive, negative, boundary, usability, and security conditions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Difference Between a Test Scenario and a Test Case?<\/strong><\/h2>\n\n\n\n<p>A test scenario provides broad testing coverage and describes a feature or user action that must be evaluated. A test case provides detailed instructions for testing a specific condition.<\/p>\n\n\n\n<p>Test scenarios are useful for understanding overall coverage, while test cases support repeatable and traceable execution. In fast-moving Agile projects, teams may use concise scenarios or checklists. In regulated or high-risk projects, detailed test cases are often required.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is a Defect or Bug?<\/strong><\/h2>\n\n\n\n<p>A defect is a difference between the expected behaviour and the actual behaviour of a software application. A defect may result from incorrect requirements, design problems, coding errors, configuration issues, environmental differences, or misunderstood business rules.<\/p>\n\n\n\n<p>A useful defect report should include a clear title, environment details, preconditions, reproduction steps, expected behaviour, actual behaviour, severity, priority, screenshots, logs, videos, and other relevant evidence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Defect Life Cycle?<\/strong><\/h2>\n\n\n\n<p>The defect life cycle describes the stages a defect passes through from discovery to closure. Common defect statuses include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>New<\/li>\n\n\n\n<li>Assigned<\/li>\n\n\n\n<li>Open<\/li>\n\n\n\n<li>In progress<\/li>\n\n\n\n<li>Fixed<\/li>\n\n\n\n<li>Ready for retesting<\/li>\n\n\n\n<li>Retest<\/li>\n\n\n\n<li>Reopened<\/li>\n\n\n\n<li>Deferred<\/li>\n\n\n\n<li>Rejected<\/li>\n\n\n\n<li>Duplicate<\/li>\n\n\n\n<li>Closed<\/li>\n<\/ul>\n\n\n\n<p>The exact workflow may vary by organisation. Candidates should explain that a tester reports the defect, the development team investigates and fixes it, and the tester retests the issue. If the problem remains, the defect is reopened. If the correction works and related functionality is unaffected, the defect can be closed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is the Difference Between Severity and Priority?<\/strong><\/h2>\n\n\n\n<p>Severity indicates how significantly a defect affects the system\u2019s functionality. Priority indicates how urgently the defect should be fixed.<\/p>\n\n\n\n<p>A system crash during payment processing is usually high severity and high priority. A spelling mistake on a highly visible home page may be low severity but high priority. A serious issue in a rarely used feature may be high severity but lower priority, depending on business impact and release plans.<\/p>\n\n\n\n<p>The QA engineer usually recommends severity, while priority is often determined collaboratively by product owners, project managers, developers, and business stakeholders.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Regression Testing?<\/strong><\/h2>\n\n\n\n<p>Regression testing verifies that recent code changes have not negatively affected previously working functionality. It is commonly performed after defect fixes, enhancements, integrations, configuration changes, and new releases.<\/p>\n\n\n\n<p>Regression test suites usually include critical business workflows, frequently used functions, high-risk modules, integration points, and areas affected by the latest changes.<\/p>\n\n\n\n<p>Because regression testing is repetitive and must often be executed across multiple releases, it is a strong candidate for automation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Retesting?<\/strong><\/h2>\n\n\n\n<p>Retesting is performed to confirm that a specific defect has been fixed successfully. The tester executes the same steps and conditions that originally exposed the defect.<\/p>\n\n\n\n<p>Regression testing has a wider scope. It checks whether the fix or code change has caused problems in other parts of the application.<\/p>\n\n\n\n<p>In practical terms, retesting asks, \u201cHas this specific bug been fixed?\u201d Regression testing asks, \u201cHas the change broken anything else?\u201d<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Smoke Testing?<\/strong><\/h2>\n\n\n\n<p>Smoke testing is a preliminary test performed on a new build to verify that its critical functions work and that the build is stable enough for detailed testing.<\/p>\n\n\n\n<p>For example, a smoke test may verify that the application launches, users can log in, major pages open, and essential services are available. If these basic checks fail, the QA team may reject the build without continuing with full functional testing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Sanity Testing?<\/strong><\/h2>\n\n\n\n<p>Sanity testing is a focused evaluation performed after a small change or defect fix. Its purpose is to confirm that the modified functionality works and that related areas remain stable.<\/p>\n\n\n\n<p>Smoke testing is broad and shallow, while sanity testing is narrow and relatively deep. Smoke testing evaluates overall build stability, whereas sanity testing concentrates on a specific change.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Functional Testing?<\/strong><\/h2>\n\n\n\n<p>Functional testing verifies whether the application performs according to documented business and system requirements. It focuses on what the system does.<\/p>\n\n\n\n<p>Examples include testing login functionality, search results, form validation, payment processing, account creation, order placement, and password recovery.<\/p>\n\n\n\n<p>Functional testing may be performed manually or through automation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Non-Functional Testing?<\/strong><\/h2>\n\n\n\n<p>Non-functional testing evaluates how well a system performs rather than what it does. Major categories include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Performance testing<\/li>\n\n\n\n<li>Load testing<\/li>\n\n\n\n<li>Stress testing<\/li>\n\n\n\n<li>Security testing<\/li>\n\n\n\n<li>Usability testing<\/li>\n\n\n\n<li>Compatibility testing<\/li>\n\n\n\n<li>Accessibility testing<\/li>\n\n\n\n<li>Reliability testing<\/li>\n\n\n\n<li>Recovery testing<\/li>\n<\/ul>\n\n\n\n<p>For example, functional testing verifies that a user can submit an order. Performance testing determines whether thousands of users can submit orders simultaneously without unacceptable delays.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Black-Box Testing?<\/strong><\/h2>\n\n\n\n<p>Black-box testing evaluates application behaviour without examining the internal source code. The tester provides inputs, observes outputs, and compares actual results with expected results.<\/p>\n\n\n\n<p>Common black-box test design techniques include equivalence partitioning, boundary value analysis, decision tables, state transition testing, and use-case testing.<\/p>\n\n\n\n<p>Manual QA engineers frequently use black-box testing to validate applications from the user\u2019s perspective.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is White-Box Testing?<\/strong><\/h2>\n\n\n\n<p>White-box testing examines the application\u2019s internal logic, code structure, paths, conditions, and data flow. It usually requires programming knowledge and is commonly performed by developers or technically skilled QA engineers.<\/p>\n\n\n\n<p>Examples include statement coverage, branch coverage, condition coverage, path testing, and unit testing.<\/p>\n\n\n\n<p>Grey-box testing combines black-box and white-box approaches. The tester has partial knowledge of the internal system but evaluates the software largely from an external perspective.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Exploratory Testing?<\/strong><\/h2>\n\n\n\n<p>Exploratory testing is an adaptive testing approach in which learning, test design, and test execution occur simultaneously. Instead of following only predefined scripts, the tester actively investigates the application and adjusts testing based on observations.<\/p>\n\n\n\n<p>Effective exploratory testing is structured rather than random. Testers may use charters, time-boxed sessions, risk areas, user personas, and documented findings to guide the process.<\/p>\n\n\n\n<p>This approach is especially useful when requirements are incomplete, deadlines are short, or the application contains complex user interactions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Agile Testing?<\/strong><\/h2>\n\n\n\n<p>Agile testing is a collaborative and continuous testing approach aligned with Agile software development. Testing occurs throughout each iteration rather than only after development is complete.<\/p>\n\n\n\n<p>QA professionals participate in requirement discussions, backlog refinement, sprint planning, daily stand-ups, test execution, defect analysis, sprint reviews, and retrospectives. They work closely with developers, product owners, business analysts, and automation engineers.<\/p>\n\n\n\n<p>In Agile teams, quality is considered a shared responsibility rather than the responsibility of the testing team alone.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Do You Test a Login Page?<\/strong><\/h2>\n\n\n\n<p>This is one of the most common practical <a href=\"https:\/\/www.h2kinfosys.com\/updated-interview-questions\/jmeter-interview-questions-for-performance-testing\/\">QA interview questions<\/a>. Candidates should cover multiple testing dimensions.<\/p>\n\n\n\n<p>Positive tests include logging in with valid credentials and verifying successful redirection. Negative tests include invalid usernames, incorrect passwords, blank fields, locked accounts, and unregistered users.<\/p>\n\n\n\n<p>Additional checks should cover password masking, case sensitivity, field length, error messages, keyboard navigation, browser compatibility, session timeout, \u201cRemember Me&#8221;, password recovery, SQL injection, cross-site scripting, multiple failed attempts, and secure transmission of credentials.<\/p>\n\n\n\n<p>A strong answer demonstrates systematic thinking rather than listing only one or two basic cases.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How do you prioritise testing when time is limited?<\/strong><\/h2>\n\n\n\n<p>When time is limited, testing should be prioritised according to risk and business impact. The QA engineer should first test critical user journeys, high-revenue functions, recently modified areas, complex integrations, security-sensitive features, and modules with a history of defects.<\/p>\n\n\n\n<p>The tester should communicate coverage limitations clearly and document any untested areas. Risk-based testing does not mean ignoring quality; it means using the available time where failures would cause the greatest damage.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Makes a Good QA Engineer?<\/strong><\/h2>\n\n\n\n<p>A good QA engineer combines technical knowledge with analytical thinking, attention to detail, curiosity, communication, and business awareness. Strong testers do not merely report defects. They investigate root causes, provide reproducible evidence, understand user expectations, identify risks, and collaborate constructively with the development team.<\/p>\n\n\n\n<p>They must also be willing to learn new domains, tools, technologies, and testing approaches as software systems evolve.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Should You Prepare for a QA Interview?<\/strong><\/h2>\n\n\n\n<p>Preparation should include reviewing testing fundamentals, practising real-world scenarios, writing sample test cases, understanding defect reports, and becoming familiar with tools such as Jira, Selenium, Postman, SQL, and test management platforms.<\/p>\n\n\n\n<p>Candidates should also prepare examples from previous projects. Interviewers often ask about challenging defects, disagreements with developers, missed bugs, release decisions, changing requirements, and situations where testing time was limited.<\/p>\n\n\n\n<p>Answers should follow a clear structure: describe the situation, explain the actions taken, and present the outcome.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Final Thoughts<\/strong><\/h2>\n\n\n\n<p>QA interviews evaluate more than memorised definitions. Employers want candidates who can apply testing principles, communicate risks, design effective test coverage, and make sound decisions under practical constraints.<\/p>\n\n\n\n<p>By studying these common QA interview questions and practising scenario-based answers, candidates can present their experience with greater clarity and confidence. Strong preparation also demonstrates the mindset that every successful QA professional needs: curiosity, precision, critical thinking, and a consistent commitment to software quality.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions About QA Interview<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1783837256211\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What Questions Are Usually Asked in a QA Interview?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>QA interviews commonly include questions about software testing fundamentals, the software testing life cycle, test cases, defect management, regression testing, smoke testing, Agile methodologies, API testing, SQL, and automation tools. Interviewers may also present practical scenarios to evaluate a candidate\u2019s analytical and problem-solving skills.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1783837280271\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How Should a Fresher Prepare for a QA Interview?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Freshers should begin by learning core testing concepts such as verification, validation, severity, priority, test scenarios, test cases, defect life cycles, and testing methodologies. They should also practise writing test cases for common applications, including login pages, registration forms, calculators, ATMs, and e-commerce websites.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1783837300301\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What Is the Best Way to Answer Scenario-Based QA Questions?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Candidates should first clarify the requirement, identify possible risks, and divide the functionality into smaller testable areas. The answer should include positive, negative, boundary, usability, compatibility, security, and performance scenarios wherever applicable.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1783837322637\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Are Coding Skills Required for a QA Interview?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Coding skills may not be mandatory for every manual QA position, but basic programming knowledge can be beneficial. Automation QA roles generally require experience with programming languages such as Java, Python, JavaScript, or C#.<br \/>Even manual testers can benefit from understanding SQL queries, browser developer tools, APIs, JSON, HTML, and basic scripting concepts.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1783837342519\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Which Tools Should a QA Candidate Know?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>he tools required depend on the role and organization. Commonly requested QA tools include Jira for defect tracking, Selenium or Cypress for web automation, Postman for API testing, Jenkins for continuous integration, Git for version control, and TestRail or Zephyr for test management.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>H2K Infosys helps aspiring software testers develop the technical knowledge, practical skills, and interview confidence required to build a successful career in quality assurance. Whether you are a fresher entering the software industry or an experienced tester preparing for your next opportunity, understanding the most common QA interview questions can significantly improve your chances of [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":42207,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[15],"tags":[156,47,51],"class_list":["post-42205","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-skill-test","tag-automation-testing","tag-qa","tag-software-testing"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/42205","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=42205"}],"version-history":[{"count":1,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/42205\/revisions"}],"predecessor-version":[{"id":42209,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/42205\/revisions\/42209"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/42207"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=42205"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=42205"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=42205"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}