1

What is sandboxing in android?

  • Every application runs in a secure sandbox environment, so other processes on the system cannnot access your code or private data.
  • Each application is called as sandbox.
  • Putting application in external memory is called as sandboxing.
  • loading application into emulator is called as sandboxing.

Answer: A Every application runs in a secure sandbox environment, so other processes on the system cannnot access your code or private data.
Description: Some of the core security features that help you build secure android apps include:
The Android Application Sandbox, which isolates your app data and code execution from other apps.
The application sandbox is implemented at the OS level, not by DVM.

2

How many levels of security available in android?

  • 2 levels - App level, kernel level
  • 3 levels - app level, dvm level, kernel level
  • only kernel level
  • only app level

Answer: A 2 levels - App level, kernel level
Description: Android supports 2 levels of security for applications. one at operating system level or kernel level. other is using <permission> tags in app level.

3

Android securities and permissions : I am downloading two applications where app1 has a service on which some permission is enforced, and app2 has an activity which will start app1's service. Now on downloading which application user will be prompted with permission dialog?

  • app1
  • app2
  • both app1 and app2.
  • none

Answer: B app2
Description: The app which is using other app in which permission enforced, has to take the permission.

4

Android securities and permissions:
For the below given problem where should I write uses-permission tag? in which application?
Problem: I am downloading two applications where app1 has a service on which some permission is enforced, and app2 has an activity which will start app1's service. Now on downloading which application user will be prompted with permission dialog?

  • uses-permission has to be written in app2's manifest file, in application tag.
  • uses-permission has to be written in app2's manifest file, after application tag.
  • uses-permission has to be written in app1's manifest file, in application tag.
  • uses-permission has to be written in app1's manifest file, after application tag.

Answer: B uses-permission has to be written in app2's manifest file, after application tag.
Description:

5

Android securities and permissions:
For the below given problem, where should I write permission tag? and how to enforce that permission on service?

Problem: I am downloading two applications where app1 has a service on which some permission is enforced, and app2 has an activity which will start app1's service. Now on downloading which application user will be prompted with permission dialog?

  • Permission tag has to be in app1's manifest file in application tag. and we have to enfoce this permission using android:permission attribute in <Service tag> of app 1.
  • Permission tag has to be in app1's manifest file above application tag. and we have to enfoce this permission using android:permission attribute in <intent-filter tag> of Service in app 1.
  • Permission tag has to be in app2's manifest file above application tag. and we have to enfoce this permission using android:permission attribute in <Service tag> of app 1.
  • Permission tag has to be in app1's manifest file above application tag. and we have to enfoce this permission using android:permission attribute in <Service tag> of app 1.

Answer: D Permission tag has to be in app1's manifest file above application tag. and we have to enfoce this permission using android:permission attribute in <Service tag> of app 1.
Description:

6

Which of the below is not an attribute of permission tag?

  • android:id
  • android:name
  • android:description
  • android:protectionlevel

Answer: A android:id
Description: android:id will not be there for permission tag.

7

What are the protection levels available in android's permission tag?

  • normal, dangerous, system, security.
  • normal, dangerous, signature, signatureOrsystem.
  • normal, dangerous, system, signatureOrsystem.
  • normal, dangerous, security, signatureOrsystem.

Answer: B normal, dangerous, signature, signatureOrsystem.
Description: normal, dangerous, signature, signatureOrsystem. These are the available protection levels available for the permission tag.

8

Android securities and permissions : Can one application having Linux process user id 1, touch other application property or elements directly?

  • No, in Linux one app cant touch or intrude into other app with out androids system permission.
  • yes, it is possible, android will not throw any problem.
  • yes, it is possible if both applications have same user id.
  • option 3 is wrong, as there is no scenario where two android applications can share same user id.

Answer: C yes, it is possible if both applications have same user id.
Description: Generally in android one application can't touch other apps components directly due to OS level security. But if two apps are having same Linux user id, it is possible.