Microsoft 070-765 Deutsch Actual Free Exam Questions & Community Discussion

Explanation:
Box 1: ADD MASKED WITH(FUNCTION = 'email()')
The email masking method exposes the first letter of an email address and the constant suffix ".com", in the form of an email address. . [email protected].
This default behavior is what we want.
Example definition syntax: Email varchar(100) MASKED WITH (FUNCTION = 'email()') NULL Box 2: ADD MASKED WITH(FUNCTION = 'partial(2,"XX-XX-XX",2) The custom masking method which exposes the first and last letters and adds a custom padding string in the middle. Syntax: prefix,[padding],suffix References:
https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking?view=sql-server-2017

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:
Box 1: Reporting
The user is to be created in the Reporting database.
Box 2: CREATE USER
Box 3: FOR LOGIN [BIAppUser]
Users are created per database and are associated with logins. You must be connected to the database in where you want to create the user. Here is some sample Transact-SQL that creates a user:
CREATE USER readonlyuser FROM LOGIN readonlylogin;
References:
https://azure.microsoft.com/en-us/blog/adding-users-to-your-sql-azure-database/

Explanation:
To use TDE, follow these steps.
- Create a master key
- Create or obtain a certificate protected by the master key
- Create a database encryption key and protect it by the certificate
- Set the database to use encryption
Example:
USE master;
GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<UseStrongPasswordHere>';
GO
CREATE CERTIFICATE MyServerCert WITH SUBJECT = 'My Certificate';
GO
USE AdventureWorks2012;
GO
CREATE DATABASE ENCRYPTION KEY
WITH ALGORITHM = AES_128
ENCRYPTION BY SERVER CERTIFICATE MyServerCert;
GO
ALTER DATABASE AdventureWorks2012
SET ENCRYPTION ON;
GO
References:
https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/transparent-data-encryption?view=sql-server-2017

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:
B: First we create a login with the CREATE LOGIN command.
E: Then we add it to the sysadmin role.
1. To add a member to a fixed server role
2. In Object Explorer, connect to an instance of Database Engine.
3. On the Standard bar, click New Query.
Copy and paste the following example into the query window and click Execute.
ALTER SERVER ROLE diskadmin ADD [Domain\Juan] ;
GO
G: Finally we add a database user for the login we created.
References:
https://technet.microsoft.com/en-us/library/aa337562(v=sql.110).aspx

Explanation:
References:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-in-memory#additional-resources
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool

Explanation:
Step 1: CREATE LOGIN
First you need to create a login for SQL Azure, it's syntax is as follows:
CREATE LOGIN username WITH password='password';
Step 2, CREATE USER
Step 3: LOGIN
Users are created per database and are associated with logins. You must be connected to the database in where you want to create the user. In most cases, this is not the master database. Here is some sample Transact-SQL that creates a user:
CREATE USER readonlyuser FROM LOGIN readonlylogin;
Step 4: loginmanager
Members of the loginmanager role can create new logins in the master database.
References:
https://azure.microsoft.com/en-us/blog/adding-users-to-your-sql-azure-database/
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-manage-logins

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:
From the scenario: SRV1 has 16 logical cores and hosts a SQL Server instance that supports a mission-critical application. The application hasapproximately 30,000 concurrent users and relies heavily on the use of temporary tables.
Box 1: Change the size of the tempdb log file.
The size and physical placement of the tempdb database can affect the performance of a system. For example, if the size that is defined for tempdb is too small, part of the system-processing load may be taken up with autogrowing tempdb to the size required to support the workload every time you restart the instance of SQL Server. You can avoid this overhead by increasing the sizes of the tempdb data and log file.
Box 2: Add additional tempdb files.
Create as many files as needed to maximize disk bandwidth. Using multiple files reduces tempdb storage contention and yields significantly better scalability. However, do not create too many files because this can reduce performance and increase management overhead. As a general guideline, create one data file for each CPU on the server (accounting for any affinity mask settings) and then adjust the number of files up or down as necessary.
Topic 2, Contoso, Ltd Case Study
Background
You are the database administrator for Contoso, Ltd. The company has 200 offices around the world. The company has corporate executives that are located in offices in London, New York, Toronto, Sydney, and Tokyo.
Contoso, Ltd. has a Microsoft Azure SQL Database environment. You plan to deploy a new Azure SQL Database to support a variety of mobile applications and public websites.
The company is deploying a multi-tenant environment. The environment will host Azure SQL Database instances. The company plans to make the instances available to internal departments and partner companies. Contoso is in the final stages of setting up networking and communications for the environment.
Existing Contoso and Customer instances need to be migrated to Azure virtual machines (VM) according to the following requirements:
The company plans to deploy a new order entry application and a new business intelligence and analysis application. Each application will be supported by a new database. Contoso creates a new Azure SQL database named Reporting. The database will be used to support the company's financial reporting requirements. You associate the database with the Contoso Azure Active Directory domain.
Each location database for the data entry application may have an unpredictable amount of activity. Data must be replicated to secondary databases in Azure datacenters in different regions.
To support the application, you need to create a database named contosodb1 in the existing environment.
Objects

Database
The contosodb1 database must support the following requirements:
Application
For the business intelligence application, corporate executives must be able to view all data in near real-time with low network latency.
Contoso has the following security, networking, and communications requirements:

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).