ServiceNow CSA Exam - Topic 2 Question 63 Discussion

Actual exam question for ServiceNow's CSA exam

Question #: 63
Topic #: 2

[All CSA Questions]

How would you define an Access Control, to allow a user with iti role to have permission to create incident records?

AName: incident''; Permission: write; Role: itil

BName: incident Any, Operation: write, Permission: itil

CName: incident.*; Operation: write; Permission: itil

DName: incident None, Permission: create: Role: itil

EName: incident. None; Operation: create; Role: itil

Show Suggested Answer

Suggested Answer: A, C, D

https://www.adzuna.in/details/3252834223

The following are the benefits of building flows using Flow Designer:

C) Provides natural-language descriptions of flow logic:This allows users without programming experience to understand and modify flows,making them more accessible to a wider range of users.

D) Supports No-Code application development:Flow Designer provides a visual interface and pre-built actions that allow users to automate processes without writing code.This can significantly reduce development time and effort.

A) Supports easy integration with 3rd party systems:Flow Designer integrates with a variety of 3rd party systems through the Integration Hub,making it easy to connect your ServiceNow instance to external applications.

Flow Designer offers a low-code/no-code approach to building automation, simplifies complex logic with natural language descriptions, and integrates seamlessly with external systems.

ServiceNow Product Documentation:Exploring Flow Designer -https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/flow-designer/concept/flow-designer.html

ServiceNow Community: Flow Designer vs Workflow -https://www.servicenow.com/community/developer-forum/what-are-the-advantages-and-disadvantages-between-flow-designer/m-p/1407094

by Delfina at Jun 22, 2024, 12:06 AM

Limited Time Offer

25%

Off

Get Premium CSA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Rory

3 months ago

B is interesting, but I think it’s not specific enough.

upvoted 0 times

...

Albina

4 months ago

Wait, can you really use "incident.*"? Sounds too broad.

upvoted 0 times

...

Elliot

4 months ago

Not so sure about that, D seems off.

upvoted 0 times

...

Vesta

4 months ago

I agree, C is the way to go!

upvoted 0 times

...

Artie

4 months ago

Option C looks correct, matches the syntax.

upvoted 0 times

...

Ashleigh

5 months ago

I vaguely recall that using "None" in the name might not be correct, but I can't remember the exact rules for naming conventions in Access Control.

upvoted 0 times

...

Chery

5 months ago

I'm a bit confused about the difference between "write" and "create." I feel like "create" is more specific to making new records.

upvoted 0 times

...

Nu

5 months ago

I remember a practice question where we had to specify roles and permissions, and I think "incident.*" might be the correct syntax for allowing all incident records.

upvoted 0 times

...

Whitley

5 months ago

I think Access Control is about defining permissions, but I'm not sure if "write" or "create" is the right term here.

upvoted 0 times

...

Derick

5 months ago

Hmm, I think I've got a handle on this. The key is to make sure the name, operation, and role are all specified correctly. I'll carefully evaluate each option.

upvoted 0 times

...

Shizue

5 months ago

Alright, time to put on my thinking cap. This is a good test of my understanding of access controls. I'll need to consider the syntax and logic behind each choice.

upvoted 0 times

...

Val

5 months ago

Okay, let me see here. I think the key is defining the name, permission, and role correctly. I'll need to analyze each option closely.

upvoted 0 times

...

Sharmaine

5 months ago

Hmm, this looks like a tricky one. I'll need to carefully read through the options and think about the key elements of an access control definition.

upvoted 0 times

...

Angelyn

5 months ago

Whew, this is a tough one. I'm a bit unsure about the exact format for defining the access control. I'll need to review my notes and try to reason through the options.

upvoted 0 times

...

Billy

5 months ago

This seems like a straightforward true/false question. I'll read it carefully and think through the definitions of risks and opportunities before selecting my answer.

upvoted 0 times

...

Francine

5 months ago

From what I recall, the architectural map helps clarify relationships in the data. Option D seems to fit best, but I could see arguments for others too.

upvoted 0 times

...

Dona

6 months ago

I feel like replaceability might be a benefit too, but I can't recall if we've covered it in detail.

upvoted 0 times

...

Lavera

6 months ago

Hmm, this is a tricky one. I can see both sides. On the one hand, we have a responsibility to the public to make sure we're getting the best value. But on the other hand, we don't want to act on hearsay or unsubstantiated claims. I think I'd try to find a middle ground - maybe reach out to a few more references, but without going overboard and making a big deal out of it.

upvoted 0 times

...

Catarina

10 months ago

B) Name: incident Any, Operation: write, Permission: itil - Ah, the classic 'incident Any' approach. Because who doesn't love a little bit of SQL injection with their access control?

upvoted 0 times

Ilene

9 months ago

E) Name: incident. None; Operation: create; Role: itil - It's important to restrict access to only what is necessary.

upvoted 0 times

...

Oliva

9 months ago

C) Name: incident.*; Operation: write; Permission: itil - I think using wildcards can be risky, better to be specific.

upvoted 0 times

...

Gary

9 months ago

A) Name: incident''; Permission: write; Role: itil - That seems like a secure way to control access.

upvoted 0 times

...

Leota

10 months ago

A) Name: incident''; Permission: write; Role: itil - Really? Single quotes around the incident? Seriously, what kind of access control is that?

upvoted 0 times

...

Lisbeth

10 months ago

E) Name: incident. None; Operation: create; Role: itil - This one is definitely wrong. The syntax doesn't make sense, and it's not clear what it's trying to do.

upvoted 0 times

Xuan

9 months ago

C) Name: incident.*; Operation: write; Permission: itil

upvoted 0 times

...

Amber

9 months ago

B) Name: incident Any, Operation: write, Permission: itil

upvoted 0 times

...

Felicidad

10 months ago

A) Name: incident''; Permission: write; Role: itil

upvoted 0 times

...

Anthony

10 months ago

D) Name: incident None, Permission: create: Role: itil - I'm not sure about this one. It seems like it would only allow the user to create incident records, but not write to them.

upvoted 0 times

Antonio

10 months ago

D) Name: incident None, Permission: create: Role: itil - It does seem a bit restrictive, doesn't it?

upvoted 0 times

...

Annice

10 months ago

C) Name: incident.*; Operation: write; Permission: itil

upvoted 0 times

...

Ivory

10 months ago

A) Name: incident''; Permission: write; Role: itil

upvoted 0 times

...

Rodney

11 months ago

C) Name: incident.*; Operation: write; Permission: itil - This looks like the correct answer, as it allows the user with the ITIL role to have write permission on any incident records.

upvoted 0 times

...