Friday, August 30, 2013

HARDWARE AND OPERATING SYSTEMS

 HARDWARE AND OPERATING SYSTEMS

Hardware and operating systems make tip the computing environment for your data warehouse. All the data extraction, transformation, integration, and staging jobs run on the selected hardware under the chosen operating system. When you transport the consolidate and integrated data from the staging area to your data warehouse repository, you make use of the server hardware and the operating system hardware. When the queries are from the client workstations, the server hardware, in conjunction with the database s ware, executes the queries and produces the results. 


Here are some general guidelines for hardware selection, nut entirely specific to ha ware for the data warehouse. 

Salability - When your data warehouse grows in terms of the number of users, number of queries, and the complexity of the queries, ensure that your selected hank could be sealed up. 

Support - Vendor support is crucial for -hardware maintenance. Make sure that the port from the hardware vendor is at the highest possible level.

 Vendor Reference - It is important to check vendor references with other sites using hardware from this vendor. You do not want to be caught with your data warehouse being down because of hardware malfunctions when the CEO wants some critical analysis to be completed. 

Vendor Stability - Check on the stability and staying power of the vendor. Next let us quickly consider a few general criteria for the selection of the operating system. First of ail, the operating system must be compatible with the hardware. A list of criteria follows. 

Scalability - Again, scalability is first on the list because this is one common feature of every data warehouse. Data warehouses grow, and they grow very fast. Along with the hardware and database software, the operating system must be able to support the increase in the number of users and applications. 
Security - When multiple client workstations access the server, the operating system must be able to protect each client and associated resources. The operating system must provide each client with secure environment. 

Reliability - The operating system must be able to protect the environment from application termination.

Availability - This is a corollary to reliability. The computing environment must continue in be available after abnormal application terminations. 

Preemptive Multitasking - The server hardware must be able to balance the allocation of time and resources among the -multiple tasks. Also, the operating system must be able to let a high priority task preempt or interrupt another task as and when needed. 

Use multithreaded approach - The operating system must be able to serve multiple requests concurrently by distributing threads to multiple processors in a multiprocessor hardware configuration. This feature is very important because multiprocessor configurations me architectures of choice in a data warehouse environment. 

Memory protection - Again, in a data warehouse environment, large numbers 'of queries arc common. That means that multiple queries will be executing concurrently. A memory protection feature in an operating system prevents one task from violating the memory space of another. 

Having reviewed the requirements for hardware and operating systems in a data warehouse environment, let us try to narrow down the choices. What are the possible options? Please go through the following list of three common options.
Mainframes

  • Leftover hardware from legacy, applications
  • Primarily designed for OLTP and not for decision support applications
  • Not cost-effective fin data warehousing
  • Not easily scalable
  •  Rarely used for data warehousing when too much spare resources are available for smaller data marts
  • Open System Servers
  • UNIX servers, the choice medium for most data warehouses
  • Generally robust
  • Adapted for parallel processing
NT Servers  

  • Support medium-sized data warehouses
  • Limited parallel processing capabilities
  • Cost-effective for medium-sized and small data warehouses 

Operational infrastructure

Operational infrastructure
To understand operational infrastructure, let us once again take the example of data staging. One part of foundational infrastructure refers to the computing hardware and the related software. You need the hardware and software to perform the data staging functions and render the appropriate services. You need software tools lo perform data transformations. You need software to create the output files. You need disk hardware to place the data in the staging area files. But what about the people involved in performing these functions? What about the business rules and procedures for the data transformations'? What about the management software to monitor and administer the data transformation tasks? Operational infrastructure to support each architectural component consists of
  • People
  • Procedures
  • Training
  • Management software
These are not the people and procedures needed for developing the data warehouse. These are the ones needed to keep the data warehouse going. These elements are as essential as the hardware and software that keep the data warehouse running. They support the Management of the data warehouse and maintain its efficiency.

Data warehouse developers pay lot of attentions to be hardware and system software elements of the infrastructure. It is right to do so. But operational infrastructure is often neglected. Even though you may have the right hardware and software neglected your data ware-house needs the operational infrastructure in place for proper functioning. Without appropriate operational infrastructure, your data warehouse is likely to just limp along and cease be effective. Pay attention to the details id your operational infrastructure,

Wednesday, June 19, 2013

350-001 Question 7

350-001 Question 7

You have forgotten the password to a Catalyst switch and need to perform a password recovery. What is the first step that should be taken to do this?


350-001

A. Reboot the switch using the reload command.
B. Reboot the switch using the restart command.
C. Set the configuration register to ignore the startup configuration.
D. Set the boot register to 0x42.
E. Power cycle the switch.
F. Type in "config-register".

Answer: E

Explanation:
The switch must be manually turned off (or unplugged), and then turned back on (plugged back in). Power cycling the switch is the only way to get into password recovery.

Reference:
http://www.cisco.com/warp/public/474/pswdrec_6000.html

350-001 Question 4

350-001 Question 4
A new TACACS+ server is configured to provide authentication to a NAS for remote access users. A user tries to connect to the network and fails. The NAS reports a FAIL message. What could be the problem? (Choose all that apply).

A. The TACACS+ service is not running on the server.
B. The password for this user is incorrect.
C. The username does not exist in the TACACS+ user database.
D. The NAS server lost its route to the TACACS+ server.
E. The TACACS+ server is down.

Answer: B, C

Explanation:
A FAIL condition is a result of incorrect username/password information. It means that an authentication request was successfully received, but that it had failed. A FAIL response is significantly different from an ERROR. A FAIL means that the user has not met the criteria contained in the applicable authentication database to be successfully authenticated. Authentication ends with a FAIL response.

An ERROR means that the security server has not responded to an authentication query. Because of this, no authentication has been attempted. Only when an ERROR is detected will AAA select the next authentication method defined in the authentication method list.

Reference:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/secur_c/scprt1/s
cdaaa. htm

Incorrect Answer:
A, D, E. These would have resulted in an ERROR condition instead of a FAIL condition.
With an error, the NAS would query the next authentication method.