AZ-300 Exam QuestionsBrowse all questions from this exam

AZ-300 Exam - Question 152


DRAG DROP -

You maintain an existing Azure SQL Database instance. Management of the database is performed by an external party. All cryptographic keys are stored in an

Azure Key Vault.

You must ensure that the external party cannot access the data in the SSN column of the Person Table.

Will each protection method meet the requirement? To answer, drag the appropriate responses to the correct protection methods.

Each response may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.

Select and Place:

Exam AZ-300 Question 152
Show Answer
Correct Answer:
Exam AZ-300 Question 152

References:

https://docs.microsoft.com/en-us/azure/security/azure-database-security-overview

Discussion

12 comments
Sign in to comment
Happiman
Mar 12, 2020

YES/NO/NO/NO

Daltonic75
Mar 11, 2020

Same question but different answer in https://www.examtopics.com/exams/microsoft/az-203/view/15/

Gjferweb
Apr 1, 2020

agree with that Yes No Yes NO https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15 In SQL Database, the VIEW permissions aren't granted by default to the public fixed database role. This enables certain existing, legacy tools (using older versions of DacFx) to work properly. Consequently, to work with encrypted columns (even if not decrypting them) a database administrator must explicitly grant the two VIEW permissions.

pieixoto
May 1, 2020

You are correct but I am thinking each answer must be a correct solution. If you assign the public fixed data base role, you cannot just assume the column was encrypted. Therefore the only answer that presents a correct solution to the question is always encrypted setting.

pieixoto
May 1, 2020

You are correct but I am thinking each answer must be a correct solution. If you assign the public fixed data base role, you cannot just assume the column was encrypted. Therefore the only answer that presents a correct solution to the question is always encrypted setting.

Prash85
Jun 17, 2020

Always On Encryption is just a typo... So answer is Y N N N

dwild
Jun 10, 2020

Always Encrypted != AlwaysON... so NO,NO,NO

tundervirld
Aug 5, 2020

Will be, NO,NO,NO,NO: Explanation: Enable Always Encryption, yes is good practice and you can configure it for individual database columns containing your sensitive data, but the question says AlwaysOn Encryption, so NO. Set Column encryption to disable, will leave to see information, we don't need it, so NO. Fixed Roles is bad practice and can be able to escalate privileges, so NO. Store Column encryption in system catalog view, doesn't make sense since it is the most efficient way to obtain, transform, and present customized forms of catalog metadata information, so NO References: https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15 https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/catalog-views-transact-sql?view=sql-server-ver15 https://docs.microsoft.com/en-us/azure/security/azure-database-security-overview

Sathian
Oct 29, 2020

4 should be yes, the column keys are stored in the catalogue views https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/overview-of-key-management-for-always-encrypted?view=sql-server-ver15

altafpatel1984
Dec 5, 2021

wrong answer. please don't misguide users.

Juanlu
Nov 29, 2020

Agree: NO | NO | NO | NO. Same as: https://www.examtopics.com/exams/microsoft/az-203/view/15/

altafpatel1984
Dec 5, 2021

wrong answer. please don't misguide users.

altafpatel1984
Dec 5, 2021

wrong answer. please don't misguide users.

altafpatel1984
Dec 5, 2021

wrong answer. please don't misguide users.

altafpatel1984
Dec 5, 2021

wrong answer. please don't misguide users.

Serena_C
Feb 16, 2020

I think this should be cell-level encryption, according to MS doc below, Cell-level encryption is available to encrypt specific columns or even cells of data with different encryption keys. https://docs.microsoft.com/en-us/azure/security/fundamentals/database-security-overview

Syd
Feb 18, 2020

Correct. Answer no,no,no,no Alwayson is for high availability and disaster recovery solution introduced when SQL Server 2012 was launched and above versions.

jcarlos
Feb 19, 2020

Completely agree unless there is typo in the answer and they mean always encrypted (there is no such thing AlwaysOn Encryption). If there is an error in the wording then it would be yes-no-no-no

qr
Feb 28, 2020

yep, or a trap for alwayson availability groups? if a trap, kinda lame

tartar
Sep 14, 2020

Y N N N

zhifu
Jun 19, 2020

there is no such thing AlwaysOn Encryption.... you are right

tartar
Sep 14, 2020

Y N N N

qr
Feb 28, 2020

yep, or a trap for alwayson availability groups? if a trap, kinda lame

tartar
Sep 14, 2020

Y N N N

Andy001
Mar 2, 2020

This is certainly a typo in the question. It should be "Always encrypted" https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15

praveen97
Jul 19, 2020

Agree with Andy001. It should be Always Encrypted.

AnilV
Apr 30, 2020

it should be always encrypted

zhifu
Jun 19, 2020

there is no such thing AlwaysOn Encryption.... you are right

praveen97
Jul 19, 2020

Agree with Andy001. It should be Always Encrypted.

tartar
Sep 14, 2020

Y N N N

morpjo
Sep 25, 2020

That AlwaysOn for HA/DR..... is Always on Availability Group.

qr
Mar 6, 2020

AlwaysOn dosent exist... Always Encrypted does... All No.

milind8451
Apr 22, 2020

Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national identification numbers (for example, U.S. social security numbers), stored in Azure SQL Database or SQL Server databases. So it should be "Always Encrypted" instead of "Always on Encryption". I think its a ttypo.

AnshMan
May 25, 2020

Yes, No, Yes, NO https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15 https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/overview-of-key-management-for-always-encrypted?view=sql-server-ver15

JeeBi
Jul 26, 2020

https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15 "You can configure Always Encrypted for individual database columns containing your sensitive data." So this should indeed work.

azurehunter
Nov 20, 2020

IMO, answer is N, N, N, Y. "AlwaysOn Encryption" not exists. MS purposely try to confuse us. Last one is how Always Encryption to store the column encryption keys.