Correct Answer: C

Explanation:

Content dependent access control involves restricting access to content, such as documents and emails,

based on embedded keywords or certain assigned metadata. It works by inspecting the content and

applying rules to determine if access is permitted. This approach is taken by many Data Loss Prevention

solutions. It is possible to combine content dependent access control with role-based access control in

order to restrict access to content by established roles.

References:

Correct Answer: A

Explanation:

TheWS-Securityspecification allows a variety of signature formats, encryption algorithms and multiple trust domains, and is open to various security token models, such as:

*

X.509 certificates (not E)

*

Kerberos tickets (not D) *UserID/Password credential (not C)

*

SAML Assertions (not B) *custom-defined tokens.

Note: WS-Security (Web Services Security, short WSS) is a flexible and feature-rich extension to SOAP to apply security to web services. It is a member of the WS-* family of web service specifications and was published by OASIS.

Correct Answer: B

Explanation: The underlying core principle of ORA Engineering is asset sharing and enterprise development through an integrated asset management approach. Most organizations use a Software Configuration Management (SCM) or Version Control System (VCS) for managing the code and configuration assets. These tools are great for managing the versioning of assets produced but they don't maintain the metadata of the assets. Without metadata assets are not organized in context and it is hard to discover them. ORA recommends an asset-centric engineering process, where an Asset Manager is used to address the challenges posed by the traditional approaches. The Asset Manager is typically an enterprise-scoped Metadata Repository working in concert with SCMs and other types of asset repositories.

References:

Correct Answer: A

Explanation:

Technical orchestration is separated from business processes. Making a clear distinction between

technical aspects and business aspects facilitates maintenance of both. Technical aspects change when the underlying systems change whereas business aspects change when the business changes.

References:

Correct Answer: BE

Explanation:

B (not C): Service consumers are able to migrate to a newer version of a SOA Service gracefully. Service

consumers should migrate to a new version of a SOA Service as part of a normal maintenance process.

The

coordinated deployment of service consumers and service providers should not be necessary.

Implications:

*

A service migration strategy needs to be established.

*

The architecture must support graceful service migration.

E(not A, not D):There may be multiple versions of a SOA Service in production concurrently. Invariably a SOA Service will require modifications to support new consumers or to expand functionality. Supporting concurrent versions of a SOA Service is essential for a sound service versioning approach. Implications:

*

A service versioning strategy needs to be established.

*

The architecture must support multiple, concurrent versions of a SOA Service.

References: