Microsoft AZ-500 Practice Test 76
Question 750
A managed SQL database needs an approved customer-managed TDE protector with valid Key Vault permissions. A review identifies this consequence: An invalid TDE protector can make the database unavailable or leave the planned key-control requirement unmet. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to delete the key vault protector before validating SQL recovery support.
- The controlled remediation is to enable HTTPS for a web API and assume SQL database storage is encrypted by that alone.
- The controlled remediation is to change a Dynamic Data Masking rule to provide file-level database encryption.
- The controlled remediation is to restore valid TDE protector access and confirm encrypted database status.
Explanation
Correct Answer
D:Test using these records: TDE state, server encryption protector, Key Vault identity and encrypted database files or backup status. TDE encrypts supported database data at rest and is separate from client transport TLS and column-level encryption.
Incorrect Answers
A:Delete the key vault protector before validating SQL recovery support. This would not reliably restore the intended security boundary. An invalid TDE protector can make the database unavailable or leave the planned key-control requirement unmet. The appropriate controlled recovery is: Restore valid TDE protector access and confirm encrypted database status.
B:Enable HTTPS for a web API and assume SQL database storage is encrypted by that alone. This would not reliably restore the intended security boundary. An invalid TDE protector can make the database unavailable or leave the planned key-control requirement unmet. The appropriate controlled recovery is: Restore valid TDE protector access and confirm encrypted database status.
C:Change a Dynamic Data Masking rule to provide file-level database encryption. This would not reliably restore the intended security boundary. An invalid TDE protector can make the database unavailable or leave the planned key-control requirement unmet. The appropriate controlled recovery is: Restore valid TDE protector access and confirm encrypted database status.
Question 751
An application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns. What is the most defensible Azure security action?
- Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients.
- Use only Dynamic Data Masking and claim the database engine never sees plaintext.
- Give SQL administrators all column master keys for convenience.
- Assume enabling TDE automatically encrypts every client query result end to end.
Explanation
Correct Answer
A:Confirm the change against these records: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
Incorrect Answers
B:TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. Use only Dynamic Data Masking and claim the database engine never sees plaintext.
C:Give SQL administrators all column master keys for convenience. The proposed change targets the wrong mechanism or lacks essential validation. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Relevant evidence is encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
D:TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The intended action is: Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients.
Question 752
An application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns. Which diagnostic record would most strongly confirm the result?
- The identity name without a corresponding workload data authorization test.
- An outdated deployment template without current effective settings.
- A powered-on VM status without the actual guest or data-plane security state.
- Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
Explanation
Correct Answer
D:These records test the actual always Encrypted client-side column protection behavior rather than an unrelated dashboard state. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
Incorrect Answers
A:On its own, that evidence does not prove the specified security control works. The more relevant observations are: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
B:On its own, that evidence does not prove the specified security control works. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
C:On its own, that evidence does not prove the specified security control works. In the given case, an application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns.
Question 753
An application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns. Which platform concept should guide the engineer’s assessment?
- Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
- A running compute resource automatically enforces least-privilege Kubernetes permissions.
- A valid Azure management role always gives full access to every blob object and SQL row.
- Encrypting network transport guarantees all storage at-rest and column-level security requirements.
Explanation
Correct Answer
A:Confirmation depends on Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query. This principle supports the security response: Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients.
Incorrect Answers
B:A running compute resource automatically enforces least-privilege Kubernetes permissions. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
C:A valid Azure management role always gives full access to every blob object and SQL row. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
D:Encrypting network transport guarantees all storage at-rest and column-level security requirements. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
Question 754
An application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns. Suppose the operator instead follows this unsafe shortcut: Use only Dynamic Data Masking and claim the database engine never sees plaintext. Which root-cause observation follows from that incorrect change?
- Collecting VM diagnostic data caused the original unauthorized storage read.
- Keeping historic blob versions is the cause of the missing RBAC assignment.
- TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns.
- The security flaw is that the team retained a tested database backup.
Explanation
Correct Answer
C:The suitable control is: Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
Incorrect Answers
A:This does not explain the real always Encrypted client-side column protection weakness after the shortcut. The material failure is: TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns.
B:This does not explain the real always Encrypted client-side column protection weakness after the shortcut. Inspect evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
D:This does not explain the real always Encrypted client-side column protection weakness after the shortcut. The security flaw is that the team retained a tested database backup.
Question 755
An application stores highly sensitive national identifiers and wants database operators unable to view plaintext columns. A review identifies this consequence: TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. Which recovery action addresses the underlying technical fault?
- Give SQL administrators all column master keys for convenience.
- Deploy compliant client drivers and key permissions and test authorized decryption.
- Assume enabling TDE automatically encrypts every client query result end to end.
- Use only Dynamic Data Masking and claim the database engine never sees plaintext.
Explanation
Correct Answer
B:Test using these records: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query. This addresses the observed security problem while providing a verifiable outcome.
Incorrect Answers
A:Give SQL administrators all column master keys for convenience. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.
C:Assume enabling TDE automatically encrypts every client query result end to end. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.
D:Use only Dynamic Data Masking and claim the database engine never sees plaintext. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.
Question 756
A team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values. What is the BEST supported implementation or corrective action?
- For this Azure workload, the team should give SQL administrators all column master keys for convenience.
- For this Azure workload, the team should assume enabling TDE automatically encrypts every client query result end to end.
- For this Azure workload, the team should use only Dynamic Data Masking and claim the database engine never sees plaintext.
- For this Azure workload, the team should configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients.
Explanation
Correct Answer
D:Confirm the change against these records: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
Incorrect Answers
A:Give SQL administrators all column master keys for convenience. The proposed change targets the wrong mechanism or lacks essential validation. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Relevant evidence is encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
B:TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. In the given case, a team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values.
C:Use only Dynamic Data Masking and claim the database engine never sees plaintext.
Question 757
A team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values. Which evidence BEST verifies the intended technical behavior?
- In this security review, examine a storage account resource name without its encryption or retention configuration.
- In this security review, examine encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
- In this security review, examine the identity name without a corresponding workload data authorization test.
- In this security review, examine an outdated deployment template without current effective settings.
Explanation
Correct Answer
B:These records test the actual always Encrypted client-side column protection behavior rather than an unrelated dashboard state. The intended action is: Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients.
Incorrect Answers
A:On its own, that evidence does not prove the specified security control works. In the given case, a team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values.
C:The more relevant observations are: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
D:Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
Question 758
A team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values. Which principle BEST explains why the recommended solution is appropriate?
- The applicable security principle is that always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
- The applicable security principle is that encrypting network transport guarantees all storage at-rest and column-level security requirements.
- The applicable security principle is that a running compute resource automatically enforces least-privilege Kubernetes permissions.
- The applicable security principle is that a protected storage account is immune to every accidental deletion and overwrite.
Explanation
Correct Answer
A:Confirmation depends on Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
Incorrect Answers
B:Encrypting network transport guarantees all storage at-rest and column-level security requirements. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
C:A running compute resource automatically enforces least-privilege Kubernetes permissions. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
D:A protected storage account is immune to every accidental deletion and overwrite. This is an incorrect assumption for always Encrypted client-side column protection. The relevant security behavior is: Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations. Check evidence such as encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query.
Question 759
A team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values. Suppose the operator instead follows this unsafe shortcut: Use only Dynamic Data Masking and claim the database engine never sees plaintext. What is the MOST significant failure introduced by that shortcut?
- The resulting security weakness is that the security flaw is that the team retained a tested database backup.
- The resulting security weakness is that inspecting encryption settings itself disables a healthy disk.
- The resulting security weakness is that keeping historic blob versions is the cause of the missing RBAC assignment.
- The resulting security weakness is that tDE alone does not prevent a privileged SQL engine from processing plaintext queried columns.
Explanation
Correct Answer
D:The suitable control is: Configure supported Azure SQL Always Encrypted columns and protect column master keys on authorized clients. This is a material consequence of the incorrect shortcut.
Incorrect Answers
A:This does not explain the real always Encrypted client-side column protection weakness after the shortcut. In the given case, a team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values.
B:The material failure is: TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns.
C:This does not explain the real always Encrypted client-side column protection weakness after the shortcut. Keeping historic blob versions is the cause of the missing RBAC assignment.
Question 760
A team uses TDE but the compliance requirement prohibits the service-side database engine from seeing selected column values. A review identifies this consequence: TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to assume enabling TDE automatically encrypts every client query result end to end.
- The controlled remediation is to use only Dynamic Data Masking and claim the database engine never sees plaintext.
- The controlled remediation is to deploy compliant client drivers and key permissions and test authorized decryption.
- The controlled remediation is to give SQL administrators all column master keys for convenience.
Explanation
Correct Answer
C:Test using these records: Encrypted column definitions, client driver behavior, key metadata and authorized decrypt versus unauthorized query. Always Encrypted protects selected column plaintext outside the SQL engine using client-side cryptographic operations.
Incorrect Answers
A:Assume enabling TDE automatically encrypts every client query result end to end. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.
B:Use only Dynamic Data Masking and claim the database engine never sees plaintext. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.
D:Give SQL administrators all column master keys for convenience. This would not reliably restore the intended security boundary. TDE alone does not prevent a privileged SQL engine from processing plaintext queried columns. The appropriate controlled recovery is: Deploy compliant client drivers and key permissions and test authorized decryption.