Autodesk Revit Quiz: Stairs Ramps And Railings

10 questions · exam conditions

0:00

Stairs Ramps And RailingsQuestion 1 of 10

The elevation difference from the stair's Base Level to its Top Level is $3600\text{ mm}$ . Base Offset is $0\text{ mm}$ , and Top Offset is set to $-150\text{ mm}$ to stop the stair below the upper level.

What total vertical rise will Revit use when calculating the stair?

3300\text{ mm}

because the top offset is deducted from both ends

3450\text{ mm}

because the stair terminates below the top level

3600\text{ mm}

because level elevations override stair offsets

3750\text{ mm}

because a negative offset increases the stair rise

← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Stairs Ramps And Railings

Practice Stairs Ramps And Railings in Autodesk Revit with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Stairs Ramps And Railings, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Revit.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

What total vertical rise will Revit use when calculating the stair?

$3300\text{ mm}$ because the top offset is deducted from both ends
$3450\text{ mm}$ because the stair terminates below the top level (correct answer)
$3600\text{ mm}$ because level elevations override stair offsets
$3750\text{ mm}$ because a negative offset increases the stair rise

Explanation: When working with Revit stairs, the actual vertical rise the software calculates is determined not by the raw level-to-level distance, but by the effective travel distance after applying both the Base Offset and Top Offset. Think of it as: Revit measures from where the stair actually starts to where it actually ends. The formula is straightforward:

\text{Total Rise} = (\text{Top Level} - \text{Base Level}) + \text{Top Offset} - \text{Base Offset}

. Plugging in the given values:

3600 + (-150) - 0 = 3450\text{ mm}

. The negative Top Offset pulls the stair's termination point downward from the upper level, shortening the total rise to

3450\text{ mm}

. That confirms B is correct. A is wrong because it suggests deducting the offset from both ends (which would give

3300\text{ mm}

). Offsets are independent — the Base Offset here is

0\text{ mm}

, so only the Top Offset affects the result. C is wrong because it assumes level elevations override offsets entirely. Offsets exist precisely to adjust the effective rise away from the raw level difference — Revit absolutely incorporates them in the calculation. D reflects a misreading of the negative sign: a negative Top Offset does not extend the stair beyond the upper level; it moves the endpoint below it, reducing the total rise. As a study tip, always treat Base Offset and Top Offset as signed adjustments applied after the level difference. When you see a negative Top Offset, immediately recognize it shrinks the effective rise — don't let the minus sign trick you into thinking it adds height.

Question 2

A designer is creating a sketch-based stair run because the run has a nonstandard outline. The sketch currently contains two side boundaries, but no transverse lines defining the individual steps.

What must be added for Revit to recognize a valid stair run?

Riser lines spanning between the two boundaries at the required step locations (correct answer)
Model lines spanning beyond both boundaries at the required step locations
Landing boundaries enclosing every tread as a separate closed region
A slope arrow connecting the lower boundary directly to the upper boundary

Explanation: When working with sketch-based stairs in Revit, it helps to understand what the sketch engine actually needs to define a stair run. A run sketch requires two types of lines working together: boundary lines (the side edges of the run) and riser lines (the transverse lines that mark each step location). Boundaries alone tell Revit where the run is wide and long, but they don't communicate where individual risers fall — so Revit has no way to calculate tread depth, riser count, or step geometry without them. Answer A is correct because riser lines are the missing ingredient. They must span between the two side boundaries at each step location, giving Revit the data it needs to generate a valid, calculable stair run. Without them, the sketch is incomplete and Revit will not allow you to finish it. Answer B is wrong because model lines are not part of the stair sketch environment — they belong to the general model context and Revit won't interpret them as stair geometry. Extending lines beyond the boundaries would also invalidate the sketch topology. Answer C confuses run sketching with landing sketching. Landings have their own closed-region boundaries, but individual treads are never enclosed as separate regions inside a run — that's not how Revit's stair logic works. Answer D describes a slope arrow, which is a tool used in floor or roof sketches to define a sloped plane, not a stair component. A good rule of thumb: in Revit stair sketches, boundaries define shape, risers define steps — you always need both for a complete run.

Question 3

A ramp has already been modeled, but it has no guardrail. The required railing must follow the ramp's inclined run and its landing automatically rather than remain at one level.

Which placement workflow should the designer use?

Start Railing, choose Place on Host, and select the completed ramp (correct answer)
Start Railing, sketch a level path, and constrain it to the ramp centerline
Start Stair, select the ramp edges, and convert them into railing boundaries
Start Model Line, trace the ramp slope, and assign the railing category afterward

Explanation: When working with railings in Revit, the key concept to understand is the difference between a hosted railing and a sketched railing. Railings can either be placed on a host element (like a stair or ramp), which causes them to automatically follow the host's geometry, or they can be sketched manually on a flat level. Because the ramp already exists and has an inclined run plus a landing, the most efficient and accurate approach is to use Place on Host. When you start the Railing tool and choose "Place on Host," then click the ramp, Revit reads the ramp's slope and landing geometry automatically — the railing path conforms to the incline without any manual sketching. This is exactly what answer A describes, making it the correct workflow. Answer B is tempting but flawed: sketching a level path means the railing stays at one elevation, which is precisely the problem the question says must be avoided. A manually sketched path won't automatically follow a slope unless you edit each segment's offset individually — a tedious and error-prone process. Answer C confuses tools entirely. The Stair tool creates stairs, not railings, and you cannot convert ramp edges into railing boundaries through it. This reflects a common misconception about Revit's tool categories. Answer D describes a workaround using Model Lines, which have no built-in railing behavior. Assigning a category afterward is not a valid Revit workflow — categories are set by the element type, not reassigned post-creation. As a study tip, remember: hosted railings follow the host; sketched railings stay level. Whenever a sloped element already exists, "Place on Host" is almost always the right answer.

Question 4

A component stair requires $18$ risers. The first straight run is placed with $9$ risers. The designer then begins a second straight run at the end of the first run and draws it in the return direction.

What is the expected Revit workflow result before the stair is finished?

Revit creates a connecting landing and sizes the second run for the remaining risers (correct answer)
Revit creates a connecting landing but repeats all of the risers in the second run
Revit joins the runs directly and requires the landing to be modeled as a floor
Revit keeps both runs separate until a sketch-based landing is drawn manually

Explanation: When working with component stairs in Revit, understanding how the stair tool manages riser counts automatically is essential. Revit tracks the total required risers and intelligently distributes them across multiple runs as you build the stair. Here's the key behavior: once you place the first run with

9

risers and begin drawing a second run in the return direction, Revit automatically inserts a connecting landing between the two runs and calculates that

18 - 9 = 9

risers remain. It then sizes the second run to accommodate exactly those remaining

9

risers. This makes answer A correct — the landing and riser distribution happen automatically, which is one of the primary advantages of the component stair workflow over the legacy sketch-based approach. Answer B is wrong because Revit does not blindly repeat all

18

risers in the second run — it tracks remaining risers globally across the entire stair assembly, not per run. Answer C is incorrect because Revit does not require you to manually model a floor as a landing; the component stair tool generates the landing automatically when runs are connected. Answer D describes behavior closer to the older sketch-based stair method, where elements were more manually managed — the component stair tool actively connects runs and generates landings without waiting for manual input. As a study tip, remember that the component stair tool in Revit is "riser-aware" — it continuously tracks how many risers are placed versus how many are needed, and automates landing creation between runs. Questions about stair workflows often test whether you know this automation behavior versus the manual sketch approach.

Question 5

A ramp must rise $600\text{ mm}$ . Its type permits a maximum slope of $1:12$ and a maximum continuous incline length of $6000\text{ mm}$ .

Which configuration satisfies both type constraints?

One inclined run measuring $6000\text{ mm}$ with no intermediate landing
One inclined run measuring $7200\text{ mm}$ with no intermediate landing
At least two inclined runs totaling $7200\text{ mm}$ , separated by a landing (correct answer)
At least two inclined runs totaling $6000\text{ mm}$ , separated by a landing

Explanation: When configuring a ramp in Revit, you need to satisfy two independent constraints simultaneously: the slope limit and the maximum continuous run length. Missing either one means the configuration fails. Start with the slope calculation. A

1:12

slope means for every

12\text{ mm}

of horizontal run, the ramp rises

1\text{ mm}

. To achieve a total rise of

600\text{ mm}

, the minimum total horizontal length required is

600 \times 12 = 7200\text{ mm}

. This tells you the ramp must span at least

7200\text{ mm}

horizontally to meet the slope constraint — you cannot make it shorter without exceeding the

1:12

limit. Now apply the second constraint: no single continuous inclined run may exceed

6000\text{ mm}

. Since the total required length is

7200\text{ mm}

, it cannot be completed in one uninterrupted run. The solution is to split it into at least two runs separated by a landing, with each individual run staying within

6000\text{ mm}

. That is exactly what C describes — at least two runs totaling

7200\text{ mm}

, separated by a landing — satisfying both constraints. A fails because

6000\text{ mm}

of total run only produces

500\text{ mm}

of rise

(6000 \div 12)

, falling short of the required

600\text{ mm}

. B achieves the correct total length of

7200\text{ mm}

but places it in a single continuous run, violating the

6000\text{ mm}

maximum run length. D uses the correct structure (split runs with a landing) but the wrong total length —

6000\text{ mm}

only yields

500\text{ mm}

of rise. A useful habit: always solve for required length first using the slope ratio, then check whether that length exceeds the single-run maximum. If it does, a landing is mandatory.

Question 6

A building has identical floor-to-floor stair conditions from Level 1 through Level 5. A completed stair currently connects Level 1 to Level 2, and the design should remain associated across the repeated stories.

Which workflow is most appropriate for extending the stair through the remaining levels?

Create one tall stair with Level 5 as its top level and add intermediate landings
Copy the stair in elevation and manually align each copy with its destination level
Array the stair vertically and lock each array member to the nearest floor slab
Create a multistory stair from the completed stair and connect the additional levels (correct answer)

Explanation: When working with repetitive vertical conditions in Revit — identical floor-to-floor heights, same stair configuration across multiple stories — the tool you should immediately think of is the Multistory Stair feature. This question tests whether you know how to leverage that built-in functionality rather than resorting to manual workarounds. Revit's Multistory Stair workflow lets you take a single completed stair run and extend it through additional levels while maintaining a single, parametric association. Once you select the stair and use the "Connect Levels" option (found in the Multistory Stairs panel), Revit replicates the stair geometry for each selected level and keeps all instances linked — change the base stair, and every story updates automatically. That's exactly why D is the correct approach here. A is tempting but wrong: creating one tall stair with intermediate landings treats the entire run as a single object, which complicates editing, doesn't respect level associations properly, and can cause structural and scheduling issues. B is a manual copy-paste approach that breaks parametric relationships — each copy becomes an independent element with no awareness of the others, meaning any design change requires repeated manual updates. C might seem clever since arrays replicate geometry, but Revit arrays don't understand level associations or stair-specific parameters; you'd end up with unconnected, dumb copies that can't be managed as a stair system. A useful study tip: whenever a Revit question describes repetitive conditions across levels, look for the purpose-built tool (Multistory Stair, linked levels, or scope boxes) rather than generic modeling workarounds — Revit almost always has a smarter, associative solution.

Question 7

A stair must initially be created without automatic railings because a custom guard system will be modeled later. The designer has started the Stair command but has not yet placed any runs.

Which action most directly prevents the standard stair railings from being generated?

Set the railing selection to None before placing and finishing the stair runs (correct answer)
Set the stair run's Structural property to off before finishing the stair
Set the landing type to None before placing the first stair run
Set the run justification to Center before finishing the stair assembly

Explanation: When creating stairs in Revit, the software automatically generates railings as part of the stair assembly — but this behavior can be controlled before you commit the stair. The key is understanding that railing generation is tied to a setting you configure during the Stair command, not something you clean up afterward. While you're in the Stair editing mode (before placing any runs), the Options Bar and contextual tools allow you to specify which railing type gets generated. By setting the railing option to None before placing and finishing the stair runs, you instruct Revit to skip automatic railing creation entirely. This is exactly what answer A describes — it's the direct, purpose-built control for this workflow. Answer B is a trap. The Structural property on a stair run affects whether the run is treated as a structural element for analysis purposes; it has no connection to railing generation whatsoever. Answer C confuses landing type with railing behavior. Landing type controls the geometry of the landing slab (none, cast-in-place, etc.), not whether railings are created along the run edges. Changing it won't suppress railings. Answer D is similarly unrelated. Run justification (Left, Center, Right) simply determines how the run aligns relative to the boundary lines you draw — it has nothing to do with railing creation. As a study tip, remember that in Revit, automatic component generation (like railings on stairs or floors between levels) is almost always controlled by a type or instance setting within that command session, not by editing the resulting elements after the fact. Look for that setting first.

Question 8

A stair connects two levels separated vertically by $3150\text{ mm}$ . The project standard limits the riser height to $180\text{ mm}$ .

Which Desired Number of Risers should be used to satisfy the height limit with the fewest risers?

$17$ risers, producing an actual riser height of approximately $185.3\text{ mm}$
$18$ risers, producing an actual riser height of exactly $175\text{ mm}$ (correct answer)
$18$ risers, producing an actual riser height of exactly $180\text{ mm}$
$19$ risers, producing an actual riser height of approximately $165.8\text{ mm}$

Explanation: When sizing a stair in Revit, your goal is to find the minimum number of risers such that the actual riser height stays at or below the code limit. You calculate actual riser height by dividing the total rise by the number of risers:

\text{Actual Riser Height} = \frac{\text{Total Rise}}{\text{Number of Risers}}

. Start by finding the theoretical minimum:

\frac{3150}{180} = 17.5

. Since you can't have a fractional riser, you must round up to the next whole number — 18 risers. Plugging that back in:

\frac{3150}{18} = 175\text{ mm}

, which is under the 180 mm limit. So 18 risers producing 175 mm is the correct answer — choice B. Choice A uses 17 risers, giving

\frac{3150}{17} \approx 185.3\text{ mm}

. This violates the 180 mm limit, making it a non-starter regardless of having fewer risers. Choice C also states 18 risers but claims an actual height of exactly 180 mm — this is simply wrong arithmetic;

3150 \div 18 = 175

, not 180. This is a trap for students who confuse the limit with the result. Choice D uses 19 risers, yielding

\approx 165.8\text{ mm}

, which is code-compliant but adds an unnecessary extra riser when 18 already satisfies the constraint. A useful rule of thumb: always divide total rise by the limit, round up, then verify by recalculating the actual height. On stair-related exam questions, watch for distractors that either break the code limit or waste risers unnecessarily — the answer is always the smallest compliant count.

Question 9

Several ramps use the same railing type. Only one ramp requires a different guard height and baluster arrangement; all other railings must remain unchanged.

What is the most appropriate workflow?

Edit the ramp type, modify its guard settings, and reload the railing geometry
Modify the existing railing type, then restore the other railings one at a time
Ungroup the selected railing, modify its balusters, and retain the original type
Duplicate the railing type, modify the duplicate, and assign it to that railing (correct answer)

Explanation: Whenever you see a Revit question about modifying one instance of a type while leaving all others unchanged, you should immediately think about type vs. instance management. Railing types in Revit are shared definitions — editing the type affects every element using it, which is exactly the trap this question is built around. The correct approach is D: duplicate the railing type, configure the duplicate with the required guard height and baluster arrangement, then assign that new type only to the one ramp that needs it. This is the fundamental Revit workflow for customizing a single element without disturbing others. The duplicate becomes an independent type, so any edits you make are fully isolated. A is wrong because ramp types and railing types are separate objects in Revit. Editing a ramp type's properties does not give you direct control over railing geometry like baluster spacing or guard height — those belong to the railing type itself. B describes the most dangerous approach: modifying the shared railing type will instantly update all railings using it, forcing you to manually restore every other railing — an error-prone, time-consuming process that defeats the purpose of type-based BIM workflows. C is a misconception. Railings in Revit are not grouped objects that you "ungroup." You cannot detach baluster settings from the type definition by ungrouping; the type still governs the element's properties. Study tip: On Revit exam questions, any time the scenario says "only one element needs to change," the answer almost always involves duplicating the type — never editing the shared original.

Question 10

A straight sketch-based ramp is valid, but its clear width must be reduced while its lower and upper endpoints remain at the same locations. The ramp has two longitudinal boundary lines and transverse riser lines at its ends.

Which edit most directly changes only the ramp width?

Move both transverse risers inward while leaving the longitudinal boundaries unchanged
Move the upper transverse riser toward the lower riser while retaining both boundaries
Move one longitudinal boundary inward while keeping valid connections to both end risers (correct answer)
Shorten one longitudinal boundary so it no longer reaches the upper transverse riser

Explanation: When editing a sketch-based ramp in Revit, it helps to think about what each sketch element controls. A ramp's sketch has two distinct element types: longitudinal boundary lines (the long sides, defining width) and transverse riser lines (the short ends, defining the ramp's start and finish elevations and length). The question asks you to change only the width while keeping both endpoints — meaning the riser positions — fixed. Moving one longitudinal boundary inward, as described in C, directly narrows the distance between the two long sides without touching either riser line. The ramp's length and endpoint locations stay exactly where they are, and both end connections remain valid. This is the most targeted and geometrically correct edit for reducing clear width only. Choice A is wrong because moving the transverse risers inward changes the length of the ramp and shifts its endpoints — precisely what the question says must not happen. Choice B compounds this error: sliding the upper riser toward the lower one shortens the ramp's run, changing both length and the elevation transition, not the width. Choice D is a trap for students who confuse "shortening a line" with "moving a boundary." Shortening one longitudinal boundary so it no longer reaches the upper riser breaks the sketch's closed-loop requirement, creating an invalid, open profile that Revit will reject entirely. A useful rule of thumb: in Revit sketch editing, width is owned by the boundary lines, length and position are owned by the riser lines. Any time a question asks you to isolate one dimension, identify which sketch element type exclusively controls it.