***NOT READY FOR STUDY*** AWS DEV-A Practice Exam 4 Flashcards
A task placement constraint is a rule that is considered during task placement. Task placement constraints can be specified when either running a task or creating a new service. The task placement constraints can be updated for existing services as well.
Cluster queries are expressions that enable you to group objects. For example, you can group container instances by attributes such as Availability Zone, instance type, or custom metadata.
The AWS Serverless Application Model (SAM) is an open-source framework for building serverless applications.
AWS Serverless Application Model (SAM) provides shorthand syntax to express functions, APIs, databases, and event source mappings. With just a few lines per resource, you can define the application you want and model it using YAML.
During deployment, SAM transforms and expands the SAM syntax into AWS CloudFormation syntax, enabling you to build serverless applications faster.
AWS SAM CLI provides a Lambda-like execution environment that lets you locally build, test, and debug applications defined by SAM templates.
You can also use the SAM CLI to deploy your applications to AWS.
With the SAM CLI you can package and deploy your source code using two simple commands:
sam package
sam deploy
Alternatively, you can use:
AWS cloudformation package
AWS cloudformation deploy
Amazon ECS supports the following types of task placement constraints:
distinctInstance
memberOf
Amazon ECS supports Task placement constraint type
distinctInstance: Place each task on a
Place each task on a different container instance.
Amazon ECS supports Task placement constraint type
memberOf: Place tasks on container instances that satisfy an expression
When you invoke a function asynchronously, you don’t wait for a response from the function code. You hand off the event to Lambda and Lambda handles the rest
To avoid request throttling, design your DynamoDB table with the right partition key to meet your access requirements and provide even distribution of data. Recommendations for doing this include the following:
Use high cardinality attributes (e.g. email_id, employee_no, customer_id etc.)
Use composite attributes
Cache popular items
Add random numbers or digits from a pre-determined range for write-heavy use cases
If you use AWS SAM to create your serverless application, it comes built-in with CodeDeploy to provide gradual Lambda deployments.
AWS SAM does the following for you during deployments: *Make this into 4 F/C
Deploys new versions of your Lambda function, and automatically creates aliases that point to the new version.
Gradually shifts customer traffic to the new version until you’re satisfied that it’s working as expected, or you roll back the update.
Defines pre-traffic and post-traffic test functions to verify that the newly deployed code is configured correctly and your application operates as expected.
Rolls back the deployment if CloudWatch alarms are triggered