THAI CPE

Mr.Kyaw said:

i am just passed CCNA today, 1-3-2011, from Myanmar.
my score is 1000/1000.
50 question, 2hr exam time.

i attended the CCNA class and i used these.
TestInside.640-802.v2010-05-23.by.Acme.356qq (100%valid) from examcollection.com

http://www.4shared.com/document/tSQDnCy9/CiscoTestInside640-802v2010-05.htm

• A Network Management Station (NMS) is using SNMP to manage some Cisco routers and switches with SNMPv2c. Using either the read-write or read-only community string is most accurately describes how the SNMP agent on a router authenticates any SNMP Get requests received from the NMS.
  SNMPv1 and SNMPv2c use community strings to authenticate Get and Set messages from an NMS. The agent defines a read-only community and can define a read-write community as well. Get requests, which read information, will be accepted if the NMS sends either the read-only or the read-write community with those requests.
  
  
• A router has been configured with the global command snmp-server community textvalue1 RO textvalue2. The meaning of this command are the router's read-only community is textvalue1, and filters incoming SNMP messages using IPv4 ACL textvalue2.
  The first parameter after the community keyword defines the community value. At the end of the command, if a text value is listed but without an ipv6 keyword, the text value is the name of an IPv4 ACL. The ACL (textvalue2 in this case) filters incoming SNMP messages received by the SNMP agent on the device.
  
  
• A router has been configured with the following command: snmp-server group one v3 auth write v1default. A command snmp-server user fred4 one auth sha pass1 would correctly define a user to associate with this SNMPv3 group to correctly define security parameters to work with an SNMP manager.
  To work correctly with an SNMP manager, the snmp-server user command must configure its parameters based on the security level in the referenced group as defined in the referenced snmp-server group command. In this case, the referenced snmp-server group command lists a security level of auth, so the snmp-server user command needs the auth keyword and associated parameters, but not the priv keyword and its associated parameters.
  
  
• show snmp commands primarily lists counters and status information, instead of configuration settings.
  
  
• ICMP Echo-based IP SLA can collect and aggregate historical statistics.
  IP Service Level Agreement (IP SLA) can generate a variety of different types of probes, including some that use ICMP Echo messages, and some that mimic voice traffic. However, the question asks about "ICMP Echo-based" IP SLA, referring to the specific IP SLA probe that sends ICMP Echo Request messages.
  ICMP Echo probes with IP SLA do not require a router to be configured as an IP SLA responder, although many other types of IP SLA probes do require a responder. The Echo probes send a normal ICMP Echo Request, so the probe can be sent to any IP address, relying on that host to send back a normal ICMP Echo Reply.
  IP SLA on the source router will gather basic statistics. With the ICMP Echo probe, the probe does not measure jitter (ruling out another incorrect answer), but it does measure round-trip time (RTT). These statistics can be gathered into a history report, which can be useful when troubleshooting problems.
  
  
• Examine the output taken from a router using IP SLA.
  
  
  
  The probe send ICMP Echos to address 10.1.1.1 and the output confirms that an Echo Reply was received back as well.
  The show ip sla summary command lists one line of information about the most recent attempt to perform the actions of an IP SLA probe. The Type implies an ICMP Echo probe, and the destination defines the IP address to which the Echo is sent. The "OK" return code means not only was the probe message sent, but in this case, that an ICMP Echo Reply packet was received back.
  The Stats column lists the round-trip time (RTT), the two-way delay. The "1" on the far left of the output refers to the IP SLA operation number.
  
  
• Host1 and Host2 connect to ports F0/1 and F0/2 on a LAN switch, respectively, so that frames sent by Host1 to Host2 will enter switch port Fa0/1 and exit switch port F0/2. All FastEthernet ports on the switch are access ports in VLAN 5. A network analyzer connects to port F0/9. A network engineer wants to use SPAN to direct traffic to the network analyzer. Use a SPAN source port of F0/2 for both direction of traffic for what traffic to direct to the analyzer with SPAN, if the goal is to gather all traffic sent between Host1 and Host2, but to avoid gathering multiple copies of the same frames. It will copy all frames sent by Host1 to Host2 (frames that the switch transmits out port F0/2), as well as frames sent by Host2 to Host1 (which will be frames received on switch port F0/2). This option does gather frames sent between Host2 and other hosts as well.
  If collecting from F0/1 for a single (transmit) direction, it gathers too little traffic. Frames sent by Host2 to Host1 would arrive in switch port F0/2 and then be sent out port F0/1 to Host1, and would be copied by the SPAN session. However, frames sent by Host1 would be received on switch port F0/1, and would not be copied by that SPAN session.
  If using VLAN 5 as a source would work, but because all FastEthernet ports on the switch are in VLAN 5, this option gathers more traffic than is necessary.
  If collecting traffic from both F0/1 and F0/2, but in both directions. This option would gather all frames sent between Host1 and Host2 twice, which would work, but more traffic than is required.
  
  
• Using more than one SPAN source port in one SPAN session and an EtherChannel port as a SPAN source port are allowed when configuring Local SPAN sessions.
  Local SPAN has a variety of configuration dependencies. Each Local SPAN session can have multiple sources, but they must be either interfaces or VLANs, and not a mix. Source ports can include both access and trunk ports as well as EtherChannel interfaces. Finally, each SPAN destination port can be used in only one SPAN session at the same time. To reuse that destination port, you must first unconfigure the destination port from the original SPAN session (no monitor session destination) and then configure it to be part of another SPAN session.
  

• Host A and Host B sit in two different subnets. The path between the
  subnets of these two hosts runs though three different Layer 3
  forwarding devices (routers and Layer 3 switches). A network engineer
  uses the APIC-EM Path Trace ACL Analysis tool to analyze the path used
  for Host A to send packets to Host B. Discovery of the topology that
  exists between the two hosts is done specifically by the ACL Analysis or
  ACL Trace part of the tool.
  APIC-EM does also these features:
  Analysis of the Layer 3 forwarding decisions in the path from Host A to B
  Analysis of the Layer 2 forwarding decisions in the path from Host A to B
  Analysis of the impact of ACLs on the packets that would flow from Host A to B
  APIC-EM
  has a built-in function to discover the topology of a network, using a
  variety of protocols such as SSH, CDP, and LLDP. Once discovered, the
  APIC-EM Path Trace feature analyzes the forwarding tables on each device
  in comparison to a source and destination as typed in by an APIC-EM
  user. Path Trace then determines the path through the network, including
  the Layer 2 and Layer 3 paths.
  The feature that uses the name Path
  Trace ACL Analysis (or Path Trace ACL Trace, or a similar name) refers
  to the additional analysis done by APIC-EM to then compare that
  imaginary packet to the ACLs that exist in the network. The tool shows
  the ACLs and points out which ACLs would deny (that is, discard) the
  packet based on its current configuration.

Cloud Terms
+ Cloud service catalog
+ Public cloud
+ Private cloud
+ Intercloud Exchange
+ Characteristics
 - On-demand self-service
 - Resource pooling
 - Rapid elasticity
+ Services
 - Infrastructure as a Service (IaaS)
 - Platform as a Service (PaaS)
 - Software as a Service (SaaS)
+ Virtual Network Function (VNF)
 - ASAv
 - Cloud Services Router (CSR)
+ Virtualization
 - Unified Computing System (UCS)
 - Virtual machine
 - Virtual CPU
 - Hypervisor
 - vNIC
 - vSwitch
 - Host (context: DC)

Programability Terms
+ Planes
 - Control Plane
 - Data Plane
 - Management Plane
 - distributed control plane
 - centralized control plane
+ Software Defined Networking (SDN)
+ Open Networking Foundation (ONF)
+ Application Centric Infrastructure (ACI)
+ OpenFlow
+ Ternary Content Addressable Memory (TCAM)
+ Application Specific Integrated Circuit (ASIC)
+ Controllers
 - Application Policy Infrastructure Controller (APIC)
 - Cisco Open SDN Controller (OSC)
 - OpenDayLight (ODL)
 - APIC Enterprise Module (APIC-EM)
+ Application Programming Interface (API)
 - Southbound API
 - Northbound API
 - Southbound Interface (SBI)
 - Northbound Interface (NBI)
 - RESTful API
 - Representational State Transfer (REST)