2.2.7 · D5Functions
Question bank — Transformations — vertical - horizontal shifts, reflections, stretches - compressions
Before we start, one reminder in plain words: the input of a function is the number you feed in (the ), and the output is the number that comes out (the height, the ). Every trap below is really about one question — did we touch the input or the output?

True or false — justify
Each of these looks obviously true or obviously false. The catch is in the reason, not the verdict.
shifts the graph up 3, and shifts it right 3.
False on the second part — shifts left 3. Adding inside the bracket makes the function reach its old behaviour at a smaller , so the graph slides toward the negatives (left).
For , a bigger multiplier means a wider, more stretched-out graph.
False. Multiplying the input by makes the function race through its values in half the horizontal distance, so it compresses toward the -axis — bigger inside multiplier means narrower.
and are the same transformation.
False. negates the output (flip over the -axis, up↔down); negates the input (flip over the -axis, left↔right). Same minus sign, opposite mirror.
Multiplying a function by only reflects it, nothing else.
False. does two things at once: reflect across the -axis (from the minus) and vertically stretch by factor (from the size). Sign and magnitude act independently.
The transformation never changes the domain of the function.
True. Adding changes only outputs (heights), so the set of allowed inputs is untouched. Only horizontal transformations can move the domain — see Domain and Range.
A vertical stretch by factor moves the -intercepts.
False. At an -intercept the output is , and , so those points are pinned in place. Only points off the -axis get pulled away.
For with , every point becomes .
True. To reproduce the old output you now need a larger input, so each point slides right by . The "" in the formula and "" for the point moving are two sides of the same compensation.
Reflecting across the -axis gives a graph with the same domain.
False. lives on ; lives on . A -axis reflection flips the domain across zero too — inputs move, so their allowed set moves.
can always be built regardless of the order you apply the four steps.
False. Because inputs are processed first (composition works inside-out), horizontal steps and vertical steps each have their own required order. Do horizontals before verticals, and inside the bracket handle the shift before the scale — see Function Composition. The worked ordering in the "Why questions" section below shows exactly what goes wrong if you don't.
Spot the error
A worked solution is shown with one flaw. Find it and say why it breaks.
"To graph , I read off and , so I compress by 2 and shift left 6."
The input isn't in the form yet. Factor first: , so (shift right 3), not . Never read off before factoring the coefficient out.
" stretches the graph horizontally because the number is large."
Backwards. Inside multipliers invert their effect: input means the graph hits each output three times sooner, so it compresses. Large inside number → narrow graph.
"For the amplitude changes from 1 to 2."
The is inside the cosine, so it changes the period (halves it), not the amplitude. Amplitude only changes when a number multiplies the output, like .
" shifts right 2 and down 5."
Down 5 is right, but shifts left 2, not right. The outside subtraction behaves as expected; the inside addition flips direction.
"To turn into I compress it, doubling the frequency."
A factor of inside means , which stretches horizontally and halves the frequency (period doubles to ). Small inside multiplier → wider graph.
"Since reflects and shifts, I'll add 1 first, then multiply by ."
Wrong order. The is the outermost operation, so it happens last. Applying it first would give , a different function. Follow the composition from inside out.
" is just a vertical reflection of ."
Only the parts below the -axis get reflected upward; parts already above stay put. It's a piecewise fold, not a full flip — see Absolute Value Functions and Piecewise Functions.
Why questions
The "obvious" answer is often the wrong instinct. Explain the real mechanism.
Why does subtracting inside the bracket, , move the graph right instead of left?
Because the graph plots outputs against inputs: to recreate the output that used to appear at input , you must now feed in (so that ). Larger required input = rightward slide.
Why do vertical transformations feel "intuitive" while horizontal ones feel reversed?
Vertical transformations act on the output after the function runs, so "" literally adds height — no inversion. Horizontal ones act on the input before the function runs, so you must compensate for what the function will do, which flips the direction.
Why must horizontals be done before verticals — walk me through what breaks otherwise?
Take and build . Correct order: shift right 1 first, sending , then stretch vertically by 2, keeping it at — the vertex lands at . If instead you stretch first to get and then try to "shift right 1" by replacing with , you get — which happens to agree here, but the shift you actually applied moved the input, not the already-scaled output. The safe rule is: inside-the-bracket steps ( then ) act on and must be settled before the outside steps ( then ) act on the finished output. See Function Composition.
Why, inside the bracket, must the shift be handled conceptually together with (not after) the scale ?
Because scales the already-shifted coordinate. Compare (shift right 1, then compress) with (compress, effectively shifting right only ). Same-looking numbers, different graphs — which is exactly why you factor to read the true from .
Why is described as "reflect and stretch" rather than one single move?
A negative carries two pieces of information: its sign (a mirror across the -axis) and its size (the scaling factor). These are logically separate, so we name both. For it's a pure reflection.
Why does a vertical stretch leave the period of unchanged?
Period is a horizontal property (how far along before it repeats), but a vertical stretch only touches outputs. Nothing about the input's spacing changes, so the wave repeats at the same rate — just taller. See Trigonometric Functions.
Why does reflecting a function's input also reflect its inverse relationship in a specific way?
Because swapping input for output is what an inverse does, so input-side transformations of correspond to output-side transformations of . The "inside vs outside" roles trade places — explored further in Inverse Functions.
Why can't we always write "" without factoring before identifying the shift?
Take . Read naively, you might call the shift . But factor: , so the true shift is , not — the was hiding inside. In general , so the real shift is ; skipping the factor step misidentifies both the distance and (if ) the direction.
Edge cases
Every quadrant, every sign, every degenerate value. These are the boundaries the rules quietly depend on.
What does do when ?
It collapses the entire graph onto the line (the -axis), because every output becomes . This is why the definition requires — at the function is destroyed, not transformed.
What does do when ?
The input becomes a constant for every , so is a flat horizontal line. All information about is lost, which is why is required.
For a general negative , say , what two things happen at once and in which order do they matter?
The magnitude compresses horizontally (points move from to ), and the minus sign reflects across the -axis (points then flip to ). Combined, a point at input lands at : for every point becomes , which folds the graph to the opposite side and squeezes/stretches it by — the special case is just the pure reflection with no scaling.
What does do when , e.g. ?
Two effects: reflect across the -axis (from the minus) and stretch horizontally by (since ). A point at maps to , farther out and flipped — showing negative with small magnitude still reflects but widens rather than narrows.
What happens to under , and why does it look like nothing changed?
Because is symmetric about the -axis (even function), reflecting across that axis maps it onto itself. The transformation happened; the graph just happens to be its own mirror image.
What is the effect of ?
Nothing — it's the identity transformation. Zero shift in both directions leaves every point exactly where it was, a useful sanity check that the point-mapping rules reduce correctly.
If but , is that a stretch, a compression, or neither?
Neither in size — it's a pure reflection across the -axis, since multiplying by keeps each output's distance from the axis but flips its sign. Only adds actual stretching or compressing.
For with , why does the domain grow rather than shrink?
A point at input moves to , and dividing by a number below makes it larger in magnitude, spreading points outward. The stretch pulls the domain wider — matching that small means horizontal stretch.
Which parameter choices in leave every point of fixed, and how do we check?
Only (the identity). Systematic check by testing the four transformations one at a time: moves the point off the axis; moves the zero at to ; changes the peak height from ; changes the period from . Since each nonzero/non-unit parameter visibly relocates at least one identified point, no non-trivial choice can fix the whole curve.