A team uses AWS SAM templates for a microservices app made of many Lambda functions and wants to automatically test new deployments by routing a small percentage of traffic to updates before full rollout. Which steps provide the most operationally efficient solution? (Choose two.)

Enabling gradual deployment preferences in AWS SAM templates is correct because SAM directly supports defining traffic shifting for Lambda functions using AWS CodeDeploy. This allows you to specify how traffic is routed to new versions during deployments, which is essential for canary or linear rollouts. Using Canary10Percent30Minutes and adding hooks to test during deployment is also correct because this specific deployment preference is a built-in CodeDeploy strategy that shifts 10% of traffic for 30 minutes, allowing for testing via hooks before fully shifting the remaining traffic. This aligns perfectly with the requirement for testing updates with a small percentage of traffic. Using Linear10PercentEvery10Minutes is incorrect because while it's a valid CodeDeploy strategy, the question specifically asks for routing a small percentage of traffic before full rollout, which is characteristic of a canary release, not a linear one that shifts traffic in increments. Using AWS SAM CLI commands inside AWS CodeDeploy is incorrect because CodeDeploy orchestrates the deployment; SAM CLI is a local development tool and not typically used for invoking functions within a CodeDeploy deployment process. Declaring EventInvokeConfig is incorrect because it configures asynchronous invocation error handling and destinations, not traffic shifting for deployments.