Microsoft 70-341 Exam Questions and Answers

Blog For Free!

2013 August
2013 June

My Profile
Send tMail
My tFriends
My Images

Create a Blog!

How is it Different?
08.19.13 (12:33 am)   [edit]

How is it Different?
Let us understand why data warehouse projects arc distinctive. You are familiar with application projects for OLTP systems. A comparison with an OLTP application project will help us recognize the differences.

Try to describe a data warehouse in terms of major functional pieces. First you have the data acquisition component. Next is the data storage component. Finally, there is the information delivery component. At a very general level, a data warehouse is made up of these three broad components. You will notice that a-data warehouse project differs from a project on OLTP application in each of these three functional areas. Let us go over the differences. Figure 4-2 lists the differences and also describes them free certification exam .

Data warehousing is it new paradigm. We almost expect a data warehouse project to be' different from an OLTP system project. We can accept the differences. But more important is the discussion of the consequences of the differences. What must you do about the differences? How should the project phases be changed and enhanced to deal with them?

Please read the following suggestions to address the differences:

  • Consciously recognize' that a data warehouse project has broader scope, tends to be more complex, and involves many different technologies.
  • Allow for extra time and effort for newer types of activities.
  • Do not hesitate to find .and use specialists wherever in-house talent is not available. A data warehouse project has many out-of-the-ordinary tasks.


  • Metadata in a data warehouse is so significant that it needs special treatment throughout the project. Pay extra attention to building the metadata framework properly.
  • Typically, you wit he using a few third-party tools during the development and for ongoing functioning or the data warehouse. In your project schedule, plan to include mine for the evaluation and selection or tools.
  • Allow ample time to build rind complete the infrastructure.
  • Include enough time for the architecture design.
  • Involve the users in every stage of the project. Data warehousing could be complete-ly new to both IT and The users in your company. A joint effort is imperative,
  • Allow sufficient time for training the users in the query and reporting tools. .
  • Because of the large number of tasks in a data warehouse project, parallel development tracks rife absolutely necessary. He prepared for the challenges of running parallel tracks in the project life cycle.

08.18.13 (11:35 pm)   [edit]

As an IT professional, you have worked on application projects before. You know what goes on in these projects and are aware of the methods needed to build the applications from planning through implementation. You have been part of the analysis, the design, the programming, or the testing phases. If you have functioned as a project manager or a team leader, you know how projects are monitored and controlled. A project is a project. If you have seen one IT project, have you not seen them all?

The answer in not a simple yes or no. Data warehouse projects are different from projects building the transaction processing systems. If you are new to data warehousing, your first data warehouse project will reveal the major differences. We will discuss these differences and also consider ways to react to them. We will also ask a basic question about the readiness of the IT and user departments to launch a data warehouse project. I low about the traditional system development he cycle (SDLC) approach'? Can we use this approach to data warehouse projects as well? II so, what are the development phases in the life cycle?

Figure 4-I Overall plan for data warehousing initiative.

The Overall Plan
08.18.13 (11:32 pm)   [edit]
The Overall Plan
The seed for a data warehousing initiative gets sown in many ways. The initiative may get ignited simply because the competition has a data warehouse. Or, the CIO makes a recommendation to the CEO or some other senior executive proposes a data warehouse as the solution for the information problems in a company. In some cases, a senior executive was exposed to the idea at a conference or seminar. Whatever may be the reason for your company to think about data warehousing, the real initiative begins with well-thought-out formal plans?

This plan is a formal plan that sets the direction, tone, and goals of the initiative. The plan lays down the motivation and the incentives. It considers the various options and reasons out the selection process. The plan discusses the type of data warehouse and enumerates the expectations.

This is not a detailed project plan. It is an overall plan to lay the foundation, to recognize the need, and to authorize a formal project. Figure 4-1 lists the types of content to be included in the formal overall plan. Review the list carefully and adapt it for your data warehouse initiative.

70-341Question 3
06.17.13 (10:03 pm)   [edit]

70-341Question 3
You need to recommend which task is required to prepare Active Directory for the planned Exchange Server 2013 implementation. What should you recommend?
A. On any domain controller in the Paris office, run setup.exe /preparead.
B. On any domain controller in the Amsterdam office, run setup.exe /preparead.
C. On any domain controller in the Paris office, run setup.exe /preparealldomains.
D. On any domain controller in the Amsterdam office, run setup.exe/preparedomain.

Answer: B

70-341Question 2
06.17.13 (10:01 pm)   [edit]
70-341Question 2
An administrator recommends removing EDGE1 from the implementation plan and adding a new Client Access server named CAS-8 instead. You need to identify which anti-spam feature will NOT be available on CAS-8. Which anti-spam feature should you identify?

A. Connection Filtering
B. Sender Filtering
C. Content Filtering
D. Recipient Filtering

Answer: C