Question 390
At the Riverbrook research laboratory, a shared deployment template accepts an arbitrary subscription ID and can modify unrelated accounts. Which issue is most directly indicated by the facts?
Explanation
Correct Answer
The situation indicates that unbounded inputs can expand a trusted workflow beyond its authorized deployment environment. The recommended response is to validate allowed template parameters and restrict the service connection's target scope, with a follow-up check that an out-of-scope subscription fails validation without resource changes. This directly addresses the reported issue at the Riverbrook research laboratory.
Incorrect Answers
Rebuilding after testing breaks assurance that production uses the validated bytes. This can occur in other projects, but it is not the primary explanation at the Riverbrook research laboratory.
This explanation belongs to desired-state guest configuration. The immediate weakness in the question is that unbounded inputs can expand a trusted workflow beyond its authorized deployment environment. For the Riverbrook research laboratory, the priority is to validate allowed template parameters and restrict the service connection's target scope.
Although an unreviewed package version should not gain production trust merely because it was published, the situation does not describe that specific cause; it instead indicates that unbounded inputs can expand a trusted workflow beyond its authorized deployment environment. For the Riverbrook research laboratory, the priority is to validate allowed template parameters and restrict the service connection's target scope.