How do you manage time-bound architecture exceptions?

Question

IT Interview Practice · Accepted Answer

Treat an **architecture exception** as an explicit, bounded acceptance of a deviation, with an accountable owner and an exit plan. A launch deadline is context for the decision, not automatic authorization to bypass a constraint.

## Decide whether an exception is possible

Identify the exact principle or standard being violated and why it exists. Check who has authority to accept the resulting risk. Some constraints are non-negotiable for the project; if no authorized exception is possible, reduce scope or change the launch plan.

Compare the proposed exception with at least one feasible alternative. Document affected systems, users, data, likely failure modes and the business consequence of delay. Avoid a broad waiver such as “temporary legacy integration.”

## Example: a temporary file exchange

Suppose a launch cannot wait for the standard integration platform. A narrowly scoped exception allows one daily order file transfer between two named systems for six weeks. It does not authorize unrelated file feeds.

The exception record includes:

- The accountable risk owner and required reviewers.
- The allowed interface and volume, with a clear start date and expiry date.
- Compensating controls, such as restricted access, validation, reconciliation and monitored delivery.
- A funded replacement task with an implementation owner and milestones.
- Evidence needed for closure, plus a fallback if replacement misses its deadline.

The controls reduce particular risks; they do not make the exception equivalent to the standard architecture.

## Review and close it

Review progress before expiry, while alternatives remain possible. Any extension needs an explicit new decision based on current evidence, not an automatically renewed date. Escalate overdue exceptions to the named owner.

Close only after verifying that the replacement works and the temporary path, credentials and operational dependencies have been retired as appropriate. A completed ticket alone is insufficient.

## Interview signal

Balance delivery with accountable risk management. Both blanket refusal and an undocumented workaround avoid the actual decision. Explain scope, authority, evidence and how the organization prevents temporary exceptions from becoming permanent architecture.

Decide whether an exception is possible

Example: a temporary file exchange

Review and close it

Interview signal

Related questions