A. Inform-request
B. Object-type
C. Module-identity
D. Notification-type
Explanation: The SMI in SNMPv2 is divided into three parts – module definitions, object definitions and notification definitions. MODULE-IDENTITY macro in ASN.1 is used to describe semantics of the information module.
A. It helps in defining new data types
B. It defines a minimum set of capabilities
C. It communicates with snmpv2 manager over the UDP transport layer
D. It helps in improving the security function of snmpv2
Explanation: Textual Conventions are designed to help define new data types. They are also intended to make the semantics consistent and clear for humans.
A. Get-next request
B. Set-request
C. Get-request
D. Inform-request
Explanation: Inform-request is a message generated by manager. It is sent using a session. As mentioned above, the receiving manager application responds with a response message. This set of communication messages is a powerful enhancement in SNMPv2, since it makes network management systems interoperable.
A. Hypertext transfer protocol
B. Manager-to-manager message
C. Bulk data transfer message
D. Simple mail transfer protocol
Explanation: The Bulk Data Transfer Message has the ability to request and receive bulk data using the get-bulk message. This speeds up the get-next-request process and is especially useful to retrieve data from tables.
A. True
B. False
C.
D.
Explanation: The most significant changes that were introduced in SNMPv2 were to improve the security function that SNMPv1 lacked. There are significant differences between the two versions of SNMP, and unfortunately version 2 is not backward compatible with version 1.
A. Row-status
B. Display-string
C. Row-pointer
D. Display-hint
Explanation: The DISPLAY-HINT clause in TEXTUAL-CONVENTION is optional. It gives a hint of the value of an instance of an object. It is applicable to situations where the underlying primitive type is either INTEGER or OCTET STRING.
A. True
B. False
C.
D.
Explanation: The messages, get-request, get-next-request, set-request, get-response, GetBulkRequest, InformRequest, and get-bulk-request are the seven protocol operations in SNMPv2.
A. DNS
B. Nms
C. Smi
D. Mib
Explanation: There are three kinds of information modules that are defined in SNMPV2. They are MIB modules, compliance statements for MIB modules, and capability statements for agent implementations. Structured Management Information (SMI) describes how to use a subset of ASN.1 to define an information module.
A. Rfc 1904
B. Rfc 1902
C. Rfc 1903
D. Rfc 1905
Explanation: The information on SNMPv2 has been split into three parts. MIB modules for SNMv2 are covered in RFC 1902. The textual conventions to be used to describe MIB modules have been formalized in RFC 1903. RFC 1904 defines SNMPv2 conformance statements for the implementation of network management standards.
A. True
B. False
C.
D.
Explanation: Notification in SMlv2 is equivalent to trap in SNMPv2. In SNMPv1, trap is formally specified by an ASN.1 macro, TRAP-TYPE.