ccna 3 v7 final exam

ccna 3 v7 final exam.Object group-based ACLs are smaller, easier to read, and also easier to configure and manage than traditional ACLs. For large user access environments, this simplifies the deployment of static and dynamic ACLs on CiscoIOS routers. Both IPv4 and IPv6 ACLs support object groups.Object groups for ACL features allow administrators to group users, devices, and protocols into groups. These groups can then be applied to ACLs to create access control policies for a set of objects. This feature lets administrators use object groups instead of the individual IP addresses, protocols, and ports used in traditional ACLs. This allows the use of fewer, more manageable ACEs.4.1.10.2 Network and Service Object GroupsObject groups can be used in ACEs by grouping similar objects into a group, rather than creating a separate ACE for each object.The following types of object groups can also be created: Networks; Services. When using object groups, the following guidelines and restrictions apply.Object groups must have unique names. You may want to create a network object group named "Engineering" and a service object group named "Engineering", and you need to add at least one identifier to the end of an object group name (or "tag") to make it unique. For example, use "Engineering_admins" and "Engineeringsvcs".After an object group has been created, additional objects can also be added to the group in the same way as creating a new object group. In this example, it is specifying the name of an existing group and then specifying the additional objects.Objects such as hosts or services can be grouped. After grouping objects, if the group name is used in a single command, the command is applied to each object in the group. If an object group is being used in ACE, it cannot be deleted or emptied.When a group is defined with the object-group command and any security device commands are used, the command is applied to every object in the group. This feature can significantly reduce the size of your configuration.4.1.10.3 Configuring each of the network armature and service object groups