A large company might have an HR department that is insulated from any of the 'technical' branches that company might have. Imagine if they had to have all sorts of knowledge about what every individual branch of the company does? It's their job to be gatekeepers that make sure the people coming in for interviews are not raising any red flags, further along in the hiring process skill will be determined.
recognizing the "JS" in AngularJS or the name of a library which has all but become synonymous with JavaScript does not require intricate knowledge of the technical branches of a company. Furthermore, if a recruiter is filtering candidates based on a technical skill, they need to know more than just that single keyword. This is not necessarily a failure on the recruiters part; it could be a failure of the hiring branch to adequately prepare the recruiter. However you look at it, it is a failure.
Actually I'm thinking of testing future candidates with a "dumb" response like this, just to see if the candidate clarifies the situation and is helpful, or if we are dealing with someone who is just rolling their eyes all day, because of all the dumb colleagues. Someone who feels the need to be condescending when someone lacks some knowledge.