Oracle 1z0-599 Exam Practice Questions (P. 1)
- Full Access (91 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #1
You deploy more than one application to the same WebLogic container. The security is set on JavaEE level and all deployed JavaEE applications use the same security roles.
What is your recommendation for architecture with those requirements?
What is your recommendation for architecture with those requirements?
- ACombine all applications into a single one.
- BDefine global roles on the WebLogic Domain level.
- CUse Ms Active Directory to keep the roles there.
- DUse Oracle Identity and Access Management solution to simplify the management.
- EKeep role mapping in the external WebLogic Role Mapped developed for that solution.
Correct Answer:
B
Note:
* Types of Security Roles: Global Roles and Scoped Roles
There are two types of security roles in WebLogic Server:
/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource
/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.
Incorrect:
Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role
Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.
B
Note:
* Types of Security Roles: Global Roles and Scoped Roles
There are two types of security roles in WebLogic Server:
/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource
/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.
Incorrect:
Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role
Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.
send
light_mode
delete
Question #2
When your WebLogic Server solution needs to be scaled out with additional capacity and you dont want to add additional hardware, which three techniques should you us?
- AAssign more than one managed server to a physical hardware that allows better CPU utilization.
- BAssign more than one application to one managed server to better utilize threads within a single JVM process.
- CAssign the same application to more than one managed server to load balance requests between servers.
- DAssign the same heap size to the managed server across the cluster for easier control of memory footprint
- ECreate a virtualized environment with hypervisor for an easier solution
Correct Answer:
BDE
BDE
send
light_mode
delete
Question #3
A highly available WebLogic cluster in UNIX is configured for automatic server migration. Node Managed is configured on both machines to start managed servers.
How should you simulate a managed server failure to test whether automatic server migration is working?
How should you simulate a managed server failure to test whether automatic server migration is working?
- AShut down the managed server from the WebLogic console.
- BShut down the managed server using the WLST command through Node Manager.
- CRun "kill -9" once to kill the managed server process.
- DRun "kill -9" to kill the managed server process, and run "kill -9" one more time if the managed server is restarting.
Correct Answer:
A
Note:
* It is recommended that you shutdown WebLogic Server instances through the Administration Console.
* If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.
A
Note:
* It is recommended that you shutdown WebLogic Server instances through the Administration Console.
* If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.
send
light_mode
delete
Question #4
A customer claims that while redeploying a web application in the production system all their customers have to log in again. What do you recommend?
- ASessions can't be preserved when redeploying applications. The customer needs to consider redeployment during late nights when the traffic is low.
- BChange the flag responsible for the development mode of their environment. In the production mode, all sessions are preserved while redeploying application.
- CChange Hotspot to JRockit. Sessions can't be preserved on HotSpot when redeploying application.
- DUse flag -version when redeploying the application. This will switch on the Side By Side deployment feature and preserve existing sessions.
- EOpen a service request with Oracle Support. This is unexpected behavior. Sessions are preserved without any extra settings.
Correct Answer:
D
Restrictions on Production Redeployment Updates
WebLogic Server can host a maximum of two different versions of an application at one time.
Note:
* When you redeploy a new version of an application, you cannot change:
An application's deployment targets
An application's security model -
A Web applications persistent store settings
To change any of the above features, you must first undeploy the active version of the application.
Incorrect:
* (not A)
Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability* to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application.
* (not C) Not dependant on whether the application is JRockit or Hotspot.
* (not E)
The production redeployment strategy is supported for:
Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
Production redeployment is not supported for:
Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and
Managing JDBC Data Sources for Oracle WebLogic Server.
Applications that obtain JDBC data sources via the Driver Manager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use
EJB 2.x CMP instead of EJB 1.1 CMP.
Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c, Redeploying Applications in a Production Environment
D
Restrictions on Production Redeployment Updates
WebLogic Server can host a maximum of two different versions of an application at one time.
Note:
* When you redeploy a new version of an application, you cannot change:
An application's deployment targets
An application's security model -
A Web applications persistent store settings
To change any of the above features, you must first undeploy the active version of the application.
Incorrect:
* (not A)
Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability* to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application.
* (not C) Not dependant on whether the application is JRockit or Hotspot.
* (not E)
The production redeployment strategy is supported for:
Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
Production redeployment is not supported for:
Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and
Managing JDBC Data Sources for Oracle WebLogic Server.
Applications that obtain JDBC data sources via the Driver Manager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use
EJB 2.x CMP instead of EJB 1.1 CMP.
Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c, Redeploying Applications in a Production Environment
send
light_mode
delete
Question #5
A common approach to solve application performance issues is to add more hardware. Which two reasons describe why this alone does not always solve performance problems?
- AThere may be a bottleneck in the application that additional hardware would not solve.
- BAdding more hardware is costly and time consuming.
- CAdding hardware at the application layer may place additional load on an already overloaded database, network appliance, or storage system.
- DAdding more hardware may introduce new configuration requirements that need to be tested.
Correct Answer:
AC
AC
send
light_mode
delete
All Pages