Service Design · interview question

Which naming or modeling choice is strongest for dependency injection?

Multiple choiceMediumchapter-13-curatedpremiumservice-designdependency-injection

python

from fastapi import Depends

def get_repo() -> OrderRepository:
    return OrderRepository()

@app.get("/orders")
def list_orders(repo: OrderRepository = Depends(get_repo)) -> list[dict]:
    return repo.list_recent()

Keep dependency injection implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Solve the symptom with comments only and avoid changing the code shape around dependency injection.Use names and structures that describe the business fact directly instead of temporary implementation noise.

Answer and explanation

Correct answer

D. Use names and structures that describe the business fact directly instead of temporary implementation noise.

Why

Clear naming and modeling shorten debugging, review, and onboarding time.

Test yourself on Service Design

A free test with instant, explained results. No account needed.

Start free test

All Service Design questions →

Which naming or modeling choice is strongest for dependency injection?

Correct answer

Why

More Service Design questions