IAM groups<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Weighted aliases<\/b><\/p>\n
Explanation:<\/b><\/p>\n
AWS Lambda aliases can be configured with weighted routing to distribute invocation traffic between two published function versions. This capability is useful when implementing gradual deployments because only a portion of requests can initially reach the new version. For example, a deployment can direct most traffic to the existing version while sending a smaller percentage to the new version for validation. If monitoring shows that the new version is healthy, the traffic distribution can be adjusted. This approach supports controlled releases and can reduce the impact of problems introduced by a newly deployed Lambda version.<\/span><\/p>\nQuestion 142. What identifies a specific published Lambda version?<\/b><\/h3>\n\n- <\/b> Security group<\/span>
\n<\/span>2.<\/b> Version number<\/span>
\n<\/span>3.<\/b> CloudWatch dashboard<\/span>
\n<\/span>4.<\/b> S3 prefix<\/span><\/li>\n<\/ol>\nCorrect Answer: 2. Version number<\/b><\/p>\n
Explanation:<\/b><\/p>\n
A published AWS Lambda function version provides an immutable snapshot of the function code and configuration at the time the version is created. Each published version receives a unique version number, allowing deployments to reference a specific application state rather than relying on the mutable <\/span>$LATEST<\/span> version. Lambda aliases can point to published versions and can be moved between versions during deployments. This separation is useful for release management because production traffic can remain associated with a known version while a newer version is tested independently. It also supports safer rollback when a previous version needs to receive traffic again.<\/span><\/p>\nQuestion 143. What controls Lambda deployment traffic shifting?<\/b><\/h3>\n\n- <\/b> Deployment preference<\/span>
\n<\/span>2.<\/b> ECR lifecycle policy<\/span>
\n<\/span>3.<\/b> S3 replication<\/span>
\n<\/span>4.<\/b> IAM group<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Deployment preference<\/b><\/p>\n
Explanation:<\/b><\/p>\n
Lambda deployment preferences define how traffic is shifted from an existing Lambda version to a newly deployed version when using deployment automation such as AWS SAM or CodeDeploy. Different strategies can gradually move traffic in stages or shift all traffic at once. Gradual strategies provide an opportunity to monitor the new version before it receives all production requests. Deployment preferences can also work with CloudWatch alarms so that an unhealthy deployment can be detected and stopped or rolled back. This makes traffic-shifting strategies an important part of controlled serverless application releases.<\/span><\/p>\nQuestion 144. What can trigger a Lambda deployment rollback?<\/b><\/h3>\n\n- <\/b> S3 versioning<\/span>
\n<\/span>2.<\/b> CloudWatch alarms<\/span>
\n<\/span>3.<\/b> Route 53 records<\/span>
\n<\/span>4.<\/b> CodeArtifact repositories<\/span><\/li>\n<\/ol>\nCorrect Answer: 2. CloudWatch alarms<\/b><\/p>\n
Explanation:<\/b><\/p>\n
CloudWatch alarms can monitor application metrics during a Lambda deployment and help detect problems with a newly released version. When a deployment strategy is configured to use alarms, conditions such as elevated error rates can cause the deployment system to stop the rollout or initiate rollback behavior. This creates an automated feedback mechanism between application health and deployment control. Rather than relying solely on a person to detect an issue, the deployment can respond to predefined operational thresholds. Proper alarm selection is important because the monitored metrics should accurately reflect whether the new Lambda version is functioning correctly.<\/span><\/p>\nQuestion 145. What does an AppConfig deployment strategy control?<\/b><\/h3>\n\n- <\/b> Configuration rollout<\/span>
\n<\/span>2.<\/b> EC2 instance termination<\/span>
\n<\/span>3.<\/b> ECR image deletion<\/span>
\n<\/span>4.<\/b> IAM password expiration<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Configuration rollout<\/b><\/p>\n
Explanation:<\/b><\/p>\n
AWS AppConfig deployment strategies control how configuration changes are gradually released to applications. Instead of immediately exposing every application instance to a new configuration, an organization can define how quickly the configuration should be distributed and how long the rollout should take. This can reduce the impact of configuration errors and provide time to monitor application behavior during the rollout. AppConfig supports controlled configuration delivery independently of application code deployment. This is particularly useful for feature flags, operational parameters, and other settings that may need to be changed frequently without rebuilding and redeploying the entire application.<\/span><\/p>\nQuestion 146. What can AppConfig use to validate configuration data?<\/b><\/h3>\n\n- <\/b> Validators<\/span>
\n<\/span>2.<\/b> Deployment groups<\/span>
\n<\/span>3.<\/b> ECR tags<\/span>
\n<\/span>4.<\/b> CloudTrail trails<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Validators<\/b><\/p>\n
Explanation:<\/b><\/p>\n
AWS AppConfig validators can check configuration data before it is deployed to applications. Validators can help confirm that a configuration follows an expected schema or satisfies application-specific requirements. By validating configuration before rollout, organizations can prevent malformed or incompatible values from reaching production workloads. This is especially valuable when configuration changes are made frequently or by different teams. Validation is an important part of safe configuration management because a syntactically valid value may still be inappropriate for an application. Combining validators with gradual deployment strategies provides multiple controls for reducing configuration-related failures.<\/span><\/p>\nQuestion 147. What can automatically reverse an unhealthy AppConfig deployment?<\/b><\/h3>\n\n- <\/b> Deployment alarm<\/span>
\n<\/span>2.<\/b> ECR repository<\/span>
\n<\/span>3.<\/b> CodeArtifact domain<\/span>
\n<\/span>4.<\/b> IAM group<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Deployment alarm<\/b><\/p>\n
Explanation:<\/b><\/p>\n
AWS AppConfig can integrate deployment monitoring with Amazon CloudWatch alarms to help detect problems during configuration rollouts. If a configured alarm enters an unhealthy state while a configuration is being deployed, AppConfig can use the deployment monitoring configuration to stop or roll back the deployment. This is useful when configuration changes affect application metrics such as error rates, latency, or availability. Automated rollback reduces the time between detecting a configuration problem and restoring the previous configuration. Organizations should select meaningful application-level metrics and configure appropriate alarm thresholds so that normal temporary variations do not cause unnecessary rollbacks.<\/span><\/p>\nQuestion 148. What pauses CloudFormation until a required signal is received?<\/b><\/h3>\n\n- <\/b> Wait condition<\/span>
\n<\/span>2.<\/b> Stack policy<\/span>
\n<\/span>3.<\/b> Change set<\/span>
\n<\/span>4.<\/b> Drift detection<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Wait condition<\/b><\/p>\n
Explanation:<\/b><\/p>\n
CloudFormation wait conditions can pause part of stack creation until a specified condition is satisfied, commonly through a signal from a resource or process. This can be useful when CloudFormation needs to wait for an external or asynchronous operation before continuing. The signal can indicate that an initialization or configuration task has completed successfully. Wait conditions should be configured carefully with appropriate timeout behavior because a missing signal can cause the stack operation to fail. They are different from ordinary resource dependencies because they allow CloudFormation to wait for an explicit external signal rather than simply waiting for another declared resource relationship.<\/span><\/p>\nQuestion 149. What controls updates allowed on protected CloudFormation resources?<\/b><\/h3>\n\n- <\/b> Stack policy<\/span>
\n<\/span>2.<\/b> Buildspec<\/span>
\n<\/span>3.<\/b> ECR scan<\/span>
\n<\/span>4.<\/b> CodeArtifact policy<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Stack policy<\/b><\/p>\n
Explanation:<\/b><\/p>\n
A CloudFormation stack policy can help protect selected resources from unintended updates during stack operations. The policy defines which update actions are allowed or denied for specific resources. This is useful for critical resources that should not be modified casually through an infrastructure update. A stack policy is different from termination protection: termination protection helps prevent deletion of the entire stack, while a stack policy focuses on controlling updates to resources within the stack. Organizations can use stack policies as an additional safeguard when managing important infrastructure through automated CloudFormation deployments.<\/span><\/p>\nQuestion 150. What detects manual changes to CloudFormation resources?<\/b><\/h3>\n\n- <\/b> StackSets<\/span>
\n<\/span>2.<\/b> Drift detection<\/span>
\n<\/span>3.<\/b> CodeDeploy<\/span>
\n<\/span>4.<\/b> CodeArtifact<\/span><\/li>\n<\/ol>\nCorrect Answer: 2. Drift detection<\/b><\/p>\n
Explanation:<\/b><\/p>\n
CloudFormation drift detection compares the current configuration of supported resources with the configuration that CloudFormation expects based on the stack template and recorded state. If a resource has been changed outside CloudFormation, the resource may be identified as having drifted from the expected configuration. This capability is useful in infrastructure-as-code environments because manual modifications can create differences between the declared infrastructure and the actual environment. Detecting drift does not automatically correct the resource. Administrators can investigate the difference and determine whether the template or the resource should be updated to restore the desired state.<\/span><\/p>\nQuestion 151. Which Systems Manager feature runs commands on managed instances?<\/b><\/h3>\n\n- <\/b> Run Command<\/span>
\n<\/span>2.<\/b> Patch Manager<\/span>
\n<\/span>3.<\/b> Inventory<\/span>
\n<\/span>4.<\/b> Maintenance Windows<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Run Command<\/b><\/p>\n
Explanation:<\/b><\/p>\n
AWS Systems Manager Run Command allows administrators and automation systems to execute commands on managed instances without requiring direct interactive access to those machines. Commands can be targeted to specific instances or groups of instances using identifiers or tags. This capability is useful for administrative tasks such as installing software, changing configuration, collecting information, or running operational scripts. Because execution is managed through Systems Manager, organizations can control access through IAM permissions and maintain command execution records. Run Command is therefore a useful component for automating operational tasks across fleets of managed servers.<\/span><\/p>\nQuestion 152. What schedules recurring Systems Manager maintenance tasks?<\/b><\/h3>\n\n- <\/b> Maintenance Windows<\/span>
\n<\/span>2.<\/b> CloudFormation Hooks<\/span>
\n<\/span>3.<\/b> ECR repositories<\/span>
\n<\/span>4.<\/b> CodeArtifact domains<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Maintenance Windows<\/b><\/p>\n
Explanation:<\/b><\/p>\n
Systems Manager Maintenance Windows allow organizations to define scheduled periods during which operational tasks can be performed on managed resources. Tasks can include patching, running commands, invoking automation workflows, or performing other supported maintenance operations. Scheduling maintenance activities within defined windows helps reduce the chance of disruptive changes occurring during critical business periods. Maintenance Windows can also define targets and task priorities so that the work is performed in a controlled manner. This makes them useful for routine operations such as patch installation, system updates, configuration changes, and other scheduled maintenance activities.<\/span><\/p>\nQuestion 153. What collects software information from managed instances?<\/b><\/h3>\n\n- <\/b> Systems Manager Inventory<\/span>
\n<\/span>2.<\/b> CodePipeline<\/span>
\n<\/span>3.<\/b> CloudFormation<\/span>
\n<\/span>4.<\/b> CodeDeploy<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Systems Manager Inventory<\/b><\/p>\n
Explanation:<\/b><\/p>\n
Systems Manager Inventory collects information about managed instances and their installed software, configurations, and other supported metadata. Organizations can use this information to understand what software and configurations exist across their fleet. Inventory data can support operational processes such as patch management, compliance reviews, troubleshooting, and asset visibility. Rather than manually connecting to each server, administrators can use centralized Systems Manager capabilities to gather information across many managed instances. This is particularly useful in larger environments where manually maintaining an accurate inventory would be difficult and error-prone.<\/span><\/p>\nQuestion 154. What defines the events that EventBridge should match?<\/b><\/h3>\n\n- <\/b> Event pattern<\/span>
\n<\/span>2.<\/b> IAM boundary<\/span>
\n<\/span>3.<\/b> Buildspec<\/span>
\n<\/span>4.<\/b> Deployment group<\/span><\/li>\n<\/ol>\nCorrect Answer: 1. Event pattern<\/b><\/p>\n
Explanation:<\/b><\/p>\n
Amazon EventBridge event patterns define the characteristics of events that a rule should match. A pattern can filter events based on fields such as event source, detail type, account, Region, and other event attributes. When an incoming event matches the configured pattern, the EventBridge rule can invoke one or more targets. This enables event-driven automation without requiring applications to continuously poll for changes. For example, a rule can respond to a particular AWS service event and trigger a Lambda function, Systems Manager automation, Step Functions workflow, or another supported target.<\/span><\/p>\nQuestion 155. What can EventBridge use when target delivery repeatedly fails?<\/b><\/h3>\n\n- <\/b> Dead-letter queue<\/span>
\n<\/span>2.<\/b> ECR repository<\/span>
\n<\/span>3.<\/b>