Why is scraping the watsonx.data web interface an unsuitable integration strategy for an application?
Select an answer to reveal the explanation.
Short Explanation
You shouldn't scrape the watsonx.data web interface because it's built for humans, not applications. Its screens and controls can change without warning, and automating it pushes you into using someone's login instead of proper service authentication.
Full Explanation
The suitable integration strategy is a documented API or driver, not scraping the watsonx.data web interface. A user interface carries no compatibility guarantee: layout, element identifiers, and workflows can change between releases, so a scraper can break without warning. It also assumes an interactive human session, which means automating it forces the use of borrowed user credentials rather than a proper service authentication model. The objection to scraping the web interface is therefore stability and authentication. The wrong option about the interface rendering results too slowly is incorrect because speed is not the fundamental objection; even a fast UI would still be unsupported and fragile. The wrong option about the interface returning only aggregated data is also incorrect because the console can display row-level results, so data restriction is not the issue. The wrong option about the interface being unavailable outside business hours is factually wrong, and availability is not what makes scraping the web interface inappropriate. For the exam, scraping a human UI lacks a stability contract and proper service authentication, while the supported alternative is always a documented API or driver.