nerdexam
Palo_Alto_Networks

PSE-PRISMACLOUD · Question #59

Which Resource Query Language (RQL) query returns a list of all Azure SQL Databases that have transparent data encryption turned in?

The correct answer is A. config from cloud.resource where api.name = 'gcloud-compute-instances-list' and json.rule = is. Note: All four answer choices reference gcloud-compute-instances-list, a Google Cloud API - not an Azure SQL API. This appears to be a flawed or truncated question, likely from a mixed question bank. The correct RQL for Azure SQL TDE would use an API name like…

Visibility and Compliance

Question

Which Resource Query Language (RQL) query returns a list of all Azure SQL Databases that have transparent data encryption turned in?

Options

  • Aconfig from cloud.resource where api.name = 'gcloud-compute-instances-list' and json.rule = is
  • Bconfig from cloud.resource where api.name = 'gcloud-compute-instances-list' = TERMINATED
  • Cconfig from cloud.resource where api.name = 'gcloud-compute-instances-list* and json.rule ==
  • Dconfig from cloud.resource where api.name = 'gcloud-compute-instances-list' and json.rule =

How the community answered

(41 responses)
  • A
    71% (29)
  • B
    17% (7)
  • C
    5% (2)
  • D
    7% (3)

Explanation

Note: All four answer choices reference gcloud-compute-instances-list, a Google Cloud API - not an Azure SQL API. This appears to be a flawed or truncated question, likely from a mixed question bank. The correct RQL for Azure SQL TDE would use an API name like azure-sql-db-list, not a GCP compute API.

Evaluating structurally why A is marked correct:

Option A has the most syntactically complete RQL structure - it includes both the api.name filter and a json.rule clause joined with and, which is the correct pattern for filtering cloud resources by configuration attributes in Prisma Cloud RQL.

Why the distractors are wrong:

  • B incorrectly appends = TERMINATED directly to api.name instead of using a separate json.rule clause, breaking RQL syntax entirely.
  • C has an unclosed string literal - the closing quote is missing after gcloud-compute-instances-list* - making it syntactically invalid.
  • D ends with a bare = and no value, making it an incomplete and non-functional query.

Memory tip: In Prisma Cloud RQL, always pair api.name with a json.rule clause connected by and to filter on specific configuration attributes - think: "Name AND Rule" as the two-part formula for any config query.

Topics

#RQL#resource query language#Azure SQL#transparent data encryption

Community Discussion

No community discussion yet for this question.

Full PSE-PRISMACLOUD Practice