Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Interviews in Terraform

        Work in the tool while you explain your decisions.

        Choose a role and level. Each interview has a new task, follow-up questions and a report that checks your work and your explanation.

        Speak or type. Sign in to save your results across devices.

        Timed assessment

        • 6 practical questions
        • 25 minutes
        • Mid level

        Questions are drawn from a bank of 18. Your report includes a skill breakdown and lessons to practice next.

        Practice interviews

        Junior tasks cover the fundamentals. Mid and senior tasks add debugging, changing requirements and review decisions.

        6 interviews

        • Cloud engineer
        • Junior
        • 30 min

        A capacity plan before release

        Save review.tfplan for the requested capacity increase. Leave the managed service unchanged for review. Scope: name hub-dispatch-120; current size 2; requested size 4.

        Start interview
        Skills and rubricA capacity plan before release
        • Complete the requested operation, identify the resource and compare its result with one source fact.
        • I save the plan before mutation because the reviewer needs to inspect one in-place update while the old service remains unchanged. I compare the requested address and proposed capacity with the managed resource. Applying the change before that review would cross the release boundary even if the new size were correct.
        • A saved plan does not mutate the provider. Compare the old managed size with the proposed new size. Editing current configuration does not rewrite a saved plan: applying it uses the recorded decisions. When requirements change, generate and review another plan; state or workspace changes can also invalidate a saved plan.
        • Platform engineer
        • Junior
        • 30 min

        Adopt an existing service

        Import the existing provider object at lab_server.api. Preserve its identifier and finish with a no-change plan. Scope: name or name prefix hub-dispatch-121; required size 3; existing provider identifier existing-121.

        Start interview
        Skills and rubricAdopt an existing service
        • Complete the requested operation, identify the resource and compare its result with one source fact.
        • I import the existing provider identifier because equal names do not establish object identity. Import creates a state binding instead of another service. I compare the imported identifier and requested attributes, then review a no-change plan; import success alone can still leave a later update or destructive replacement.
        • The provider identifier distinguishes adoption from creating an equal-looking replacement. Compare that identifier after import and inspect the next plan. A zero-change plan on a newly created duplicate would not satisfy the original identity requirement.
        • DevOps engineer
        • Mid
        • 30 min

        Rename an address without replacement

        Rename lab_server.api to lab_server.dispatch with a moved block. Apply the state migration and preserve the provider identifier. Scope: name or name prefix hub-dispatch-122; required size 4; existing provider identifier existing-122.

        Start interview
        Skills and rubricRename an address without replacement
        • Demonstrate the named failure boundary and repeat the relevant check after the requirement changes.
        • An address rename changes state identity even when resource arguments are identical. The moved declaration maps the prior address, allowing the provider identifier to survive. Check both the absent old address and the present new address before relying on the result.
        • Another team already uses the destination address. Stop the migration and inspect ownership before editing state. Choose an unused approved destination and review the whole move map because overwriting another binding would lose the evidence needed for safe recovery.
        • Cloud engineer
        • Mid
        • 30 min

        A module output contract

        Call ./modules/service as dispatch. Pass the supplied name and capacity and expose server_id as root output dispatch_id. Apply the configuration. Scope: name or name prefix hub-dispatch-123; required size 5; existing provider identifier existing-123.

        Start interview
        Skills and rubricA module output contract
        • Demonstrate the named failure boundary and repeat the relevant check after the requirement changes.
        • Child output and root output are separate interfaces. Exposing a child value does not automatically create a root output. Read the declared child output and compare the resulting root value with the child resource instead of creating a separate root object.
        • A new module version renames its output. Review the interface change, update the caller and check the root value before applying. The provider lockfile does not pin module source versions, so retain the exact module reference with the reviewed plan.
        • Platform engineer
        • Senior
        • 30 min

        Record drift without reverting the provider

        Use refresh-only apply to record the authorized external capacity change. Keep configuration unchanged for its owner to review. Scope: name hub-dispatch-124; configured size 2; observed provider size 5; identifier existing-124.

        Start interview
        Skills and rubricRecord drift without reverting the provider
        • Defend the provider identity, approval and recovery boundaries before another engineer applies this change.
        • The owner now approves the externally observed capacity as desired. Update configuration to match it, then review an ordinary no-change plan. A refresh-only apply alone would leave the old configuration capable of proposing a rollback later.
        • I retain the request, configuration, provider identifiers, prior state and reviewed plan because another engineer must reproduce the result. I record which operation changed state and which changed infrastructure, test an unrelated object remains intact and name the owner of any unresolved desired-state decision.
        • DevOps engineer
        • Senior
        • 30 min

        Stable service keys

        Create two lab_server.api instances with for_each keys east and west. Use the supplied name prefix and capacity and apply. Numeric count addresses do not satisfy the identity requirement. Scope: name or name prefix hub-dispatch-125; required size 3; existing provider identifier existing-125.

        Start interview
        Skills and rubricStable service keys
        • Defend the provider identity, approval and recovery boundaries before another engineer applies this change.
        • Add a north service without changing the east and west keys. Review the plan for one creation and preserve the two existing provider identifiers. Removing a key represents a separate deletion decision and must not be hidden inside the addition.
        • I retain the request, configuration, provider identifiers, prior state and reviewed plan because another engineer must reproduce the result. I record which operation changed state and which changed infrastructure, test an unrelated object remains intact and name the owner of any unresolved desired-state decision.

        Interview Hub access

        The Interview Hub is included in All Access. Choose a plan or sign in to your account to continue.

        View plansSign in or join

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Change your plan

        Checking the price

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.