HOTSPOT (Drag and Drop is not supported)You have an Azure SQL logical server.You run the following script.For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: NoRows can be inserted into the table. The APPEND_ONLY = ON option is not specified.Ledger functionality is introduced to tables in two forms:* Updatable ledger tables, which allow you to update and delete rows in your tables.* Append-only ledger tables, which only allow insertions to your tables. You can create an append-only ledger table by specifying the LEDGER = ON argument in your CREATE TABLE (Transact-SQL) statement and specifying the APPEND_ONLY = ON option.Box 2: NoThis is not a Ledger database. The database was not created using the clause: WITH LEDGER = ON.Note: Enable ledger database using T-SQLOpen a query editor like SQL Server Management Studio (SSMS) or Azure Data Studio and connect to your logical SQL Server. The below example creates a General Purpose database. The WITH LEDGER=ON clause will create the ledger database.SQLCREATE DATABASE Database01(EDITION = 'GeneralPurpose',SERVICE_OBJECTIVE='GP_Gen5_2',MAXSIZE = 2 GB)WITH LEDGER = ON;GOLedger databaseLedger databases provide an easy solution for applications that require the integrity of all data to be protected for the entire lifetime of the database. A ledger database can only contain ledger tables. Creating regular tables (that are not ledger tables) is not supported. Each table is, by default, created as an Updatable ledger table with default settings, which makes creating such tables very easy. You configure a database as a ledger database at creation. Once created, a ledger database cannot be converted to a regular database.Box 3: YesA system-versioned temporal table must have a primary key defined and have exactly one PERIOD FOR SYSTEM_TIME defined with two datetime2 columns, declared as GENERATED ALWAYS AS ROW START / ENDNote 1: In the example below, a new table is created with system-versioning enabled without defining the name of the history table.SQLCREATE TABLE Department(DeptID INT NOT NULL PRIMARY KEY CLUSTERED, DeptName VARCHAR(50) NOT NULL, ManagerID INT NULL, ParentDeptID INT NULL, ValidFrom DATETIME2 GENERATED ALWAYS AS ROW START NOT NULL , ValidTo DATETIME2 GENERATED ALWAYS AS ROW END NOT NULL, PERIOD FOR SYSTEM_TIME (ValidFrom, ValidTo))WITH (SYSTEM_VERSIONING = ON);Note 2: What is a system-versioned temporal table?A system-versioned temporal table is a type of user table designed to keep a full history of data changes, allowing easy point-in-time analysis. This type of temporal table is referred to as a system-versioned temporal table because the period of validity for each row is managed by the system (that is, the database engine).
https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-append-only-ledger-tables https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-overview https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-how-to-configure-ledger- database https://learn.microsoft.com/en-us/sql/relational-databases/tables/creating-a-system-versioned-temporal-table
You have an Azure SQL database named DB1.You need to encrypt DB1. The solution must meet the following requirements:Encrypt data in motion.Support comparison operators.Provide randomized encryption.What should you include in the solution?
Always Encrypted with secure enclavesAlways Encrypted with secure enclaves expands confidential computing capabilities of Always Encrypted by enabling in-place encryption and richer confidential queries.Always Encrypted protects the data by encrypting it on the client side and never allowing the data or the corresponding cryptographic keys to appear in plaintext inside the Database Engine. As a result, the functionality on encrypted columns inside the database is severely restricted. The only operations the Database Engine can perform on encrypted data are equality comparisons (only available with deterministic encryption).All other operations, including cryptographic operations (initial data encryption or key rotation) and richer queries (for example, pattern matching) aren't supported inside the database. Users need to move their data outside of the database to perform these operations on the client-side.Always Encrypted with secure enclaves addresses these limitations by allowing some computations on plaintext data inside a secure enclave on the server side. A secure enclave is a protected region of memory within the Database Engine process.The two key benefits of Always Encrypted with secure enclaves are in-place encryption and rich confidential queries.1. In-place encryptionIn-place encryption allows cryptographic operations on database columns inside the secure enclave, without moving the data outside of the database. In-place encryption improves the performance and the reliability of cryptographic operations.In-place encryption is allowed with both deterministic and randomized encryption, as long as the column encryption keys involved in a cryptographic operation are enclave-enabled.2. Confidential queriesConfidential queries are DML queries that involve operations on enclave-enabled columns performed inside the secure enclave.The operations supported inside the secure enclaves are:Incorrect:* Always EncryptedAlways Encrypted protects the data by encrypting it on the client side and never allowing the data or the corresponding cryptographic keys to appear in plaintext inside the Database Engine. As a result, the functionality on encrypted columns inside the database is severely restricted. The only operations the Database Engine can perform on encrypted data are equality comparisons (only available with deterministic encryption).All other operations, including cryptographic operations (initial data encryption or key rotation) and richer queries (for example, pattern matching) aren't supported inside the database. Users need to move their data outside of the database to perform these operations on the client-side.
https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-enclaves
You have an instance of SQL Server on Azure Virtual Machines.You need to ensure that a user named User1 can configure proxy accounts for SQL Server Agent jobs. The solution must use the principle of least privilege.Which role should you assign to User1?
PermissionsOnly members of the sysadmin fixed server role have permission to create, modify, or delete proxy accounts.Users who are not members of the sysadmin fixed server role must be added to one of the following SQL Server Agent fixed database roles in the msdb database to use proxies: SQLAgentUserRole,SQLAgentReaderRole, or SQLAgentOperatorRole.Incorrect:Not B: SQLAgentUserRole is the least privileged of the SQL Server Agent fixed database roles. It has permissions on only operators, local jobs, and job schedules. Members of SQLAgentUserRole have permissions on only local jobs and job schedules that they own.Not C: SQLAgentReaderRole includes all the SQLAgentUserRole permissions as well as permissions to view the list of available multiserver jobs, their properties, and their history. Members of this role can also view the list of all available jobs and job schedules and their properties, not just those jobs and job schedules that they own.Not D: SQLAgentOperatorRole is the most privileged of the SQL Server Agent fixed database roles. It includes all the permissions of SQLAgentUserRole and SQLAgentReaderRole. Members of this role can also view properties for operators and proxies, and enumerate available proxies and alerts on the server.
https://learn.microsoft.com/en-us/sql/ssms/agent/create-a-sql-server-agent-proxy https://learn.microsoft.com/en-us/sql/ssms/agent/sql-server-agent-fixed-database-roles
You have an Azure SQL database named DB1. DB1 has a table named Table1 that contains the following columns.You plan to enable Always Encrypted for Table1.Which two columns support encryption? Each correct answer presents a complete solution.Note: Each correct selection is worth one point.
Answer(s): D,E
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription that contains an Azure SQL managed instance named SQL1.You use the Microsoft Power BI service.You need to configure connectivity from the Power BI service to SQL1. The solution must ensure that only the Power BI service can initiate connections to SQL1.Which type of endpoint should you use for SQL1, and what should you use to control the connections to SQL1? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: PublicPublic endpoint for a managed instance enables data access to your managed instance from outside the virtual network. You're able to access your managed instance from multi-tenant Azure services like Power BI, Azure App Service, or an on-premises network. By using the public endpoint on a managed instance, you don't need to use a VPN, which can help avoid VPN throughput issues.Box 2: A network security groupAllow public endpoint traffic on the network security group1. If you have the configuration page of the managed instance still open, navigate to the Overview tab. Otherwise, go back to your SQL managed instance resource. Select the Virtual network/subnet link, which will take you to the Virtual network configuration page.2. Select the Subnets tab on the left configuration pane of your Virtual network, and make note of the SECURITY GROUP for your managed instance.3. Go back to your resource group that contains your managed instance. You should see the Network security group name noted above. Select the name to go into the network security group configuration page.4. Select the Inbound security rules tab, and Add a rule that has higher priority than the deny_all_inbound rule with the following settings:* Details omitted *
https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/public-endpoint-configure
Post your Comments and Discuss Microsoft DP-300 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the DP-300 content, but please register or login to continue.