100% Latest & Updated Microsoft DP-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 170
Three independently confirmed SQL platform issues require separate evidence checks. Case A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection. Case B: A regulated Azure SQL deployment requires customer control over the database encryption key lifecycle. Case C: A test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. Select exactly THREE distinct diagnostic checks, one for each case.
- Column encryption metadata driver support and client-side key access
- Client connection encryption setting and negotiated TLS version
- Private endpoint connection status and private DNS resolution to the private address
- Azure SQL firewall rules and connection rejection code
- Encrypted payload representation and decryption-key ownership record
- Key Vault key identifier and Azure SQL TDE protector configuration
Explanation
Correct Answers
D:Azure SQL firewall rules and connection rejection code directly tests the observation that a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. It helps the team evaluate whether it should apply a least-permissive logical-server or database-level firewall rule for the authorized source. The check has a boundary: An open firewall path does not grant database login or object access.
E:Encrypted payload representation and decryption-key ownership record directly tests the observation that only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection. It helps the team evaluate whether it should choose supported object or column encryption explicitly for that attribute. The check has a boundary: Database-level encryption alone cannot replace column confidentiality controls.
F:Key Vault key identifier and Azure SQL TDE protector configuration directly tests the observation that a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle. It helps the team evaluate whether it should configure a supported customer-managed TDE protector using Azure Key Vault. The check has a boundary: Deleting or denying access to the protector can impair database availability.
Incorrect Answers
A:Column encryption metadata driver support and client-side key access is appropriate for the separate condition that a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. The actual 3 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A regulated Azure SQL deployment requires customer control over the database encryption key lifecycle; C: A test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. This option is not the specific diagnostic evidence for any of those stated cases.
B:Client connection encryption setting and negotiated TLS version is appropriate for the separate condition that a security scan detects a SQL client using insecure transport despite encryption-at-rest controls. The actual 3 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A regulated Azure SQL deployment requires customer control over the database encryption key lifecycle; C: A test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. This option is not the specific diagnostic evidence for any of those stated cases.
C:Private endpoint connection status and private DNS resolution to the private address is appropriate for the separate condition that a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint. The actual 3 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A regulated Azure SQL deployment requires customer control over the database encryption key lifecycle; C: A test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. This option is not the specific diagnostic evidence for any of those stated cases.
Question 171
A migration or configuration change request describes the following problem: A regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries. Which technical or administrative action most directly addresses this requirement?
- Enable or verify transparent data encryption for the database and supporting assets
- Require encrypted SQL client transport with valid certificate verification
- Configure a supported customer-managed TDE protector using Azure Key Vault
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
Explanation
Correct Answer
A:Enable or verify transparent data encryption for the database and supporting assets directly resolves the reported requirement that a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries. Storage-level database data is encrypted without changing SQL application statements. The implementation must also respect this constraint: TDE does not conceal plaintext from users who have query access.
Incorrect Answers
B:Require encrypted SQL client transport with valid certificate verification applies when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls, not when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries.
C:Configure a supported customer-managed TDE protector using Azure Key Vault applies when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle, not when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries.
D:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries.
Question 172
Before implementation the team records this technical condition: A payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. Which technical or administrative action most directly addresses this requirement?
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Configure a Private Link endpoint and private DNS integration for Azure SQL
- Implement Always Encrypted for the protected columns with supported client drivers
- Choose supported object or column encryption explicitly for that attribute
Explanation
Correct Answer
C:Implement Always Encrypted for the protected columns with supported client drivers directly resolves the reported requirement that a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. Column plaintext can remain inaccessible to the database engine for supported operations. The implementation must also respect this constraint: Unsupported predicates and application driver requirements must be evaluated.
Incorrect Answers
A:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys.
B:Configure a Private Link endpoint and private DNS integration for Azure SQL applies when a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint, not when a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys.
D:Choose supported object or column encryption explicitly for that attribute applies when only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection, not when a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys.
Question 173
The DBA must resolve this concrete requirement: A sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators. Which technical or administrative action most directly addresses this requirement?
- Enable or verify transparent data encryption for the database and supporting assets
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Require encrypted SQL client transport with valid certificate verification
- Configure supported Always Encrypted with secure enclaves and eligible client drivers
Explanation
Correct Answer
D:Configure supported Always Encrypted with secure enclaves and eligible client drivers directly resolves the reported requirement that a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators. Supported confidential computations become possible over protected columns. The implementation must also respect this constraint: Enclave support requires compatible clients and hosting; the attestation requirement varies by enclave type.
Incorrect Answers
A:Enable or verify transparent data encryption for the database and supporting assets applies when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries, not when a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators.
B:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators.
C:Require encrypted SQL client transport with valid certificate verification applies when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls, not when a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators.
Question 174
A migration or configuration change request describes the following problem: A finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint. Which technical or administrative action most directly addresses this requirement?
- Choose supported object or column encryption explicitly for that attribute
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Implement Always Encrypted for the protected columns with supported client drivers
- Configure a Private Link endpoint and private DNS integration for Azure SQL
Explanation
Correct Answer
D:Configure a Private Link endpoint and private DNS integration for Azure SQL directly resolves the reported requirement that a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint. Clients can route to the SQL service through the private address. The implementation must also respect this constraint: Creating a private endpoint does not automatically disable public network access.
Incorrect Answers
A:Choose supported object or column encryption explicitly for that attribute applies when only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection, not when a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint.
B:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint.
C:Implement Always Encrypted for the protected columns with supported client drivers applies when a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys, not when a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint.
Question 175
Before implementation the team records this technical condition: A test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. Which technical or administrative action most directly addresses this requirement?
- Configure a supported customer-managed TDE protector using Azure Key Vault
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Configure supported Always Encrypted with secure enclaves and eligible client drivers
- Require encrypted SQL client transport with valid certificate verification
Explanation
Correct Answer
B:Apply a least-permissive logical-server or database-level firewall rule for the authorized source directly resolves the reported requirement that a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. Eligible clients can establish network connections to the SQL service. The implementation must also respect this constraint: An open firewall path does not grant database login or object access.
Incorrect Answers
A:Configure a supported customer-managed TDE protector using Azure Key Vault applies when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle, not when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy.
C:Configure supported Always Encrypted with secure enclaves and eligible client drivers applies when a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators, not when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy.
D:Require encrypted SQL client transport with valid certificate verification applies when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls, not when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy.
Question 176
The DBA must resolve this concrete requirement: A security scan detects a SQL client using insecure transport despite encryption-at-rest controls. Which technical or administrative action most directly addresses this requirement?
- Require encrypted SQL client transport with valid certificate verification
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Configure a supported customer-managed TDE protector using Azure Key Vault
- Choose supported object or column encryption explicitly for that attribute
Explanation
Correct Answer
A:Require encrypted SQL client transport with valid certificate verification directly resolves the reported requirement that a security scan detects a SQL client using insecure transport despite encryption-at-rest controls. The client-to-server database connection is protected against passive interception. The implementation must also respect this constraint: Encrypting files at rest alone does not secure traffic over the network.
Incorrect Answers
B:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls.
C:Configure a supported customer-managed TDE protector using Azure Key Vault applies when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle, not when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls.
D:Choose supported object or column encryption explicitly for that attribute applies when only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection, not when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls.
Question 177
A migration or configuration change request describes the following problem: A regulated Azure SQL deployment requires customer control over the database encryption key lifecycle. Which technical or administrative action most directly addresses this requirement?
- Require encrypted SQL client transport with valid certificate verification
- Enable or verify transparent data encryption for the database and supporting assets
- Configure a supported customer-managed TDE protector using Azure Key Vault
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
Explanation
Correct Answer
C:Configure a supported customer-managed TDE protector using Azure Key Vault directly resolves the reported requirement that a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle. The customer controls key rotation and access policy for the encryption protector. The implementation must also respect this constraint: Deleting or denying access to the protector can impair database availability.
Incorrect Answers
A:Require encrypted SQL client transport with valid certificate verification applies when a security scan detects a SQL client using insecure transport despite encryption-at-rest controls, not when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle.
B:Enable or verify transparent data encryption for the database and supporting assets applies when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries, not when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle.
D:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a regulated Azure SQL deployment requires customer control over the database encryption key lifecycle.
Question 178
Before implementation the team records this technical condition: A team wants column master key operations separated from database administration and stored in a key vault. Which technical or administrative action most directly addresses this requirement?
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Enable or verify transparent data encryption for the database and supporting assets
- Store supported Always Encrypted column master keys in a protected key store
- Configure a Private Link endpoint and private DNS integration for Azure SQL
Explanation
Correct Answer
C:Store supported Always Encrypted column master keys in a protected key store directly resolves the reported requirement that a team wants column master key operations separated from database administration and stored in a key vault. Client-held keys can remain outside the database engine's direct control. The implementation must also respect this constraint: Key loss or incorrect driver configuration can make encrypted values unreadable.
Incorrect Answers
A:Apply a least-permissive logical-server or database-level firewall rule for the authorized source applies when a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy, not when a team wants column master key operations separated from database administration and stored in a key vault.
B:Enable or verify transparent data encryption for the database and supporting assets applies when a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries, not when a team wants column master key operations separated from database administration and stored in a key vault.
D:Configure a Private Link endpoint and private DNS integration for Azure SQL applies when a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint, not when a team wants column master key operations separated from database administration and stored in a key vault.
Question 179
Two independent Azure SQL administration tickets require separate actions. Case A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection. Case B: A team wants column master key operations separated from database administration and stored in a key vault. Select exactly TWO distinct implementation steps, one for each case.
- Configure a Private Link endpoint and private DNS integration for Azure SQL
- Choose supported object or column encryption explicitly for that attribute
- Apply a least-permissive logical-server or database-level firewall rule for the authorized source
- Enable or verify transparent data encryption for the database and supporting assets
- Store supported Always Encrypted column master keys in a protected key store
Explanation
Correct Answers
B:Choose supported object or column encryption explicitly for that attribute directly resolves the reported requirement that only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection. The sensitive payload is protected at a narrower data boundary. The implementation must also respect this constraint: Database-level encryption alone cannot replace column confidentiality controls.
E:Store supported Always Encrypted column master keys in a protected key store directly resolves the reported requirement that a team wants column master key operations separated from database administration and stored in a key vault. Client-held keys can remain outside the database engine's direct control. The implementation must also respect this constraint: Key loss or incorrect driver configuration can make encrypted values unreadable.
Incorrect Answers
A:Configure a Private Link endpoint and private DNS integration for Azure SQL is appropriate for the separate condition that a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint. The actual 2 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A team wants column master key operations separated from database administration and stored in a key vault. This option is not the specific implementation or corrective step for any of those stated cases.
C:Apply a least-permissive logical-server or database-level firewall rule for the authorized source is appropriate for the separate condition that a test system can use the correct SQL credentials but its current source IP is blocked by Azure SQL firewall policy. The actual 2 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A team wants column master key operations separated from database administration and stored in a key vault. This option is not the specific implementation or corrective step for any of those stated cases.
D:Enable or verify transparent data encryption for the database and supporting assets is appropriate for the separate condition that a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries. The actual 2 cases are A: Only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection; B: A team wants column master key operations separated from database administration and stored in a key vault. This option is not the specific implementation or corrective step for any of those stated cases.
Question 180
Three independently confirmed SQL platform issues require separate evidence checks. Case A: A regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries. Case B: A security scan detects a SQL client using insecure transport despite encryption-at-rest controls. Case C: A payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. Select exactly THREE distinct diagnostic checks, one for each case.
- Column encryption metadata driver support and client-side key access
- Encrypted payload representation and decryption-key ownership record
- Client connection encryption setting and negotiated TLS version
- Secure enclave attestation settings and encrypted-column operation capability
- Azure SQL TDE state and protector key configuration
- Private endpoint connection status and private DNS resolution to the private address
Explanation
Correct Answers
A:Column encryption metadata driver support and client-side key access directly tests the observation that a payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. It helps the team evaluate whether it should implement Always Encrypted for the protected columns with supported client drivers. The check has a boundary: Unsupported predicates and application driver requirements must be evaluated.
C:Client connection encryption setting and negotiated TLS version directly tests the observation that a security scan detects a SQL client using insecure transport despite encryption-at-rest controls. It helps the team evaluate whether it should require encrypted SQL client transport with valid certificate verification. The check has a boundary: Encrypting files at rest alone does not secure traffic over the network.
E:Azure SQL TDE state and protector key configuration directly tests the observation that a regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries. It helps the team evaluate whether it should enable or verify transparent data encryption for the database and supporting assets. The check has a boundary: TDE does not conceal plaintext from users who have query access.
Incorrect Answers
B:Encrypted payload representation and decryption-key ownership record is appropriate for the separate condition that only one legacy sensitive attribute needs an application-controlled encryption path rather than whole-database disk protection. The actual 3 cases are A: A regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries; B: A security scan detects a SQL client using insecure transport despite encryption-at-rest controls; C: A payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. This option is not the specific diagnostic evidence for any of those stated cases.
D:Secure enclave attestation settings and encrypted-column operation capability is appropriate for the separate condition that a sensitive encrypted column needs supported server-side computations without exposing general plaintext to SQL administrators. The actual 3 cases are A: A regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries; B: A security scan detects a SQL client using insecure transport despite encryption-at-rest controls; C: A payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. This option is not the specific diagnostic evidence for any of those stated cases.
F:Private endpoint connection status and private DNS resolution to the private address is appropriate for the separate condition that a finance database must be reached through approved VNet private IP connectivity rather than an exposed public endpoint. The actual 3 cases are A: A regulator requires database files transaction logs and backups to be encrypted at rest without modifying SQL queries; B: A security scan detects a SQL client using insecure transport despite encryption-at-rest controls; C: A payroll application must prevent database administrators from reading salary plaintext while the client retains decryption keys. This option is not the specific diagnostic evidence for any of those stated cases.
Administering Microsoft Azure SQL Solutions (DP-300) Practice Tests