What are the outputs of performing a web application mapping process? (Choose two)

Question

Options

• AA flowchart of application functionality
• BA report of missing patches
• CA list of accessible URLs and endpoints
• DA database schema

• A
  73% (27)
• B
  11% (4)
• D
  16% (6)

Explanation

Web application mapping is the reconnaissance process of discovering and documenting the structure of a web application - what pages exist, what endpoints are exposed, and how the application flows. This process produces a flowchart of application functionality (A) because mappers diagram how pages link together and how user interactions traverse the app. It also produces a list of accessible URLs and endpoints (C) since tools like spidering/crawling enumerate every reachable resource - forms, APIs, parameters, and directories.

Why the distractors are wrong:

• B (missing patches): Patch identification is the output of a vulnerability scan or patch audit, not application mapping.
• D (database schema): Schema discovery requires database enumeration or code review - mapping only sees what's exposed over HTTP, not the backend data model.

Memory tip: Think of mapping as drawing a map - you get a visual diagram (flowchart) and a list of destinations (URLs/endpoints). Patches and databases live "behind the walls" of the map and require separate tools to uncover.

No community discussion yet for this question.