Explanation: For each secondary index, you must specify the following:
The type of index to be created either a local secondary index or a global secondary index. A name for the index. The naming rules for indexes are the same as those for tables, as listed in Limits in DynamoDB. The name must be unique for the table it is associated with, but you can use the same name for indexes that are associated with different tables. The key schema for the index. Every attribute in the index key schema must be a scalar data type, not a multi value set. Other requirements for the key schema depend on the type of index: For a local secondary index, the hash key must be the same as the tables hash key, and the range key must be a non key table attribute. For a global secondary index, the hash key can be any table attribute. A range key is optional, and it too can be any table attribute. Additional attributes, if any, to project from the table into the index. These attributes are in addition to the table key attributes, which are automatically projected into every index. You can project attributes of any data type, including scalar data types and multi-valued sets. The provisioned throughput settings for the index, if necessary: For a local secondary index, you do not need to specify read and write capacity unit settings. Any read and write operations on a local secondary index draw from the provisioned throughput settings of its parent table. For a global secondary index, you must specify read and write capacity unit settings. These provisioned throughput settings are independent of the tables settings. For maximum query flexibility, you can create up to five local secondary indexes and up to five global secondary indexes per table.
Question : For AWS CloudFormation Resources, if you want to map an Amazon Elastic Block Store to an Amazon EC instance 1. Reference the logical IDs of the instance 2. Reference the logical IDs of both the block stores and the instance 3. Access Mostly Uused Products by 50000+ Subscribers 4. Reference the physical IDs of both the block stores and the instance
Explanation: In the Resources sections of a template, you declare the AWS resources that you want AWS CloudFormation to manage, such as an Amazon EC2 instance or an Amazon S3 bucket. All templates must declare a Resources section with at least one resource. You must declare each resource separately; however, you can specify multiple resources of the same type.
Each resource declaration includes three parts: A logical name that is unique within the template A resource type Properties for that resource
You use the logical name to reference the resource in other parts of the template. For example, if you want to map an Amazon Elastic Block Store to an Amazon EC2 instance, you reference the logical IDs of both the block stores and the instance to specify the mapping. Logical names must be alphanumeric (A-Za-z0-9). For a list of all the resource types.
In addition to the logical ID, certain resources also have a physical ID, which is the actual assigned name for that resource, such as an Amazon EC2 instance ID or an Amazon S3 bucket name. You use the physical IDs to identify resources outside of AWS CloudFormation templates, but only after the resources have been created.
Question : In VPC Network access control lists (ACLs) Act as a firewall for associated subnets, controlling both inbound and outbound traffic at the ___________ level 1. Full VPC 2. Customer Gateway 3. Access Mostly Uused Products by 50000+ Subscribers 4. Subnet
Explanation: Amazon VPC provides two features that you can use to increase security for your VPC: Security groups Act as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic at the instance level Network access control lists (ACLs) Act as a firewall for associated subnets, controlling both inbound and outbound traffic at the subnet level
When you launch an instance in a VPC, you can associate one or more security groups that youve created. Each instance in your VPC could belong to a different set of security groups. If you dont specify a security group when you launch an instance, the instance automatically belongs to the default security group for the VPC.
1. Submit GCM notification credentials to Amazon SNS; Receive Registration ID for each mobile device; Pass device token to SNS; SNS then creates a mobile subscription endpoint for each device and communicates with the GCM service on your behalf
2. Pass device token to SNS to create mobile subscription endpoint for each mobile device; Request device token from each mobile device; SNS then communicates on your behalf to the GCM service 3. Access Mostly Uused Products by 50000+ Subscribers Amazon SNS; pass GCM token credentials to Amazon SNS