Question 16 :
Report Builder has no built in support for source control. Which of the following choices could be implemented if you decided that those reports needed to be under source control?
Have users save the RDL files locally and check into source control using a source control utility, or write code to script them out each night and check them into source control
Users can do faux source control by just saving copies of their RDL files locally before they make a change. Beyond that, you either teach them how to use a source control utility or you write a utility you can run on a schedule.
Question 17 :
Setting the TRUSTWORTHY database property to ON allows you to execute the following from within the context of the database ?
Objects from unsigned CLR assemblies with EXTERNAL_ACCESS or UNSAFE permissions
In order to execute objects from CLR assemblies with EXTERNAL_ACCESS or UNSAFE permissions, the assemby must either be signed with a key pair or the database hosting the assembly must have the TRUSTWORTHY database property set to ON. Executing the other answers is essentially controlled by permissions. Setting the TRUSTWORTHY database property to ON also allows you to use the EXECUTE AS clause to allow impersonation outside the scope of the database within the instance but this was not one of the answers.
Question 18 :
What tool is available for ad hoc reporting by non IT end users in Reporting Services 2005?
Report Builder is bundled as part of Reporting Services 2005 and is targeted at end users needing to build ad hoc reports. BI Design Studio could be used, but typically requires more time and experience to use than the average end user will be willing to invest.
Question 19 :
You have just upgraded your SQL Server 2000 instance on Windows 2000 to SQL Server 2005. You are looking to begin implementing encryption capabilities and need to choose an algorithm for your data. Which of the following is not available to you?
While all of these are valid encryption algorithms on SQL Server 2005, the AES algorithms (128-bit, 192-bit, and 256-bit) are not supported on Windows XP or Windows 2000. To use these, you would need to upgrde to Windows 2003.
Question 20 :
Which types of replication work with Oracle publishers?
Snapshot and transactional
Oracle publishing with SQL Server works as both snapshot and transactional publication issues.