Page: 1
/ 42
Total 209 questions
Scenario 1 -
Application Information -
Your company receives invoices in XML format from customers. Currently, the invoices are stored as files and processed by a desktop application. The application has several performance and security issues. The application is being migrated to a SQL Server-based solution. A schema named InvoiceSchema has been created for the invoices xml.
The data in the invoices is sometimes incomplete. The incomplete data must be stored and processed as-is. Users cannot filter the data provided through views.
You are designing a SQL Server database named DB1 that will be used to receive, process, and securely store the invoice data. A third-party Microsoft .NET
Framework component will be purchased to perform tax calculations. The third-party tax component will be provided as a DLL file named Treytax.dll and a source code file named Amortize.cs. The component will expose a class named TreyResearch and a method named Amortize(). The files are located in c:\temp\.
The following graphic shows the planned tables:
You have a sequence named Accounting.InvoiceID_Seq.
You plan to create two certificates named CERT1 and CERT2. You will create CERT1 in master. You will create CERT2 in DB1.
You have a legacy application that requires the ability to generate dynamic T-SQL statements against DB1. A sample of the queries generated by the legacy application appears in Legacy.sql.
Application Requirements -
The planned database has the following requirements:
All tables must be disk-based
All stored procedures must be signed.
The original XML invoices must be stored in the database.
An XML schema must be used to validate the invoice data.
Dynamic T-SQL statements must be converted to stored procedures.
Access to the .NET Framework tax components must be available to T-SQL objects.
Columns must be defined by using data types that minimize the amount of space used by each table.
Invoices stored in the InvoiceStatus table must refer to an invoice by the same identifier used by the Invoice table.
To protect against the theft of backup disks, invoice data must be protected by using the highest level of encryption.
The solution must provide a table-valued function that provides users with the ability to filter invoices by customer.
Indexes must be optimized periodically based on their fragmentation by using the minimum amount of administrative effort.
Usp_InsertInvoices.sql -
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number.
The following is a sample of a customer invoice in XML format:
InvoicesByCustomer.sql -
Legacy.sql -
CountryFromID.sql -
IndexManagement.sql -
You are testing disaster recovery procedures.
You attempt to restore DB1 to a different server and you receive the following error message:
"Msg 33111.
Level 16, State 3, Line 1 -
Cannot find server certificate with thumbprint
,0xA694FBEA88C9354E5E2567C30A2A69E8FB4C44A9\
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally."
You need to ensure that you can restore DB1 to a different server.
Which code segment should you execute?
- A. Option A
- B. Option B
- C. Option C
- D. Option D
Answer : B
Scenario 1 -
Application Information -
Your company receives invoices in XML format from customers. Currently, the invoices are stored as files and processed by a desktop application. The application has several performance and security issues. The application is being migrated to a SQL Server-based solution. A schema named InvoiceSchema has been created for the invoices xml.
The data in the invoices is sometimes incomplete. The incomplete data must be stored and processed as-is. Users cannot filter the data provided through views.
You are designing a SQL Server database named DB1 that will be used to receive, process, and securely store the invoice data. A third-party Microsoft .NET
Framework component will be purchased to perform tax calculations. The third-party tax component will be provided as a DLL file named Treytax.dll and a source code file named Amortize.cs. The component will expose a class named TreyResearch and a method named Amortize(). The files are located in c:\temp\.
The following graphic shows the planned tables:
You have a sequence named Accounting.InvoiceID_Seq.
You plan to create two certificates named CERT1 and CERT2. You will create CERT1 in master. You will create CERT2 in DB1.
You have a legacy application that requires the ability to generate dynamic T-SQL statements against DB1. A sample of the queries generated by the legacy application appears in Legacy.sql.
Application Requirements -
The planned database has the following requirements:
All tables must be disk-based
All stored procedures must be signed.
The original XML invoices must be stored in the database.
An XML schema must be used to validate the invoice data.
Dynamic T-SQL statements must be converted to stored procedures.
Access to the .NET Framework tax components must be available to T-SQL objects.
Columns must be defined by using data types that minimize the amount of space used by each table.
Invoices stored in the InvoiceStatus table must refer to an invoice by the same identifier used by the Invoice table.
To protect against the theft of backup disks, invoice data must be protected by using the highest level of encryption.
The solution must provide a table-valued function that provides users with the ability to filter invoices by customer.
Indexes must be optimized periodically based on their fragmentation by using the minimum amount of administrative effort.
Usp_InsertInvoices.sql -
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number.
The following is a sample of a customer invoice in XML format:
InvoicesByCustomer.sql -
Legacy.sql -
CountryFromID.sql -
IndexManagement.sql -
You need to create the InvoiceStatus table in DB1.
How should you define the InvoiceID column in the CREATE TABLE statement?
- A. Option A
- B. Option B
- C. Option C
- D. Option D
Answer : C
Scenario 1 -
Application Information -
Your company receives invoices in XML format from customers. Currently, the invoices are stored as files and processed by a desktop application. The application has several performance and security issues. The application is being migrated to a SQL Server-based solution. A schema named InvoiceSchema has been created for the invoices xml.
The data in the invoices is sometimes incomplete. The incomplete data must be stored and processed as-is. Users cannot filter the data provided through views.
You are designing a SQL Server database named DB1 that will be used to receive, process, and securely store the invoice data. A third-party Microsoft .NET
Framework component will be purchased to perform tax calculations. The third-party tax component will be provided as a DLL file named Treytax.dll and a source code file named Amortize.cs. The component will expose a class named TreyResearch and a method named Amortize(). The files are located in c:\temp\.
The following graphic shows the planned tables:
You have a sequence named Accounting.InvoiceID_Seq.
You plan to create two certificates named CERT1 and CERT2. You will create CERT1 in master. You will create CERT2 in DB1.
You have a legacy application that requires the ability to generate dynamic T-SQL statements against DB1. A sample of the queries generated by the legacy application appears in Legacy.sql.
Application Requirements -
The planned database has the following requirements:
All tables must be disk-based
All stored procedures must be signed.
The original XML invoices must be stored in the database.
An XML schema must be used to validate the invoice data.
Dynamic T-SQL statements must be converted to stored procedures.
Access to the .NET Framework tax components must be available to T-SQL objects.
Columns must be defined by using data types that minimize the amount of space used by each table.
Invoices stored in the InvoiceStatus table must refer to an invoice by the same identifier used by the Invoice table.
To protect against the theft of backup disks, invoice data must be protected by using the highest level of encryption.
The solution must provide a table-valued function that provides users with the ability to filter invoices by customer.
Indexes must be optimized periodically based on their fragmentation by using the minimum amount of administrative effort.
Usp_InsertInvoices.sql -
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number.
The following is a sample of a customer invoice in XML format:
InvoicesByCustomer.sql -
Legacy.sql -
CountryFromID.sql -
IndexManagement.sql -
Which data type should you use for CustomerID?
- A. varchar(11)
- B. bigint
- C. nvarchar(11)
- D. char(11)
Answer : D
Explanation:
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number. int: -2^31 (-2,147,483,648) to 2^31-1 (2,147,483,647) (just 10 digits max) bigint: -2^63 (-9,223,372,036,854,775,808) to 2^63-1
(9,223,372,036,854,775,807)
References:
http://msdn.microsoft.com/en-us/library/ms176089.aspx
http://msdn.microsoft.com/en-us/library/ms187745.aspx
Scenario 1 -
Application Information -
Your company receives invoices in XML format from customers. Currently, the invoices are stored as files and processed by a desktop application. The application has several performance and security issues. The application is being migrated to a SQL Server-based solution. A schema named InvoiceSchema has been created for the invoices xml.
The data in the invoices is sometimes incomplete. The incomplete data must be stored and processed as-is. Users cannot filter the data provided through views.
You are designing a SQL Server database named DB1 that will be used to receive, process, and securely store the invoice data. A third-party Microsoft .NET
Framework component will be purchased to perform tax calculations. The third-party tax component will be provided as a DLL file named Treytax.dll and a source code file named Amortize.cs. The component will expose a class named TreyResearch and a method named Amortize(). The files are located in c:\temp\.
The following graphic shows the planned tables:
You have a sequence named Accounting.InvoiceID_Seq.
You plan to create two certificates named CERT1 and CERT2. You will create CERT1 in master. You will create CERT2 in DB1.
You have a legacy application that requires the ability to generate dynamic T-SQL statements against DB1. A sample of the queries generated by the legacy application appears in Legacy.sql.
Application Requirements -
The planned database has the following requirements:
All tables must be disk-based
All stored procedures must be signed.
The original XML invoices must be stored in the database.
An XML schema must be used to validate the invoice data.
Dynamic T-SQL statements must be converted to stored procedures.
Access to the .NET Framework tax components must be available to T-SQL objects.
Columns must be defined by using data types that minimize the amount of space used by each table.
Invoices stored in the InvoiceStatus table must refer to an invoice by the same identifier used by the Invoice table.
To protect against the theft of backup disks, invoice data must be protected by using the highest level of encryption.
The solution must provide a table-valued function that provides users with the ability to filter invoices by customer.
Indexes must be optimized periodically based on their fragmentation by using the minimum amount of administrative effort.
Usp_InsertInvoices.sql -
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number.
The following is a sample of a customer invoice in XML format:
InvoicesByCustomer.sql -
Legacy.sql -
CountryFromID.sql -
IndexManagement.sql -
You need to modify InsertInvoice to comply with the application requirements.
Which code segment should you execute?
- A. Option A
- B. Option B
- C. Option C
- D. Option D
Answer : D
Scenario 1 -
Application Information -
Your company receives invoices in XML format from customers. Currently, the invoices are stored as files and processed by a desktop application. The application has several performance and security issues. The application is being migrated to a SQL Server-based solution. A schema named InvoiceSchema has been created for the invoices xml.
The data in the invoices is sometimes incomplete. The incomplete data must be stored and processed as-is. Users cannot filter the data provided through views.
You are designing a SQL Server database named DB1 that will be used to receive, process, and securely store the invoice data. A third-party Microsoft .NET
Framework component will be purchased to perform tax calculations. The third-party tax component will be provided as a DLL file named Treytax.dll and a source code file named Amortize.cs. The component will expose a class named TreyResearch and a method named Amortize(). The files are located in c:\temp\.
The following graphic shows the planned tables:
You have a sequence named Accounting.InvoiceID_Seq.
You plan to create two certificates named CERT1 and CERT2. You will create CERT1 in master. You will create CERT2 in DB1.
You have a legacy application that requires the ability to generate dynamic T-SQL statements against DB1. A sample of the queries generated by the legacy application appears in Legacy.sql.
Application Requirements -
The planned database has the following requirements:
All tables must be disk-based
All stored procedures must be signed.
The original XML invoices must be stored in the database.
An XML schema must be used to validate the invoice data.
Dynamic T-SQL statements must be converted to stored procedures.
Access to the .NET Framework tax components must be available to T-SQL objects.
Columns must be defined by using data types that minimize the amount of space used by each table.
Invoices stored in the InvoiceStatus table must refer to an invoice by the same identifier used by the Invoice table.
To protect against the theft of backup disks, invoice data must be protected by using the highest level of encryption.
The solution must provide a table-valued function that provides users with the ability to filter invoices by customer.
Indexes must be optimized periodically based on their fragmentation by using the minimum amount of administrative effort.
Usp_InsertInvoices.sql -
Invoices.xml -
All customer IDs are 11 digits. The first three digits of a customer ID represent the customer's country. The remaining eight digits are the customer's account number.
The following is a sample of a customer invoice in XML format:
InvoicesByCustomer.sql -
Legacy.sql -
CountryFromID.sql -
IndexManagement.sql -
You attempt to process an invoice by using usp_InsertInvoice.sql and you receive the following error message: "Msg 515, Level 16, State 2, Procedure usp_InsertInvoice, Line 10 Cannot insert the value NULL into column 'InvoiceDate', table 'DB1.Accounting.Invoices'; column does not allow nulls. INSERT fails."
You need to modify usp_InsertInvoice.sql to resolve the error.
How should you modify the INSERT statement?
- A. InvoiceDate varchar(l00) 'InvoiceDate',
- B. InvoiceDate varchar(100) 'Customer/InvoiceDate', '
- C. InvoiceDate date '@InvoiceDate',
- D. InvoiceDate date 'Customer/@InvoiceDate',
Answer : C
31 days access 