210-060 Implementing Cisco Collaboration Devices (CICD)

---

QUESTION 1
Which two services define cloud networks? (Choose two.)

A. Infrastructure as a Service
B. Platform as a Service
C. Security as a Service
D. Compute as a Service
E. Tenancy as a Service

Answer: A,B

Explanation:

---

QUESTION 2
In which two situations should you use out-of-band management? (Choose two.)

A. when a network device fails to forward packets
B. when you require ROMMON access
C. when management applications need concurrent access to the device
D. when you require administrator access from multiple locations
E. when the control plane fails to respond

Answer: A,B

Explanation:

---

QUESTION 3
In which three ways does the TACACS protocol differ from RADIUS? (Choose three.)

A. TACACS uses TCP to communicate with the NAS.
B. TACACS can encrypt the entire packet that is sent to the NAS.
C. TACACS supports per-command authorization.
D. TACACS authenticates and authorizes simultaneously, causing fewer packets to be transmitted.
E. TACACS uses UDP to communicate with the NAS.
F. TACACS encrypts only the password field in an authentication packet.

Answer: A,B,C

Explanation:

---

QUESTION 4
According to Cisco best practices, which three protocols should the default ACL allow on an
access port to enable wired BYOD devices to supply valid credentials and connect to the network?
(Choose three.)

A. BOOTP
B. TFTP
C. DNS
D. MAB
E. HTTP
F. 802.1x

Answer: A,B,C

Explanation:

---

QUESTION 5
Which two next-generation encryption algorithms does Cisco recommend? (Choose two.)

A. AES
B. 3DES
C. DES
D. MD5
E. DH-1024
F. SHA-384

Answer: A,F

Explanation:

Click here to view complete Q&A of 210-060 exam

Best Cisco 210-060 Certification, Cisco 210-060 Training at certkingdom.com

200-601 IMINS2 Managing Industrial Networks for Manufacturing with Cisco Technologies

200-601 IMINS2
Managing Industrial Networks for Manufacturing with Cisco Technologies

Exam Number 200-601 IMINS2
Associated Certifications CCNA Industrial
Duration 90 Minutes (65 - 75 questions)

This exam tests concepts and technology commonly found in the automated manufacturing environment. This exam tests candidates on the Common Industrial Protocol (CIP) and ProfiNET industrial protocols and the underlying support network infrastructure design to maximize efficiency within Industrial Ethernet.

Exam Description
The exam Managing Industrial Networks for Manufacturing with Cisco Technologies (CCNA IMINS2) certification exam (200-601) is a 90 minute, 65 – 75 question assessment. This exam tests concepts and technology commonly found in the automated manufacturing environment. This exam tests candidates on the Common Industrial Protocol (CIP) and ProfiNET industrial protocols and the underlying support network infrastructure design to maximize efficiency within Industrial Ethernet.

The following topics are general guidelines for the content likely to be included on the exam. However, other related topics may also appear on any specific delivery of the exam. In order to better reflect the contents of the exam and for clarity purposes, the guidelines below may change at any time without notice.

1.0 IP Networking 20%
1.1 Describe the difference between enterprise environments and industrial environments
1.2 Describe the components for making the data flow highly available and predictable in an industrial environment (QoS, IP addressing, protocol, and hardware resiliency)
1.3 Interpret and diagnose problems that are related to QoS
1.4 Describe the differences between redundancy and resiliency requirements / approaches between the Enterprise and the plant floor
1.5 Differentiate the capabilities of switch types
1.6 Describe the life cycle of a multicast group
1.7 Describe and configure the operation and use cases for NAT
1.8 Describe and configure the operation and use cases for static routing
1.9 Describe and configure VLAN trunking to a virtual switch
1.10 Describe and configure Layer 2 resiliency protocols (Spanning Tree, REP, Flex Links, and Etherchannels)
1.11 Configure switch ports ( macros, threshold alarms)

2.0 Common Industrial Protocol (CIP) Knowledge and Configuration 19%
2.1 Explain the CIP connection establishment process
2.2 Explain producer/consumer models and implicit/explicit message models
2.3 Recognize communication abilities and capacities in different hardware/hardware generations (revisions)
2.4 Identify and describe the technologies that enable CIP Motion and CIP Safety
2.5 Identify the applicability, limitations, and components of a DLR implementation
2.6 Implement multicast features for CIP within a LAN
2.7 Optimize RPI on a CIP connection given a set of parameters
2.8 Enable and configure IEEE 1588 PTP at the system level
2.9 Configure the Stratix using the Add On Profile (AOP) in Studio 5000

3.0 ProfiNET Knowledge and Configuration 19%
3.1 Describe the differences in ProfiNET support between Cisco catalyst and Cisco Industrial Ethernet (IE) switches
3.1.a Support for VLAN 0
3.1.b Support for ProfiNET LLDP
3.1.c Support for GSDs (integration into SIMATIC STEP 7)

3.2 Describe the operation and purpose of ProfiSAFE
3.3 Describe the three basic ProfiNET devices and conformanceclasses
3.4 Describe the ProfiNET application classes and communication channels
3.5 Describe DHCP and how it can be used for IP addressing of devices and configuration pushes
3.6 Describe ring network requirements for ProfiNET
3.7 Enable ProfiNET on the switch
3.8 Enable Layer 2 QoS to ensure ProfiNET is prioritized
3.9 Integrate the Cisco Industrial Ethernet Switch in SIMATIC STEP 7
3.10 Configure and monitor ProfiNET alarm profiles on IE switches

4.0 Security 12%
4.1 Describe the defense in-depth approach to securing the industrial zone
4.2 Identify how a security component (hardware/software) applies to a network device to meet the network security definition of defense in depth
4.3 Describe network device hardening
4.4 Describe the concept and mechanisms of implementing logical segmentation
4.5 Identify possible options to control traffic between zones (ACLs, firewalls, VLANs)

5.0 Wireless 10%
5.1 Describe the differences between 802.11a/b/g/n/ac
5.2 Describe the components that you need to build multiple wireless networks on a single access point
5.3 Describe the difference between autonomous and controller-based access points and wireless workgroup bridges
5.4 Demonstrate a typical switchport configuration for autonomous and controller-based access points
5.5 Describe the limitations of using a workgroup bridge with a control communication

6.0 Troubleshooting 20%
6.1 Troubleshoot advanced Layer 1 problems such as mechanical deterioration, electromagnetic noise issues, and infrastructure mismatches
6.2 Troubleshoot VLAN trunking
6.3 Troubleshoot an error disabled port
6.4 Troubleshoot basic spanning tree port state and root priority problems
6.5 Troubleshoot Layer 3 problems by inspecting route tables and NAT tables
6.6 Troubleshoot Layer 3 problems in a VRF-lite enabled environment
6.7 Demonstrate the ability to find the location of a device within a multi-switch network given an IP address
6.8 Identify methods for troubleshooting a communication problem in a CIP environment
6.9 Troubleshoot CIP using an Ethernet/IP browse tool, command line, and a web browser
6.10 Troubleshoot device communications performance
6.11 Identify the source of cable and device faults in a DLR
6.12 Identify methods for troubleshooting a communication problem in a ProfiNET environment
6.13 Troubleshoot ProfiNET using SIMATIC STEP 7 to view network topology, use the switch command line

Click here to view complete Q&A of 200-601 exam

Best Cisco 200-601 Certification, Cisco 200-601 Training at certkingdom.com

5 dead operating systems, and what their ghosts can tell us

We conduct a séance of sorts to call forth the souls of operating systems past—not so we can gaze upon their ghastly interfaces, but to learn from their tragic demises.

Tremble, mortals! Halloween is upon us. Ghosts, ghouls, and other undesirable creatures are prepared to slink out of their domains and into ours—it’s said that even the dead can rise on Halloween.

In that spirit, let us light some candles, cover the mirrors, and conduct a séance of sorts to call forth the souls of operating systems past. Not so we can gaze upon their ghastly interfaces, but to see if we can learn anything from their digital carcasses and signs of a life well-lived—or not. Who knows, perhaps they bring secrets from beyond the grave.

Windows XP
Windows XP proved to be a hit since its inception. Sure, it took Service Pack 2 to create the operating system we call XP today, but at the operating system’s launch in 2001 the basics were already there. It’s a good thing too, as Windows XP was destined to live long past its shelf life.

Windows XP’s extended life started with Microsoft’s Sisyphean effort on project ‘Longhorn,’ which included ambitious hopes for new features. As due date after due date slipped for Longhorn, more people became invested in the familiar and near-universal XP, and to disdain change of any kind.

When Longhorn finally emerged from its 5.5 year development in 2007 as Windows Vista, users were shocked and appalled by Microsoft's proposed XP replacement. It took another two years of development and the release of Windows 7 before Windows XP would finally begin to lose ground. Yet it was another four to five years (depending on whom you ask) before Windows 7 would replace XP as the most widely used operating system in the world.

Today, four iterations of Windows after XP, the 14 year-old OS still claims more than 12 percent of online PC usage worldwide, according to Net Applications. This is despite the fact that Microsoft ceased delivering security updates for XP in April 2014—a year and a half ago.

Lesson learned: Don’t let your software live on too long, or it will grow up to be a dangerous zombie.

Windows RT
When Microsoft announced Windows RT, originally known as Windows on ARM, people were excited about the possibility. Finally, the energy-efficient ARM processor architecture—ubiquitous on mobile devices—would earn its own version of Windows.

What became Windows RT, however, was a terrible joke of an OS. Like Windows 8, RT offered a dual-identity desktop interface and modern UI. The desktop was hobbled, because it couldn’t run any other traditional Windows software—just Internet Explorer and Microsoft Office. Windows RT users didn’t have much to do on the touch-friendly side of Windows either, due to Microsoft’s poor efforts to convince developers to build Modern apps for the Windows Store.

Toward the end of its life, RT was no better than a glorified web browser with a smattering of ho-hum apps. Meanwhile, Intel’s Atom chips quickly closed the gap with ARM’s energy efficiency, leaving little reason to opt for Windows on ARM.

Microsoft was never clear enough on what it wanted to do with Windows RT. The result was a poorly thought-out ecosystem that led to death by indifference. Windows RT tablets aren’t being upgraded to Windows 10, and even Microsoft’s own budget Surface line ditched Windows RT for Windows proper in its third iteration.

Lesson learned: Ghosts of Windows RT linger on in Windows 10’s universal apps and Windows Phone compatibility, but Windows RT was nothing short of a disaster with consumers—understandably so, given its radical new interface and limited software capabilities. Even if you’re trying to move an ecosystem forward, don’t throw out the baby with the bathwater.

Mac OS in all its graphical interface glory.
One of Apple’s founding principles is that PCs—and technology in general—should be a delightful, even magical, experience. That vision came to the fore with the original Macintosh operating system. The first Mac OS was a revelation that popularized the visual PC interface and mouse navigation for home users.

The downside, however, is that a lot of what made Mac OS so magical required technological trickery and clever solutions to help a constrained system perform beyond what was expected. Original Macintosh users were forced to constantly swap out disks constantly because of RAM restrictions.

It was a pain to do—sometimes literally—but many people didn’t mind because the user experience on the screen was simply so much better than anything else out there.

os2box
During the early days of computing, IBM was a dominating force with its line of personal computers. When the company began producing the operating system OS/2 with Microsoft, the plan was to use the new OS to push even more sales of IBM hardware. That worked for a while, but the end of the line for OS/2 took shape once Microsoft produced Windows 3.0. After that, Microsoft ceased co-development of OS/2 to focus on Windows, and IBM was chasing Microsoft ever after. Pundits still argue over whether early Windows or OS/2 was better.

Regardless, OS/2’s undoing was that Microsoft outflanked IBM at every turn.
Microsoft bundled Windows with all kinds of hardware, as it does today, while OS/2 was sold separately and designed to push IBM machines. That approach just didn’t work when faced with the juggernaut that was Microsoft—it also didn’t help that Microsoft cheated. Once Windows 95 came out, OS/2 was all but done. IBM’s operating system faded out by 2000, but just like with Windows XP, you can probably find the odd ATM or small business inventory system still running on OS/2.

Lesson learned: Even juggernauts can fall. Adapt—which is exactly what Microsoft’s trying to do with Windows 8 and 10—or die.
The ghosts of Linux past

In 2015, we officially bid goodbye to Mandriva, a once-popular Linux distribution. This version of Linux started out life as Mandrake until the company running the distro merged with Conectiva in 2005 to become Mandriva. Many veteran Linux users cut their teeth on Mandrake or Mandriva, including PCWorld’s own Linux watcher, Chris Hoffman.

Get it? A penguin skeleton?
Mandriva lost its spot as the “easy Linux” distro after Canonical’s Ubuntu appeared in 2004. Seven years later, development ceased. Mandriva is just one of the many Linux distributions that have faded into oblivion—CrunchBang, supported by a single developer, is another one we recently covered.

Linux may be a force in the server world, but it has never succeeded at winning over masses of desktop users. Its openness encourages many developers to create their own Linux distributions and then fight with the hundreds of other distros for a slice of a tiny user base. Unsurprisingly, there’s a healthy amount of churn among distributions, even the popular ones.

Lesson learned: Like your Linux distro, but don’t fall in love. You may wind up leaving the party sooner than you think.

That’s the end of our ghoulish walk through the graves of operating systems past. Now we close the PC crypt for yet another year…until the ghouls of dead PCs past rise again.

---

Click here to view complete Q&A of 70-355 exam

Best Microsoft MCTS Certification, Microsoft 70-355 Training at certkingdom.com