QUESTION: 109

For Application Access there is a configuration option called Allow access to this table via web services.
Which one of the following statements is true when this option is selected?

This option restricts the ability to delete records via web services but records can always be read
The user performing the query via web services must have the correct permissions to access the table's records
Even when not selected, users with the correct permissions can use web services to access the table's records
This option restricts access only to SOAP web services but does not apply to REST

Answer(s): B

Explanation:

Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. By selecting the Allow access to this table via web services option, you can enable other application scopes to access your data tables using web services, such as SOAP or REST. However, the user performing the query via web services must have the correct permissions to access the table's records. The user must have the appropriate roles and access controls to perform the operations on the table, such as create, read, write, or delete. The other statements are not true when this option is selected. This option does not restrict the ability to delete records via web services, nor does it allow records to be always read. The access to the records depends on the user's permissions and the web service method. This option also does not restrict access only to SOAP web services, but applies to both SOAP and REST web services. Finally, this option is not the only way to enable web service access to the table's records. Even when this option is not selected, users with the correct permissions can use web services to access the table's records, as long as they specify the application scope in the web service request.

Reference:

Application Access
Web service access to scoped applications

Reveal Solution Next Question

QUESTION: 110

Which one of the following database operations cannot be controlled with Application Access?

Update
Delete
Create
Query

Answer(s): D

Explanation:

Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. You can use Application Access to control the following database operations:
Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option.

Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option. Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option. Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option. The one database operation that cannot be controlled with Application Access is Query. Query is not an operation, but a method of the GlideRecord class that is used to retrieve records from the database on the server-side. Query is not part of the Application Access rules, but it is affected by the Access Controls and the user's roles.

Reference:

Application Access

[GlideRecord methods]

Reveal Solution Next Question

QUESTION: 111

Identify characteristic(s) of a Record Producer.
Choose 3 answers

Graphics can be included on the user interface.
All records created using this strategy are inserted into the Requested Item [sc_req_item] table.
You can script behaviors of fields in the user interface.
They must be scripted.
Each field prompts the user with a question rather than a field label.

Answer(s): A,C,E

Explanation:

A Record Producer is a type of service catalog item that allows users to create records on a specified table. A Record Producer has the following characteristics:
Graphics can be included on the user interface: You can add images, icons, or banners to the Record Producer to make it more appealing and informative for the user. You can also use HTML and CSS to customize the layout and style of the Record Producer.
You can script behaviors of fields in the user interface: You can use Client Scripts and UI Policies to control the behavior and appearance of the fields on the Record Producer. For example, you can use Client Scripts to validate the field inputs, perform calculations, or populate default values. You can also use UI Policies to show or hide fields, make fields mandatory or read-only, or set field values based on conditions.
Each field prompts the user with a question rather than a field label: You can use the Variable Question field to define the question that prompts the user for the field value. The question can be more descriptive and user-friendly than the field label. For example, you can use the question "What is the name of the project?" instead of the field label "Name". The other statements are not true for Record Producers. Record Producers do not always insert records into the Requested Item [sc_req_item] table. They can insert records into any table that is specified in the Record Producer properties. Record Producers also do not have to be scripted. They can use the default script that maps the variable values to the record fields, or they can use a custom script that defines the logic for creating the record.

Reference:

[Record Producers]
[Record Producer properties]
[Record Producer scripts]

Reveal Solution Next Question

QUESTION: 112

Which server-side API debug log method is available for scoped applications?

gs.print()
gs.log()
gs.debuglog()
gs.info()

Answer(s): D

Explanation:

The server-side API debug log method available for scoped applications is gs.info(). This method logs informational messages that describe the progress of the application. Older methods such as gs.print() and gs.log() are not available in scoped applications. The gs.debuglog() method does not exist. The gs.info(), gs.warn(), gs.error(), and gs.debug() methods work in both scoped applications and global, and are therefore more versatile going forward in future versions.

Reference:

Debugging best practices

Reveal Solution Next Question

Free CAD Exam Braindumps (page: 28)

QUESTION: 109

Explanation:

Reference:

QUESTION: 110

Explanation:

Reference:

QUESTION: 111

Explanation:

Reference:

QUESTION: 112

Explanation:

Reference: