Question 120
While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: An API orchestration stores refresh tokens in plain log output while attempting to recover from access-token expiration. What acceptance check would prove the intended behavior was restored?
Explanation
Correct Answer
The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately. This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. It checks the technical distinction: An access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. Applied here, the relevant facts are: An API orchestration stores refresh tokens in plain log output while attempting to recover from access-token expiration. The question asks what acceptance check would prove the intended behavior was restored.
Incorrect Answers
This observation would test a different technical dependency: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The current issue is governed by: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. Its decisive check is “The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately”.
The alternative verifies a different condition: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The current case instead depends on: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. Confirm that “The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately”.
That test belongs to another control with this basis: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. In the current case, the governing reason is: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The direct verification is “The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately”.