There are two ways I might consider handling this...
The first, using Segments.
I would create a Hit level segment with two containers inside it, one being a "hit" level, the other being a "visit" level.
HIT
HIT (container)
Page equals "Page B"
AND
VISIT (container)
Page equals "Page A"
THEN
Page equals "Page B"
This will limit the resulting data to just "Page B", where in the visit the user hit Page A followed by Page B
If Page A and Page B are directly in line with one another, you can strengthen the "THEN" clause by adding a "within 1 Page View", meaning that it will restrict the Page A to Page B more than just that order any time during the visit.
The second option is to use a Fallout Report
Drag in Page A to the first touchpoint
then drag in Page B to the second touchpoint
Fallout visualizations already restrict the order of the pages within the fallout... in order for Page B to show in this visualization, the user must first have visited Page A
You can change the setting from "Visitor" which will cross visits, to "Visit" so that Page A > Page B must be in the same Visit, and in the fallout, you can change the paths between "Eventual Path" which means Page A > some other pages > Page B, or to "Next Hit" which again should restrict the fallout to the user going directly from Page A to Page B