- Home
- Server Administration
- Windows
- Developing Microsoft Azure Solutions
41.
Which of the following is true about the Cloud Services feature? (Choose all that apply.)
- A.Before you create a cloud service project, you have to know which web and worker roles you will include in the cloud service solution.
- B.The only way to create a worker role that listens to a Service Bus queue is to select the role template while creating the cloud service project.
- C.You must provide an implementation for the RoleEntryPoint when creating a worker role.
- D.Web.config settings do not work with web roles. You have to use cloud service configuration settings.
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
A. Incorrect: When you create a new cloud service project, you can choose to add
web or worker roles from the provided role templates, or you can create an empty
cloud service (no roles) and later add the desired roles to the project using either
new role templates or by adding existing projects as roles. B. Incorrect: Any role template is merely a starting point for creating a role implementation. The Service Bus Queue template includes code to follow a queue but still requires customization and configuration for your specific requirements. Likewise, you could manually write the same code for a worker role you implement from scratch. C. Correct: By default, the RoleEntryPoint does nothing. To create a worker role with any functionality you have to provide custom code in the Run() override. Optionally, you also override OnStart() and OnStop() to provide functionality that runs before the role receives requests and cleans up before the role shuts down or recycles. D. Incorrect: Your existing web.config settings work as expected with your web roles while running both locally and in the cloud. The reason for using the role configuration settings is to surface those settings to the management portal for editing without having to redeploy. |
42.
Which of these is true about startup tasks? (Choose all that apply.)
- A.Simple tasks run before the role starts processing requests.
- B.Foreground tasks run before the role starts accepting requests.
- C.Background tasks run before the role starts accepting requests
- D.A startup task can interact with the RoleEnvironment object.
- Answer & Explanation
- Report
Answer : [A]
Explanation :
Explanation :
A. Correct: All simple tasks run in sequence prior to the role being put into ready
state to start receiving requests. B. Incorrect: Foreground tasks run asynchronously in parallel to simple and background tasks. The role may be put into ready state after simple tasks are completed but before the foreground or background task has completed. Further, the role cannot be recycled while a foreground task is still running. C. Incorrect: Background tasks run asynchronously in parallel to simple and foreground tasks. The role may be put into ready state after simple tasks are completed but before the foreground or background task has completed. Unlike foreground tasks, the role CAN be recycled while a background task is still running. D. Incorrect: Startup tasks cannot rely on any information related to the role environment, nor can they interact with the RoleEnvironment object. To work with RoleEnvironment, use the OnStart() override in the RoleEntryPoint class. |
43.
Which of the following is not true regarding scaling the instance count of a cloud service?
(Choose all that apply.)
- A.You can only scale in even multiples.
- B.You must pre-provision all role instances before scaling up.
- C.You can scale the instance count using auto-scale.
- D.You can scale the instance count using the existing portal.
- Answer & Explanation
- Report
Answer : [C, D]
Explanation :
Explanation :
A. Incorrect: You can scale up or down in any increment you specify. B. Incorrect: This is true for VMs, but not possible or required with cloud services. C. Correct: Auto-scale only controls the instance count. D. Correct: You can scale the instance count using the existing portal or by deploying an update from Visual Studio. |
44.
Which of the following is NOT true about cloud service networking?
- A.You can use network traffic rules to restrict inter-role communication.
- B.You can configure ACL to restrict access to a specified subnet.
- C.You cannot join a cloud service to a virtual network.
- D.A public IP does not require a port to reach a role instance.
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
A. Incorrect: Inter-role communication can be secured using network traffic rules. B. Incorrect: ACLs are used to restrict access to a range of IPs (for example, a subnet). C. Correct: A cloud service can be joined to a virtual network. D. Incorrect: By using a public IP, you do not have to specify a port to reach an instance of a role. |
45.
Which of the following are valid configuration options for In-Role Cache? (Choose all
that apply.)
- A.Dedicated cache
- B.Persistent cache
- C.Co-located cache
- D.Named cache
- Answer & Explanation
- Report
Answer : [A, C, D]
Explanation :
Explanation :
A. Correct: In-role supports configuring a dedicated cache. B. Incorrect: In-role does not support a persistent cache; all caching is purely in memory. C. Correct: In-role supports configuring a co-located cache. D. Correct: In-role supports the creation of named caches. |