SDD Assessment | Azure AI Deployment Patterns

Ten scenario-based questions organized into four focus areas with immediate scoring and evidence-based explanations.

Section 1

Requirements and Acceptance Criteria

Evaluate whether requirements are measurable, precise, and testable.

3 questions

1. Requirement Clarity

Which requirement is written in the most testable way?

A. System must respond quickly during peak traffic. B. API response time must remain under 300 ms at p95 while handling 200 requests per second for 15 continuous minutes. C. Service should scale if usage increases significantly.

2. Acceptance Criteria Strength

For an input validation feature, which acceptance criterion is strongest?

A. Validation should pass in most cases. B. Requests missing required fields are rejected with HTTP 400 and field-level error messages. C. Validation behavior should be user friendly.

3. Boundary Coverage

A field allows 1 to 50 characters. Which acceptance criterion best covers the boundary?

A. The field should usually accept valid values. B. Inputs of 0 and 51 characters are rejected, while inputs of 1 and 50 characters are accepted. C. The field length should be checked before saving.

Section 2

Traceability and Release Controls

Assess traceability coverage and release governance decisions.

3 questions

4. Traceability Mapping

If requirement FR-03 has implementation changes but no linked test case, which practice is missing?

A. Better commit message B. Requirement-to-test traceability C. More architecture diagrams

5. Gate-Based Release Decisions

A release gate fails because rollback steps are missing. What is the correct next action?

A. Proceed and document rollback after release B. Treat the gate as informational and proceed without approval C. Stop the release until rollback steps are documented and reviewed

6. Release Readiness Evidence

Which artifact best supports a claim that a feature is ready to release?

A. A message saying the team feels confident B. A checklist showing tests passed, approvals completed, and rollback steps reviewed C. A slide deck summarizing the sprint

Section 3

Spec Writing Quality

Identify subjective language and anti-patterns that reduce specification quality.

3 questions

7. Anti-Pattern Diagnosis

Which line is the clearest example of a spec anti-pattern because it is subjective?

A. "System must feel fast and stable." B. "Error rate must remain below 0.5% over a 24-hour window." C. "All required fields are validated before deployment trigger."

8. Implementation Leakage

Which line is least appropriate in a high-level feature spec because it over-prescribes implementation?

A. "The service exposes a searchable document catalog to authenticated users." B. "The handler must use a for-loop with exactly three retries and a 250 ms sleep call." C. "Failed requests are logged with correlation IDs for investigation."

9. Non-Functional Requirement Quality

Which statement is the best non-functional requirement?

A. "The application should be reliable." B. "The service should avoid downtime whenever possible." C. "Monthly uptime must be at least 99.9%, excluding approved maintenance windows."

Section 4

Verification, Risk, and Change Control

Confirm that changes and release decisions remain evidence-driven and formally controlled.

1 question

10. Controlled Scope Change

During implementation, the team wants to add behavior that is not in the approved spec. What should happen first?

A. Add the change immediately and update the spec after release B. Update the spec, review the impact, and get approval before treating the change as in scope C. Reject the request entirely because an approved spec can never change

Complete all 10 questions. Select one response for each question before submitting.

Spec-Driven Development Assessment

Assessment Overview

Requirements and Acceptance Criteria

Traceability and Release Controls

Spec Writing Quality

Verification, Risk, and Change Control

Frequently Asked Questions