Q: Along the Mexican border, NEXUS members may utilize Secure Electronic Network for Travelers Rapid Inspection (SENTRI) lanes when entering the US by land, but must be traveling in an approved, registered vehicle (SENTRI requires members to register their vehicles into the program, which involves a thorough inspection by CBP, whereas NEXUS has no such requirement). Regardless of whether the traveler is in an approved vehicle or not, the NEXUS card is a WHTI compliant document, and may be used in any standard lane from Mexico into the United States as proof of identity and citizenship. Pedestrians can use dedicated SENTRI lines for expedited entry into the U.S. from Tijuana at the San Ysidro border crossing.
Can we conclude that can i use my nexus card in a non nexus lane?
A: yes

Q: The card security code is typically the last three or four digits printed, not embossed like the card number, on the signature strip on the back of the card. On American Express cards, the card security code is the four digits printed (not embossed) on the front towards the right. The card security code is not encoded on the magnetic stripe but is printed flat.
Can we conclude that does american express card have a security code?
A: yes

Q: A foreign national wishing to enter Canada must obtain a temporary resident visa from one of the Canadian diplomatic missions unless he or she holds a passport issued by one of the 51 eligible visa exempt countries and territories or proof of permanent residence in the United States.
Can we conclude that when did you have to have a passport to go to canada?
A: yes

Q: Packet filters act by inspecting the ''packets'' which are transferred between computers on the Internet. If a packet does not match the packet filter's set of filtering rules, the packet filter will drop (silently discard) the packet or reject it (discard it, and send ''error responses'' to the source). Conversely, if the packet matches one or more of the programmed filters, the packet is allowed to pass. This type of packet filtering pays no attention to whether a packet is part of an existing stream of traffic (i.e. it stores no information on connection ''state''). Instead, it filters each packet based only on information contained in the packet itself (most commonly using a combination of the packet's source and destination address, its protocol, and, for TCP and UDP traffic, the port number). TCP and UDP protocols constitute most communication over the Internet, and because TCP and UDP traffic by convention uses well known ports for particular types of traffic, a ''stateless'' packet filter can distinguish between, and thus control, those types of traffic (such as web browsing, remote printing, email transmission, file transfer), unless the machines on each side of the packet filter are both using the same non-standard ports.
Can we conclude that when a firewall filters traffic the firewall drops the traffic?
A:
yes