Infrastructure for a test-account permitting stack is defined in TypeScript with the AWS CDK. Which action applies that definition to the test environment?
Select an answer to reveal the explanation.
Short Explanation
cdk deploy is the "make it real" button for your TypeScript stack in the test account. Screenshots and console-only edits leave the CDK app as fan fiction.
Full Explanation
When infrastructure for a test-account permitting stack is defined in TypeScript with the AWS CDK, applying that definition means running cdk deploy against the intended stack (for example AppStack-Test) so CloudFormation changes are synthesized and executed in the test account. The CDK app remains the source of truth; deploy makes the TypeScript constructs real AWS resources for permitting experiments without click-ops drift.
Editing production resources in the console only and discarding the CDK app creates irreversible drift and bypasses the test account path. Emailing a screenshot of CDK code to operations is not a deploy mechanism. Synthesizing CloudFormation locally forever without deploying any stack never provisions the test environment the team needs.
Exam caveat: cdk synth produces templates; cdk deploy applies them (via CloudFormation). Associate questions expect you to know deploy is what changes the account.
Operational check: from a clean CI role or workstation profile for the test account, run cdk deploy for AppStack-Test, review the change set, confirm stack CREATE/UPDATE completes, and verify permitting resources match the TypeScript definition before promoting toward production.